User development, A new message was posted in the thread "Client hangs when get JMS connection factory": http://community.jboss.org/message/519933#519933 Author : mingjun jiang Profile : http://community.jboss.org/people/mjjiangbhr Message: -------------------------------------------------------------- Ron, thanks for your explaination. I know the meaning of "validatorPingTimeout" and "timeout". In Li Lin's original post, he said he solved this problem by changing the value of "timeout", actually, the changing of timeout value doesn't solve our problem, the changing of timeout value incurred another issue: you know, if there is no message in topic/queue in server side, then the remote client (message listener)  won't receive any message, that mean the connection is idle, if the idle duration exceeds the "timeout" value, then the JBM will forcibly close the connection, so the remoting client won't receive any subsequent messages any more, it's a serious problem!   Once more, as what I mentioned in this thread or https://jira.jboss.org/jira/browse/JBREM-1169, if we pull the physical ethernet connection, the connection Validator won't detect the failure and close the failure connection correspondingly. But if we killed the client (i.e. kill the process of message listener in "Task Manager" of Windows OS), the value of "currentClientPoolSize" will decrease to 0 immediately, that meants the Connectionvalidator could detect and close the failure connection under such situation. Ron, do you mean your test result show the ConnectionValidator could detect and close the failure connection when pulling out the physical ethernet connection?  Are you using the same version of JBM and remoting jar mentioned in Li Lin's post? -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/519933#519933