-
1. Re: ClassLoader issue with user classes and JBM 1.0.1SP4
ovidiu.feodorov Mar 2, 2007 11:16 PM (in response to jcasp)I would suggest migrating directly to 1.2. We've addressed some classloading related issues in it. Give it a try. If you still have troubles, send us specifics, and we'll try to help.
-
2. Re: ClassLoader issue with user classes and JBM 1.0.1SP4
vishal423 Mar 31, 2008 9:27 AM (in response to jcasp)Hi,
I am using Jboss 4.2.2GA with Jboss Messaging 1.4.0SPI.
I am getting same exception in following scenario:
1. I created a web service client which invokes my web-service which in turns sends object message to queue.
2. I created message listener bound to web application deployed on same machine.
Once message received, during invocation of OnMessage function, i am getting this exception at same point as mentioned in original thread.
Any suggestions welcomed.
Thanks & Regards,
Vishal -
3. Re: ClassLoader issue with user classes and JBM 1.0.1SP4
vishal423 Apr 1, 2008 10:23 AM (in response to jcasp)Am i missing something in Jboss Messaging configuration?
Or it has something to do with my listener configured inside web application?
When i first send same object message using jsp/servlet, everything works fine. After this subsequent sending and receiving from plain java class works.
But when i first send it using plain java class, message listener throws following exception
"java.lang.RuntimeException: No ClassLoaders found for: <fully classified custom class name>
Please reply, i got stuck with this issue.
Thanks & Regards,
vishal -
4. Re: ClassLoader issue with user classes and JBM 1.0.1SP4
vishal423 Apr 3, 2008 10:12 AM (in response to jcasp)Hi All,
Inserting this statement before retrieving object from ObjectMessageProxy inside onMessage method in listener, class loaders exception got resolved:
Thread.currentThread().setContextClassLoader(<class-name>.class.getClassLoader());
Thanks & Regards,
Vishal -
5. Re: ClassLoader issue with user classes and JBM 1.0.1SP4
timfox Apr 3, 2008 10:17 AM (in response to jcasp)This is a known issue http://jira.jboss.org/jira/browse/JBMESSAGING-924 which was fixed about a year ago.
It's also discussed here: http://jboss.com/index.html?module=bb&op=viewtopic&p=4028694
Moral of the story: If you have a problem always search the forums and JIRA first to see if it's already known/fixed - it will save you a lot of time in the long run.