1:07 p.m.
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Tim Fox
Attachments: cluster-nodes-config-files.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue in
each node.
If the failover kick off then after few min both BackUp and Live servers will be listening
to the cluster which leads to "more than one broadcasters on the network broadcasting
the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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
1:07 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Abdel Dridi updated JBMESSAGING-1691:
-------------------------------------
Attachment: cluster-nodes-config-files.zip
config files for both cluster pairs (Live/Backup)
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Tim Fox
Attachments: cluster-nodes-config-files.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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
1:09 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Abdel Dridi updated JBMESSAGING-1691:
-------------------------------------
Attachment: Jbm2ClusterTest-NodeA.zip
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Tim Fox
Attachments: cluster-nodes-config-files.zip, Jbm2ClusterTest-NodeA.zip,
Jbm2ClusterTest-NodeB.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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
1:09 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Abdel Dridi updated JBMESSAGING-1691:
-------------------------------------
Attachment: Jbm2ClusterTest-NodeB.zip
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Tim Fox
Attachments: cluster-nodes-config-files.zip, Jbm2ClusterTest-NodeA.zip,
Jbm2ClusterTest-NodeB.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:18 p.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Clebert Suconic reassigned JBMESSAGING-1691:
--------------------------------------------
Assignee: Clebert Suconic (was: Tim Fox)
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Clebert Suconic
Attachments: cluster-nodes-config-files.zip, Jbm2ClusterTest-NodeA.zip,
Jbm2ClusterTest-NodeB.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:27 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Clebert Suconic commented on JBMESSAGING-1691:
----------------------------------------------
I will hold working on this issue until Abdel Adridi provides some guidance on how to run
this.
Also: We have another task on the roadmap for soak tests anyway.
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Clebert Suconic
Attachments: build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:27 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Clebert Suconic updated JBMESSAGING-1691:
-----------------------------------------
Attachment: build.xml
adding a build.xml for the client part. Copy the libraries into ./lib
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Clebert Suconic
Attachments: build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:29 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Abdel Dridi commented on JBMESSAGING-1691:
------------------------------------------
To replicate the issue, please follow the below steps:
1. In a physical nodeA, configure a live JMB2 micro-container using attached
clutered-configuration.
2. In an other physical nodeB, configure a live JBM2 micro-container
3. In NodeA configure the backup server of Live-NodeB server
4. In NodeB configure the backup server of Live-NodeA server
5. NodeA and NodeB are connected with an Ethernet-cross-cable for fast access.
6. Setup both client project (eclipse project) - make sure that some
micro-container/server/lib is in classpath - I forgot to add them to lib.
7. In NodeA run the Junit test case "TestLauncher.testTenantPool()" of eclipse
project Jbm2ClusterTest-NodeA.zip.
8. In NodeB run the Junit test case "TestLauncher.testTenantPool()" of eclipse
project Jbm2ClusterTest-NodeB.zip.
9. After some time consumer connection will fail after packet-sent timeout - Problem1.
10. then Backup-server will kick-off while Live-server still have live connections which
leads to Problem2: more than one broadcasters on the network broadcasting the same node
id.
11. I attached a pic of the test case.
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Clebert Suconic
Attachments: build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Abdel Dridi updated JBMESSAGING-1691:
-------------------------------------
Attachment: jbmTest.JPG
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Clebert Suconic
Attachments: build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip, jbmTest.JPG
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:30 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Abdel Dridi updated JBMESSAGING-1691:
-------------------------------------
Attachment: build.xml
updated build.xml and attached lib.zip that includes all used libs
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Clebert Suconic
Attachments: build.xml, build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip, jbmTest.JPG
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:32 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Abdel Dridi updated JBMESSAGING-1691:
-------------------------------------
Attachment: lib.zip
updated build.xml and attached lib.zip that includes all used libs
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Clebert Suconic
Attachments: build.xml, build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip, jbmTest.JPG, lib.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:37 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1691:
--------------------------------------
A couple of questions:
1) Why do you have the live and backup on the same node? If that node crashes the backup
will crash too and will be useless
2) Does the problem occur if you run the tests *outside* eclipse? I don't recommend
running test clients in eclipse - if you set breakpoints then that will cause pings not to
be sent and the system will fail over.
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Clebert Suconic
Attachments: build.xml, build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip, jbmTest.JPG, lib.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:41 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Abdel Dridi commented on JBMESSAGING-1691:
------------------------------------------
Tim,
Please find my comments to your questions inline;
1) Why do you have the live and backup on the same node? If that node crashes the backup
will crash too and will be useless
-----> What I have in each node is Live and "backup-server of the other
node", so if that node (A) goes down then I still have Live server of NodeB up plus
the backup of Live-NodeA which is in NodeB.
If you have any recomendation to setup a JBM2 cluster in 2 physical node, I will be very
happy to try it.
2) Does the problem occur if you run the tests *outside* eclipse? I don't recommend
running test clients in eclipse - if you set breakpoints then that will cause pings not to
be sent and the system will fail over.
-----> Yes Tim, the problem still happens while executing the program outside of
eclipse.
Thanks,
Abdel
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Clebert Suconic
Attachments: build.xml, build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip, jbmTest.JPG, lib.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:10 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Tim Fox updated JBMESSAGING-1691:
---------------------------------
Fix Version/s: 2.0.0
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Clebert Suconic
Fix For: 2.0.0
Attachments: build.xml, build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip, jbmTest.JPG, lib.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:17 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Tim Fox reassigned JBMESSAGING-1691:
------------------------------------
Assignee: Tim Fox (was: Clebert Suconic)
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Tim Fox
Fix For: 2.0.0
Attachments: build.xml, build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip, jbmTest.JPG, lib.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:39 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Abdel Dridi commented on JBMESSAGING-1691:
------------------------------------------
Tim,
I find out that this problem is originally caused by "CLIENT_ACKNOWLEDGE" that
Im using.
I saw an other Jira open for this "JBMESSAGING-1693" - Andy closed it today.
I took a build from the trunk and retested but still see the problem happening, but when I
use "AUTO_ACKNOWLEDGE" things works fine.
Would you please clarify the status of this?
Thanks,
Abdel
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Tim Fox
Fix For: 2.0.0
Attachments: build.xml, build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip, jbmTest.JPG, lib.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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:39 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1691) JBM2 cluster fails under heavy load
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1691?page=com.atlassian.ji...
]
Tim Fox closed JBMESSAGING-1691.
--------------------------------
Resolution: Done
JBM2 cluster fails under heavy load
-----------------------------------
Key: JBMESSAGING-1691
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1691
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Clustering
Affects Versions: 2.0.0.beta4
Environment: Linux-debian 64bits 8G RAM - Java1.6 update14
Reporter: Abdel Dridi
Assignee: Tim Fox
Fix For: 2.0.0.beta5
Attachments: build.xml, build.xml, cluster-nodes-config-files.zip,
Jbm2ClusterTest-NodeA.zip, Jbm2ClusterTest-NodeB.zip, jbmTest.JPG, lib.zip
I have a cluster of 2 nodes; A and B:
In nodeA, I have JMB2-NodeA-live and JBM2-NodeB-backup.
In nodeB, I have JMB2-NodeB-live and JBM2-NodeA-backup.
I have a client running in NodeA (eclipseProject "Jbm2ClusterTest-NodeA.zip")
and an other client running in NodeB (eclipseProject
"Jbm2ClusterTest-NodeB.zip") - Both client starts on the same time.
In each project there's a Junit testcase (TestLauncher.testTenantPool) to start the
test.
I also attached the configuration (config/stand-alone/clustered) for each node
(Live/Backup).
BTW; I tried with the trunk build (07-23-2009) and JBM2-Beta3.
I faced the following issues:
Connection failure after producing 600k and consuming 400K messages of the InboundQueue
in each node.
If the failover kick off then after few min both BackUp and Live servers will be
listening to the cluster which leads to "more than one broadcasters on the network
broadcasting the same node id".
I also see "failed to accept connection: too many open files".
Let me know if you have any question,
Abdel
--
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
5625
days inactive
5650
days old
16 comments
3 participants
participants (3)
-
Abdel Dridi (JIRA) -
Clebert Suconic (JIRA)
-
Tim Fox (JIRA)