[
https://issues.apache.org/jira/browse/SMXCOMP-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paweł Ciechański updated SMXCOMP-972:
-------------------------------------
Attachment: partialRequestHashmapMexStructure.txt
I have checked about half of MessageExchanges that piled up in our BeanEndpoint
instance.
All exchanges were InOnly.
I have found:
- 4 incoming requests, already processed, status: Error, error:
java.lang.OutOfMemoryError
- 2 incomming requests, not yet processed, status: Active
- 34 outgoing requests, probably processed, status: Done.
I have attached file showing how those requests were structured in
ConcurrentHashMap request field. I am not sure if it will help.
Please note that my heap dump was done few minutes after OutOfMemoryError, not
right after. Also, processing might still have been ongoing.
> memory leak in org.apache.servicemix.bean.BeanEndpoint
> -------------------------------------------------------
>
> Key: SMXCOMP-972
> URL: https://issues.apache.org/jira/browse/SMXCOMP-972
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-bean
> Affects Versions: 2013.01
> Reporter: Paweł Ciechański
> Priority: Critical
> Attachments: 1.LeakSuspect.PNG, 2.Object.bmp,
> partialRequestHashmapMexStructure.txt
>
>
> When OutOfMemoryError occurs during processing in
> org.apache.servicemix.bean.BeanEndpoint, sent requests are not deleted from
> "requests" field.
--
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
