[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: Ability to restart a Connect with SocketServerInvoker

[ron.sigal@jboss.com]

Hi Brian,

I suppose the idea was that UnifiedInvoker wouldn't be sharing it's Connector/SocketServerInvoker with anyone else.  Conceptually, I think you're right that an invocation handler shouldn't shut down its server.  Of course, it's probably reasonable to think of UnifiedInvoker as a special case.

It seems to me that there are two solutions.

1. Let UnifiedInvoker continue to shut down its Connector and restart the Connector before restarting UnifiedInvoker.

2. Remove


  |       if(serverInvoker != null)
  |       {
  |          serverInvoker.stop();
  |       }
  | 

from UnifiedInvoker.stopService().  

Either solution should eliminate the problem with restarting SocketServerInvoker.  The first solution creates a new SocketServerInvoker, and the second reuses a running SocketServerInvoker.

Since you're doing the testing, do you mind making the changes?

-Ron

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156036#4156036

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156036