camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-3236) Camel JMX Component
Date Sat, 06 Nov 2010 18:06:00 GMT


Claus Ibsen commented on CAMEL-3236:

We are getting closer

I get some timestamp errors still

Expected :1262878215000
Actual   :1262856615000
	at org.junit.Assert.assertEquals(
	at org.junit.Assert.assertEquals(
	at org.apache.camel.component.jmx.SimpleBeanFixture.assertMessageReceived(
	at org.apache.camel.component.jmx.JMXConsumerTest.waitAndAssertMessageReceived(
	at org.apache.camel.component.jmx.JMXConsumerTest.attributeChange(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(

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:
>             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.

View raw message