I am migrating EJB application from websphere 9.0 to Liberty. I am using the application server migration utility to help me with the migration. One of the listed issue is:
JMS sessions in general will work in Liberty. However, transacted JMS sessions won't work. Therefore, applications using transacted JMS sessions which are ported to Liberty will not work as expected.
A transacted JMS session allows a client to collect different JMS operations (e.g. sending and consuming messages) into a single unit of work that is committed or rolled back atomically.
To be clear, a transacted JMS session uses what is sometimes called a "local" transaction because the transaction only applies to the specific JMS session involved. This is in contrast to a "global" transaction (sometimes called a "JTA" or "XA" transaction) which can involve many different kinds of resources (e.g. JMS, JDBC, etc.) and whose commit and roll-back is atomic across all those resources.