[
https://issues.apache.org/jira/browse/CXF-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Birnie updated CXF-6835:
-----------------------------
Description:
When starting up a service with WS-Discovery, there is a deadlock which can
occur if the service is invoked from outside before the WS-Discovery
registration has completed. Please see attached stacktraces.
In order to reproduce, create a spring project and run with new
ClasspathXmlApplicationContext(...). Configure this to provide a jaxws service.
Then you'll need a client to simply poll this service repeatedly. Start the
client first, then the server. In my experience you'll find the deadlock on the
server side most of the time.
was:When starting up a service with WS-Discovery, there is a deadlock which
can occur if the service is invoked from outside. Please see attached
stacktraces.
> Deadlock in WS-Discovery when service called during startup
> -----------------------------------------------------------
>
> Key: CXF-6835
> URL: https://issues.apache.org/jira/browse/CXF-6835
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 3.1.4
> Reporter: Nick Birnie
>
> When starting up a service with WS-Discovery, there is a deadlock which can
> occur if the service is invoked from outside before the WS-Discovery
> registration has completed. Please see attached stacktraces.
> In order to reproduce, create a spring project and run with new
> ClasspathXmlApplicationContext(...). Configure this to provide a jaxws
> service. Then you'll need a client to simply poll this service repeatedly.
> Start the client first, then the server. In my experience you'll find the
> deadlock on the server side most of the time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
