[
https://issues.jboss.org/browse/JBTM-1936?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1936:
--------------------------------
Priority: Critical (was: Major)
Cannot start managed container after JMX upgrade
------------------------------------------------
Key: JBTM-1936
URL:
https://issues.jboss.org/browse/JBTM-1936
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Priority: Critical
Fix For: 5.0.0.M5
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/TESTS=MAIN,jdk=jd...
http://172.17.131.2/view/Narayana+BlackTie/job/narayana/264/TESTS=XTS,jdk...
Based on [~paul.robinson] research, this was caused by
https://github.com/wildfly/wildfly/commit/c400b512be5fae6c02ef0a11886ac77...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira