Robert Munteanu created SLING-2954:
--------------------------------------
Summary: Event ITs spuriosly fail on Jenkins
Key: SLING-2954
URL: https://issues.apache.org/jira/browse/SLING-2954
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: Extensions Event 3.1.4
Reporter: Robert Munteanu
Fix For: Extensions Event 3.2.0
For instance,
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.event/1723/consoleText
failed. One guess is that it's caused by the org.apache.felix.http.jetty
bundle failing to start due to the port being in use.
09.07.2013 06:42:23.821 *WARN* [Jetty HTTP Service] org.apache.felix.http.jetty
failed [email protected]:8080: java.net.BindException: Address
already in use
09.07.2013 06:42:23.822 *WARN* [Jetty HTTP Service] org.apache.felix.http.jetty
failed Server@3ec561: java.net.BindException: Address already in use
09.07.2013 06:42:23.822 *ERROR* [Jetty HTTP Service]
org.apache.felix.http.jetty Exception while initializing Jetty.
(java.net.BindException: Address already in use) java.net.BindException:
Address already in use
at sun.nio.ch.Net.bind(Native Method)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:124)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
at
org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
at
org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:315)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.Server.doStart(Server.java:235)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.apache.felix.http.jetty.internal.JettyService.initializeJetty(JettyService.java:164)
at
org.apache.felix.http.jetty.internal.JettyService.startJetty(JettyService.java:115)
at
org.apache.felix.http.jetty.internal.JettyService.run(JettyService.java:290)
at java.lang.Thread.run(Thread.java:662)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
