Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final)
Affects Version/s: 7.1.1.Final, 7.1.2.Final (EAP)
Component/s: EJB
Labels:
None

Steps to Reproduce:

Hide

set up 2 JBoss clusters, connect them as described in https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance,
run a few thousand transaction across the clusters

Show
set up 2 JBoss clusters, connect them as described in https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance , run a few thousand transaction across the clusters
Git Pull Request:
https://github.com/jbossas/jboss-as/pull/2532, https://github.com/jbossas/jboss-as/pull/2533

Description

When running distributed transaction over multiple clusters, memory is depleted in a matter of minutes.

We are using EJB's without transaction annotations (default behavior) and remoting as described in
https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance.

Heap dumps are available at http://people.cs.kuleuven.be/~bart.vanbrabant/jboss_dump/.

The IBM heap analyzer blames org/jboss/as/ejb3/remote/EJBRemoteTransactionsRepository as the root cause, taking up 95.73% of memory, through the transaction map.

If more info is required, I can provided our test application.

Thanks,
Wouter

Attachments

Activity

People

Assignee:: Jaikiran Pai (Inactive)

Reporter:: Wouter De Borger (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 2012/06/06 10:48 AM

Updated:: 2012/06/21 2:43 AM

Resolved:: 2012/06/21 2:43 AM