JMS / MBean WL7 bug - Weblogic

This is a discussion on JMS / MBean WL7 bug - Weblogic ; Hi, We have a message driven bean with a configured max pool size of 8 and min pool size of one. The message driven bean is heavily used. When viewing active JMS destinations, the JMS queue has 8 consumers which ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: JMS / MBean WL7 bug

  1. JMS / MBean WL7 bug


    Hi,

    We have a message driven bean with a configured max pool size of 8 and min pool
    size of one. The message driven bean is heavily used. When viewing active JMS
    destinations, the JMS queue has 8 consumers which is correct However, when we
    pull the stats from the mbeans regarding the idle count and in_use count of the
    message driven bean it starts off correct as 8 in_use and 0 idle . After some
    time the figure changes and is now at 386 (idle) and -83 (in use).

    Kevin

  2. Re: JMS / MBean WL7 bug

    I agree. I suggest reporting this to customer support.

    Tom

    Kevin Sharfman wrote:
    > Hi,
    >
    > We have a message driven bean with a configured max pool size of 8 and min pool
    > size of one. The message driven bean is heavily used. When viewing active JMS
    > destinations, the JMS queue has 8 consumers which is correct However, when we
    > pull the stats from the mbeans regarding the idle count and in_use count of the
    > message driven bean it starts off correct as 8 in_use and 0 idle . After some
    > time the figure changes and is now at 386 (idle) and -83 (in use).
    >
    > Kevin



+ Reply to Thread