|
From: Thomas R. <tho...@tr...> - 2006-01-07 22:38:20
|
I've seen quite a few of the following errors lately:
Unit Test Error Details: (1)
Test: testRegisterWithMBeanServer
Class: org.springframework.jmx.support.ConnectorServerFactoryBeanTests
Type: java.net.BindException
Message: Address already in use
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at com.sun.jmx.remote.socket.SocketConnectionServer.start
(SocketConnectionServer.java:128)
at
com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start
(SynchroMessageConnectionServerImpl.java:39)
at javax.management.remote.generic.GenericConnectorServer.start
(GenericConnectorServer.java:235)
at
org.springframework.jmx.support.ConnectorServerFactoryBean.afterProperti
esSet(ConnectorServerFactoryBean.java:167)
at
org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegi
sterWithMBeanServer(ConnectorServerFactoryBeanTests.java:78)
Since I could reproduce this on my Linux machine I played around with
some potential fixes. Looks like a timing issue so I added a brief
sleep at the beginning of the failing test methods. Seems to take
care of it but occasionally I see the following warnings:
tests:
[junit] Running
org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed:
0.921 sec
[junit] Testsuite:
org.springframework.jmx.support.ConnectorServerFactoryBeanTests
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed:
0.921 sec
[junit] ------------- Standard Error -----------------
[junit] Jan 7, 2006 5:30:22 PM ClientCommunicatorAdmin restart
[junit] WARNING: Failed to restart: java.net.ConnectException:
Connection refused
[junit] Jan 7, 2006 5:30:22 PM ClientCommunicatorAdmin restart
[junit] WARNING: Failed to restart: java.net.ConnectException:
Connection refused
[junit] ------------- ---------------- ---------------
[junit] Testcase: testStartupWithLocatedServer took 0.429 sec
[junit] Testcase: testStartupWithSuppliedServer took 0.029 sec
[junit] Testcase: testRegisterWithMBeanServer took 0.013 sec
[junit] Testcase: testNoRegisterWithMBeanServer took 0.002 sec
Not sure if this indicates a problem or not - it does not show up all
the time.
I've committed my change, let's see how the automated tests respond.
Thomas
On Jan 7, 2006, at 5:38 AM, Darren Davison wrote:
> 1136630281
> FAILED
>
> [junit] Testcase: testNaming took 0,005 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
> 0,014 sec
> [junit] Testsuite:
> org.springframework.jmx.export.naming.PropertiesFileNamingStrategyTest
> s
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
> 0,014 sec
>
> [junit] Testcase: testNaming took 0,003 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
> 0,012 sec
> [junit] Testsuite:
> org.springframework.jmx.export.naming.PropertiesNamingStrategyTests
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
> 0,012 sec
>
> [junit] Testcase: testNaming took 0 sec
> [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed:
> 0,059 sec
> [junit] Testsuite:
> org.springframework.jmx.support.ConnectorServerFactoryBeanTests
> [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed:
> 0,059 sec
>
> [junit] Testcase: testStartupWithLocatedServer took 0,031 sec
> [junit] Testcase: testStartupWithSuppliedServer took 0,01 sec
> [junit] Caused an ERROR
> [junit] Address already in use
> [junit] java.net.BindException: Address already in use
> [junit] at java.net.PlainSocketImpl.socketBind(Native Method)
> [junit] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:
> 331)
> [junit] at java.net.ServerSocket.bind(ServerSocket.java:318)
> [junit] at
> com.sun.jmx.remote.socket.SocketConnectionServer.start
> (SocketConnectionServer.java:128)
> [junit] at
> com.sun.jmx.remote.generic.SynchroMessageConnectionServerImpl.start
> (SynchroMessageConnectionServerImpl.java:39)
> [junit] at
> javax.management.remote.generic.GenericConnectorServer.start
> (GenericConnectorServer.java:235)
> [junit] at
> org.springframework.jmx.support.ConnectorServerFactoryBean.afterProper
> tiesSet(ConnectorServerFactoryBean.java:167)
> [junit] at
> org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testSt
> artupWithSuppliedServer(ConnectorServerFactoryBeanTests.java:65)
>
> Last CVS updates prior to this build were:
> 1136628781
> ? ?
> ? junit423465713.properties
> ? junittestcases2136842450.properties
> ? sandbox/src/org/springframework/core/closure/ElementGenerator.java
> ? sandbox/src/org/springframework/core/closure/support/
> AbstractElementGenerator.java
> ? sandbox/src/org/springframework/core/closure/support/
> AbstractElementGeneratorWorkflow.java
> ? sandbox/src/org/springframework/core/closure/support/IfBlock.java
> ? sandbox/src/org/springframework/jms/listener
> ? test/org/springframework/beans/factory/xml/dependencies-prop-
> inTheMiddle.xml
> C test/org/springframework/beans/factory/xml/dependencies-prop-
> inTheMiddle.xml
>
> 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
> successful build occurs on the machine in question.
>
> See http://springframework.sourceforge.net/test/ for further
> information.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through
> log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD
> SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
|