[jboss-jira] [JBoss JIRA] Resolved: (JBAS-5762) Binding service deployed after RMI port opened

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-5762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved JBAS-5762.
------------------------------------

    Resolution: Done


Work on JBAS-5192 has moved the binding service deploy before anything in conf/jboss-service.xml.

> Binding service deployed after RMI port opened
> ----------------------------------------------
>
>                 Key: JBAS-5762
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5762
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-5.0.0.CR1
>            Reporter: Peter Johnson
>            Assignee: Brian Stansberry
>             Fix For: JBossAS-5.0.0.CR2
>
>
> The binding service is being deployed too late during startup and thus the RMI service always binds to the default port (8083).  (Actually, CR1 has made some progress - in beta3 and beta4 the AJP and HTTP ports were also being assigned before the binding service started.)  I do not recall if the JNDI service is using the binding service (sort of hard to tell because the naming service no longer logs the JNDI port on the console log).

-- 
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