servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] Updated: (SMXCOMP-96) ServiceMix JMS MultiplexingConsumerProcessor memory bloat due to hung/delayed exchanges
Date Sun, 06 Feb 2011 09:51:31 GMT

     [ https://issues.apache.org/jira/browse/SMXCOMP-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jean-Baptiste Onofré updated SMXCOMP-96:
----------------------------------------

    Fix Version/s:     (was: 2011.01)
                   2011.02

> ServiceMix JMS MultiplexingConsumerProcessor memory bloat due to hung/delayed exchanges
> ---------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-96
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-96
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-jms
>    Affects Versions: 3.2.1
>            Reporter: Trevor Pounds
>             Fix For: 2011.02
>
>
> There is a pendingMessages data structure which holds onto JMS Message object references
until the exchange is returned.  If the asynchronous exchanges are hung or delayed the pendingMessages
can grow quite large resulting in heap allocation errors if the messages are large.  A heap
dump on one of our data sets showed > 700MB of messages being referenced due to this data
structure.  As far as I can tell the JMS Message reference pulled from the map is only used
to retrieve certain JMS Message properties (getJMSReplyTo, getJMSMessageID, getJMSCorrelationID).

> Possible fixes:
> 1) On InOnly exchanges do not store the Message since the method exits without using
any of the message attributes
> 2) Store only the attributes needed for exchanges needing a reply

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message