java.rmi.MarshalException: CORBA MARSHAL

[GoogleCodeExporter]

What steps will reproduce the problem?
[root@prulmasqtza01 libexec]#  wget -q -O - 
'http://localhost:9090/wlsagent/WlsAgent?hostname=XXXXX&port=XXXX&username=XXXX&
password=XXXX&thread-pool=ThreadStuckCount;5;10'

What is the expected output? What do you see instead?
3|XXXX is in RUNNING state, status UNKNOWN - java.rmi.MarshalException: CORBA 
MARSHAL 1398079698 Maybe; nested exception is:
        org.omg.CORBA.MARSHAL:   vmcid: SUN  minor code: 210 completed: Maybe|

What version of the product are you using? On what operating system?
wlsagent-r160.jar

Please provide any additional information below.
Corrected by previous release 147

It's only occur for the service thread-pool=ThreadStuckCount, all check are ok.

Original issue reported on code.google.com by xavier.b...@adeoservices.com on 18 Jan 2013 at 10:23

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ok , I know why. My wlsagent run with a diffrent release of the java hotspot. I 
have to  modify the run.sh to point the the same as weblogic.

Can we avoid this king of error by a patch in wlsagent ?

This workarround only work with release 147 (not 160)

Original comment by xavier.b...@adeoservices.com on 18 Jan 2013 at 10:34

[GoogleCodeExporter]

Hello, are you referencing the weblogic.jar of the running instance in the 
agent's classpath ? Could be a compatibility issue.

Original comment by yann.lambret@gmail.com on 18 Jan 2013 at 10:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi, thanks for your response. Yes the classpath is correct (i checked all
path). The starnge thing is :
same jdk weblo + agent 160 = ko
same jdk weblo + agent 147 = ok

other jdk + agent 160 = ko
other jdk + agent 147 = ok

Original comment by xavier.b...@adeoservices.com on 18 Jan 2013 at 10:59

[GoogleCodeExporter]

Can you please compile the plug-in by yourself with your target JDK, and make a 
new test ?

Original comment by yann.lambret@gmail.com on 18 Jan 2013 at 1:55

[GoogleCodeExporter]

Hi, sorry for the late answer. I think you have to use the wlfullclient.jar 
instead of the weblogic.jar to solve this issue.

To generate the wlfullclient.jar, go to the ${WL_HOME}/server/lib directory of 
your WebLogic distribution and issue the following command:

java -jar wljarbuilder.jar

Then copy the new file to the lib directory of the agent (or use a symlink) and 
replace 'weblogic.jar' by 'wlfullclient.jar' in the CLASSPATH directive of the 
'run.sh' script. Beware that the wlfullclient.jar must be loaded after the 
other dependencies.

Let me know if it works.

Yann

Original comment by yann.lambret@gmail.com on 20 Jun 2013 at 2:37

[GoogleCodeExporter]

Hello,

Yes, since a while I use the wlfullclient.jar file instead of weblogic.jar with 
wlsagent-r160.jar. 

Thanks :)

Original comment by xavier.b...@adeoservices.com on 20 Jun 2013 at 2:46

[GoogleCodeExporter]

Well, I'm glad to here it :)

Original comment by yann.lambret@gmail.com on 20 Jun 2013 at 3:20

[GoogleCodeExporter]

I'm going to update the wiki with the required informations.

Original comment by yann.lambret@gmail.com on 20 Jun 2013 at 3:21

• Changed state: Fixed