[JBoss JIRA] Created: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
4:44 a.m.
Starting two node clusters simultaneously may end in failed messaging server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.Beta2
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:07 p.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=all ]
Clebert Suconic reassigned JBMESSAGING-693:
-------------------------------------------
Assignee: Clebert Suconic (was: Ovidiu Feodorov)
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Clebert Suconic
Fix For: 1.2.0.Beta2
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:44 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=all ]
Ovidiu Feodorov updated JBMESSAGING-693:
----------------------------------------
Fix Version/s: 1.2.0.CR1
(was: 1.2.0.Beta2)
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Clebert Suconic
Fix For: 1.2.0.CR1
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:50 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=all ]
Ovidiu Feodorov updated JBMESSAGING-693:
----------------------------------------
Priority: Critical (was: Major)
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 1.2.0.CR1
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:07 p.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=all ]
Ovidiu Feodorov reassigned JBMESSAGING-693:
-------------------------------------------
Assignee: Juha Lindfors (was: Clebert Suconic)
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Juha Lindfors
Priority: Critical
Fix For: 1.2.0.CR1
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:32 p.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=all ]
Tim Fox reassigned JBMESSAGING-693:
-----------------------------------
Assignee: Tim Fox (was: Juha Lindfors)
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.2.0.CR1
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:23 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=all ]
Tim Fox closed JBMESSAGING-693.
-------------------------------
Resolution: Cannot Reproduce Bug
After many cycles of starting and stopping servers at the same time - I cannot reproduce
this problem.
I can only assume it has been inadvertently fixed along the way.
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.2.0.CR1
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:13 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=comments#action_12... ]
Juha Lindfors commented on JBMESSAGING-693:
-------------------------------------------
It still exists in CR1, although is fairly difficult to reproduce with full server startup
sequence:
11:07:59,504 INFO [ServerPeer] JBoss Messaging 1.2.0.CR1 server [2] started
11:08:17,570 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:2840
-------------------------------------------------------
11:08:22,867 WARN [GMS] join(127.0.0.1:2840) sent to 127.0.0.1:2825 timed out, retrying
11:08:26,923 INFO [DefaultClusteredPostOffice] ClusteredPostOffice[2:Clustered
JMS:127.0.0.1:2840] got new view [127.0.
0.1:2840|0] [127.0.0.1:2840]
11:08:27,554 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 127.0.0.1:2846
-------------------------------------------------------
11:08:44,929 INFO [ConnectionFactory] Connector socket://10.11.14.93:4657 has leasing
enabled, lease period 20000 milli
seconds
11:08:44,929 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory,
java:/ConnectionFactory, java:/XAConne
ctionFactory] started
11:08:44,979 INFO [ConnectionFactory] Connector socket://10.11.14.93:4657 has leasing
enabled, lease period 20000 milli
seconds
11:08:44,979 INFO [ConnectionFactory] [/NonClusteredConnectionFactory,
/NonClusteredXAConnectionFactory, java:/NonClust
eredConnectionFactory, java:/NonClusteredXAConnectionFactory] started
11:08:46,882 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
11:08:48,645 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
11:08:48,645 INFO [TopicService] Topic[/topic/testTopic] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
11:08:48,655 INFO [TopicService] Topic[/topic/securedTopic] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
11:08:48,655 INFO [TopicService] Topic[/topic/testDurableTopic] started, fullSize=75000,
pageSize=2000, downCacheSize=2
000
11:08:49,255 INFO [QueueService] Queue[/queue/testQueue] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
11:08:49,836 INFO [QueueService] Queue[/queue/A] started, fullSize=75000, pageSize=2000,
downCacheSize=2000
11:08:50,617 INFO [QueueService] Queue[/queue/B] started, fullSize=75000, pageSize=2000,
downCacheSize=2000
11:08:51,018 INFO [QueueService] Queue[/queue/C] started, fullSize=75000, pageSize=2000,
downCacheSize=2000
11:08:51,739 INFO [QueueService] Queue[/queue/D] started, fullSize=75000, pageSize=2000,
downCacheSize=2000
11:08:53,231 INFO [QueueService] Queue[/queue/ex] started, fullSize=75000, pageSize=2000,
downCacheSize=2000
11:08:54,303 INFO [QueueService] Queue[/queue/PrivateDLQ] started, fullSize=75000,
pageSize=2000, downCacheSize=2000
11:08:54,984 INFO [QueueService] Queue[/queue/PrivateExpiryQueue] started,
fullSize=75000, pageSize=2000, downCacheSize
=2000
11:08:56,426 INFO [QueueService] Queue[/queue/QueueWithOwnDLQAndExpiryQueue] started,
fullSize=75000, pageSize=2000, do
wnCacheSize=2000
11:08:56,426 INFO [TopicService] Topic[/topic/TopicWithOwnDLQAndExpiryQueue] started,
fullSize=75000, pageSize=2000, do
wnCacheSize=2000
11:08:57,267 INFO [QueueService] Queue[/queue/QueueWithOwnRedeliveryDelay] started,
fullSize=75000, pageSize=2000, down
CacheSize=2000
11:08:57,267 INFO [TopicService] Topic[/topic/TopicWithOwnRedeliveryDelay] started,
fullSize=75000, pageSize=2000, down
CacheSize=2000
11:08:57,778 INFO [QueueService] Queue[/queue/testDistributedQueue] started,
fullSize=75000, pageSize=2000, downCacheSi
ze=2000
11:08:57,788 INFO [TopicService] Topic[/topic/testDistributedTopic] started,
fullSize=75000, pageSize=2000, downCacheSi
ze=2000
11:08:58,198 INFO [ConnectionFactoryBindingService] Bound ConnectionManager
'jboss.jca:service=ConnectionFactoryBinding
,name=JmsXA' to JNDI name 'java:JmsXA'
11:09:05,329 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console,
warUrl=.../deploy/jmx-console.war/
11:10:08,299 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8280
11:10:12,265 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8209
11:10:12,986 INFO [JkMain] Jk running ID=0 time=0/2364 config=null
11:10:13,026 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0
date=200610162339)] Started in 9m
:34s:66ms
11:14:18,389 WARN [NAKACK] 127.0.0.1:2846] discarded message from non-member
127.0.0.1:2828, my view is [127.0.0.1:2846
|0] [127.0.0.1:2846]
11:14:20,442 WARN [NAKACK] 127.0.0.1:2846] discarded message from non-member
127.0.0.1:2828, my view is [127.0.0.1:2846
|0] [127.0.0.1:2846]
11:14:30,045 WARN [NAKACK] 127.0.0.1:2840] discarded message from non-member
127.0.0.1:2825, my view is [127.0.0.1:2840
|0] [127.0.0.1:2840]
11:14:30,075 WARN [NAKACK] 127.0.0.1:2846] discarded message from non-member
127.0.0.1:2828, my view is [127.0.0.1:2846
|0] [127.0.0.1:2846]
11:14:31,407 INFO [DefaultClusteredPostOffice] ClusteredPostOffice[2:Clustered
JMS:127.0.0.1:2840] got new view MergeVi
ew::[127.0.0.1:2825|2] [127.0.0.1:2825, 127.0.0.1:2840], subgroups=[[127.0.0.1:2825|1]
[127.0.0.1:2825, 127.0.0.1:2840],
[127.0.0.1:2840|0] [127.0.0.1:2840]]
11:14:32,048 WARN [GMS] failed to collect all ACKs (1) for view
MergeView::[127.0.0.1:2825|2] [127.0.0.1:2825, 127.0.0.
1:2840], subgroups=[[127.0.0.1:2825|1] [127.0.0.1:2825, 127.0.0.1:2840],
[127.0.0.1:2840|0] [127.0.0.1:2840]] after 2000
ms, missing ACKs from [127.0.0.1:2840] (received=[]), local_addr=127.0.0.1:2840
11:14:32,138 WARN [GMS] failed to collect all ACKs (1) for view
MergeView::[127.0.0.1:2828|1] [127.0.0.1:2828, 127.0.0.
1:2846], subgroups=[[127.0.0.1:2828|0] [127.0.0.1:2828], [127.0.0.1:2846|0]
[127.0.0.1:2846]] after 2000ms, missing ACKs
from [127.0.0.1:2846] (received=[]), local_addr=127.0.0.1:2846
11:14:33,661 INFO [DefaultClusteredPostOffice] ClusteredPostOffice[2:Clustered
JMS:127.0.0.1:2840] got new view [127.0.
0.1:2825|3] [127.0.0.1:2825, 127.0.0.1:2840, 127.0.0.1:2940]
11:14:34,672 INFO [DefaultClusteredPostOffice] ClusteredPostOffice[2:Clustered
JMS:127.0.0.1:2840] got new view [127.0.
0.1:2825|4] [127.0.0.1:2825, 127.0.0.1:2840, 127.0.0.1:2940, 127.0.0.1:2925]
11:15:07,920 ERROR [DefaultClusteredPostOffice] Caught Exception in RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultCl
usteredPostOffice.java:524)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle
(DefaultClusteredPostOffice.java:2519)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:608)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:650)
at org.jgroups.blocks.RequestCorrelator.access$100(RequestCorrelator.java:38)
at org.jgroups.blocks.RequestCorrelator$Request.run(RequestCorrelator.java:939)
at org.jgroups.util.ReusableThread.run(ReusableThread.java:220)
at java.lang.Thread.run(Thread.java:595)
11:15:08,340 ERROR [RequestCorrelator] error invoking method
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultCl
usteredPostOffice.java:524)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle
(DefaultClusteredPostOffice.java:2519)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:608)
at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:650)
at org.jgroups.blocks.RequestCorrelator.access$100(RequestCorrelator.java:38)
at org.jgroups.blocks.RequestCorrelator$Request.run(RequestCorrelator.java:939)
at org.jgroups.util.ReusableThread.run(ReusableThread.java:220)
at java.lang.Thread.run(Thread.java:595)
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.2.0.CR1
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:13 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=all ]
Juha Lindfors reopened JBMESSAGING-693:
---------------------------------------
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.2.0.CR1
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=comments#action_12... ]
alfred karma commented on JBMESSAGING-693:
------------------------------------------
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/7/index.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/8/keno1.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/9/keno2.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/10/keno3.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/11/keno4.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/12/keno5.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/13/keno6.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/14/keno7.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/15/keno8.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/16/keno9.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/17/keno10.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/18/keno11.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/19/keno12.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/20/keno13.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/21/keno14.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/23/keno15.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/24/keno16.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/25/keno17.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/26/keno18.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/27/keno19.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/28/keno20.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/29/keno21.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/30/keno22.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/31/keno23.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/32/keno24.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/33/keno25.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/34/keno26.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/35/keno27.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/36/keno28.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/37/keno29.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/38/keno30.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/39/keno31.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/40/keno32.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/41/keno33.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/42/keno34.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/43/keno35.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/44/keno36.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/45/keno37.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/46/keno38.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/47/keno39.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/48/keno40.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/49/keno41.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/50/keno42.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/51/keno43.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/52/keno44.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/53/keno45.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/54/keno46.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/55/keno47.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/56/keno48.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/57/keno49.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/58/keno50.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/59/keno51.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/60/keno52.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/61/keno53.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/62/keno54.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/63/keno55.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/64/keno56.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/65/keno57.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/66/keno58.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/67/keno59.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/68/keno60.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/69/keno61.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/70/keno62.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/71/keno63.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/72/keno64.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/73/keno65.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/74/keno66.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/75/keno67.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/76/keno68.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/77/keno69.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/78/keno70.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/79/keno71.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/80/keno72.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/81/keno73.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/82/keno74.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/84/keno75.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/85/keno76.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/86/keno77.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/87/keno78.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/88/keno79.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/89/keno80.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/90/keno81.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/91/keno82.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/92/keno83.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/93/keno84.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/94/keno85.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/95/keno86.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/96/keno87.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/97/keno88.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/98/keno89.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/99/keno90.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/100/keno91.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/101/keno92.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/102/keno93.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/103/keno94.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/104/keno95.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/105/keno96.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/106/keno97.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/107/keno98.html
http://appforge2.apc.edu.ph/tracker/download.php/39/232/69/108/keno99.html
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.2.0.CR1
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:45 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=all ]
Ovidiu Feodorov updated JBMESSAGING-693:
----------------------------------------
Comment: was deleted
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.2.0.CR1
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:17 p.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-693) Starting two node clusters simultaneously may end in failed messaging server node boot
[ http://jira.jboss.com/jira/browse/JBMESSAGING-693?page=all ]
Tim Fox closed JBMESSAGING-693.
-------------------------------
Resolution: Done
Starting two node clusters simultaneously may end in failed messaging
server node boot
--------------------------------------------------------------------------------------
Key: JBMESSAGING-693
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-693
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ovidiu Feodorov
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.2.0.CR1
Tim Fox: 10:24:05,296 ERROR [DefaultClusteredPostOffice] Caught Exception in
RequestHandler
java.lang.IllegalStateException: Don't know about node id: 1
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice.addBindingFromCluster(DefaultClusteredPostOffice.java:597)
at
org.jboss.messaging.core.plugin.postoffice.cluster.BindRequest.execute(BindRequest.java:55)
at
org.jboss.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOffice$PostOfficeRequestHandler.handle(DefaultClusteredPostOffice.java:2526)
at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:602)
at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:623)
at org.jgroups.blocks.RequestCorrelator.access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6840
days inactive
7077
days old
11 comments
6 participants
participants (6)
-
alfred karma (JIRA) -
Clebert Suconic (JIRA) -
Juha Lindfors (JIRA)
-
Ovidiu Feodorov (JIRA)
-
Ovidiu Feodorov (JIRA)
-
Tim Fox (JIRA)