Clebert - Thank you for your input!
I try and avoid XA transactions whenever possible as well. I do have a few customers that insist on transactions when they do JMS->JMS routes (the JMS destination are in different brokers/servers - hence the need for XA). This is really the last piece I need to figure out before I’ll be able to implement Artemis (core only) into our standard flows. I know we can always use the JMS layer, but I’d like to be able to use just the core if I can. I’m planning on doing the integration in Camel, and it’s looking more and more like I’ll need an “artemis-camel” (hosted in the Artemis source) or a “camel-artemis” (hosted in the Camel Components source). Any thoughts on which would be the most appropriate place for the component? ActiveMQ 5.x has the activemq-camel component, but it always seemed to me it was in the wrong place - that it should be camel-activemq. > On Oct 18, 2016, at 10:08 AM, Clebert Suconic <clebert.suco...@gmail.com> > wrote: > > Most of the usecases around XA are around an application server, and > hence around MDBs, And JMS. > > ClientSession extends XAResource so you should be able to use / enlist > on a Transaction Manager, or if you really wanted (I'm not advising > you) you could play the TransactionManager on some fakes (for tests > maybe). > > > I always advise people to use messaging for fast services as much as > possible. Transactions will introduce a point of sync and you will be > using your messaging system pretty much as a database. if you really > need that at least try to batch your transactions so you can scale > without requiring many servers to support your load. > > On Tue, Oct 18, 2016 at 11:06 AM, Quinn Stevenson > <qu...@pronoia-solutions.com> wrote: >> Is there an example of using the Artemis Core APIs with XA? It appears that >> all of the XA examples use JMS. Am I missing something? >> >> >> > > > > -- > Clebert Suconic