What configuration do you use and what do you change?
Could you attach the XML configurationfile.
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.
Did you ever find a solution for this? We see it, too.
Robby, are you also using JDBC PING as Alexander?
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):
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.