Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-2795

Memory leaks in case of incorrect SOAP/JMS response

    XMLWordPrintableJSON

    Details

    • Estimated Complexity:
      Unknown

      Description

      1. Generate CXF client (Conduit) from WSDL
      2. Transport = JMS
      3. receiveTimeout set to some value

      4. Send request to some backend (e.g. Mock)
      5. Get correct (according WSDL) response .
      6. Observe objects in memory, related to message caching (com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl and related ones). In appropriate time they disappear. OK.

      7. Send request
      8. Get exception response according WSDL schema, or other responce according schema that leads to exception (e.g. wrong WS policy)
      9. Observe same objects in memory. In appropriate time they disappear. OK.

      10. Send request
      11. Put to the output queue response to request NOT according WSDL schema, e.g. just text string. This case imitates e.g. wrong backend functionality.
      12. Observe same objects in memory.

      The mentioned objects are kept in memory FOREVER

      So, it means that the memory leaks exist. In case of big requested the OutOfMemory error appears.

        Attachments

        1. memory-usage-for-jms-error-2.png
          69 kB
          Andrei Shakirin
        2. memory-usage-for-jms-error-1.png
          81 kB
          Andrei Shakirin

          Activity

            People

            • Assignee:
              ashakirin Andrei Shakirin
              Reporter:
              ku Konstantin Ushakov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: