[JBoss JIRA] Created: (JBMESSAGING-1747) ClassNotFoundException while consuming a message in a JMS Queue
by Stephan Lagraulet (JIRA)
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
11 years, 7 months
[JBoss JIRA] Created: (JBMESSAGING-1763) Bisocket connection won't be closed if pulling out the ethernet cable between client and server. The failure detection code won't close the failure connection, as a result, the subsequent requests will hang after connection account exceeds the threshold
by mingjun jiang (JIRA)
Bisocket connection won't be closed if pulling out the ethernet cable between client and server. The failure detection code won't close the failure connection, as a result, the subsequent requests will hang after connection account exceeds the threshold
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1763
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1763
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Remoting
Affects Versions: 1.4.5.GA
Environment: OS: Windows Server 2003. JBoss App Server 4.2.3.GA, JBoss Messaging 1.4.5 GA, JBoss Remoting 2.2.3 SP1
Reporter: mingjun jiang
We are using JBoss App Server 4.2.3.GA, JBoss Messaging 1.4.5 GA and JBoss Remoting 2.2.3 SP1. In our application, there are a lot of Message listeners running on the client side, these message listeners will receive messages from queue/topic deployed in JBoss Messaging
Configuration:
We created our own JMS Connection factory which uses the default remoting connector. As you know, the default remoting connector is configured to use the bisocket transport. We didn't change the default value of the remoting connector
During we run our application, we open the JBoss web console to monitor the value of currentClientPoolSize under "Jboss.remoting" JMX MBean.
How to reproduce this issue:
1. Run 5 message listeners in the client side to receive messages from JBoss Messaging, then we observe the value of currentClientPoolSize is 10
2. After processing several messages, we manually pull out the ethernet cable. The value of currentClientPoolSize is still 10.
3. We run another 5 message listeners in client side, then the value of currentClientPoolSize will become 20
4. After we do the same operations above several times, the value of currentClientPoolSize will increase continuously. Once the value of currentClientPoolSize is equal to the MaxPoolSize, then the subsequent incoming client requests will hang, and we will encounter the following exception in server side
2009-10-20 18:08:09,655 ERROR [org.jboss.remoting.transport.socket.ServerThread] Worker thread initialization failure
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at java.io.FilterInputStream.read(FilterInputStream.java:66)
at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:859)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:545)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
Conclusion: JBoss Messaging won't close the failure connections if they are caused by manually pulling out ethernet cable. As a result, the value of currentClientPoolSize will increase continuously and finally the new client requests will hang
Note: If we killed the process of message listener in client side, then the value of currentClientPoolSize will decrease to 0 immediately, it seems that the server could detect the failure connection and perform the corresponding resource releasing.
--
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
11 years, 7 months
[JBoss JIRA] Created: (JBMESSAGING-1777) Error in addMessageIDInHeader while bridging from JBossMQ
by Pedro Gontijo (JIRA)
Error in addMessageIDInHeader while bridging from JBossMQ
---------------------------------------------------------
Key: JBMESSAGING-1777
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1777
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.3.GA
Environment: JBoss AS 5.1.0.GA
Reporter: Pedro Gontijo
When addMessageIDInHeader is set to true in a JBossMQ->JBM bridge scenerio the following error occurs:
WARN [org.jboss.jms.server.bridge.Bridge] (Thread-27) jboss.messaging:name=MyBridge,service=Bridge Failed to send + acknowledge batch, closing JMS objects
javax.jms.JMSException: Illegal property name: JMSXDeliveryCount
at org.jboss.mq.SpyMessage.checkProperty(Unknown Source)
at org.jboss.mq.SpyMessage.setObjectProperty(Unknown Source)
at org.jboss.jms.server.bridge.Bridge.addMessageIDInHeader(Bridge.java:1481)
at org.jboss.jms.server.bridge.Bridge.sendMessages(Bridge.java:1391)
at org.jboss.jms.server.bridge.Bridge.sendBatchNonTransacted(Bridge.java:1261)
at org.jboss.jms.server.bridge.Bridge.sendBatch(Bridge.java:1375)
at org.jboss.jms.server.bridge.Bridge.access$1900(Bridge.java:68)
at org.jboss.jms.server.bridge.Bridge$BatchTimeChecker.run(Bridge.java:1638)
at java.lang.Thread.run(Thread.java:595)
As you can see the error is due JMSX properties, actually, because the addMessageIDInHeader sets then in the MQ message (which is not allowed).
--
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
11 years, 7 months
[JBoss JIRA] Created: (JBASMP-12) Move JBossAS Maven Plugins into their own tree
by Andrew Lee Rubinger (JIRA)
Move JBossAS Maven Plugins into their own tree
----------------------------------------------
Key: JBASMP-12
URL: https://jira.jboss.org/jira/browse/JBASMP-12
Project: JBoss AS Maven Plugins
Issue Type: Task
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Currently under maven/plugins/jboss/trunk is:
drwxrwxr-x 4 alrubinger alrubinger 4096 2008-10-21 21:35 maven-buildmagic-thirdparty-plugin
drwxrwxr-x 5 alrubinger alrubinger 4096 2008-09-24 06:10 maven-jboss-as-build
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-common
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:55 maven-jboss-as-control-example
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-21 21:50 maven-jboss-as-control-plugin
drwxrwxr-x 7 alrubinger alrubinger 4096 2008-10-02 05:34 maven-jboss-ejb3-testrunner-plugin
drwxrwxr-x 4 alrubinger alrubinger 4096 2008-09-15 11:15 maven-jboss-license-plugin
drwxrwxr-x 12 alrubinger alrubinger 4096 2008-10-21 21:49 maven-jboss-surefire
-rw-rw-r-- 1 alrubinger alrubinger 1229 2008-10-21 21:35 pom.xml
Those prefixed with "maven-jboss-as" should be in their own tree
--
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
11 years, 7 months