Open glassfishrobot opened 10 years ago
@glassfishrobot Commented Reported by genomeprjct
@glassfishrobot Commented @nigeldeakin said: I wrote an explanation of why this was not permitted in JMS 2.0 in the JMS 2.0 Reasons FAQ. The main difficulty was in getting an async message send to participate correctly in an XA transaction. It's worth revisiting this to see if these issues can be overcome.
@glassfishrobot Commented @nigeldeakin said: Adding to the list of issues to be considered for JMS 2.1 and tagging accordingly.
@glassfishrobot Commented This issue was imported from java.net JIRA JMS_SPEC-145
Currently, we explicitly disallow the execution of async message sending in an application server.
I believe we can allow it by leveraging the Java EE concurrency utilities. The sending of a message this way can be done using a call wrapped inside of a ManagedExecutorService.
Affected Versions
[2.0]