Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
User reported:
"I am using the the jaxws:endpoint Spring bean which when destroyed calls Endpoint.stop(). This means when the container removes an application, i.e. stops an endpoint, the resources for this endpoint will not be cleaned up. A user may think they are removing an application when in fact they are not, which after a period of time will cause problems. We need to either change the semantics of Endpoint.stop() or add some kind of destroy() method to EndpointImpl.
I can get out of memory error after as little as 14 times endpoint publishing/stopping."