This content has been marked as final. Show 1 reply
I read in the Jboss wiki that this exception is related to a stroy with distributed commits to be performed, and the coordination in order to have all nodes that commit or not.
Yes, this is telling you that you won't get transactional semantics guaranteed in the presence of failures. It's a polite way of suggesting you fix this.
In the exception message they talk about a risk for an inconsistent data, so I want to check that I understood well:
This is dangerous only in case we have failures in our application, so in case everything is fine and works well, we don't have to worry about this warning. And if we have some failure, we have to expect having what they call "inconsistent data" in the future.
Yes. That's why we recommedn that you only use one 1-phase aware participant in a transaction and use the Last Resource Commit Optimization.