[jbossws-issues] [JBoss JIRA] (JBWS-3717) EndpointResolver implementations do not verify endpoint state before using endpoint

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/JBWS-3717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12823564#comment-12823564 ] 

RH Bugzilla Integration commented on JBWS-3717:
-----------------------------------------------

Alessio Soldano <asoldano at redhat.com> made a comment on [bug 1017550|https://bugzilla.redhat.com/show_bug.cgi?id=1017550]

https://github.com/jbossas/jboss-eap/pull/576
                
> EndpointResolver implementations do not verify endpoint state before using endpoint
> -----------------------------------------------------------------------------------
>
>                 Key: JBWS-3717
>                 URL: https://issues.jboss.org/browse/JBWS-3717
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-integration, jbossws-native
>            Reporter: Alessio Soldano
>            Assignee: Alessio Soldano
>             Fix For: jbossws-cxf-4.2.2
>
>
> Currently the implementors of EndpointResolver (namely, WebAppResolver and PortComponentResolver do not check the state of an endpoint before trying using it. This is a problem as with JBWS-3643 the EndpointRegistry is now based on the AS service registry, so it's possible for the resolvers to see endpoints that are not started yet. The issue would likely affect scenarios with frequent and concurrent deploy/undeploy sequences or requests reaching the AS during boot.

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