Uploaded image for project: 'Axis'
  1. Axis
  2. AXIS-1765

Memory leak when setting server's service as global scope

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.2RC2
    • Fix Version/s: None
    • Component/s: Basic Architecture
    • Labels:
    • Environment:
      MS windows xp, sp2

      Description

      When setting the scope of my service to application, the client side will run out of memory after 5-10 thousand hits. The service object on the server side is thread safe and works with both application and request scope. The server does not have any leak.

      To fix memory leak, inside the generated stub, I wrap the call with a try/catch/finally, and in that, I put:

      _call.getMessageContext().getRequestMessage().getSOAPEnvelope().getRecorder().clear();

      This would clear out the memory and no more leak.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              st946tbf@drexel.edu vd
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: