[JBoss JIRA] Created: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
8:19 p.m.
Messages are piling up in the queues in clustered environment and not pulled by message
sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Tim Fox
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files the
problem seems to disappear or at least show up much less frequently. Specifically I'm
talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files as
well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
8:21 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Victor Starenky updated JBMESSAGING-1631:
-----------------------------------------
Attachment: logs-and-config-prod.zip
production cluster logs and config
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Tim Fox
Attachments: logs-and-config-prod.zip
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
8:23 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Victor Starenky updated JBMESSAGING-1631:
-----------------------------------------
Attachment: logs-and-config-test.zip
test cluster (2 machines) logs and config
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Tim Fox
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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:02 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao reassigned JBMESSAGING-1631:
---------------------------------------
Assignee: Howard Gao (was: Tim Fox)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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:04 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1631:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP09
1.4.5.GA
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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:02 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1631:
-----------------------------------------
Hi Victor,
Do you have a test MDB for the issue? I'm trying to make a test to reproduce it.
Thanks.
Howard
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
4:08 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1631:
-----------------------------------------
Hi Victor,
I wrote up a test case that looks like that:
1) Start up a two-node jbm cluster, messaging-node0 and messaging-node1. A distributed
queue also deployed.
2) Deploy a MDB jar to messaging-node0/farm. The MDB receives messages from the
distributed queue.
3) Start a message sending application and send the messages over
ClusteredConnectionFactory. The messages will be sent to the two node in round-robin
fashion.
I got it run on one machine. However, to be able to reproduce the issue, I think I need to
deploy the cluster to two machines.
If you got a chance, can you comment on whether my test is suitable or not? Thanks.
I'll update you once I got it run over certain time.
Howard
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
6:05 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Hossein Attar commented on JBMESSAGING-1631:
--------------------------------------------
(On behalf of Victor)
The test MDB is attached
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip,
TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
6:05 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Hossein Attar updated JBMESSAGING-1631:
---------------------------------------
Attachment: TestRecommendationSentProcessorMDB.java
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip,
TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
7:13 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Hossein Attar commented on JBMESSAGING-1631:
--------------------------------------------
Howard:
I think your test case is right. Here are some details about our environment that may be
useful.
We use java:/JmsXA as our connection factory
In hajndi-jms-ds.xml, we have
<!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
<tx-connection-factory>
<jndi-name>JmsXA</jndi-name>
<xa-transaction/>
<rar-name>jms-ra.rar</rar-name>
<connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
<config-property name="SessionDefaultType"
type="java.lang.String">javax.jms.Topic</config-property>
<config-property name="JmsProviderAdapterJNDI"
type="java.lang.String">java:/DefaultJMSProvider</config-property>
<max-pool-size>20</max-pool-size>
<security-domain-and-application>JmsXARealm</security-domain-and-application>
</tx-connection-factory>
and in connection-factories-service.xml, we have
<!-- The default connection factory does not support automatic failover or load
balancing-
this is so we can maintain compatiblity with applications written for JBoss MQ
which use this
connection factory.
-->
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
name="jboss.messaging.connectionfactory:service=ConnectionFactory"
xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends
optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=bisocket</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="JNDIBindings">
<bindings>
<binding>/ConnectionFactory</binding>
<binding>/XAConnectionFactory</binding>
<binding>java:/ConnectionFactory</binding>
<binding>java:/XAConnectionFactory</binding>
</bindings>
</attribute>
</mbean>
<!-- A clustered connection factory that supports automatic failover and load
balancing of created
connections.
This factory is not suitable to be used by MDBs.
-->
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
name="jboss.messaging.connectionfactory:service=ClusteredConnectionFactory"
xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends
optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=bisocket</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="JNDIBindings">
<bindings>
<binding>/ClusteredConnectionFactory</binding>
<binding>/ClusteredXAConnectionFactory</binding>
<binding>java:/ClusteredConnectionFactory</binding>
<binding>java:/ClusteredXAConnectionFactory</binding>
</bindings>
</attribute>
<attribute name="SupportsFailover">true</attribute>
<attribute name="SupportsLoadBalancing">true</attribute>
</mbean>
<!-- A connection factory with no JNDI bindings that is used in clustering to create
the connections that
pull messages from one node to another
-->
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
name="jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory"
xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends
optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=bisocket</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute name="SupportsFailover">false</attribute>
<attribute name="SupportsLoadBalancing">false</attribute>
</mbean>
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip,
TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
5:31 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1631:
-----------------------------------------
Hi Hossein,
Thanks a lot for the info!
Howard
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip,
TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
10:40 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Victor Starenky commented on JBMESSAGING-1631:
----------------------------------------------
I think one important thing to reproduce the problem is to cause client/server failover
due to timeouts. This could happen either because of unreliable network or due to high cpu
usage / lack of resources. If both servers are pretty much idle and sit on a good network
it's quite unlikely we'll see the problem.
Another difference between your test case and our environment is that we\re sending
messages to the queue from the same application farmed across both servers. We're
using both stateless EJB beans to get the XA clustered factory injected by the container
for sending messages and just a jndi lookup. I don't think all of this matters as the
problems seem to be on a receiving side but still thought I would mention this.
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip,
TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1631:
-----------------------------------------
Thanks Victor. One thing I can do to trigger failover is reduce the ping timeout in
remoting configuration, that worked well in my dealing with JBMESSAGING-1456.
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip,
TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
8:03 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1631:
-----------------------------------------
Hi Victor,
Just an update. My test has been running over night without message pile up at either
node. I found the client failover didn't happen as my two machines are in a local
network.
I'll further reduce the ping timeout (already 500ms). However, as the MDB is deployed
within the App Server. If the MDB is connected to the same Server, it's unlikely that
client failover will happen.
One possible reason that may affect the message sucker is that if the message sucker's
connection has ping timeout. I'll try to make this happen to see if I can made any
progress.
Alse please note you should use remoting 2.2.3. remoting 2.5.1 doesn't include all the
fixes for JBMESSAGING-1456.
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip,
TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
3:32 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Victor Starenky commented on JBMESSAGING-1631:
----------------------------------------------
We've switched to the latest jars for messaging that has fix for JBMESSAGING-1456 and
as well switched all other required libaries including remoting (to the version 2.2.3 as
per documentation).
Still this morning we see one node piling up topic messages. As far as I can tell we
mostly experience this issue with topics. One or more nodes stop receiving messages and in
JMX console we see thousands of them sitting on these nodes.
As I mentioned before we're pushing servers to the limits overnight so timeouts are
likely caused by exessive load more than network.
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip,
TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
4:47 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1631:
-----------------------------------------
Thanks Victor. I'll change to topic then.
A question: when you find the messaging piling up, did you stop the sending and wait to
see if the messages are still there?
Also my sending program just keep sending messages in a loop, 20 messages for each
transaction. is that enough to load the servers?
Howard
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip,
TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
5:44 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Victor Starenky commented on JBMESSAGING-1631:
----------------------------------------------
Messages are sent intermittently, there isn't a huge stream of these. But
AllMessageCount is in the order of thousands and only increases with every new message.
What happens with topics is that some node stops receiving messages. It shows all
SubscriptionCounts = 0. Once it gets into this state is stays there.
We created our own monitoring system that records every sent message and every received
message into database stamped with the time and machine name. This is how we find these
problems.
Also when I was speaking about the load I wasn't talking about JMS load but rather the
overall machine load. All servers run a large application that's doing tons of jobs
overnight. So this might affect ping timeouts - when machine is too busy to respond in
time. This is only a theory though.
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: logs-and-config-prod.zip, logs-and-config-test.zip,
TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
5:40 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1631:
-----------------------------------------
Hi Hossein,
I still can't reproduce it in my env. I changed the MDB to use Topic and send messaged
every 10 minutes, and 2000 messages for each sending. It looks like both MDB got all the
messages in the overnight test.
I'm uploading my test source (1631-test-source.zip), can you help me how to get this
reproduced? Thanks.
Howard
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
5:40 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1631:
------------------------------------
Attachment: 1631-test-source.zip
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
3:33 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1631:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP10
1.4.6.GA
(was: 1.4.5.GA)
(was: 1.4.0.SP3.CP09)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP10, 1.4.6.GA
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
4:28 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1631:
------------------------------------
Fix Version/s: 1.4.7.GA
(was: 1.4.6.GA)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP10, 1.4.7.GA
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
4:28 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1631?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1631:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP11
1.4.8.GA
(was: 1.4.0.SP3.CP10)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.7.GA, 1.4.8.GA
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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:03 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira.pl...
]
Howard Gao updated JBMESSAGING-1631:
------------------------------------
Fix Version/s: (was: 1.4.7.GA)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP11, 1.4.8.GA
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
1:38 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://jira.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira.pl...
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.0.SP3.CP12
(was: 1.4.0.SP3.CP11)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://jira.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP12, 1.4.8.GA
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
3:01 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.0.SP3.CP13
(was: 1.4.0.SP3.CP12)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP13, 1.4.8.GA
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.8.SP1
(was: 1.4.8.GA)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:52 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.8.SP2
(was: 1.4.8.SP1)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP13, 1.4.8.SP2
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:33 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.0.SP3.CP14
(was: 1.4.0.SP3.CP13)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP14, 1.4.8.SP2
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:54 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.0.SP3.CP15
(was: 1.4.0.SP3.CP14)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP2
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:57 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.8.SP3
(was: 1.4.8.SP2)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP3
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:33 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.8.SP4
(was: 1.4.8.SP3)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP4
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:44 a.m.
New subject: [JBoss JIRA] (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.8.SP5
(was: 1.4.8.SP4)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP5
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
3:22 p.m.
New subject: [JBoss JIRA] (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.8.SP6
(was: 1.4.8.SP5)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP6
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
4:25 a.m.
New subject: [JBoss JIRA] (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.8.SP7
(was: 1.4.8.SP6)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP7
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
1:54 p.m.
New subject: [JBoss JIRA] (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Daniel Dumitrescu commented on JBMESSAGING-1631:
------------------------------------------------
Hello there
We're facing the same situation with JBM 1.4.5 SP1
In our case we work a lot with clustered topics, so inside this clustered topic there are
like 500 messages/second and we reach to the messages stuck situation.
We tried out the workaround specified inside
https://community.jboss.org/thread/129484?tstart=0, and wait to see the results.
We have configured the message sucker, ClusterPullConnectionFactoryName and we have the
failover support switched on.
Do you have additional information about the state of this issue?
Regards,
Daniel
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP7
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
6:07 a.m.
New subject: [JBoss JIRA] (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.8.SP8
(was: 1.4.8.SP7)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP8
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
6:58 a.m.
New subject: [JBoss JIRA] (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.8.SP9
(was: 1.4.8.SP8)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP9
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
4:26 a.m.
New subject: [JBoss JIRA] (JBMESSAGING-1631) Messages are piling up in the queues in clustered environment and not pulled by message sucker
[
https://issues.jboss.org/browse/JBMESSAGING-1631?page=com.atlassian.jira....
]
Yong Hao Gao updated JBMESSAGING-1631:
--------------------------------------
Fix Version/s: 1.4.8.SP10
(was: 1.4.8.SP9)
Messages are piling up in the queues in clustered environment and not
pulled by message sucker
----------------------------------------------------------------------------------------------
Key: JBMESSAGING-1631
URL: https://issues.jboss.org/browse/JBMESSAGING-1631
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 1.4.0.SP3.CP08
Environment: Cluster of a few JBoss 4.2.3 servers with JBM 1.4.2.GA-SP1 or
1.4.0.SP3_CP08 running on x64 windows servers.
JBoss Remoting 2.5.1 or 2.2.3
Clustered XA connection factory, clustered queues, both server and client (MDBs) are
deployed as one application - identical deployment for all servers in a cluster
Reporter: Victor Starenky
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP15, 1.4.8.SP10
Attachments: 1631-test-source.zip, logs-and-config-prod.zip,
logs-and-config-test.zip, TestRecommendationSentProcessorMDB.java
We have an EJB3 application is running on a cluster of 7 servers.
All servers have the same application farmed across them.
We have a clustered queue and using clustered connection factory.
Originally we ran into the bug JBMESSAGING-1456 and while testing the fix ran into a
different problem. After the cluster was running for some time (usually overnight with
lots of heavy background processing hapenning at that time) we see messages are
"piling up" in some queues on some nodes.
Sympthoms are:
MessageCount is not zero (rather in the order of hundreeds), DeliveringCount is zero.
These nodes have ConsumerCount=0 for the queues experiencing the problem. Message sucker
is configured as far as I can tell. Looks like the problem might be related to client
and/or server failover leaving some nodes without consumers while sucker not doing
it's job (if I understand it correctly).
Once we bump the timeout values much higher than they are in the original config files
the problem seems to disappear or at least show up much less frequently. Specifically
I'm talking about these values:
messaging-service.xml:
<attribute name="FailoverStartTimeout">180000</attribute>
remoting-bisocket-service.xml:
<attribute name="clientLeasePeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingPeriod"
isParam="true">30000</attribute>
<attribute name="validatorPingTimeout"
isParam="true">20000</attribute>
<attribute
name="registerCallbackListener">false</attribute>
<attribute name="timeout"
isParam="true">240000</attribute>
While this serves as a temporary workaround we don't feel we can rely on JBM in a
production clustered environment without having failover working properly.
This is a big showstopper for us at the moment.
Attached are the log files from the prod environment of 7 servers with the config files
as well as log files from the test environment with just 2 servers (having same issue) and
corresponding configs. The logs were produced by the test version of the messaging code
with added logging as per JBMESSAGING-1456.
--
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
4208
days inactive
5453
days old
37 comments
6 participants
participants (6)
-
Daniel Dumitrescu (JIRA) -
Hossein Attar (JIRA)
-
Howard Gao (JIRA)
-
Victor Starenky (JIRA)
-
Yong Hao Gao (JIRA)
-
Yong Hao Gao (Updated) (JIRA)