[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Number of threads per jms client connection
timfox
do-not-reply at jboss.com
Thu Aug 9 06:56:17 EDT 2007
Hello Bart
"bartvh" wrote :
| I noticed that each connection creates two threads : a "control: Socket[....]" thread and a "Timer-..." thread.
|
The extra timer is due to a bug in the version of remoting used in AS 4.2.0. Ron has already fixed this and this new remoting jar will be available soon.
anonymous wrote :
| I can see understand that the first one is unavoidable without a complete rewrite of jboss-remoting to use nio and select.
|
Yes indeed, blocking IO is one of our major bugbears and the reason why we will be concentrating effort on a completely new socket transport based on Apache MINA for JBM 2.0.
anonymous wrote :
| Now, after stopping one of the nodes of the cluster, I see the number of threads increase: there are new threads called " WorkerThread#..[....]" with the following stack trace:
| java.net.SocketInputStream.socketRead0(Native Method)
| java.net.SocketInputStream.read(SocketInputStream.java:129)
| java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
| java.io.BufferedInputStream.read(BufferedInputStream.java:235)
| java.io.FilterInputStream.read(FilterInputStream.java:66)
| org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:810)
| org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:506)
| org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:383)
| org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:165)
|
| This looks rather odd for a jms client. Is this the callback channel of the bi-socket protocol?
I'm not sure what is going on there - maybe Ron can advise?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072432#4072432
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072432
More information about the jboss-dev-forums
mailing list