[jira] [Commented] (SLING-2954) Event ITs spuriosly fail on Jenkins

2013-07-09 Thread Carsten Ziegeler (JIRA)

[ 
https://issues.apache.org/jira/browse/SLING-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704235#comment-13704235
 ] 

Carsten Ziegeler commented on SLING-2954:
-

I've removed the code from the it test again

> 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 SelectChannelConnector@0.0.0.0: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


[jira] [Commented] (SLING-2954) Event ITs spuriosly fail on Jenkins

2013-07-09 Thread Carsten Ziegeler (JIRA)

[ 
https://issues.apache.org/jira/browse/SLING-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703854#comment-13703854
 ] 

Carsten Ziegeler commented on SLING-2954:
-

I'm fine with just keeping the maven based one

> 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 SelectChannelConnector@0.0.0.0: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


[jira] [Commented] (SLING-2954) Event ITs spuriosly fail on Jenkins

2013-07-09 Thread Robert Munteanu (JIRA)

[ 
https://issues.apache.org/jira/browse/SLING-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703523#comment-13703523
 ] 

Robert Munteanu commented on SLING-2954:


I've updated the pax-exam and pax-url versions in 
http://svn.apache.org/viewvc?view=revision&revision=1501393 . _Maybe_ that does 
something.

[~cziegler] - we now have two ways of setting a random network port : 
maven-based and java-based. We should only have one - do you have a preference 
on which to keep?

> 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 SelectChannelConnector@0.0.0.0: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


[jira] [Commented] (SLING-2954) Event ITs spuriosly fail on Jenkins

2013-07-09 Thread Robert Munteanu (JIRA)

[ 
https://issues.apache.org/jira/browse/SLING-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703059#comment-13703059
 ] 

Robert Munteanu commented on SLING-2954:


I just did the same ... configured a random port for the OSGi HTTP service in 
http://svn.apache.org/viewvc?view=revision&revision=1501133 . Anyway, this 
should fix it.

> 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
>Assignee: 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 SelectChannelConnector@0.0.0.0: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


[jira] [Commented] (SLING-2954) Event ITs spuriosly fail on Jenkins

2013-07-09 Thread Carsten Ziegeler (JIRA)

[ 
https://issues.apache.org/jira/browse/SLING-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703044#comment-13703044
 ] 

Carsten Ziegeler commented on SLING-2954:
-

I've committed a change to the ITs which gets a free port and configures jetty 
to use this one instead of the default one - even if that's not our problem, 
doing this is better anyway

> 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 SelectChannelConnector@0.0.0.0: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