[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-992) Can't restart a Connector that uses SocketServerInvoker

Doychin Bondzhev (JIRA) jira-events at lists.jboss.org
Sun Jan 4 02:50:54 EST 2009


    [ https://jira.jboss.org/jira/browse/JBREM-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444420#action_12444420 ] 

Doychin Bondzhev commented on JBREM-992:
----------------------------------------

>From what I can see in the source code this problem is not visible in 2.2.x.

There is this code in SocketServerInvoker.start() method:

         if(maxPoolSize <= 0)
         {
            //need to reset to default
            maxPoolSize = MAX_POOL_SIZE_DEFAULT;
         }



> Can't restart a Connector that uses SocketServerInvoker
> -------------------------------------------------------
>
>                 Key: JBREM-992
>                 URL: https://jira.jboss.org/jira/browse/JBREM-992
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.GA (Pinto), 2.4.0.SP1 (Pinto), 2.5.0.GA (Flounder)
>            Reporter: Brian Stansberry
>            Assignee: Ron Sigal
>            Priority: Minor
>             Fix For: 2.5.0.SP3 (Flounder)
>
>
> You can't take a Connector that uses SocketServerInvoker through a restart, i.e. these lifecycle steps:
> create/start/stop/start.
> You have to do a full transition to destroy and back through create.
> This is because SocketServerInvoker sets its maxPoolSize field to 0 as part of its cleanup work in stop(). If you then call start() you get a failure due to 0 being an invalid value for maxPoolSize:
> 2008-06-04 12:33:00,382 DEBUG [org.jboss.invocation.unified.server.UnifiedInvokerHA] (RMI TCP Connec
> tion(31)-127.0.0.1) Starting failed jboss:service=invoker,type=unifiedha,partitionName=RestartPartit
> ion
> java.lang.IllegalArgumentException: Illegal cache capacities
> 	at org.jboss.util.LRUCachePolicy.<init>(LRUCachePolicy.java:77)
> 	at org.jboss.remoting.transport.socket.LRUPool.<init>(LRUPool.java:44)
> 	at org.jboss.remoting.transport.socket.SocketServerInvoker.start(SocketServerInvoker.java:231)
> 	at org.jboss.invocation.unified.server.UnifiedInvoker.startService(UnifiedInvoker.java:140)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
> 	at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)	

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-remoting-issues mailing list