Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy cant Jboss AS 7.1 with Hornet Que - Message Driven Bean use pooled connection?
    text
    copied!<p>We are trying using HornetQ for messaging on Jboss AS 7.1 and the documentation at </p> <p><a href="https://docs.jboss.org/author/display/AS71/Messaging+configuration" rel="nofollow">https://docs.jboss.org/author/display/AS71/Messaging+configuration</a> says </p> <p>There is also a pooled-connection-factory which is special in that it leverages the outbound adapter of the HornetQ JCA Resource Adapter. It is also special because:</p> <pre><code>* It is only available to local clients, although it can be configured to point to a remote server. * As the name suggests, it is pooled and therefore provides superior performance to the clients which are able to use it. The pool size can be configured via the max-pool-size and min-pool-size attributes. * It should only be used to send (i.e. produce) messages. * It can be configured to use specific security credentials via the user and password attributes. This is useful if the remote server to which it is pointing is secured. </code></pre> <p>Every thing made sense except the third bullet which says</p> <p><strong>* It should only be used to send (i.e. produce) messages.</strong></p> <p>My mdb uses Pooled connection factory and is consuming messages (Not sending). </p> <p>My understanding is Pooled connection factory is what the MDB should use for better performance. Also the hornetq Author's say </p> <p><a href="http://hornetq.blogspot.com/2011/06/hornetq-on-jboss-as7.html" rel="nofollow">http://hornetq.blogspot.com/2011/06/hornetq-on-jboss-as7.html</a></p> <pre><code> The pooled connection factories also define the incoming connection factory for MDB's, the name of the connection factory refers to the resource adapter name used by the MDB, </code></pre> <p>Can some guru's throw some light on this ?</p> <p>Thanks Rama</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload