[
https://issues.apache.org/activemq/browse/CAMEL-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63139#action_63139
]
Claus Ibsen commented on CAMEL-3236:
------------------------------------
We are getting closer
I get some timestamp errors still
{code}
org.junit.ComparisonFailure:
Expected :1262878215000
Actual :1262856615000
at org.junit.Assert.assertEquals(Assert.java:123)
at org.junit.Assert.assertEquals(Assert.java:145)
at
org.apache.camel.component.jmx.SimpleBeanFixture.assertMessageReceived(SimpleBeanFixture.java:288)
at
org.apache.camel.component.jmx.JMXConsumerTest.waitAndAssertMessageReceived(JMXConsumerTest.java:94)
at
org.apache.camel.component.jmx.JMXConsumerTest.attributeChange(JMXConsumerTest.java:44)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
{code}
All 7 tests fail on JMXConsumerTest on both JDK 1.5 and 1.6.
And the change to pom.xml was not needed as camel-core will bring in the JAXB
stuff if on JDK 1.5. I got some maven activation for that.
I will apply the patch but keep the JMXConsumerTest at @Ignore
> Camel JMX Component
> -------------------
>
> Key: CAMEL-3236
> URL: https://issues.apache.org/activemq/browse/CAMEL-3236
> Project: Apache Camel
> Issue Type: New Feature
> Components: jmx
> Reporter: Tracy Snell
> Assignee: Claus Ibsen
> Fix For: 2.6.0
>
> Attachments: camel-jmx-patch.txt, camel-jmx-timestamp.txt,
> camel-jmx-tstamp-jdk15.txt
>
>
> Mark Ford is donating his Camel-JMX component. Providing a Jira for the code
> to be submitted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
