You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andrei Shakirin (JIRA)" <ji...@apache.org> on 2012/12/27 19:12:13 UTC
[jira] [Updated] (CXF-2795) Memory leaks in case of incorrect
SOAP/JMS response
[ https://issues.apache.org/jira/browse/CXF-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Shakirin updated CXF-2795:
---------------------------------
Attachment: memory-usage-for-jms-error-1.png
> Memory leaks in case of incorrect SOAP/JMS response
> ---------------------------------------------------
>
> Key: CXF-2795
> URL: https://issues.apache.org/jira/browse/CXF-2795
> Project: CXF
> Issue Type: Bug
> Components: Configuration, Soap Binding, Transports
> Affects Versions: 2.2.7
> Environment: Windows XP, Solaris,
> Tibco EMS v.4.4.3,
> JProfiler 6.0.3
> Reporter: Konstantin Ushakov
> Labels: conduit, jms, memory_leak, soap
> Attachments: memory-usage-for-jms-error-1.png, memory-usage-for-jms-error-2.png
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira