[jbossts-issues] [JBoss JIRA] (JBTM-2247) Memory leak in TransactionImple

Tom Jenkinson (JIRA) issues at jboss.org
Fri Sep 5 08:19:00 EDT 2014


     [ https://issues.jboss.org/browse/JBTM-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson closed JBTM-2247.
-------------------------------
    Resolution: Rejected


Hi Sergey,

I am going to close this issue and as Mark has already suggested, I too would recommend opening a support case for your issue.

With more detail it appears as though EJB is enlisting many XAResources with the same transaction. As Mike says, we maintain the list of duplicates for spec compliance reasons. Although the EJB usage is legal it may still be possible to optimize that aspect of the system to avoid duplicate registration. I believe it registers the XAR in order to propagate certain information to remote servers in the case where the application requires that behaviour. If you are not using multiple servers it may be possible that EJB would not require its XAR registering at all.

So I do not believe this to be a bug in JBTM, hence why I have to close the issue here.

I am sure your report will assist the support engineer responsible as it was very helpful to diagnose the issue so far.

Thanks again,
Tom

> Memory leak in TransactionImple
> -------------------------------
>
>                 Key: JBTM-2247
>                 URL: https://issues.jboss.org/browse/JBTM-2247
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTA
>    Affects Versions: 4.16.2
>            Reporter: Sergey Shilin
>            Assignee: Tom Jenkinson
>            Priority: Critical
>         Attachments: OOM-jboss-1.JPG, OOM-jboss-2.JPG
>
>
> There is a problem in com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.
> HashTable _duplicateResources contains of 6 millions of objects and takes 2Gb of memory. Is there any patches or solutions for this problem?



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jbossts-issues mailing list