4:35 p.m.
Statement of problem:
anonymous wrote :
| 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.
|
"ron" wrote :
| Kumarselvan, what is your evidence for this behavior? Do you have some log file(s)?
|
"Kumarselvan" wrote :
| 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
|
|
| jboss.aop:service=AspectDeployer
| socket://${jboss.bind.address}:3873
|
|
| org.jboss.aspects.remoting.AOPRemotingInvocationHandler
|
|
|
|
| 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...
|
Kumarselvan, after a worker thread [org.jboss.remoting.transport.socket.ServerThread]
processes an invocation, it should just go to the top of a loop and wait for the next
invocation. If the load is very high, the server will try to close a ServerThread's
socket and reuse it with another socket, but I wouldn't expect the regular behavior
you're seeing. Another possibility is that some exception is being thrown in the
course of handling an invocation, which would cause the socket to be closed.
Could you turn on trace logging so we can get more information? Add
| <category name="org.jboss.remoting">
| <priority value="TRACE"/>
| </category>
|
to jboss-log4j.xml in the conf directory. See
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigureLogging for a discussion of logging in
the Application Server. Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114821#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...