[
http://jira.jboss.com/jira/browse/JBMESSAGING-1268?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1268:
--------------------------------------
Tyronne-
You're last comment is *not* correct, you do not need need to set the attribute
DisableRemotingChecks, if you are using the correct version of EAP i.e. EAP 4.3. CP02.
You must be using EAP 4.3 CP02! Look at the fix version on this task.
If you need to set this attribute it means you are using an older version of JBM which
*won't work*.
Work around for connection validator hanging when cable is pulled
-----------------------------------------------------------------
Key: JBMESSAGING-1268
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1268
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.4.0.SP3.CP02, 1.4.1.CR1
If ethernet cable between client and server is pulled, or server "disappears" -
e.g. whole server box fails, then connection validator will hang on the socket write until
socket timeout is reached.
JBM uses socket timeout of 0 (infinite) so will hang potentially for ever, and client
side exception listener will never get called.
Workaround for now is to make the socket timeout to some lower value e.g. 10 seconds.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira