We are using Jboss4.2.4 with JBM 1.4.2.GA-SP1 and jboss-remoting-2.2.2.SP11.jar. | <invoker transport="bisocket"> | <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute> | <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute> | <attribute name="dataType" isParam="true">jms</attribute> | <attribute name="socket.check_connection" isParam="true">false</attribute> | <attribute name="timeout" isParam="true">0</attribute> | <attribute name="serverBindAddress">${jboss.bind.address}</attribute> | <attribute name="serverBindPort">4557</attribute> | <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute> | <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute> | <attribute name="numberOfCallRetries" isParam="true">1</attribute> | <attribute name="pingFrequency" isParam="true">214748364</attribute> | <attribute name="pingWindowFactor" isParam="true">10</attribute> | <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute> | | <attribute name="clientLeasePeriod" isParam="true">10000</attribute> | <attribute name="numberOfRetries" isParam="true">10</attribute> | <attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute> | <!-- The maximum time to wait before timing out on trying to write a message to socket for delivery --> | <attribute name="callbackTimeout">10000</attribute> | </invoker> | The remoting guys resolve the problem by setting TCP TTL.This is a ugly way. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223154#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...