[Remoting] - Re: version confusion
by ron.sigal@jboss.com
I can tell you that Remoting 2 is entering the twilight of its lifetime, though I expect it to be in active maintenance mode for a few years. That is, there won't be much new development, but I'll continue to fix bugs. It's in some of our products supported by contacts, so we're obligated to keep it working. So I think it's safe to start using Remoting 2.
Remoting 3 will be the Remoting of the future. David Lloyd could tell you more about the status of Remoting 3, but I believe 3.0.0.GA is missing some functionality. I believe 3.1.0 will be more "featureful", and the next release will be 3.1.0.CR1. I can't tell you when it will appear. Remoting 3 will have the advantage of being in active development, so, if there's a feature you want, you're more likely to get it Remoting 3 than in Remoting 2.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244413#4244413
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244413
17 years
[Remoting] - Re: ServerInvocationHandler Performance problem
by ron.sigal@jboss.com
Hi Alfonso,
Sorry to be dense, but I'm just not following you. Are you asking how to determine how many connections are coming into a Remoting server?
If so, and assuming you are using the socket transport, then I can tell you that each connection to the server is represented by an org.jboss.remoting.transport.socket.ServerThread. The ServerThread manages invocations coming in over a single socket. It sits in a loop like this:
| while (socket is open)
| read invocation
| process invocation
| return result
|
So the ServerThread could be sitting in SocketInputStream.read() waiting for the next invocation, but I guess you could still consider it an active connection. To get the number of currently active ServerThreads, you can do something like:
| ((SocketServerInvoker) serverInvoker).getCurrentClientPoolSize()
|
assuming you have access to the ServerInvoker. For example, if you're trying to make the call from an implementation of org.jboss.remoting.ServerInvocationHandler, you can implement ServerInvocationHandler.setInvoker() to store a reference to the ServerInvoker.
If I've misunderstood your question, please try again.
-Ron
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244411#4244411
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244411
17 years