4 Replies Latest reply on Apr 27, 2017 9:11 AM by Carl Ellam-speed

    Unexpected behaviour with JBoss 6.3 and WebSphere MQ 8.0 Adapter

    Carl Ellam-speed Newbie

      Good morning, can anyone help me?

       

      I'm working for a client that has JBoss EAP 6.3 implemented, communicating with MQ 8.0 using the MQ Resource Adapter. MDB's are configured:

       

      @ResourceAdapter("wmq.jmsra.rar")
      @DependsOn("stc.instation:service=SystemStartUpTime")
      @MessageDriven(name = "ConnectedPartyTca1Listener", activationConfig = {
              @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
              @ActivationConfigProperty(propertyName = "destination", propertyValue = "QL.CPARTIES_TCA1"),
              @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"),
              @ActivationConfigProperty(propertyName = "hostName", propertyValue = "${cp.hostName}"),
              @ActivationConfigProperty(propertyName = "queueManager", propertyValue = "${cp.queueManager}"),        
              @ActivationConfigProperty(propertyName = "port", propertyValue = "${cp.port}"),
              @ActivationConfigProperty(propertyName = "channel", propertyValue = "${cp.tca1.channel}"),        
              @ActivationConfigProperty(propertyName = "maxPoolDepth", propertyValue = "${cp.tca1.maxPoolDepth}")})
      

       

      Where maxPoolDepth is set to limit the number maximum number of MDB's that are started by the thread pool. (EDIT: Where we default maxPoolDepth to 15)

       

      What we observe when the system is running is this:

       

      • MQ Reports there are 16 open consumers in the MQ Client window, not 15 as expected
      • Logging inside the EJB's show that 15 of them execute correctly and the unexpected 16th also tries to run, but is triggering a JMSCC0108 error, i.e. the browsed with mark message from MQ is not allocated (or has been correctly timed out)

       

      Is this normal behaivour? For each MDB, we always get "+1" MDB's in the JBoss container and connected to MQ (client window), when there are enough messages on the queue and threads are available.

       

      My client needs certainty of the number of MDB's running, due to their logic design.

       

      Is there a setting or advice we should consider?

       

      One small extra piece of information is the fact the client is currently using the MQ Resource Adapter 7.0.1.12-k701-112-140319. I've been informed that they tried v8 of the adapter, but things went horribly wrong (I've yet to find out what/why). Could this be the cause?

       

      Any help would be REALLY appreciated.

       

      Kind regards

       

      Carl