activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Santos (JIRA)" <>
Subject [jira] Updated: (AMQ-2556) Memory leaks with XA Transactions (case of read-only transactions)
Date Mon, 04 Jan 2010 14:20:15 GMT


Daniel Santos updated AMQ-2556:


1- Launch a broker
2- Launch this ready to use app (consumer in a XA transaction, implemented as a Spring's MessageListenner.
The config is taken from atomikos

No producer nor another XAResource is needed to show the problem

Simply use a debugger, (j)visualvm, jmap/jhat or another memory profiler tool to see grow
up indefinitly (at each receiveTimeout unit of time : 3s) the number of TransactionContext
instances on client and TransactionState instances on broker

> Memory leaks with XA Transactions (case of read-only transactions)
> ------------------------------------------------------------------
>                 Key: AMQ-2556
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.1.0, 5.2.0, 5.3.0
>         Environment: ActiveMQ 5.3.0
> Atomikos Transactions Essentials 3.5.8
> Spring 2.5.6
> Oracle 11g (thin driver version
>            Reporter: Daniel Santos
>         Attachments:
> Some transaction related information are not released in case of read-only transactions
(where not messages have been consumed or produced) by broker and client, that causes an OutOfMemory
after running some time.
> Fields that hold these "transaction related information" are (at least) :
> - {{org.apache.activemq.state.ConnectionState.transactions}}
> - {{org.apache.activemq.TransactionContext.ENDED_XA_TRANSACTION_CONTEXTS}}
> After serach, it seems that the case of read-only XA transactions (that terminates at
prepare time) has been missed in some code like :
> - {{}} that puts TransactionState in {{org.apache.activemq.state.ConnectionState.transactions}}
at the beginning, release them at commit (or rollback) time *but not at prepare time where
result is {{XAResource.XA_RDONLY}}*
> - {{org.apache.activemq.TransactionContext}} that do the same mistake via ENDED_XA_TRANSACTION_CONTEXTS
in prepare()
> _Note that the case of read-only transactions seems correctly done by {{org.apache.activemq.transaction.XATransaction}}
(very interesting comment here

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message