https://wsit.dev.java.net/issues/show_bug.cgi?id=1260 Issue #|1260
Summary|memory leak from ws security
Component|wsit
Version|2.0
Platform|All
OS/Version|All
URL|
Status|NEW
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P3
Subcomponent|security
Assigned to|kumarjayanti
Reported by|geturnerlmco
------- Additional comments from
geturnerlmco@... Mon Sep 21 21:20:57 +0000 2009 -------
This issue was discovered while performing leak testing using JProbe 8.1. The
leak is from security classes that are allocated from using a WebServiceRef in
an EJB or servlet. The leak can be partially cleanup up by calling the close
method of the Closeable interface of the port type, but this is only a
documented feature of the Reliable Messaging handling. This has been discussed
with
Vbkumar.Jayanti@.... I have created a test case that uses a servlet
to trigger the leak (
https://localhost:8181/MetroLeakTest/test?LEAK=no, or
LEAK=yes) will either call the close method, or not. The servlet class must be
updated with the correct constants for the local server.
---------------------------------------------------------------------
To unsubscribe, e-mail:
issues-unsubscribe@...
For additional commands, e-mail:
issues-help@...
