activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Bailey (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-3487) Topic message rollback memory leak (XA transaction)
Date Wed, 09 Nov 2011 10:27:51 GMT

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

Thomas Bailey updated AMQ-3487:
-------------------------------

    Comment: was deleted

(was: We have created the requested heap dumps, but cannot find a way to attach them to this
defect. Perhaps I do not have the required permission?)
    
> Topic message rollback memory leak (XA transaction)
> ---------------------------------------------------
>
>                 Key: AMQ-3487
>                 URL: https://issues.apache.org/jira/browse/AMQ-3487
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2, 5.6.0
>         Environment: Glassfish 3.1
>            Reporter: Thomas Bailey
>         Attachments: heapdump-after.txt, heapdump-before.txt
>
>
> We have Glassfish sending messages to an activeMQ topic using an XA Transaction. This
seems to work correctly when transactions are committing.
> However, *every* time we have a transaction rollback we have a slight memory leak from
activeMQ. After 1000 rollbacks our 1mb queue memory is full.
> The logs show:
> 2011-06-06 11:50:06,842 | DEBUG | Setting up new connection id: ID:HOTCPC8567-53061-1307352319478-0:338,
address: /127.0.0.1:56674 | org.apache.activemq.broker.TransportConnection | ActiveMQ Transport:
tcp:///127.0.0.1:56674
> 2011-06-06 11:50:06,843 | DEBUG | localhost adding consumer: ID:HOTCPC8567-53061-1307352319478-0:338:-1:102
for destination: topic://ActiveMQ.Advisory.TempQueue,topic://ActiveMQ.Advisory.TempTopic |
org.apache.activemq.broker.region.AbstractRegion | ActiveMQ Transport: tcp:///127.0.0.1:56674
> 2011-06-06 11:50:06,846 | DEBUG | XA Transaction new/begin : XID:4871251:c51600003f724564484f54435043383536372c7365727665722c5033373030:484f54435043383536372c7365727665722c50333730302c00
| org.apache.activemq.transaction.XATransaction | ActiveMQ Transport: tcp:///127.0.0.1:56674
> 2011-06-06 11:50:06,849 | DEBUG | Main:memory:topic://createBookingTopic:memory: usage
change from: 9% of available memory, to: 10% of available memory | org.apache.activemq.usage.Usage
| ActiveMQ Transport: tcp:///127.0.0.1:56674
> 2011-06-06 11:50:06,852 | DEBUG | XA Transaction rollback: XID:4871251:c51600003f724564484f54435043383536372c7365727665722c5033373030:484f54435043383536372c7365727665722c50333730302c00
| org.apache.activemq.transaction.XATransaction | ActiveMQ Transport: tcp:///127.0.0.1:56674
> 2011-06-06 11:50:06,884 | DEBUG | localhost removing consumer: ID:HOTCPC8567-53061-1307352319478-0:338:-1:102
for destination: topic://ActiveMQ.Advisory.TempQueue,topic://ActiveMQ.Advisory.TempTopic |
org.apache.activemq.broker.region.AbstractRegion | ActiveMQ Transport: tcp:///127.0.0.1:56674
> 2011-06-06 11:50:06,885 | DEBUG | remove connection id: ID:HOTCPC8567-53061-1307352319478-0:338
| org.apache.activemq.broker.TransportConnection | ActiveMQ Transport: tcp:///127.0.0.1:56674
> So no obvious issue in ActiveMQ. Also, this does not happen when we use a queue and the
transaction is rolled back.
> This is a serious problem for us as we are needing to restart activeMQ on a daily basis
to keep the production servers running.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message