The MDB problem we eventually solved by deploying MDB as ha-singleton. In JBoss
4.0.3 it seemed to work ok, but upgrading was not an option for us.
With remote EJB clients, we were able to reduce the failover time by editing
TCP settings. In Linux we reduced /proc/sys/net/ipv4/tcp_retries2 value
I experienced similar problems. In my case, I tested stateful session beans
failover. I unplugged the network cable of the JBoss server which was
responding to the request. The other clustered JBoss server discovered the
failure but did not respond until five minutes later. I have no idea where
Hi,
Did you find any solution to this? I'm having the same problem with JBoss 4.0.2.
13:36:25,997 WARN [Connection] Connection failure, use
javax.jms.Connection.setExceptionListener() to handle this error and reconnect
| org.jboss.mq.SpyJMSException: No pong received; - nested throwable:
(j
