-
1. Re: SEVERE [org.jgroups.protocols.TCP] (Timer-3,<ADDR>) failed sending message to cluster
wdfink Jul 6, 2012 3:14 PM (in response to radzish)What configuration do you use and what do you change?
Could you attach the XML configurationfile.
-
2. Re: SEVERE [org.jgroups.protocols.TCP] (Timer-3,<ADDR>) failed sending message to cluster
radzish Jul 8, 2012 6:48 AM (in response to wdfink)Find standalone-ha.xml attached in original message:
https://community.jboss.org/servlet/JiveServlet/download/746671-61568/standalone-ha.xml
-
3. Re: SEVERE [org.jgroups.protocols.TCP] (Timer-3,<ADDR>) failed sending message to cluster
wdfink Jul 9, 2012 2:40 AM (in response to radzish)I've no idea at the moment.
Is it always the same node where this happen?
Do you compare the configuration with the other ones? It might be a network problem, so I would check the IP configuration
Maybe setting the 'org.jgroups' logger to TRACE before you start redeploy might geive a hint.
-
4. Re: SEVERE [org.jgroups.protocols.TCP] (Timer-3,<ADDR>) failed sending message to cluster
freerobby Oct 4, 2012 8:38 PM (in response to radzish)Did you ever find a solution for this? We see it, too.
-
5. Re: SEVERE [org.jgroups.protocols.TCP] (Timer-3,<ADDR>) failed sending message to cluster
rhusar Oct 5, 2012 6:22 AM (in response to freerobby)Robby, are you also using JDBC PING as Alexander?
-
6. Re: SEVERE [org.jgroups.protocols.TCP] (Timer-3,<ADDR>) failed sending message to cluster
freerobby Dec 12, 2012 4:58 PM (in response to rhusar)Radoslav,
Sorry, I forgot to reply to this back in October. Yes, we are using JDBC PING like Alexander, and are still seeing this issue via latest Torquebox 2.2.0.
(I assume you're referring to this):
<protocol type="JDBC_PING">
<property name="datasource_jndi_name">
java:jboss/datasources/ed
</property>
</protocol>
-
7. Re: SEVERE [org.jgroups.protocols.TCP] (Timer-3,<ADDR>) failed sending message to cluster
rhusar Dec 13, 2012 6:17 AM (in response to freerobby)Robby & Alexander, you need to provide more verbose logs for us to look into it, stack traces and TRACE logs will be a good start.