Details
-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
Description
Some of the clients are getting read timeout when using dist sync and the node is gracefully shut down.
This is even more suspicions since the TOs in clustering are probably all set to max 15 seconds but the client timeout is set to 30 seconds. This looks fishy.
2012/05/13 17:22:54:388 EDT [WARN ][Runner - 1749] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: IO error: java.net.SocketTimeoutException: Read timed out>
The exceptions seem to correlate with
./perf20.log:[JBossINF] 17:23:11,344 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20/10.16.90.58:8009-109) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.RuntimeException: JBAS018060: Exception acquiring ownership of K5VcZ4gGFzRaLKYMesOQk0zD
being thrown on the server.