3:38 p.m.
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05
Reporter: Justin Bertram
Assignee: Tim Fox
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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:42 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1657) IllegalStateException upon cluster fail-over
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1657?page=com.atlassian.ji...
]
Justin Bertram updated JBMESSAGING-1657:
----------------------------------------
Attachment: JmsTest.java
127.0.0.1.log
127.0.0.2.log
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05
Reporter: Justin Bertram
Assignee: Tim Fox
Attachments: 127.0.0.1.log, 127.0.0.2.log, client.log, JmsTest.java
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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:42 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1657) IllegalStateException upon cluster fail-over
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1657?page=com.atlassian.ji...
]
Justin Bertram updated JBMESSAGING-1657:
----------------------------------------
Description:
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1 (using kill -9 <pid>)
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
was:
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05
Reporter: Justin Bertram
Assignee: Tim Fox
Attachments: 127.0.0.1.log, 127.0.0.2.log, client.log, JmsTest.java
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1 (using kill -9 <pid>)
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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:42 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1657) IllegalStateException upon cluster fail-over
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1657?page=com.atlassian.ji...
]
Justin Bertram updated JBMESSAGING-1657:
----------------------------------------
Attachment: client.log
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05
Reporter: Justin Bertram
Assignee: Tim Fox
Attachments: 127.0.0.1.log, 127.0.0.2.log, client.log, JmsTest.java
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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:51 p.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1657) IllegalStateException upon cluster fail-over
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1657?page=com.atlassian.ji...
]
Justin Bertram reassigned JBMESSAGING-1657:
-------------------------------------------
Assignee: Howard Gao (was: Tim Fox)
I'm assigning this to Howard as he is the 1.4.x maintainer.
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05
Reporter: Justin Bertram
Assignee: Howard Gao
Attachments: 127.0.0.1.log, 127.0.0.2.log, client.log, JmsTest.java
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1 (using kill -9 <pid>)
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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:53 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1657) IllegalStateException upon cluster fail-over
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1657?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1657:
-----------------------------------------
The test does not always fail, sometimes it is ok.
My observation:
1. client connects to node1, whenever a consumer is created, node1 will tell node2 to do
something (in case of topic, node2 will add a binding accordingly). whenever a consumer is
closed, node1 will tell node2 to remove the binding. This is achieved through jgroups.
2. when node1 is killed, client failover to node 2 and continue the operation. node2 will
get notification of node1's death and do server side failover.
if client requests come in after node1's death but before node2 get notified, node2
still keeps the node1 in its cluster view, so it will try to tell node1 and expect
response. But in fact node1 is already dead, so it will throw the exception.
3. actually if we kill node2, there is still a chance to get the same error.
I'll try to figure out how to fix it and update soon.
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05
Reporter: Justin Bertram
Assignee: Howard Gao
Attachments: 127.0.0.1.log, 127.0.0.2.log, client.log, JmsTest.java
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1 (using kill -9 <pid>)
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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:46 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1657) IllegalStateException upon cluster fail-over
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1657?page=com.atlassian.ji...
]
Justin Bertram commented on JBMESSAGING-1657:
---------------------------------------------
I have also seen the test succeed on occasion. This is definitely an issue of timing.
The shorter the "sleep" in the client the more easy the problem is to produce.
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05
Reporter: Justin Bertram
Assignee: Howard Gao
Attachments: 127.0.0.1.log, 127.0.0.2.log, client.log, JmsTest.java
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1 (using kill -9 <pid>)
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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:23 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1657) IllegalStateException upon cluster fail-over
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1657?page=com.atlassian.ji...
]
Andy Goldstein commented on JBMESSAGING-1657:
---------------------------------------------
FYI this is not limited to co-located JBoss Messaging servers & JMS client. We've
had this happen when JBoss Messaging was on 1 machine, and the client was on another
machine.
Our test case was slightly different from Justin's (which aligns with #3 above):
-Start test client connecting to node2
-Observe client log filling up with "."
-Drop JBoss running on node1 (using kill -9 <pid>)
-Client fails with org.jboss.jms.exception.MessagingJMSException
-Observe java.lang.IllegalStateException on node2
The difference is we had our JmsTest client connecting to the 2nd server instead of the
1st. So the test client was always trying to connect to node2, and when we killed node1,
the next attempt by the client to connect to node2 that immediately followed node1's
death failed (presumably for the reason stated in #2 above).
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05
Reporter: Justin Bertram
Assignee: Howard Gao
Attachments: 127.0.0.1.log, 127.0.0.2.log, client.log, JmsTest.java
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1 (using kill -9 <pid>)
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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:19 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1657) IllegalStateException upon cluster fail-over
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1657?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1657:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP09
1.4.5.GA
Affects Version/s: 1.4.0.SP3.CP08
1.4.0.SP3.CP07
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05, 1.4.0.SP3.CP07, 1.4.0.SP3.CP08
Reporter: Justin Bertram
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: 127.0.0.1.log, 127.0.0.2.log, client.log, JmsTest.java
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1 (using kill -9 <pid>)
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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:28 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1657) IllegalStateException upon cluster fail-over
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1657?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1657:
-----------------------------------------
The fix:
In GroupMember.multicastConstrol, where ever a multicast message is not received be any
member, we do a check on the member's status. If the member is actually dead, it can
be safely ignored. the code is like:
if (!rsp.wasReceived())
{
if (!rsp.wasSuspected())
{
throw new IllegalStateException(this + " response not received from " +
rsp.getSender() + " - there may be others");
}
}
where the rsp.wasSuspected() can be used to detected whether the member is really dead or
not. (I consulted jgroup lead Bela Ban).
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05, 1.4.0.SP3.CP07, 1.4.0.SP3.CP08
Reporter: Justin Bertram
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: 127.0.0.1.log, 127.0.0.2.log, client.log, JmsTest.java
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1 (using kill -9 <pid>)
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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:33 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1657) IllegalStateException upon cluster fail-over
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1657?page=com.atlassian.ji...
]
Howard Gao closed JBMESSAGING-1657.
-----------------------------------
Resolution: Done
IllegalStateException upon cluster fail-over
--------------------------------------------
Key: JBMESSAGING-1657
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1657
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP05, 1.4.0.SP3.CP07, 1.4.0.SP3.CP08
Reporter: Justin Bertram
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
Attachments: 127.0.0.1.log, 127.0.0.2.log, client.log, JmsTest.java
I set up two cluster nodes like so:
1) unzipped fresh JBoss EAP 4.3 CP04
2) renamed
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
to hsqldb-persistence-service.xml.rej
3) copied <JBOSS_HOME>/docs/examples/jms/mysql-persistence-service.xml to
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar
4) Modified the "Clustered" attribute to be "true" in
<JBOSS_HOME>/server/default/deploy/jboss-messaging.sar/mysql-persistence-service.xml
5) copied <JBOSS_HOME>/docs/examples/jca/mysql-ds.xml to
<JBOSS_HOME>/server/default/deploy and changed the jndi-name to
"DefaultDS" and pointed it at my local MySQL
6) copied MySQL driver to <JBOSS_HOME>/server/default/lib
7) copied jgroups.jar from <JBOSS_HOME>/server/all/lib to
<JBOSS_HOME>/server/default/lib
8) copied <JBOSS_HOME> to <JBOSS_HOME2>
9) Start first instance with "./run.sh -c default -b 127.0.0.1
-Djboss.messaging.ServerPeerID=1"
10) Start second instance with "./run.sh -c default -b 127.0.0.2
-Djboss.messaging.ServerPeerID=2"
Then I ran the test (which is attached as JmsTest.java)
-Start test client connecting to 127.0.0.1
-Observe client log filling up with "."
-Drop JBoss running on 127.0.0.1 (using kill -9 <pid>)
-Client fails with org.jboss.jms.exception.MessagingJMSException (see log attached as
client.log)
-Observe java.lang.IllegalStateException on the 127.0.0.2 (attached as 127.0.0.2.log)
--
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
6256
days inactive
6259
days old
10 comments
3 participants
participants (3)
-
Andy Goldstein (JIRA) -
Howard Gao (JIRA)
-
Justin Bertram (JIRA)