Skip to main content

Transaction-Service Monitoring Memory Leak

5 replies [Last post]
hapi
Offline
Joined: 2012-04-04

We've got an application deployed in 3.1.2.2 that seems to leak memory but only when the Transaction Service Monitoring Level is set to High.

We don't notice memory leaking with the level set to off. The app has been combed over with JProfiler and turned up nothing definitive.

Is this a known glassfish issue? If not, what would this tend to point to?

Thanks.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
mvatkina
Offline
Joined: 2005-04-04

It is a known issue (rolled back transactions stay in monitored table), and is fixed on trunk (most probably in 3.1, if not in 3.1.1)

-marina

hapi
Offline
Joined: 2012-04-04

Thanks for the reply, but as I stated we're on 3.1.2.2 (build 5). Shouldn't we have the fix?

hapi
Offline
Joined: 2012-04-04

As I continue to dig into this, there seems to be a growing number of "active transactions" that never go away, even after the app is undeployed.

This would seem to be the memory leak. Is this a known issue?

mvatkina
Offline
Joined: 2005-04-04

No, this shouldn't happen. If you can provide a reproducible test case or a detailed scenario, please file a bug.

thanks,
-marina

hapi
Offline
Joined: 2012-04-04

I have narrowed this down further. Thread migrated to my "Timer Creating Active Transactions" thread.