Howard, please try to add
registry.shutdown();
to the end of TestPerformanceMonitorFactory#testIntegration.
I can't quite explain it, but it seems, that the test is executed
twice, and on the second run there are still existing some registered
mbeans from the first run.
Moreover I noticed that the sun jmx implementation is used
instead of mx4j. This may point to some differences in the classpath.
Achim
Am Sun, 19 Mar 2006 19:16:25 +0100 schrieb Howard Lewis Ship
<[EMAIL PROTECTED]>:
It's coming along very nicely; I'll have stuff checked in shortly.
For the moment, I'm having one problem, in the JMX area, that I'm not
familiar with.
Things are working well inside Eclipse, but the Maven build fails on
just one test for JMX:
Anyone have any clues on this? I'm at a loss ... some aspect of
runtime code, classpath, lifecycle, or something must differ between
Eclipse build and Maven build.
I'm off to update the .classpath to match what Maven uses, see if that
helps.
Here's the error report:
-------------------------------------------------------------------------------
Battery: org.apache.hivemind.management.TestPerformanceMonitorFactory
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.57 sec
testIntegration(org.apache.hivemind.management.TestPerformanceMonitorFactory)
Time elapsed: 0.57 sec <<< ERROR!
[ stdout ]
---------------------------------------------------------------
[ stderr ]
---------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
