Facing a memory leak issue due to internal weblogic objects?

This is the internal WL class for an XA-enabled persistent store. If you are using JDBC then check if your DB is full. If you are using the default store, or a file store, check your filesystem for errors or to see if its full.

Up vote 2 down vote favorite share g+ share fb share tw.

I have an app running on Weblogic 10 app server. I am facing a memory leak issue due to internal weblogic objects. The following class objects are occupying a lot of memory and not clearing it off.

Can anyone help me figure out what these classes are meant for and what possible could be causing the leak? Googling didn't help much. Weblogic.store.xa.internal.

PersistentStoreXAImpl Thanks, Sid java memory memory-leaks weblogic link|improve this question asked Apr 25 '11 at 20:41SidCool856317 90% accept rate.

This is the internal WL class for an XA-enabled persistent store. If you are using JDBC then check if your DB is full. If you are using the default store, or a file store, check your filesystem for errors or to see if its full.

There should not be very many of these. Are you using JMS in your app? Perhaps you also have a configuration issue.

Try opening a ticket with Oracle support, or if you can share the code and configuration with me you can email me at Jeffrey. West@oracle.com. If you have a support contract you should open a case as opposed to emailing me.

If you open a case, please email me the SR# and I can look into it. If you don't have a support contract then email me with the details of your problem...

We don't have a support contract with Oracle. Could you tell me how to know if there were errors in the file system? Also, there is no code that is giving error, it's the heap dump that is showing this class as occupying 32% memory.

– SidCool Apr 25 '11 at 21:37 1 What version of WLS are you using, and on what operating system? – Jeff West Apr 26 '11 at 15:44 We are using Weblogic 10.3 on a Linux machine. – SidCool Apr 26 '11 at 16:29.

To add to Jeff's answer, This is the persistent store used by Weblogic for various subsytems such as JMS, JTA and even Web services and EJB timers If you have not configured this in your instance, it usually should default to a Filestore located at bea_home\user_projects\domains\domain-name\servers\server-name\data\store\default So you could check for file system disk space issues there. If you can afford to shut down your Weblogic, can you clear out the file system above - or check how old the objects persisted there are?

XA" usually means "two-phase commit" to me. I think this is a JDBC driver for two-phase commit to a persistent store. I can't understand why these wouldn't be cleaned up.

How are you looking at the heap. What tool is telling you that this is the source of the leak? Could it be that your classes aren't cleaning up persistent resources?

I am using the heap dump extracted from the Weblogic server at an instance when the heap usage was 87%. I am using Eclipse Memory Analyzer Tool to analyze the heap dump. When you say persistent resources, isn't it something related to database?

I am sorry, I am not very well versed with Weblogic. Also, how is the file store loaded in the web application context? – SidCool Apr 25 '11 at 21:35.

We had seen a similar problem once, when JDBC profiler was enabled. Do you have any profiling enabled either on application or WebLogic level?

Yes, we are using Eclipe's Memory Analyzer Tool (MAT) – SidCool May 10 '11 at 21:32.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.