[jboss-jira] [JBoss JIRA] Commented: (JBREM-877) New Socket Connection is being Created for Every Client Request to the Server
Kumarselvan Somasundaram (JIRA)
jira-events at lists.jboss.org
Tue Dec 18 00:09:43 EST 2007
[ http://jira.jboss.com/jira/browse/JBREM-877?page=comments#action_12392518 ]
Kumarselvan Somasundaram commented on JBREM-877:
------------------------------------------------
i am getting the following log:
2007-12-17 20:12:33,138 DEBUG [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 60000
2007-12-17 20:12:33,143 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#1[131.10.20.210:40824] closing socketWrapper: ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40824,localport=3873].229885]
2007-12-17 20:12:33,143 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper] wrote CLOSING
2007-12-17 20:12:33,143 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40824,localport=3873].229885] closing
2007-12-17 20:12:33,231 DEBUG [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 60000
2007-12-17 20:12:33,236 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#0[131.10.20.210:40825] closing socketWrapper: ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40825,localport=3873].aea1a2]
2007-12-17 20:12:33,236 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper] wrote CLOSING
2007-12-17 20:12:33,236 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40825,localport=3873].aea1a2] closing
2007-12-17 20:12:33,247 DEBUG [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 60000
2007-12-17 20:12:33,252 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#1[131.10.20.210:40826] closing socketWrapper: ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40826,localport=3873].5cf1a4]
2007-12-17 20:12:33,252 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper] wrote CLOSING
2007-12-17 20:12:33,252 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40826,localport=3873].5cf1a4] closing
2007-12-17 20:12:33,259 DEBUG [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 60000
2007-12-17 20:12:33,265 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#0[131.10.20.210:40827] closing socketWrapper: ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40827,localport=3873].150a19a]
2007-12-17 20:12:33,265 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper] wrote CLOSING
2007-12-17 20:12:33,265 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40827,localport=3873].150a19a] closing
2007-12-17 20:12:33,331 DEBUG [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 60000
2007-12-17 20:12:33,336 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#1[131.10.20.210:40828] closing socketWrapper: ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40828,localport=3873].1c3f810]
2007-12-17 20:12:33,336 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper] wrote CLOSING
2007-12-17 20:12:33,336 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40828,localport=3873].1c3f810] closing
2007-12-17 20:12:33,372 DEBUG [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 60000
2007-12-17 20:12:33,376 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#0[131.10.20.210:40829] closing socketWrapper: ServerSocketWrapper[Socket[addr=/131.10.20.210,port=40829,localport=3873].1be1b4]
"se
This is keep on happening.....
also i have seen in the netstat -nac | grep 3873
in this i am able to see the client side port is changing and it is increasing for each connections made
I am using default configuration of ejb3 remoting conf
<mbean code="org.jboss.remoting.transport.Connector"
name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
<depends>jboss.aop:service=AspectDeployer</depends>
<attribute name="InvokerLocator">socket://${jboss.bind.address}:3873</attribute>
<attribute name="Configuration">
<handlers>
<handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
</handlers>
</attribute>
</mbean>
Is there is any other configration change i need to make it with the current release so that the problem i am having will get resolved...
One thing i am not able to understand is y the connection getting closed for each call at the server side, this closing needs to happen only after the timeout.
i Hope there is some exception which causes the connection to close forcely...
> New Socket Connection is being Created for Every Client Request to the Server
> -----------------------------------------------------------------------------
>
> Key: JBREM-877
> URL: http://jira.jboss.com/jira/browse/JBREM-877
> Project: JBoss Remoting
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: transport
> Affects Versions: 2.2.2.SP2
> Environment: Linux os , Pentium duo Processor with 3.6 Ghz clock Speed, 4GB Ram in this Postgresql Database also Running
> Reporter: Kumarselvan Somasundaram
> Priority: Critical
> Fix For: 2.4.0.Beta1 (Pinto)
>
>
> whenever EJB3 client requests the Server new socket is being created. at the client side the socket connection pool is not being used. Hope there is some issue with the socket connection after getting response from the server,becoz of which the server side the connection is being closed. this increases the CPU utilization,
> The same code is running fine in jboss 4.0.4 with jboss remoting 1.4.0
> new remoting 2.2.2 SP4 only handling 1/4 of the load with high CPU utilization.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list