7 Replies Latest reply on Mar 24, 2003 2:16 PM by Adrian Brock

    JBossMQ memory issue

    AaronH Newbie

      When running Java Heap Inspector on JBoss to track down an OutOfMemory error, there were an increasing number of java.io.BufferedInputStreams and java.io.BufferedOutputStreams listed as being in memory. I tried to track down the root references of these objects, to see why they weren't being garbage collected, and found that they were being created in two main places:

      The first place was in a thread created by org.jboss.mq.il.oil.OILClientILService. Drilling down further into the references revealed: org.jboss.mq.SpyConnection, org.jboss.mq.Connection$PingTask, EDU.oswego.cs.dl.util.concurrent.ClockDaemon$TaskNode, org.jboss.mq.SpyConnection, org.jboss.mq.Connection$PingTask, and so-on in a loop.

      The second place was in a java.io.DataInputStream, created by org.jboss.mq.il.oil.OILClientIL, which was itself created by an instance of org.jboss.mq.ConnectionToken.

      Has anybody else experienced this problem with an increasing number of BufferedInputStreams and BufferedOutputStreams being created, and could they advise me of a solution?