gastaldi
commented
1 year ago Actually that's not an IronJacamar issue, but a transaction question. Being discussed in https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/jms.20with.20quarkus-jca
I did some more tests. I am assuming non xa behavior, and it behaves as if it was supporting it. specifically those tests should fail (and do not):
there should be an error saying that you can't enlist 2 non-xa resource managers in the same tx if there is no error, it is either:
it is probably one of the last 2 situations. if so we should have the tx logs somewhere (e.g.
data\tx-object-store) and a recovery manager?? and that would make the application stateful. we need to investigate that. the default behavior for quarkus should assume the app to be stateless (12 factors, microservice, ...)Originally posted by @vsevel in https://github.com/quarkiverse/quarkus-ironjacamar/issues/25#issuecomment-1705939888