[
https://issues.jboss.org/browse/JBWS-3691?page=com.atlassian.jira.plugin....
]
Alessio Soldano updated JBWS-3691:
----------------------------------
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.
was:
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 this 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.
Refactor default webservice port retrieval mechanism
----------------------------------------------------
Key: JBWS-3691
URL:
https://issues.jboss.org/browse/JBWS-3691
Project: JBoss Web Services
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: jbossws-cxf, jbossws-integration
Reporter: Alessio Soldano
Fix For: jbossws-cxf-4.3
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira