[jboss-jira] [JBoss JIRA] Commented: (JBESB-157) Socket listeners might introduce a port conflict when reinstantiated by the controlling GpListener at parameter reload time

[Mark Little (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-157?page=comments#action_12351035 ] 
            
Mark Little commented on JBESB-157:
-----------------------------------

Still relevant?

> Socket listeners might introduce a port conflict when reinstantiated by the controlling GpListener at parameter reload time
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBESB-157
>                 URL: http://jira.jboss.com/jira/browse/JBESB-157
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.0 CR1
>            Reporter: Esteban Schifman
>         Assigned To: Esteban Schifman
>            Priority: Minor
>             Fix For: 4.0
>
>
> GpListener has at present two mechanisms to reload it's configuration parameters:  a) timer driven  2) message driven.
> At parameter reload time, the controlling instance of GpListener will try to instantiate new child processes according to the new configuration values.  It will allow active child threads to gracetully finish.
> New listener classes that are accepting connections on specific sockets will have a conflict when the new instance tries to listen on a port that is being used by the active instance.

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