[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2370) Ensure correct JBossWS startup if there are Webservice archived in deploy directory during JBossAS bootstrap

[Richard Opalka (JIRA)]

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

Richard Opalka updated JBWS-2370:
---------------------------------

    Comment: was deleted


> Ensure correct JBossWS startup if there are Webservice archived in deploy directory during JBossAS bootstrap
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JBWS-2370
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2370
>             Project: JBoss Web Services
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-metro, jbossws-native
>    Affects Versions: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4
>            Reporter: Richard Opalka
>            Assignee: Richard Opalka
>             Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0
>
>
> During deployment of the endpoints declared in my wars a call is made to AbstractServerConfig.getConnectorPort(). This fetches the WS Server MBean and tries to lookup objects of type "jboss.web:type=Connector,*". At the point where the lookup fails the jboss.web MBean has only one entry for the WebServer.
> In the run that I managed to debug the type=Connector entries were added at a later point. So, some of the subsequent calls to getConnectorPort() succeeded and also the AS bootstrap did not hang. I was unable to debug a case where the bootstrap did hang. 

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