Consumer number for a JMS queue continues to grow

Question

          I am using WLS 7.0 SP2. I have a JMS Queue and number of consumers continues to
          grow.
          Is there any way to stop it from growing? If not, should I be concerned about
          the memory usage by those consumers?
          Thanks.
          Rick
          

Answer 1

          Tom,
          You are right on JMS resources. We found that developer didn't close JMS session
          and conneciton which caused the memory leak. Now it has being running more than
          10 hours without crashing.
          Thanks.
          Rick
          Tom Barnes <[email protected]> wrote:
          >
          >Rick Chang wrote:
          >> I am using WLS 7.0 SP2. I have a JMS Queue and number of consumers
          >continues to
          >> grow.
          >>
          >> Is there any way to stop it from growing?
          >
          >No.
          >
          >> If not, should I be concerned about
          >> the memory usage by those consumers?
          >
          >Before jumping to conclusions though, make sure
          >that you are looking at the right statistic, there
          >are three for consumer count:
          > current -- active consumer count
          > high -- highest active consumer count
          > total -- total consumers ever created
          > (ever increasing by definition)
          >
          >If you are looking at "current"
          >the statistics point to a likely memory/resource leak.
          >Perhaps some part of your application is failing to close
          >its JMS resources when it is finished with them.
          >
          >>
          >> Thanks.
          >>
          >> Rick
          >