Why isn't WL finding the class in the jar file as it should normally do?Could
it be a JMS configuration thing?
Thanks for any help
The exception generated is the following:
weblogic.jms.common.JMSException: Error deserializing object
at weblogic.jms.common.ObjectMessageImpl.getObject(ObjectMessageImpl.java:113)
at eu.ohim.common.adm.log.ADMLoggingReceiver.onMessage(Unknown Source)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
----------- Linked Exception -----------
java.lang.ClassNotFoundException: eu.ohim.common.adm.log.AdmLoggingEvent
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:183)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:281)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:310)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at weblogic.jms.common.ObjectMessageImpl$ObjectInputStream2.resolveClass(ObjectMessageImpl.java:238)
at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:913)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:361)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1181)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
at weblogic.jms.common.ObjectMessageImpl.getObject(ObjectMessageImpl.java:109)
at eu.ohim.common.adm.log.ADMLoggingReceiver.onMessage(Unknown Source)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
You are running your own thread on the server by registering
an onMessage listener on the server, technically, this
is not supported. (This thread has no
knowledge of the EJB it comes from, and consequently
no knowledge about which class-loader to use.) Instead,
MDBs are normally used for this purpose.
Coincidentally, this happened to another newsgroup
poster this week. Look for the thread
with the subject "Error deserializing object"
for an (unsupported) work-around.
Tom
P.S. A "google" search of "error deserializing object" in
this newsgroup would likely have led you to the answer.