[jboss-user] [Remoting] - Re: How to set ping timeout of ConnectionValidator?

Wed Nov 19 15:55:09 EST 2008

Ron,

I can see this message on both sides of the connection:

2008-11-19 12:36:11,934 DEBUG [org.jboss.remoting.Client] starting callback Connector: InvokerLocator [bisocket://10.101.110.64:395136647/callback?callbackServerHost=10.101.110.64&callbackServerPort=395136647&callbackServerProtocol=bisocket&clientMaxPoolSize=1&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&guid=a2t321s-96w9c6-fnqfpbmc-1-fnqfprfi-c1&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper]

12:36:56,881 DEBUG [MicroSocketClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:114
57] setting maxPoolSize to 112:36:56,881 DEBUG [MicroSocketClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:114
57] setting client socket wrapper class name to org.jboss.jms.client.remoting.ClientSocketWrapper12:36:56,881 DEBUG [MicroSocketClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:114
57] setting shouldCheckConnection to false12:36:56,881 DEBUG [SocketClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:11457] s
etting timeout to 012:36:56,881 DEBUG [MicroSocketClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:114
57] constructed
12:36:56,881 DEBUG [MicroSocketClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:114
57] setting maxPoolSize to 112:36:56,881 DEBUG [MicroSocketClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:114
57] setting client socket wrapper class name to org.jboss.jms.client.remoting.ClientSocketWrapper
12:36:56,881 DEBUG [MicroSocketClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:11457] setting shouldCheckConnection to false12:36:56,881 DEBUG [SocketClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:11457] s
etting timeout to 012:36:56,881 DEBUG [BisocketClientInvoker] Setting ping frequency to: 214748364
12:36:56,881 DEBUG [MicroRemoteClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:11457] connecting12:36:56,881 DEBUG [MicroSocketClientInvoker] Creating semaphore with size 112:36:56,881 TRACE [MicroSocketClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:11457] added new pool ([]) as ServerAddress[10.101.110.64:11457, NO enableTcpNoDelay timeout 0 ms, maxPoolSize=1]
12:36:56,881 DEBUG [MicroRemoteClientInvoker] SocketClientInvoker[207f7d58, bisocket://serenity.solarworldusa.net:11457] connected
12:36:56,882 DEBUG [Client] starting callback Connector: InvokerLocator [bisocket://10.101.110.64:1072374883/callback?callbackServerHost=10.101.110.64&callbackServerPort=1072374883&callbackServerProtocol=bisocket&clientMaxPoolSize=1&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&guid=a2t321s-pldl5n-fnqfqp2i-1-fnqfqq41-g&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper]
12:36:56,953 DEBUG [ServerInvoker] SocketServerInvoker[10.101.110.64:1072374883] did not find server socket factory configuration as mbean service or classname. Creating default server socket factory.
12:36:56,954 DEBUG [ServerInvoker] SocketServerInvoker[10.101.110.64:1072374883] created server socket factory javax.net.DefaultServerSocketFactory at 7c502d56
12:36:56,955 DEBUG [BisocketServerInvoker] SocketServerInvoker[10.101.110.64:1072374883] setting pingFrequency to 214748364
12:36:56,955 DEBUG [BisocketServerInvoker] SocketServerInvoker[10.101.110.64:1072374883] setting pingWindowFactor to 10
12:36:56,971 DEBUG [Connector] org.jboss.remoting.transport.Connector at 61917b9e started
12:36:56,973 TRACE [LocalClientInvoker] Using local client invoker for invocation.
12:36:56,973 TRACE [ServerInvoker] SocketServerInvoker[10.101.110.64:1072374883] received InternalInvocation[3ea7f915]
12:36:56,973 TRACE [ServerInvoker] handling InternalInvocation where method name = addClientListener
12:36:56,974 DEBUG [ServerInvoker] ServerInvoker (SocketServerInvoker[10.101.110.64:1072374883]) added client callback handler CallbackManager[5514cd80] with session id of a2t321s-pldl5n-fnqfqp2i-1-fnqfqq12-c+a2t321s-pldl5n-fnqfqp2i-1-fnqfqq6k-h and callback handle object of null.
12:36:56,974 TRACE [ServerInvoker] SocketServerInvoker[10.101.110.64:1072374883] successfully dispatched invocation, returning null from subsystem 'JMS' to client a2t321s-pldl5n-fnqfqp2i-1-fnqfqq12-c
12:36:56,974 TRACE [InvokerRegistry] destroying client invoker InvokerLocator [bisocket://10.101.110.64:1072374883/callback?callbackServerHost=10.101.110.64&callbackServerPort=1072374883&callbackServerProtocol=bisocket&clientMaxPoolSize=1&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&guid=a2t321s-pldl5n-fnqfqp2i-1-fnqfqq41-g&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper], config {}
12:36:56,974 DEBUG [InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker at 6ee3572b from registry
12:36:56,974 TRACE [InvokerRegistry] disconnecting org.jboss.remoting.transport.local.LocalClientInvoker at 6ee3572b

Not sure if this helps, but I don't see anywhere in my client logs (TRACE level enabled for both org.jboss.remoting and org.jboss.messaging) that shows the validator timeout parameter being passed. It is clearly pinging every 2000ms (the default) even though I have the parameter configured differently. 

The LeasePinger does in fact get my modified parameters (ping frequency = 20000ms):
<client log>
12:37:22,285 TRACE [LeasePinger] LeasePinger[SocketClientInvoker[e1ddc89, bisocket://serenity.solarworldusa.net:11457](a2t321s-ujh9t3-fnqfr96u-1-fnqfr9p4-e)] adding new client with session ID a2t321s-ujh9t3-fnqfr96u-1-fnqfr9p2-c and lease period 20000

I haven't verified the timeout, but I can probably set it to a very short period (10ms) and verify that the lease times out. Unsure why the lease pinger gets his parameters and the connection validator does not.

what else can i try?

Thanks,

Mark

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190637#4190637

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190637