activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SuoNayi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-4311) Large transaction that contains lots of penging messages can cause OOM
Date Tue, 12 Feb 2013 05:15:12 GMT

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

SuoNayi updated AMQ-4311:
-------------------------

    Description: 
Currently MemoryTransactionStore is used to hold pending messages in a transaction.
More pending messages in a transaction more memory is consumed.
Because the message size of pending messages is not counted in usage limit before they are
committed so PFC wont block producers as well and large transaction will cause broker throws
OOM at last.
Spooling pending messages in the transaction to the disk is one of solution.

  was:
Currently MemoryTransactionStore is used to hold pending messages in a transaction.
More pending messages in a transaction more memory is consumed.
Because the message size of pending messages is not counted in usage limit before they are
committed so PFC wont block producers as well and large transaction will cause broker throws
OOM at last.


    
> Large transaction that contains lots of penging messages can cause OOM
> ----------------------------------------------------------------------
>
>                 Key: AMQ-4311
>                 URL: https://issues.apache.org/jira/browse/AMQ-4311
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker, Message Store
>    Affects Versions: 5.x
>            Reporter: SuoNayi
>             Fix For: 5.9.0
>
>
> Currently MemoryTransactionStore is used to hold pending messages in a transaction.
> More pending messages in a transaction more memory is consumed.
> Because the message size of pending messages is not counted in usage limit before they
are committed so PFC wont block producers as well and large transaction will cause broker
throws OOM at last.
> Spooling pending messages in the transaction to the disk is one of solution.

--
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

Mime
View raw message