[jbossts-issues] [JBoss JIRA] (JBTM-1936) Cannot start managed container after JMX upgrade
Tom Jenkinson (JIRA)
jira-events at lists.jboss.org
Thu Sep 19 10:58:03 EDT 2013
[ https://issues.jboss.org/browse/JBTM-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805855#comment-12805855 ]
Tom Jenkinson commented on JBTM-1936:
-------------------------------------
Elevating to critical as it would impact M5 release
> 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=jdk7.latest,label=linux/264/consoleText
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/264/TESTS=XTS,jdk=jdk7.latest,label=linux/consoleText
> Based on [~paul.robinson] research, this was caused by https://github.com/wildfly/wildfly/commit/c400b512be5fae6c02ef0a11886ac7701835b550
--
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
More information about the jbossts-issues
mailing list