Menu
▾
▴
Re: [Springframework-developer] FAILED BUILD: x86-linux2 (last 30 lines included)
|
From: Mark St G. <stg...@ca...> - 2005-03-18 21:22:09
|
Hey Rob,
Dont know if you fixed the tests.... however from what I can tell it looks
like the object "bean:name=proxyTestBean1" is
being registered ... then unregistered from the MBeanServer...
I put some debugging in MBeanExporter and I see it being registered ..
.then unregisterBeans() is called ...
.. hence the InstanceNotFoundException?
[junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,04 sec
[junit] ------------- Standard Output ---------------
[junit] MJS: Registering Bean instance [bean:name=proxyTestBean1]
[junit] MJS: Unregistering beans...
[junit] MJS: [bean:name=proxyTestBean1]
[junit] MJS: Registering Bean instance [bean:name=proxyTestBean1]
[junit] MJS: Unregistering beans!
[junit] MJS: [bean:name=proxyTestBean1]
[junit] ------------- ---------------- ---------------
[junit] Testcase: testPropertiesReplaced took 0,02 sec
[junit] Testcase: testPropertiesCorrectInJmx took 0,01 sec
[junit] Caused an ERROR
[junit] bean:name=proxyTestBean1
[junit] javax.management.InstanceNotFoundException:
bean:name=proxyTestBean1
. . .
Anyway thats just what I see...
Cheers
Mark
Rob Harrop
<robh@cakesolutio
ns.net> To
Sent by: spr...@li...
springframework-d rceforge.net
eveloper-admin@li cc
sts.sourceforge.n
et Subject
Re: [Springframework-developer]
FAILED BUILD: x86-linux2 (last 30
03/18/2005 12:58 lines included)
PM
Please respond to
springframework-d
eveloper
Did you check out from public CVS - I guess you did? I'll try that and
do some more investigation.
Rob
Mark St Godard wrote:
>
>
>Rob,
>
>I just did a fresh cvs co, build and test... and it fails the same way...
>
>
>
>> [junit] Testcase: testPropertiesCorrectInJmx took 0,031 sec
>> [junit] Caused an ERROR
>> [junit] bean:name=proxyTestBean1
>> [junit] javax.management.InstanceNotFoundException:
>>
>>
>bean:name=proxyTestBean1
>
>
>> [junit] at
>>
>>
>com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1015)
>
>
>
>> [junit] at
>>
>>
>com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:634)
>
>
>
>You are working on the JMX stuff no? Seems odd that it would work for
you.
>Some residual configs laying around?
>Very odd.
>
>Cheers
>Mark
>
>
>
>
> Rob Harrop
> <robh@cakesolutio
> ns.net> To
> Sent by: spr...@li...
> springframework-d rceforge.net
> eveloper-admin@li cc
> sts.sourceforge.n
> et Subject
> Re: [Springframework-developer]
> FAILED BUILD: x86-linux2 (last 30
> 03/18/2005 12:44 lines included)
> PM
>
>
> Please respond to
> springframework-d
> eveloper
>
>
>
>
>
>
>So I did two fresh checkout/build/test phases on my Windows machine and
>on my Mac and I cannot get that test to fail - someone please shoot me :).
>
>Can someone else try a completely fresh checkout/test cycle.
>
>Interestingly, on my machines the Caucho remoting tests hang and do not
>complete at all.
>
>Rob
>
>Darren Davison wrote:
>
>
>
>>1111170364
>>FAILED
>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,069 sec
>> [junit] Testsuite:
>>
>>
>org.springframework.jmx.export.MBeanAutodetectionTests
>
>
>> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,069 sec
>>
>> [junit] Testcase: testAutodetectMBean took 0,058 sec
>> [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,131 sec
>> [junit] Testsuite: org.springframework.jmx.export.MBeanExporterTests
>> [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,131 sec
>>
>> [junit] Testcase: testWithLocatedMBeanServer took 0,04 sec
>> [junit] Testcase: testWithSuppliedMBeanServer took 0,004 sec
>> [junit] Testcase: testUserCreatedMBeanRegWithDynamicMBean took 0,006
>>
>>
>sec
>
>
>> [junit] Testcase: testAutodetectSkipsConnectorServerFactoryBean took
>>
>>
>0,071 sec
>
>
>> [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,086 sec
>> [junit] Testsuite:
>>
>>
>org.springframework.jmx.export.PropertyPlaceholderConfigurerTests
>
>
>> [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 0,086 sec
>>
>> [junit] Testcase: testPropertiesReplaced took 0,038 sec
>> [junit] Testcase: testPropertiesCorrectInJmx took 0,031 sec
>> [junit] Caused an ERROR
>> [junit] bean:name=proxyTestBean1
>> [junit] javax.management.InstanceNotFoundException:
>>
>>
>bean:name=proxyTestBean1
>
>
>> [junit] at
>>
>>
>com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1015)
>
>
>
>> [junit] at
>>
>>
>com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:634)
>
>
>
>> [junit] at
>>
>>
>com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:667)
>
>
>
>> [junit] at
>>
>>
>org.springframework.jmx.export.PropertyPlaceholderConfigurerTests.testPropertiesCorrectInJmx(PropertyPlaceholderConfigurerTests.java:41)
>
>
>
>> [junit] at
>>
>>
>sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>
>> [junit] at
>>
>>
>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
>
>
>> [junit] at
>>
>>
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
>
>
>>This is an automated mail from one of the SF Compile Farm machines.
>>The machine name noted in the subject encountered a failure building
>>or running the Spring test suite. The last few lines of the output
>>were included for info.
>>
>>NB: No further mail will be sent from this machine until a
>>manual reset occurs on the cf-shell machine, although builds will
>>continue as scheduled.
>>
>>See http://springframework.sourceforge.net/test/ for further
>>information.
>>
>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now.
>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>>
>>
>>
>>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
