AnsweredAssumed Answered

Leak Hunter issues with JVM heap Size

Question asked by NikhilKotagiri on Apr 7, 2010
Latest reply on Nov 18, 2010 by mparikh
Hello all,    I need a small clarification on the below issue.    We enabled Leak hunter in one of our applications. When we enabled leak hunter the application is not working it’s throwing some errors every time and as soon as after disabling leak hunter the application is working fine with out any errors.  We are running this application on Web logic server 10 , in order to trouble shoot the issue we increased the heap of the JVM from 2 GB to 3 GB , with 3 GB of heap and enabling   leak hunter it’s is working fine but after some time it’s showing the same behavior. And we are getting some error messages in the Application server logs about the leak hunter.    4/06/10 02:59:12 PM MST [DEBUG] [IntroscopeAgent] NullPointerException while calling size(), will skip current class on this pass
java.lang.NullPointerException
              at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.initSessionInfo(ServletRequestImpl.java:2314)
              at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInternal(ServletRequestImpl.java:2089)
              at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(ServletRequestImpl.java:2079)
              at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1211)
              at weblogic.servlet.jsp.PageContextImpl.getAttributeNamesInScope(PageContextImpl.java:376)
              at javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects$3.enumerateKeys(ImplicitObjectELResolver.java:812)
              at javax.servlet.jsp.el.ImplicitObjectELResolver$EnumeratedMap.convertToMap(ImplicitObjectELResolver.java:1223)
              at javax.servlet.jsp.el.ImplicitObjectELResolver$EnumeratedMap.getAsMap(ImplicitObjectELResolver.java:1207)
              at javax.servlet.jsp.el.ImplicitObjectELResolver$EnumeratedMap.size(ImplicitObjectELResolver.java:1162)
              at com.wily.introscope.agent.leakhunter.TrackedMapReference.getTrackedObjectSize(TrackedMapReference.java:36)
              at com.wily.introscope.agent.leakhunter.ATrackedLeakReference.ITrackedLeakReference_checkForLeak(ATrackedLeakReference.java:249)
              at com.wily.introscope.agent.leakhunter.PotentialLeakTracker.checkTrackedLeakReference(PotentialLeakTracker.java:273)
              at com.wily.introscope.agent.leakhunter.PotentialLeakTracker.checkTrackedLeakReferences(PotentialLeakTracker.java:229)
              at com.wily.introscope.agent.leakhunter.PotentialLeakTracker.access$200(PotentialLeakTracker.java:26)
              at com.wily.introscope.agent.leakhunter.PotentialLeakTracker$PotentialLeakPoller.ITimestampedRunnable_execute(PotentialLeakTracker.java:381)
              at com.wily.util.heartbeat.IntervalHeartbeat$BehaviorNode.execute(IntervalHeartbeat.java:944)
              at com.wily.util.heartbeat.IntervalHeartbeat.executeNextBehaviorAndCalculateSleepTime(IntervalHeartbeat.java:489)
              at com.wily.util.heartbeat.IntervalHeartbeat.access$300(IntervalHeartbeat.java:28)
              at com.wily.util.heartbeat.IntervalHeartbeat$HeartbeatRunnable.run(IntervalHeartbeat.java:665)
              at java.lang.Thread.run(Thread.java:595)  We are running wily agents on 8.2.2 version and we enable the below property in IntroscopeAgent.profile.  introscope.agent.reduceAgentMemoryOverhead=true        Thanks,Nikhil  

Outcomes