Community
Participate
Working Groups
Build ID: M20070212-1330 Steps To Reproduce: 1.Launch the Web service explorer numerous times on a WSDL. More information: Memory will continue to build up unless the user is able to access the same session to clear nodes. If the browser is closed, the user will not be able to access the WSE(especially for external browsers), and so the memory accumulates until the user re-starts their workspace.
Here's an assessment of the impact/risk for this candidate fix. A MaxTimeOutInterval of 30mins will be set for the Web service Explorer session. Currently, it will never time out. The behavior will change for 'timed out' sessions (left idle for 30mins). Any action to select a (WSDL)node, refresh the node tree, or clear an item in the node tree will result in the browser being redirected to a new SessionTimedOut.jsp which displays a message indicating the session has expired - and to relaunch the WSE. Without this fix, we've observed that memory consumed by each WSE launch will accumulate in non-heap space, and eventually result in poor performance. This memory will never be reclaimed by GC as long as the session is still active, and the user has not 'cleared' the item from the WSDL node tree. It is a common occurance to launch the WSE, and then close the browser after testing. Since the node tree is not cleared, memory will accumulate. By setting a MaxTimeOutInterval for the wsexplorer.jsp, the memory can be GC'd when the session times out, and the objects are relinquished.
Since there is a workaround for this problem (clearing the WSDL from WSE manually), I don't think the severity of this bug should be critical. Seng, I believe you have a fix in hand already. Please attach the patch to this bug.
Created attachment 88838 [details] wst.ws.explorer plugin patch
Created attachment 89032 [details] wst.ws.explorer plugin patch Replaces message with externalized strings from explorer.properties file.
Gil, please review this patch. We would like to include it in M6.
Patch committed and released to HEAD as v200803261855.
mass change to add 'contributed' keyword based on bugzilla query, please correct if that's not accurate (by marking patches as obsolete and removing the 'contributed' keyword.
Verified.
Verified, closing.
