[
http://jira.jboss.com/jira/browse/JBMESSAGING-843?page=all ]
Ovidiu Feodorov updated JBMESSAGING-843:
----------------------------------------
Description:
Needed by MDB containers.
An MDB creates several connections during its deployment. If using a load-balancing
clustered ConnectionFactory, they'll end up on different cluster nodes, which is
precisely what the MDB container doesn't need. On the other hand, if using a
"dumb" non-clustered ConnectionFactory, the MDB container doesn't benefit
from the cluster failover capabilities. A clustered ConnectionFactory with no load
balancing, but failover capabilities is needed.
was:
Needed by the MDB containers.
An MDB creates several connections during its deployment. If using a load-balancing
clustered ConnectionFactory, they'll end up on different cluster nodes, which is
precisely what the MDB container doesn't need. On the other hand, if using a
"dumb" non-clustered ConnectionFactory, the MDB container doesn't benefit
from the cluster failover capabilities. A clustered ConnectionFactory with no load
balancing, but failover capabilities is needed.
Clustered ConnectionFactory with no load balancing, but failover
capabilities needed
------------------------------------------------------------------------------------
Key: JBMESSAGING-843
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-843
Project: JBoss Messaging
Issue Type: Feature Request
Components: AS Integration
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.CR2
Needed by MDB containers.
An MDB creates several connections during its deployment. If using a load-balancing
clustered ConnectionFactory, they'll end up on different cluster nodes, which is
precisely what the MDB container doesn't need. On the other hand, if using a
"dumb" non-clustered ConnectionFactory, the MDB container doesn't benefit
from the cluster failover capabilities. A clustered ConnectionFactory with no load
balancing, but failover capabilities is needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira