[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-843) Clustered ConnectionFactory with no load balancing, but failover capabilities needed
[ http://jira.jboss.com/jira/browse/JBMESSAGING-843?page=all ]
Tim Fox updated JBMESSAGING-843:
--------------------------------
Fix Version/s: 1.2.0.SP2
(was: 1.2.1.CR1)
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046775#...
Assignee: Tim Fox
This is a major issue.
Both the old JMSContainerInvoker and JCA infflow create 3 connections per MDB:
1) For DLQ handler
2) For connection consumer
3) For MDB session
problem is 2) and 3) will be created on different servers if load balancing is enabled
The JMSContainerInvoker and JCA inflow should use the same connection for 2) and 3)
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: Tim Fox
Fix For: 1.2.0.SP2
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