12:50 p.m.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1456?page=com.atlassian.ji...
]
Zach Kurey commented on JBMESSAGING-1456:
-----------------------------------------
Tim and Howard,
Justin has been reproducing the issue quite consistently in his labs, so while I
understand the desire to take Spring out of the equation I think its best to start with
reproducing the same way he has. The issue here is with the configuration of the server
not meeting the test clients expectations.
All of the relevant information for configuring the server in order to properly inter
operate with the client is included in the internal ticket. Howard have you seen and been
able to look at this ticket? There is also a decent amount of discussion about the
configuration there and steps Justin(and Jay) took to reproduce and various items he has
ruled out. Also attached to that ticket are the various configuration files that need to
be deployed to the app server to configure it similarly to ours. Obviously we do not want
any of that information/files published to this ticket. I'm fine with fielding
questions in that ticket as well.
JBoss 4.3.0.CP02 is required as the client side lib used in the test application is using
that collection of jars.
As far as the connection refused error its because a default out of the box download of
CP02 is being employed. Howard there are a couple of port properties in the client
configuration file: conf/configuration/testclient.configuration.properties
See: jboss.broker.port, jndi.connection.host, jndi.connection.port. These are most likely
wrong for your configuration. However, your likely to run into more road blocks
configuration wise, so please see the other ticket for configuration information.
Messages stuck in being-delivered state in cluster
--------------------------------------------------
Key: JBMESSAGING-1456
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1456
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP03
Reporter: Justin Bertram
Assignee: Howard Gao
Priority: Critical
Attachments: BaseProducerThread.java, kill3_thread_dump.txt, thread_dump.txt
Messages become "stuck" in being-delivered state when clients use a clustered
XA connection factory in a cluster of at least 2 nodes.
JBoss setup:
-2 nodes of JBoss EAP 4.3 CP02
-commented out "ClusterPullConnectionFactory" in messaging-service.xml to
prevent message redistribution and eliminate the "message suckers" as the
potential culprit
-MySQL backend using the default mysql-persistence-service.xml (from
<JBOSS_HOME>/docs/examples/jms)
Client setup:
-both nodes have a client which is a separate process (i.e. not inside JBoss)
-clients are Spring based
-one client produces and consumes, the other client just consumes
-both clients use the ClusteredXAConnectionFactory from the default
connection-factories-service.xml
-both clients publish to and consume from "queue/testDistributedQueue"
-clients are configured to send persistent messages, use AUTO_ACKNOWLEDGE, and
transacted sessions
Symptoms of the issue:
-when running the clients I watch the JMX-Console for the
"queue/testDistributedQueue"
-as the consumers pull messages off the queue I can see the MessageCount and
DeliveringCount go to 0 every so often
-after a period of time (usually a few hours) the MessageCount and DeliveringCount
never go back to 0
-I "kill" the clients and wait for the DeliveringCount to go to 0, but it
never does
-after the clients are killed the ConsumerCount for the queue will drop, but never to 0
when messages are "stuck"
-a thread dump reveals at least one JBM server session that is apparently stuck (it
never goes away) - ostensibly this is the consumer that is showing in the JMX-Console for
"queue/testDistributedQueue"
-a "killall -3 java" doesn't produce anything from the clients so I know
their dead
-nothing is in any DLQ or expiry queue
-the database contains as many rows in the JBM_MSG and JBM_MSG_REF tables as the
DeliveringCount in the JMX-Console
-rebooting the node with the stuck messages frees the messages to be consumed (i.e.
un-sticks them)
Other notes:
-nothing else is happening on either node but running the client and running JBoss
-this only appears to happen when a clustered connection factory is used. I tested
using a normal connection factory and after 24 hours couldn't reproduce a stuck
message.
--
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