Performance issues after switching from mq to jboss messagin
For few days now, i'm working on switching from mq to jboss messaging on jboss 4.2.0. I successfully started the server with jboss messaging without any errors and messages are processed by the mdbs.
So yesterday we did the same in the production environment but unfortunately customers are complaining that the web application is too slow although it was early in the morning with not much activity.
When we switched back to mq everything worked fine. Seems like the problem is messaging. we cheched that all the connections are closed normally. I noticed that we get many logs like that
2009-10-08 09:06:02,722 DEBUG [org.jboss.remoting.Client] starting callback Connector: InvokerLocator [bisocket://84.246.229.70:1724524841/callback?serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper&isCallbackServer=true&callbackServerProtocol=bisocket&datatype=jms&guid=2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6we&callbackServerHost=84.246.229.70&callbackServerPort=1724524841&clientMaxPoolSize=1&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper] 2009-10-08 09:06:02,722 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SocketServerInvoker[UNINITIALIZED] setting pingFrequency to 214748364 2009-10-08 09:06:02,722 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SocketServerInvoker[UNINITIALIZED] setting pingWindowFactor to 10 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] did not find server socket factory configuration as mbean service or classname. Creating default server socket factory. 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] created server socket factory javax.net.DefaultServerSocketFactory@10efd7c 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.transport.Connector] org.jboss.remoting.transport.Connector@ce79ab started 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.ServerInvoker] ServerInvoker (SocketServerInvoker[UNINITIALIZED]) added client callback handler CallbackManager[1ced81d] with session id of 2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf and callback handle object of null. 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@196046f from registry 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] Session id for callback handler is 2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] ServerInvokerCallbackHandler[2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf] using callbackTimeout value 10000 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] DefaultCallbackErrorHandler[UNITIALIZED] setting server invoker to SocketServerInvoker[127.0.0.1:4457] 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] DefaultCallbackErrorHandler[SocketServerInvoker[127.0.0.1:4457]] setting callback handler to ServerInvokerCallbackHandler[2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf] 2009-10-08 09:06:02,724 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] adding callback handler ServerInvokerCallbackHandler[2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf] 2009-10-08 09:06:02,724 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] found calllback handler for remoting session ...-g0jaad7m-6wc UID=2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc 2009-10-08 09:06:02,724 DEBUG [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] registered connection ConnectionEndpoint[iw6-o7daaj0g-1-byjvoi0g-cdp89-y1d6u6c2] as ...-g0jaad7m-6wc 2009-10-08 09:06:02,725 DEBUG [org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was available for Q_PENDING_MESSAGE_OUT, using default security config 2009-10-08 09:06:02,726 DEBUG [org.jboss.remoting.ServerInvoker] Thread pool class supplied is not an object name. 2009-10-08 09:06:02,731 DEBUG [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] unregistered connection ConnectionEndpoint[iw6-o7daaj0g-1-byjvoi0g-cdp89-y1d6u6c2] with remoting session ID ...-g0jaad7m-6wc 2009-10-08 09:06:02,731 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] removing callback handler ServerInvokerCallbackHandler[2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf] 2009-10-08 09:06:02,731 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@78c932 from registry 2009-10-08 09:06:02,731 DEBUG [org.jboss.remoting.ServerInvoker] ServerInvoker (SocketServerInvoker[UNINITIALIZED]) removing client callback handler with session id of 2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf. 2009-10-08 09:06:02,731 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] unrecognized listener ID: 2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf 2009-10-08 09:06:02,731 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@1e0f1db from registry 2009-10-08 09:06:02,731 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] stopped
I wonder if it doesn't have anything to do with this line : bisocket://84.246.229.70:1724524841
may be it should be 127.0.0.1 instead.
Any Thought ?
