[jbossts-issues] [JBoss JIRA] (JBTM-1936) Cannot start managed container after JMX upgrade

Gytis Trikleris (JIRA) jira-events at lists.jboss.org
Wed Sep 25 10:18:02 EDT 2013


     [ https://issues.jboss.org/browse/JBTM-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gytis Trikleris updated JBTM-1936:
----------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/jbosstm/narayana/pull/458

    
> 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