[
https://issues.jboss.org/browse/WFLY-124?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated WFLY-124:
----------------------------------
Assignee: Paul Ferraro (was: Brian Stansberry)
Read timed out on server shutdown and DIST SYNC
-----------------------------------------------
Key: WFLY-124
URL:
https://issues.jboss.org/browse/WFLY-124
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Fix For: 8.0.0.Alpha1
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.
{noformat}
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>
{noformat}
The exceptions seem to correlate with
{noformat}
./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
{noformat}
being thrown on the server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira