After further investigation, it seems that the problem is due to a cleanup 
problem with the org.jboss.remoting.InvokerRegistry. The client invoker and 
server invoker from the previously created connection are not cleaned when the 
close method fails. I modified my code to clean this up manually 
using the following code before trying to recreate a connection:

  |          ServerInvoker[] serverInvokers = 
InvokerRegistry.getServerInvokers();
  |          for (ServerInvoker invoker : serverInvokers)
  |          {
  |             invoker.stop();
  |             invoker.destroy();
  |             InvokerRegistry.destroyServerInvoker(invoker);
  |          }
  |          ClientInvoker[] clientInvokers = 
InvokerRegistry.getClientInvokers();
  |          for (ClientInvoker invoker : clientInvokers)
  |          {
  |             InvokerRegistry.destroyClientInvoker(invoker.getLocator(),  
null);
  |          }
  | 
and the connection could be created without stopping my application, this also 
took care of the WorkerThread that I mentionned in my previous post.

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

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037747
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to