[JBoss JIRA] Created: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
4:13 p.m.
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears that
the class doesn't have the right classloader as it reuses a thread previously setup
with an other classloader (the application is packaged in different ears while the queues
are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:12 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1747?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1747:
-----------------------------------------
Hi Stephan,
The correct JBM version for JBoss 5.0.1 should be 1.4.3.GA. I see you report this jira
against 1.4.1. Can you verify this? Thanks.
Howard
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:23 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1747?page=com.atlassian.ji...
]
Stephan Lagraulet commented on JBMESSAGING-1747:
------------------------------------------------
I've determined this version by doing these actions:
$ jar xf /usr/local/jboss-5.0.1.GA/common/lib/jboss-messaging.jar
$ grep providerVersion VERSION
jboss.messaging.providerVersion=1.4.1.GA
Is this correct?
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:26 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1747?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1747:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP10
1.4.6.GA.SP1
1.4.7.GA
Assignee: Howard Gao
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:28 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1747?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1747:
-----------------------------------------
Hi Stephan,
No it's not correct. You need to use 1.4.3.GA, or 1.4.6.GA which is better because of
a lot of bug fixes included in it.
Howard
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:34 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1747?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1747:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP11
(was: 1.4.0.SP3.CP10)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.6.GA.SP1, 1.4.7.GA
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:57 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1747?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1747:
------------------------------------
Fix Version/s: (was: 1.4.6.GA.SP1)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.7.GA
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:18 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira.pl...
]
Howard Gao commented on JBMESSAGING-1747:
-----------------------------------------
Hi Stephan,
Any update?
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.7.GA
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:45 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira.pl...
]
Stephan Lagraulet commented on JBMESSAGING-1747:
------------------------------------------------
The patch we made is still in production on our jboss server.
I gave the patch to another person who had the same problem a few weeks ago but I
don't know which version of jboss was installed.
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.7.GA
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:29 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira.pl...
]
Howard Gao commented on JBMESSAGING-1747:
-----------------------------------------
Thanks Stephan for the update.
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.7.GA
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:03 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira.pl...
]
Howard Gao updated JBMESSAGING-1747:
------------------------------------
Fix Version/s: 1.4.8.GA
(was: 1.4.7.GA)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.8.GA
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:38 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://jira.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira.pl...
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.0.SP3.CP12
(was: 1.4.0.SP3.CP11)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://jira.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP12, 1.4.8.GA
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:01 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.0.SP3.CP13
(was: 1.4.0.SP3.CP12)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP13, 1.4.8.GA
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.8.SP1
(was: 1.4.8.GA)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:52 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.8.SP2
(was: 1.4.8.SP1)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP13, 1.4.8.SP2
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:33 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.0.SP3.CP14
(was: 1.4.0.SP3.CP13)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP14, 1.4.8.SP2
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:54 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.0.SP3.CP15
(was: 1.4.0.SP3.CP14)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP2
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:57 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.8.SP3
(was: 1.4.8.SP2)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP3
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:33 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.8.SP4
(was: 1.4.8.SP3)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP4
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:44 p.m.
New subject: [JBoss JIRA] (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.8.SP5
(was: 1.4.8.SP4)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP5
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:21 a.m.
New subject: [JBoss JIRA] (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.8.SP6
(was: 1.4.8.SP5)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP6
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:25 p.m.
New subject: [JBoss JIRA] (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.8.SP7
(was: 1.4.8.SP6)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP7
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:07 p.m.
New subject: [JBoss JIRA] (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.8.SP8
(was: 1.4.8.SP7)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP8
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:58 p.m.
New subject: [JBoss JIRA] (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.8.SP9
(was: 1.4.8.SP8)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP9
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:26 p.m.
New subject: [JBoss JIRA] (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
[
https://issues.jboss.org/browse/JBMESSAGING-1747?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1747:
--------------------------------------
Fix Version/s: 1.4.8.SP10
(was: 1.4.8.SP9)
ClassNotFoundException while consuming a message in a JMS Queue
---------------------------------------------------------------
Key: JBMESSAGING-1747
URL: https://issues.jboss.org/browse/JBMESSAGING-1747
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Destination Manager
Affects Versions: 1.4.1.GA
Environment: Jboss version : 5.0.1 GA
Reporter: Stephan Lagraulet
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP10
We have several JMS queues setup on our jboss server.
We are using spring to handle the messages.
When several clients simultaneously post some messages in different queues, the consumer
doesn't find the class for the task, ending with this stack trace:
2009-07-28 17:10:21,089 WARN [SimpleMessageListenerContainer] [] - Execution of JMS
message listener failed
java.lang.RuntimeException:
fr.billetel.interfaces.ws.allotement.business.etatventes.request.CodificationsTaskRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:279)
at
org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772)
at
org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
We debugged the class org.jboss.messaging.util.OrderedExecutorFactory, and it appears
that the class doesn't have the right classloader as it reuses a thread previously
setup with an other classloader (the application is packaged in different ears while the
queues are defined in deploy), ending in this exception.
For the moment, we patched the code so that the classloader is reloaded for every call,
but it does not seem like a good solution on a long term.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4228
days inactive
5321
days old
24 comments
4 participants
participants (4)
-
Howard Gao (JIRA) -
Stephan Lagraulet (JIRA)
-
Yong Hao Gao (JIRA)
-
Yong Hao Gao (Updated) (JIRA)