[
https://issues.apache.org/jira/browse/SM-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krzysztof Sobkowiak resolved SM-2538.
-------------------------------------
Resolution: Fixed
> JMSAppenderTest fails on Jenkins
> --------------------------------
>
> Key: SM-2538
> URL: https://issues.apache.org/jira/browse/SM-2538
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 5.4.1
> Reporter: Krzysztof Sobkowiak
> Assignee: Krzysztof Sobkowiak
> Fix For: 5.4.1, 5.5.0
>
>
> The last Jenkins builds for {{servicemix-5.4.x}} fail with following error
> {code}
> [org.apache.camel.test.junit4.CamelTestSupport] : tearDownAfterClass test
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.103 sec <<<
> FAILURE! - in org.apache.servicemix.logging.jms.JMSAppenderTest
> org.apache.servicemix.logging.jms.JMSAppenderTest Time elapsed: 0.103 sec
> <<< ERROR!
> java.lang.NoSuchMethodError:
> org.apache.activemq.thread.TaskRunnerFactory.setThreadClassLoader(Ljava/lang/ClassLoader;)V
> at
> org.apache.activemq.broker.BrokerService.getTaskRunnerFactory(BrokerService.java:1214)
> at
> org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:2255)
> at
> org.apache.activemq.broker.BrokerService.createBroker(BrokerService.java:2214)
> at
> org.apache.activemq.broker.BrokerService.getBroker(BrokerService.java:967)
> at
> org.apache.activemq.broker.BrokerService.getAdminConnectionContext(BrokerService.java:2485)
> at
> org.apache.activemq.broker.BrokerService.startVirtualConsumerDestinations(BrokerService.java:2625)
> at
> org.apache.activemq.broker.BrokerService.startDestinations(BrokerService.java:2476)
> at
> org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:678)
> at
> org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:670)
> at
> org.apache.activemq.broker.BrokerService.start(BrokerService.java:606)
> at
> org.apache.servicemix.logging.jms.JMSAppenderTest.setupBroker(JMSAppenderTest.java:45)
> {code}
> I cannot reproduce this problem on my local machine
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
