[
https://issues.apache.org/jira/browse/CXF-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719542#action_12719542
]
Alberto García Pañoso commented on CXF-2277:
--------------------------------------------
I have been debugging the sources of CXF and I think the problem is that the
queues for executing the One-Way Web Services (class AutomaticWorkQueueImpl)
aren't stopped (invoking the shutdown method of ThreadExecutorPool, its
superclass) when Tomcat stop. I have done a test and if you create a
ThreadExecutorPool and don't stop it invoking the shutdown method, then Tomcat
doesn't stop right.
> Error stopping Tomcat after executing a one-way Web Service
> -----------------------------------------------------------
>
> Key: CXF-2277
> URL: https://issues.apache.org/jira/browse/CXF-2277
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.2.1, 2.2.2
> Environment: Apache Tomcat 6.0.14 and Sun Java 1.6.0_10
> Reporter: Alberto García Pañoso
>
> I have a Web application using Apache CXF that implements several Web
> Service. This application is deployed in a Tomcat 6.0.14. When I try to stop
> the Tomcat the server doesn't stop correctly. I have done a lot of tests and
> my conclussions are the following:
> - If a Web Service deployed like One-Way service is invoked (I mean, the web
> service implementation run in my application) then the Tomcat Server doesn't
> stop.
> - If no One-Way Web Services are invoked then the server stop right.
> I think there is some problem with the implementation of One-Way services. I
> think some thread or pool doesn't stop and, consequently, Tomcat neither
> stop. Do you think this is an error of CXF or the Sun JVM?
> Thanks in advance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
