-
1. Re: Fixing JMSBridge with HA connection issue
clebert.suconic Jul 18, 2013 9:04 PM (in response to gaohoward)1 of 1 people found this helpfulI'm very concerned about the CreateSessionV2 for the JMS layer. I would prefer having it fixed above that layer with retries or whatever else needed.
I'm not sure why you really would need that... Can't you just change the JMS Bridge to retry the JNDI logic or whatever else is needed?
-
2. Re: Fixing JMSBridge with HA connection issue
jbertram Jul 18, 2013 9:05 PM (in response to gaohoward)1 of 1 people found this helpfulFor HornetQ-to-HornetQ bridging shouldn't we exclusively recommend using a "core" bridge rather than a JMS bridge? How does the "core" bridge handle these scenarios?
I've always seen the JMS bridge as a way to integrate with other JMS vendors.
-
3. Re: Fixing JMSBridge with HA connection issue
gaohoward Jul 18, 2013 9:30 PM (in response to clebert.suconic)I believe there are other ways to fix that, but I just picked this CreaeSessionV2 to solve it. I agree it's not a good idea to change the core to suit JMS, I'll spend some time investigating other solutions.
-
4. Re: Fixing JMSBridge with HA connection issue
gaohoward Jul 18, 2013 9:36 PM (in response to jbertram)The core bridge is ideal for HQ-HQ bridge, and it doesn't use a Transaction manager to guarenttee once and only once. I think the JMS bridge is used for HQ-to-Other JMS provider scenario. The JMS bridge uses an external Tx manager to handle the once and only once mode, which is not as simple as the core bridges. During failover the tx needs some sort of 'failover' even if the tx is just going to be rolled back.
-
5. Re: Fixing JMSBridge with HA connection issue
clebert.suconic Jul 18, 2013 9:39 PM (in response to gaohoward)That is correct!