Menu
▾
▴
[Springframework-developer] Failed Builds
|
From: Alef A. <al...@in...> - 2006-01-10 01:28:08
|
Thanks for looking into this Thomas. It's been bothering me for some time, but due to holidays I couldn't get to it... On the subject of automatic building, it seems the builds running at SF.net fail quite often (if not always). I haven't looked at all the error messages, but some come from binding errors, some I can't seem to find the error message for. Darren, are x86-linux and sparc-solaris the only platforms the builds are running on, or is it an issue related to those platforms only? regards, Alef Thomas Risberg wrote: > 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.afterPropertiesSet(ConnectorServerFactoryBean.java:167) > at > org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testRegisterWithMBeanServer(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.PropertiesFileNamingStrategyTests >> [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.afterPropertiesSet(ConnectorServerFactoryBean.java:167) >> [junit] at >> org.springframework.jmx.support.ConnectorServerFactoryBeanTests.testStartupWithSuppliedServer(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 >> <http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click> >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> <mailto:Spr...@li...> >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > -- Alef Arendsen Interface21 NL Spring Services from the Source http://www.interface21.com Spring Core Developer http://www.springframework.org Author, "Professional Java Development with the Spring Framework" (June 2005, with Rod Johnson, Juergen Hoeller, Colin Sampaleanu and Thomas Risberg) http://www.amazon.com/exec/obidos/ASIN/0764574833/ Interface21 NL B.V. Donker Curtiusstraat 7-400c 1051JL Amsterdam Phone: 020 486 20 36 Fax: 084 837 00 00 Mail: al...@in... Skype: aarendsen ************************************ DISCLAIMER ********************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. ********************************************************************* |
