Open daneshk opened 5 years ago
Comment by orthoxerox Wednesday Dec 05, 2018 at 22:23 GMT
Update: if I wrap the body of onMessage
in transaction
, the send operation completes, but any unhandled exceptions still do not return the message to Q1 or broker's default DLQ.
Comment by aashikam Friday Dec 07, 2018 at 09:06 GMT
Currently the Ballerina JMS module doesn't support XA transactions. We have added it to our roadmap hoping to support that by Q1 next year.
Comment by orthoxerox Friday Dec 07, 2018 at 09:43 GMT
Ah, I see, thank you. Then this page is incorrect: https://ballerina.io/learn/by-example/xa-transactions.html
Comment by orthoxerox Friday Dec 07, 2018 at 14:12 GMT
One more note: your current approach to creating JMS connections cannot obtain an XA connection from IBM MQXAConnectionFactory, as it returns an MQConnection from createConnection()
and returns an MQXAConnection only from createXAConnection()
.
Comment by anupama-pathirage Tuesday Dec 11, 2018 at 13:34 GMT
Created https://github.com/ballerina-platform/ballerina-lang/issues/12712 to track the documentation issue.
Issue by orthoxerox Wednesday Dec 05, 2018 at 12:04 GMT Originally opened as https://github.com/ballerina-platform/ballerina-lang/issues/12517
Description: See gist.
If I change
connectionFactoryName
to"ConnectionFactory"
, the message is still not sent, but at least I get it back in Q1 when the service is killed.I can change
acknowledgementMode
to"AUTO_ACKNOWLEDGE"
and the message is delivered to Q2, but I need cross-broker XA support in production.Steps to reproduce:
ballerina run -e b7a.log.level=TRACE bridge.bal
Affected Versions:
Ballerina 0.983.0
OS, DB, other environment details and versions: