JMS concurrent triggers creating multiple sessions on provider

,
1

When we create a JMS trigger for a queue provided by webphere MQ we see two anomalies

  1. The number of sessions on the MQ channel keeps on growing. It even exceeds the maximum concurrent setting on the JMS trigger.
  2. The sessions constantly close and open.

This is hurting MQ performance. Any ideas?

We already have the following settings set but that didn’t help
watt.server.jms.trigger.pooledConsumer.timeout=1800000
watt.server.jms.trigger.reuseSession=true

Thanks.