Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ClassNotFound Exception

7 views
Skip to first unread message

luigi

unread,
Oct 10, 2003, 6:48:25 AM10/10/03
to

Hi everyone,
I have deployed a jar file on WL 6.1 . I have a JMS Listener which
doesn't find an application class called AdmLoggingEvent even though is in the
jar file I have deployed . The only way to quick fix the problem so far is to
put this class in the classpath variable of the startweblogic script...

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)

Tom Barnes

unread,
Oct 10, 2003, 6:13:51 PM10/10/03
to luigi
I'm assuming the stacktrace is from the server?

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.

0 new messages