[JBoss JIRA] Created: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
1:37 p.m.
Reconnect message continually repeated in logs after a node has failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Tim Fox
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover should occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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
2:37 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=all ]
Tim Fox updated JBMESSAGING-1240:
---------------------------------
Fix Version/s: 1.4.0.SP3.CP02
1.4.1.beta2
Priority: Minor (was: Major)
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Tim Fox
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover should occur, but afterwards the following message will be
logged every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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
1:52 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=all ]
Tim Fox updated JBMESSAGING-1240:
---------------------------------
Description:
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
was:
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover should occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Tim Fox
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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
1:54 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1240:
--------------------------------------
What version of JB AS did you install JBM in?
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Tim Fox
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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
2:28 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=all ]
Tim Fox reassigned JBMESSAGING-1240:
------------------------------------
Assignee: Phillip Thurmond (was: Tim Fox)
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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
2:28 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1240:
--------------------------------------
I believe this problem is because of http://jira.jboss.org/jira/browse/JBMESSAGING-1213
Phillip, can you replicate the problem is solved if you use remoting 2.2.2.SP5?
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Tim Fox
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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
10:01 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=comments#action_1... ]
Phillip Thurmond commented on JBMESSAGING-1240:
-----------------------------------------------
I originally saw this problem in eap 4.3. I will try it with remoting 2.2.2.SP5.
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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
10:24 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=comments#action_1... ]
Phillip Thurmond commented on JBMESSAGING-1240:
-----------------------------------------------
Using remoting 2.2.2.SP5 gets rid of one of the warnings. I still see the following in
the logs.
11:21:45,137 WARN [FD] ping_dest is null: members=[172.17.66.89:35668,
172.17.64.89:53512], pingable_mbrs=[172.17.64.89:53512], local_addr=172.17.64.89:53512
11:21:55,139 WARN [FD] ping_dest is null: members=[172.17.66.89:35668,
172.17.64.89:53512], pingable_mbrs=[172.17.64.89:53512], local_addr=172.17.64.89:53512
11:22:05,141 WARN [FD] ping_dest is null: members=[172.17.66.89:35668,
172.17.64.89:53512], pingable_mbrs=[172.17.64.89:53512], local_addr=172.17.64.89:53512
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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:54 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1240:
--------------------------------------
What value of the new remoting parameter "stopLeaseOnFailure" did you use?
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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
9 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=comments#action_1... ]
Jeff Mesnil commented on JBMESSAGING-1240:
------------------------------------------
11:21:45,137 WARN [FD] ping_dest is null:
members=[172.17.66.89:35668, 172.17.64.89:53512], pingable_mbrs=[172.17.64.89:53512],
local_addr=172.17.64.89:53512
This log comes from JGroups, not JBoss Remoting afaik
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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:06 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=all ]
Tim Fox reassigned JBMESSAGING-1240:
------------------------------------
Assignee: Tim Fox (was: Phillip Thurmond)
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Tim Fox
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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:11 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1240:
--------------------------------------
Are you sure you have waited long enough for JGroups to give up?
The FD config from the default stack is:
<FD timeout="10000" max_tries="5" down_thread="false"
up_thread="false" shun="true"/>
So it will retry for 5 x 10000 = 50 seconds.
Can you verify that it gives up after this time.
See http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroupsFD for more info
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Tim Fox
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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:12 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=all ]
Tim Fox reassigned JBMESSAGING-1240:
------------------------------------
Assignee: Phillip Thurmond (was: Tim Fox)
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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:12 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=comments#action_1... ]
Phillip Thurmond commented on JBMESSAGING-1240:
-----------------------------------------------
StopLeaseOnFailure is set to true.
I believe I was seeing these messages after 50 seconds, but I will double check.
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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
1:10 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=comments#action_1... ]
Phillip Thurmond commented on JBMESSAGING-1240:
-----------------------------------------------
Message continues long after 50 seconds.
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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:30 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=comments#action_1... ]
Andy Taylor commented on JBMESSAGING-1240:
------------------------------------------
Does this occur every single time?
Are there any stacktraces on the server during failover, I'm thinking of something
with the following in:
org.jboss.messaging.core.impl.postoffice.GroupMember$ControlMembershipListener.viewAccepted(GroupMember.java:498)
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Phillip Thurmond
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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:46 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=all ]
Andy Taylor reassigned JBMESSAGING-1240:
----------------------------------------
Assignee: Andy Taylor (was: Phillip Thurmond)
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Andy Taylor
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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:34 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1240) Reconnect message continually repeated in logs after a node has failed over.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1240?page=all ]
Tim Fox closed JBMESSAGING-1240.
--------------------------------
Resolution: Done
Reconnect message continually repeated in logs after a node has
failed over.
----------------------------------------------------------------------------
Key: JBMESSAGING-1240
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1240
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3_CP01
Reporter: Phillip Thurmond
Assigned To: Andy Taylor
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.CR1
To reproduce:
1) bring up a JBM cluster with clustered queues/topics.
2) generate a load against the cluster
3) kill -9 one of the nodes.
4) Transparent failover does occur, but afterwards the following message will be logged
every few seconds for the remainder of the time the server is up:
14:27:25,157 WARN [FD] ping_dest is null: members=[172.17.66.89:35329,
172.17.64.89:52972], pingable_mbrs=[172.17.64.89:52972], local_addr=172.17.64.89:52972
14:27:27,143 WARN [LeasePinger] LeasePinger[SocketClientInvoker[1ff335bb,
bisocket://172.17.66.89:4457](ai03d-4vcpjz-fd4p7oty-1-fd4p8bdv-a)] failed to ping to
server: Can not get connection to server. Problem establishing socket connection for
InvokerLocator
[bisocket://172.17.66.89:4457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=10000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=10&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat]
Maybe we need some type of timeout here so that it doesn't try to reconnect forever?
--
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
6627
days inactive
6658
days old
17 comments
4 participants
participants (4)
-
Andy Taylor (JIRA) -
Jeff Mesnil (JIRA)
-
Phillip Thurmond (JIRA)
-
Tim Fox (JIRA)