[WFLY-3159] Upgrade Generic JMS RA to 1.0.3.Final #6085
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* upgrade generic JMS RA to 1.0.3.Final * add config property TransactionSynchronizationRegistryLookup in the ra.xml file of the org.jboss.generic.jms module to lookup WildFly transaction synchronization registry. The registry will be used by the RA to determine whether there is an active transaction when JMS session are created. If that's the case, session creation parameters are ignore and the JMS session will always be transacted. JIRA: https://issues.jboss.org/browse/WFLY-3159
|
Build 3066 is now running using a merge of 35d8f30 |
|
Build 3066 outcome was SUCCESS using a merge of 35d8f30 |
kabir
added a commit
that referenced
this pull request
Mar 25, 2014
…_1.0.3.Final [WFLY-3159] Upgrade Generic JMS RA to 1.0.3.Final
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ra.xml file of the org.jboss.generic.jms module to lookup WildFly
transaction synchronization registry. The registry will be used by the
RA to determine whether there is an active transaction when JMS
session are created. If that's the case, session creation parameters are
ignore and the JMS session will always be transacted.
JIRA: https://issues.jboss.org/browse/WFLY-3159