Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.1
    • Component/s: security
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      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@Sun.COM. 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.

        Activity

        Hide
        wap added a comment -

        A stuck thread that waits forever on an input stream.

        Show
        wap added a comment - A stuck thread that waits forever on an input stream.
        Hide
        wap added a comment -

        The leak is fixed for me in Metro 2.2-b13. However, the workaround with invocation of Closable.close() throws an NPE now. But this is only a very minor issues, as the client should not invoke it at all.

        Show
        wap added a comment - The leak is fixed for me in Metro 2.2-b13. However, the workaround with invocation of Closable.close() throws an NPE now. But this is only a very minor issues, as the client should not invoke it at all.
        Hide
        Nithya Ramakrishnan added a comment - - edited

        Could you please provide the stack trace ? Also would the previously attached test case help to reproduce the error?

        Thanks
        Nithya

        Show
        Nithya Ramakrishnan added a comment - - edited Could you please provide the stack trace ? Also would the previously attached test case help to reproduce the error? Thanks Nithya
        Hide
        geturnerlmco added a comment -

        There was no stack trace, it was a memory leak. All of the information to reproduce the problem is in the original filing. Thanks.

        Show
        geturnerlmco added a comment - There was no stack trace, it was a memory leak. All of the information to reproduce the problem is in the original filing. Thanks.
        Hide
        kumarjayanti added a comment -

        You mentioned the workaround with invocation of Closable.close() throws an NPE now, so we are asking what is the stack trace. Otherwise we understand the issue is fixed ?.

        Show
        kumarjayanti added a comment - You mentioned the workaround with invocation of Closable.close() throws an NPE now, so we are asking what is the stack trace. Otherwise we understand the issue is fixed ?.

          People

          • Assignee:
            kumarjayanti
            Reporter:
            geturnerlmco
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: