[jboss-jira] [JBoss JIRA] (WFLY-4424) NullPointerException in AbstractCommonConfigResolver.resolveEndpointConfig
[
https://issues.jboss.org/browse/WFLY-4424?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on WFLY-4424:
---------------------------------------
I figured out this is sometimes reproducible also by starting a WildFly instance already
having ws deployments. So I'm increasing the priority. This should likely block the
Beta release; if the required wildfly-core upgrade can't be done in time, I suggest we
apply a simple workaround in wildfly (that is, use actual hex phase values in
WSDeploymentActivator instead of constants to force proper DUP ordering).
NullPointerException in
AbstractCommonConfigResolver.resolveEndpointConfig
--------------------------------------------------------------------------
Key: WFLY-4424
URL: https://issues.jboss.org/browse/WFLY-4424
Project: WildFly
Issue Type: Bug
Components: Web Services
Reporter: Gytis Trikleris
Assignee: Alessio Soldano
Fix For: 9.0.0.Beta1
Lately we started to get following exception in our XTS tests:
{code}
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start
service jboss.deployment.unit."xtstest.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."xtstest.war".PARSE: WFLYSRV0153: Failed to process phase
PARSE of deployment "xtstest.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.NullPointerException
at
org.jboss.ws.common.configuration.AbstractCommonConfigResolver.resolveEndpointConfig(AbstractCommonConfigResolver.java:129)
at
org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER.processAnnotation(WSIntegrationProcessorJAXWS_HANDLER.java:95)
at
org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:74)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
... 5 more
{code}
It is intermittent and seems to be caused by some sort of race condition.
It started to happen once this commit was introduced:
https://github.com/wildfly/wildfly/commit/c0c1e82d8472e1b29c679380d5e0aea...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)