Details
-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
Description
The AbstractServerConfig has a getConnectorPort method for finding the default port to be used for endpoint addresses; that looks for the proper configured http connector.
The retrieval goes through a MSC service lookup (ServiceName.JBOSS.append("web", "common", "server")) in org.jboss.as.webservices.config.WebServerInfoFactoryImpl / WebServerInfoImpl. This creates a possible race condition at boot, given the web common server service might possibly start after a ws deployment process hit the EndpointAddressDeploymentAspect (actually to be verified). To be honest, the AbstractServerConfig has sensible defaults that would mitigate the problem if happening, but still this should be fixed.
A proposal would be to modify the WebServerInfoFactoryImpl / WebServerInfoImpl to wait for the availability of WS service having dependency on the web common server service.