-
1. Re: ClassLoader issue with MDB and Hibernate
timfox Jul 27, 2007 2:22 PM (in response to genman)But JBAS 4.2.0 uses JBoss MQ not JBoss Messaging.
Or maybe you have de-installed JBoss MQ and installed JBoss Messaging? It wasn't clear from your post. -
2. Re: ClassLoader issue with MDB and Hibernate
genman Jul 30, 2007 9:26 PM (in response to genman)I am using JBoss Messaging.
Actually, this is seeming more like an EJB3 question, as I'm using that too... If you could move this question to that forum, I would appreciate it. -
3. Re: ClassLoader issue with MDB and Hibernate
timfox Jul 31, 2007 6:14 PM (in response to genman)We only set the context classloader in one place and this is nowhere near any message delivery code.
We also unset is immediately afterwards in a finally, so I doubt it is the cause of your problem.
Earlier versions of JBM did set the context classloader in other places - what version are you using?
FWIW - I can see code in JBAS 4.2 (org.jboss.ejb.plugins.jms.JMSContainerInvoker::invoke) that sets the context classloader. -
4. Re: ClassLoader issue with MDB and Hibernate
genman Jul 31, 2007 7:18 PM (in response to genman)Well, the problem is not during the message processing, but during the transaction commit. Hibernate doesn't see the context classloader used in a transaction commit, because the transaction commit happens outside the message delivery handling. Or so I'm guessing.
-
5. Re: ClassLoader issue with MDB and Hibernate
timfox Aug 8, 2007 2:46 PM (in response to genman)Hi genman - did you solve this yet?
-
6. Re: ClassLoader issue with MDB and Hibernate
genman Aug 21, 2007 1:02 PM (in response to genman)Sorry I didn't, I came up with a work around. And I'm filing a bug.
I'm certain this is part of the JBossAS side of things, and not to do with messaging.
Thanks for trying to help.