This content has been marked as final. Show 1 reply
I think you have a few options:
- Suspend the XA transaction before calling send and then resume it just after:
- Put the "send()" call in a separate stateless EJB method that's annotated with TransactionAttributeType.NOT_SUPPORTED. (I think this particular annotation causes a suspend/resume.)
- Configure and use a custom WL JMS connection factory that has "XA enabled" set to false. Any JMS producer or consumers that are created with this CF will not participate in XA transactions.