Ron, Yes it does appear these settings are propagated to the client as you indicated. 2008-11-19 01:15:47,389 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[Serenity.local:11457] started for locator InvokerLocator [bisocket://Serenity.local:11457/?JBM_clientMaxPoolSize=200&clientLeasePeriod=20000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&leasePingerTimeout=10000&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=2&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat&validatorPingPeriod=15000&validatorPingTimeout=10000] I will attach a remoting / messaging package trace log on the client side when I get a chance. There is no debug nor trace msg that explicitly states the values when the connection validator is created, but when a timeout error occurs it's pretty clear. I looked through some of the source, but it's not immediately evident to me where the timeout would get set on the connection validator. I'll attach more data when I can get it. Thanks for your nudge in the right direction. At least I now know the problem is on the client side. Mark View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190418#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...