3 Replies Latest reply on Oct 8, 2013 4:23 PM by aqtwrdnr aqtwrdnr

    Can someone explain why a pooled-connection-factory is used to consume messages, while the documentation says it should only be used to produce messages?

    aqtwrdnr aqtwrdnr Newbie

      Hello,

       

      I am working on a Message Driven Bean server application (no clients and all in the same JVM) and have a question about the default configuration of messaging and message driven beans in JBoss 7.2.0.Final. In the JBoss documentation it says (my bold):

       

      A pooled-connection-factory referencing an in-vm-connector is suitable to be used by a local client only to send messages to a local server.

       

      While in standalone-full.xml it is configuring the pooled-connection-factory on message driven beans which consume messages:

       

      <mdb>

          <resource-adapter-ref resource-adapter-name="hornetq-ra"/>

          <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>

      </mdb>

       

      The resource-adapter-ref refers to the following pooled-connection-factory:

       

      <pooled-connection-factory name="hornetq-ra">

          <transaction mode="xa"/>

          <connectors>

              <connector-ref connector-name="in-vm"/>

          </connectors>

          <entries>

              <entry name="java:/JmsXA"/>

          </entries>

      </pooled-connection-factory>

       

      Can someone explain why a pooled-connection-factory is used to consume messages, while the documentation says it should only be used to produce messages?

       

      Thanks in advance,

       

      Barry NL