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

[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

[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

Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling JCR Resource Resolver #1730

[Apache Jenkins Server]

See 

Build failed in Jenkins: sling-trunk-1.6 #1730

[Apache Jenkins Server]

See 

Changes:

[rombert] SLING-2958 - Spurios test failures in GeneratedNodeNameTest 

Cleanup generated content between test method invocations, to ensure
that there are no conflicts due to method execution order.

--
[...truncated 20159 lines...]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [6.833s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [6.011s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [5.187s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [4.641s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [5.333s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [5.035s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [6.681s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [4.366s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [4.435s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [4.519s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [31.682s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [7.048s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [5.965s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [3.622s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [5.215s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [5.015s]
[INFO] Apache Sling Discovery API  SUCCESS [4.128s]
[INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [3:05.132s]
[INFO] Apache Sling Discovery Support Bundle . SUCCESS [4.508s]
[INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [4.166s]
[INFO] Apache Sling Event Support  FAILURE [9:46.768s]
[INFO] Apache Sling Filesystem Resource Provider . SKIPPED
[INFO] Apache Sling javax.activation bundle .. SKIPPED
[INFO] Apache Sling Settings . SKIPPED
[INFO] Apache Sling Thread Dumper  SKIPPED
[INFO] Apache Sling Web Console Branding . SKIPPED
[INFO] Apache Sling Web Console Security Provider  SKIPPED
[INFO] Apache Sling Groovy Extensions  SKIPPED
[INFO] Apache Sling Explorer . SKIPPED
[INFO] Apache Sling Test Tools ... SKIPPED
[INFO] Apache Sling JUnit Core ... SKIPPED
[INFO] Apache Sling JUnit Scriptable Tests Provider .. SKIPPED
[INFO] Apache Sling JUnit Remote Tests Runners ... SKIPPED
[INFO] Apache Sling Testing Resource Resolver Mock ... SKIPPED
[INFO] Apache Sling Installer  SKIPPED
[INFO] Apache Sling Installer WebConsole Plugin .. SKIPPED
[INFO] Apache Sling File Installer ... SKIPPED
[INFO] Apache Sling JCR Installer  SKIPPED
[INFO] Apache Sling Installer Configuration Admin Support  SKIPPED
[INFO] Apache Sling Deployment Package Installer . SKIPPED
[INFO] Apache Sling Installer Integration Tests .. SKIPPED
[INFO] Apache Sling Launchpad API  SKIPPED
[INFO] Apache Sling Launchpad Base ... SKIPPED
[INFO] Apache Sling Launchpad Installer .. SKIPPED
[INFO] Apache Sling Launchpad Content  SKIPPED
[INFO] Apache Sling Launchpad Application Builder  SKIPPED
[INFO] Apache Sling Sample Server-Side Tests . SKIPPED
[INFO] Apache Sling Failing Server-Side Tests  SKIPPED
[INFO] Apache Sling Sample Integration Tests . SKIPPED
[INFO] Apache Sling Launchpad Testing Services ... SKIPPED
[INFO] Apache Sling Launchpad Testing Services WAR ... SKIPPED
[INFO] Apache Sling Launchpad Testing Fragment Bundle  SKIPPED
[INFO] Apache Sling Launchpad Test Bundles ... SKIPPED
[INFO] Apache Sling Integration Tests  SKIPPED
[INFO] Apache Sling Launchpad Testing  SKIPPED
[INFO] Apache Sling Launchpad Testing WAR version  SKIPPED
[INFO] Apache Sling (Builder)  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 22:26.482s
[INFO] Finished at: Tue Jul 09 20:59:48 UTC 2013
[INFO] Final Memory: 129M/325M
[INFO] 
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[J

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1730

[Apache Jenkins Server]

See 


--
[...truncated 9449 lines...]
09.07.2013 20:59:47.584 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [86] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.584 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [87] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.585 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [88] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.585 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [89] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.585 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [90] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.586 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [91] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.586 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [92] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.586 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [93] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.587 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [94] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.587 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [95] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.588 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [96] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.588 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [97] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.588 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 Service [98] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.589 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 BundleEvent STOPPED
09.07.2013 20:59:47.590 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 BundleEvent UNRESOLVED
09.07.2013 20:59:47.591 *INFO* [main] 
PAXEXAM-PROBE-52cc40ea-4dee-4a0b-9041-bee66e799044 BundleEvent UNINSTALLED
09.07.2013 20:59:47.592 *INFO* [FelixDispatchQueue] org.apache.felix.framework 
FrameworkEvent PACKAGES REFRESHED
09.07.2013 20:59:47.593 *INFO* [FelixShutdown] org.apache.felix.framework 
BundleEvent STOPPING
09.07.2013 20:59:47.593 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit BundleEvent STOPPING
09.07.2013 20:59:47.594 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit Service [81] ServiceEvent UNREGISTERING
09.07.2013 20:59:47.594 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit BundleEvent STOPPED
09.07.2013 20:59:47.594 *INFO* [FelixStartLevel] 
org.ops4j.pax.tipi.hamcrest.core BundleEvent STOPPING
09.07.2013 20:59:47.594 *INFO* [FelixStartLevel] 
org.ops4j.pax.tipi.hamcrest.core BundleEvent STOPPED
09.07.2013 20:59:47.595 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.WebConsolePlugin,108] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.597 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.InventoryPlugin,110] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.597 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.deprecated.JobStatusProviderImpl,109] 
ServiceEvent UNREGISTERING
09.07.2013 20:59:47.598 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.jmx.AllJobStatisticsMBean,112] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.598 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobConsumerManager Updating property provider 
with: 
09.07.2013 20:59:47.599 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobManagerImpl Received topology event 
TopologyEvent [type=PROPERTIES_CHANGED, 
oldView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@163f68b,
 
newView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@163f68b]
09.07.2013 20:59:47.599 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.queues.ParallelJobQueue.test Outdating queue 
test, renaming to test(5448649).
09.07.2013 20:59:47.600 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.deprecated.EventAdminBridge,113] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.600 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.deprecated.EventAdminBridge Apache Sling Job 
Event Bridge stopped on instance 939a7326-51e1-4101-b439-6ef03d5b4cfa
09.07.2013 20:59:47.602 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.jcr.PersistenceHandler,107] ServiceEvent 
UNREGISTERING
09.07.2013 20:59:47.602 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobManagerImpl Apache Sling Job Manager 
stopping on instance 939a7326

Jenkins build is back to stable : sling-trunk-1.7 #102

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Launchpad Testing #102

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Launchpad Testing WAR version #102

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-2958) Spurious test failures in GeneratedNodeNameTest

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-2958:


Fixed in http://svn.apache.org/viewvc?view=revision&revision=1501532 by 
cleaning up content between test executions.

> Spurious test failures in GeneratedNodeNameTest
> ---
>
> Key: SLING-2958
> URL: https://issues.apache.org/jira/browse/SLING-2958
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> junit.framework.AssertionFailedError: Location 
> http://localhost:40478/GeneratedNodeNameTest/1373392381765/hello_there_1 ends 
> with hello_there
>   at junit.framework.Assert.fail(Assert.java:47)
>   at junit.framework.Assert.assertTrue(Assert.java:20)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest.testTitle(GeneratedNodeNameTest.java:38)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at junit.framework.TestCase.runTest(TestCase.java:168)
>   at junit.framework.TestCase.runBare(TestCase.java:134)
>   at junit.framework.TestResult$1.protect(TestResult.java:110)
>   at junit.framework.TestResult.runProtected(TestResult.java:128)
>   at junit.framework.TestResult.run(TestResult.java:113)
>   at junit.framework.TestCase.run(TestCase.java:124)
>   at junit.framework.TestSuite.runTest(TestSuite.java:232)
>   at junit.framework.TestSuite.run(TestSuite.java:227)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
>   at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:36)
>   at junit.framework.TestSuite.runTest(TestSuite.java:232)
>   at 
> org.apache.sling.launchpad.testing.LoggingSuite.runTest(LoggingSuite.java:56)
>   at junit.framework.TestSuite.run(TestSuite.java:227)
>   at 
> org.apache.sling.launchpad.testing.LoggingSuite.run(LoggingSuite.java:46)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

--
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] [Updated] (SLING-2958) Spurious test failures in GeneratedNodeNameTest

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2958:
---

Remaining Estimate: 0h
 Original Estimate: 0h
   Summary: Spurious test failures in GeneratedNodeNameTest  (was: 
Spurios test failures in GeneratedNodeNameTest)

> Spurious test failures in GeneratedNodeNameTest
> ---
>
> Key: SLING-2958
> URL: https://issues.apache.org/jira/browse/SLING-2958
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> junit.framework.AssertionFailedError: Location 
> http://localhost:40478/GeneratedNodeNameTest/1373392381765/hello_there_1 ends 
> with hello_there
>   at junit.framework.Assert.fail(Assert.java:47)
>   at junit.framework.Assert.assertTrue(Assert.java:20)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest.testTitle(GeneratedNodeNameTest.java:38)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at junit.framework.TestCase.runTest(TestCase.java:168)
>   at junit.framework.TestCase.runBare(TestCase.java:134)
>   at junit.framework.TestResult$1.protect(TestResult.java:110)
>   at junit.framework.TestResult.runProtected(TestResult.java:128)
>   at junit.framework.TestResult.run(TestResult.java:113)
>   at junit.framework.TestCase.run(TestCase.java:124)
>   at junit.framework.TestSuite.runTest(TestSuite.java:232)
>   at junit.framework.TestSuite.run(TestSuite.java:227)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
>   at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:36)
>   at junit.framework.TestSuite.runTest(TestSuite.java:232)
>   at 
> org.apache.sling.launchpad.testing.LoggingSuite.runTest(LoggingSuite.java:56)
>   at junit.framework.TestSuite.run(TestSuite.java:227)
>   at 
> org.apache.sling.launchpad.testing.LoggingSuite.run(LoggingSuite.java:46)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

--
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] [Resolved] (SLING-2958) Spurious test failures in GeneratedNodeNameTest

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-2958.


Resolution: Fixed

> Spurious test failures in GeneratedNodeNameTest
> ---
>
> Key: SLING-2958
> URL: https://issues.apache.org/jira/browse/SLING-2958
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> junit.framework.AssertionFailedError: Location 
> http://localhost:40478/GeneratedNodeNameTest/1373392381765/hello_there_1 ends 
> with hello_there
>   at junit.framework.Assert.fail(Assert.java:47)
>   at junit.framework.Assert.assertTrue(Assert.java:20)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest.testTitle(GeneratedNodeNameTest.java:38)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at junit.framework.TestCase.runTest(TestCase.java:168)
>   at junit.framework.TestCase.runBare(TestCase.java:134)
>   at junit.framework.TestResult$1.protect(TestResult.java:110)
>   at junit.framework.TestResult.runProtected(TestResult.java:128)
>   at junit.framework.TestResult.run(TestResult.java:113)
>   at junit.framework.TestCase.run(TestCase.java:124)
>   at junit.framework.TestSuite.runTest(TestSuite.java:232)
>   at junit.framework.TestSuite.run(TestSuite.java:227)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
>   at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:36)
>   at junit.framework.TestSuite.runTest(TestSuite.java:232)
>   at 
> org.apache.sling.launchpad.testing.LoggingSuite.runTest(LoggingSuite.java:56)
>   at junit.framework.TestSuite.run(TestSuite.java:227)
>   at 
> org.apache.sling.launchpad.testing.LoggingSuite.run(LoggingSuite.java:46)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

--
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] [Assigned] (SLING-2958) Spurios test failures in GeneratedNodeNameTest

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu reassigned SLING-2958:
--

Assignee: Robert Munteanu

> Spurios test failures in GeneratedNodeNameTest
> --
>
> Key: SLING-2958
> URL: https://issues.apache.org/jira/browse/SLING-2958
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> junit.framework.AssertionFailedError: Location 
> http://localhost:40478/GeneratedNodeNameTest/1373392381765/hello_there_1 ends 
> with hello_there
>   at junit.framework.Assert.fail(Assert.java:47)
>   at junit.framework.Assert.assertTrue(Assert.java:20)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest.testTitle(GeneratedNodeNameTest.java:38)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at junit.framework.TestCase.runTest(TestCase.java:168)
>   at junit.framework.TestCase.runBare(TestCase.java:134)
>   at junit.framework.TestResult$1.protect(TestResult.java:110)
>   at junit.framework.TestResult.runProtected(TestResult.java:128)
>   at junit.framework.TestResult.run(TestResult.java:113)
>   at junit.framework.TestCase.run(TestCase.java:124)
>   at junit.framework.TestSuite.runTest(TestSuite.java:232)
>   at junit.framework.TestSuite.run(TestSuite.java:227)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
>   at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:36)
>   at junit.framework.TestSuite.runTest(TestSuite.java:232)
>   at 
> org.apache.sling.launchpad.testing.LoggingSuite.runTest(LoggingSuite.java:56)
>   at junit.framework.TestSuite.run(TestSuite.java:227)
>   at 
> org.apache.sling.launchpad.testing.LoggingSuite.run(LoggingSuite.java:46)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

--
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] [Created] (SLING-2958) Spurios test failures in GeneratedNodeNameTest

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-2958:
--

 Summary: Spurios test failures in GeneratedNodeNameTest
 Key: SLING-2958
 URL: https://issues.apache.org/jira/browse/SLING-2958
 Project: Sling
  Issue Type: Bug
  Components: Testing
Reporter: Robert Munteanu


junit.framework.AssertionFailedError: Location 
http://localhost:40478/GeneratedNodeNameTest/1373392381765/hello_there_1 ends 
with hello_there
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at 
org.apache.sling.launchpad.webapp.integrationtest.GeneratedNodeNameTest.testTitle(GeneratedNodeNameTest.java:38)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:36)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at 
org.apache.sling.launchpad.testing.LoggingSuite.runTest(LoggingSuite.java:56)
at junit.framework.TestSuite.run(TestSuite.java:227)
at 
org.apache.sling.launchpad.testing.LoggingSuite.run(LoggingSuite.java:46)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)


--
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

Re: [VOTE] New Module Releases

[Antonio Sanso]

+1

On Jul 9, 2013, at 4:46 PM, Carsten Ziegeler wrote:

> Hi,
> 
> this vote is about some important bug fix releases.
> 
> So please vote for:
> Parent POM 17
> https://issues.apache.org/jira/browse/SLING/fixforversion/12324381
> 
> JCR ClassLoader 3.2.0
> https://issues.apache.org/jira/browse/SLING/fixforversion/12324058
> 
> Commons FileSystem ClassLoader 1.0.0
> First Release
> 
> Servlets Post 2.3.2
> https://issues.apache.org/jira/browse/SLING/fixforversion/12324380
> 
> I18n 2.2.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12323577
> 
> Discovery API 1.0.0
> First Release
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-119/
> 
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 119 /tmp/sling-staging
> 
> 
> Please vote to approve this release:
> 
> [ ] +1 Approve the release
> [ ]  0 Don't care
> [ ] -1 Don't release, because ...
> 
> This vote will be open for 72 hours.
> 
> Regards
> 
> -- 
> Carsten Ziegeler
> cziege...@apache.org

Re: [VOTE] New Module Releases

[Antonio Sanso]

+1

On Jul 9, 2013, at 4:46 PM, Carsten Ziegeler wrote:

> Hi,
> 
> this vote is about some important bug fix releases.
> 
> So please vote for:
> Parent POM 17
> https://issues.apache.org/jira/browse/SLING/fixforversion/12324381
> 
> JCR ClassLoader 3.2.0
> https://issues.apache.org/jira/browse/SLING/fixforversion/12324058
> 
> Commons FileSystem ClassLoader 1.0.0
> First Release
> 
> Servlets Post 2.3.2
> https://issues.apache.org/jira/browse/SLING/fixforversion/12324380
> 
> I18n 2.2.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12323577
> 
> Discovery API 1.0.0
> First Release
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-119/
> 
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 119 /tmp/sling-staging
> 
> 
> Please vote to approve this release:
> 
> [ ] +1 Approve the release
> [ ]  0 Don't care
> [ ] -1 Don't release, because ...
> 
> This vote will be open for 72 hours.
> 
> Regards
> 
> -- 
> Carsten Ziegeler
> cziege...@apache.org

Jenkins build became unstable: sling-trunk-1.7 #101

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #101

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing WAR version #101

[Apache Jenkins Server]

See 

Re: Build failed in Jenkins: sling-trunk-1.6 » Apache Sling JCR Resource Resolver #1729

[Robert Munteanu]

This error and others similar to it in the Event bundle seem to be
tracked under [1] . There no sense in chasing the problem in the Sling
codebase, please add any info you might have in that issue.

Robert

[1]: https://issues.apache.org/jira/browse/INFRA-6218

On Tue, Jul 9, 2013 at 8:31 PM, Apache Jenkins Server
 wrote:
> See 
> 
>
> --
> [...truncated 1433 lines...]
> 65927 [main] INFO 
> org.apache.jackrabbit.core.observation.ObservationDispatcher - Notification 
> of EventListeners stopped.
> 65928 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
> closed: 
> 
> 65984 [main] INFO org.apache.jackrabbit.core.util.db.DerbyConnectionHelper - 
> Database 
> '
>  shutdown.
> 65984 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace 
> 'default' has been shutdown
> 65984 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - shutting down 
> workspace 'security'...
> 65984 [main] INFO 
> org.apache.jackrabbit.core.observation.ObservationDispatcher - Notification 
> of EventListeners stopped.
> 65985 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
> closed: 
> 
> 66023 [main] INFO org.apache.jackrabbit.core.util.db.DerbyConnectionHelper - 
> Database 
> '
>  shutdown.
> 66023 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace 
> 'security' has been shutdown
> 66070 [main] INFO org.apache.jackrabbit.core.util.db.DerbyConnectionHelper - 
> Database 
> '
>  shutdown.
> 66072 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - Repository has 
> been shutdown
> 66072 [main] INFO org.apache.jackrabbit.core.TransientRepository - Transient 
> repository shut down
> 66080 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - Starting 
> repository...
> 66080 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
> LocalFileSystem initialized at path 
> 
> 66088 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
> LocalFileSystem initialized at path 
> 
> 66324 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - initializing 
> workspace 'default'...
> 66324 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
> LocalFileSystem initialized at path 
> 
> 66625 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
> initialized: 
> 
>  Version: 3
> 66642 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
> initialized: 
> 
>  Version: 3
> 66642 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace 
> 'default' initialized
> 66642 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - Repository 
> started
> 66642 [main] INFO org.apache.jackrabbit.core.TransientRepository - Transient 
> repository initialized
> 66643 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - initializing 
> workspace 'security'...
> 66643 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
> LocalFileSystem initialized at path 
> 
> 67036 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
> initialized: 
> 
>  Version: 3
> 67036 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace 
> 'security' initialized
> 67036 [main] INFO org.apache.jackrabbit.core.DefaultSecurityManager - init: 
> use

Build failed in Jenkins: sling-trunk-1.6 #1729

[Apache Jenkins Server]

See 

Changes:

[rombert] SLING-2954 - Event ITs spuriosly fail on Jenkins

Update pax-exam version and pax-url versions to be similar to the
healthcheck and installer ITs. Not sure if it will do good, but it
definitely won't hurt.

--
[...truncated 8402 lines...]
[INFO] Apache Sling Authentication Selector .. SUCCESS [3.288s]
[INFO] Apache Sling Engine Implementation  SUCCESS [16.738s]
[INFO] Apache Sling Repository API Bundle  SUCCESS [3.013s]
[INFO] Apache Sling JCR Base Bundle .. SUCCESS [4.254s]
[INFO] Apache Sling JCR ClassLoader .. SUCCESS [4.239s]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [5.462s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [6.236s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [4.236s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[2.924s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [4.028s]
[INFO] Apache Sling Object Content Mapping ... SUCCESS [5.177s]
[INFO] Apache Sling JCR Resource Resolver  FAILURE [1:15.625s]
[INFO] Apache Sling JCR Repository Registration .. SKIPPED
[INFO] Apache Sling Simple WebDAV Access to repositories . SKIPPED
[INFO] Apache Sling DavEx Access to repositories . SKIPPED
[INFO] Apache Sling JCR WebConsole Bundle  SKIPPED
[INFO] Apache Sling Servlet Resolver . SKIPPED
[INFO] Apache Sling Default GET Servlets . SKIPPED
[INFO] Apache Sling Default POST Servlets  SKIPPED
[INFO] Apache Sling Compat Servlets .. SKIPPED
[INFO] Apache Sling Scripting Implementation API . SKIPPED
[INFO] Apache Sling Scripting Core implementation  SKIPPED
[INFO] Apache Sling Scripting JavaScript Support . SKIPPED
[INFO] Apache Sling Scripting JSP Support  SKIPPED
[INFO] Apache Sling JSP Tag Library .. SKIPPED
[INFO] Apache Sling JSP Standard Tag Library . SKIPPED
[INFO] Apache Sling Adapter Manager Implementation ... SKIPPED
[INFO] Apache Sling Bundle Resource Provider . SKIPPED
[INFO] Apache Sling Discovery API  SKIPPED
[INFO] Apache Sling Resource-Based Discovery Service . SKIPPED
[INFO] Apache Sling Discovery Support Bundle . SKIPPED
[INFO] Apache Sling Discovery Standalone Implementation .. SKIPPED
[INFO] Apache Sling Event Support  SKIPPED
[INFO] Apache Sling Filesystem Resource Provider . SKIPPED
[INFO] Apache Sling javax.activation bundle .. SKIPPED
[INFO] Apache Sling Settings . SKIPPED
[INFO] Apache Sling Thread Dumper  SKIPPED
[INFO] Apache Sling Web Console Branding . SKIPPED
[INFO] Apache Sling Web Console Security Provider  SKIPPED
[INFO] Apache Sling Groovy Extensions  SKIPPED
[INFO] Apache Sling Explorer . SKIPPED
[INFO] Apache Sling Test Tools ... SKIPPED
[INFO] Apache Sling JUnit Core ... SKIPPED
[INFO] Apache Sling JUnit Scriptable Tests Provider .. SKIPPED
[INFO] Apache Sling JUnit Remote Tests Runners ... SKIPPED
[INFO] Apache Sling Testing Resource Resolver Mock ... SKIPPED
[INFO] Apache Sling Installer  SKIPPED
[INFO] Apache Sling Installer WebConsole Plugin .. SKIPPED
[INFO] Apache Sling File Installer ... SKIPPED
[INFO] Apache Sling JCR Installer  SKIPPED
[INFO] Apache Sling Installer Configuration Admin Support  SKIPPED
[INFO] Apache Sling Deployment Package Installer . SKIPPED
[INFO] Apache Sling Installer Integration Tests .. SKIPPED
[INFO] Apache Sling Launchpad API  SKIPPED
[INFO] Apache Sling Launchpad Base ... SKIPPED
[INFO] Apache Sling Launchpad Installer .. SKIPPED
[INFO] Apache Sling Launchpad Content  SKIPPED
[INFO] Apache Sling Launchpad Application Builder  SKIPPED
[INFO] Apache Sling Sample Server-Side Tests . SKIPPED
[INFO] Apache Sling Failing Server-Side Tests  SKIPPED
[INFO] Apache Sling Sample Integration Tests . SKIPPED
[INFO] Apache Sling Launchpad Testing Services ... SKIPPED
[INFO] Apache Sling Launchpad Testing Services WAR ... SKIPPED
[INFO] Apache Sling Launchpad Testing Fragment Bundle  SKIPPED
[INFO] Apache Sling Launchpad Test Bundles ... SKIPPED
[INFO] Apache Sling Integration Tests  SKIPPED
[INFO] Apache Sling Launchpad Testing  SKIPPED
[INFO] Apache Sling 

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling JCR Resource Resolver #1729

[Apache Jenkins Server]

See 


--
[...truncated 1433 lines...]
65927 [main] INFO org.apache.jackrabbit.core.observation.ObservationDispatcher 
- Notification of EventListeners stopped.
65928 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
closed: 

65984 [main] INFO org.apache.jackrabbit.core.util.db.DerbyConnectionHelper - 
Database 
'
 shutdown.
65984 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace 
'default' has been shutdown
65984 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - shutting down 
workspace 'security'...
65984 [main] INFO org.apache.jackrabbit.core.observation.ObservationDispatcher 
- Notification of EventListeners stopped.
65985 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
closed: 

66023 [main] INFO org.apache.jackrabbit.core.util.db.DerbyConnectionHelper - 
Database 
'
 shutdown.
66023 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace 
'security' has been shutdown
66070 [main] INFO org.apache.jackrabbit.core.util.db.DerbyConnectionHelper - 
Database 
'
 shutdown.
66072 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - Repository has 
been shutdown
66072 [main] INFO org.apache.jackrabbit.core.TransientRepository - Transient 
repository shut down
66080 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - Starting 
repository...
66080 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
LocalFileSystem initialized at path 

66088 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
LocalFileSystem initialized at path 

66324 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - initializing 
workspace 'default'...
66324 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
LocalFileSystem initialized at path 

66625 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
initialized: 

 Version: 3
66642 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
initialized: 

 Version: 3
66642 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace 
'default' initialized
66642 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - Repository started
66642 [main] INFO org.apache.jackrabbit.core.TransientRepository - Transient 
repository initialized
66643 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - initializing 
workspace 'security'...
66643 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
LocalFileSystem initialized at path 

67036 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
initialized: 

 Version: 3
67036 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - workspace 
'security' initialized
67036 [main] INFO org.apache.jackrabbit.core.DefaultSecurityManager - init: use 
Repository Login-Configuration for Jackrabbit
67041 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - SecurityManager = 
class org.apache.jackrabbit.core.DefaultSecurityManager
67043 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
opened
67084 [main] INFO org.apache.jackrabbit.core.TransientRepository - Session 
closed
67084 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - Shutting down 
repository...
67085 [main] INFO org.apache.jackrabbit.cor

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

[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

Jenkins build is back to stable : sling-trunk-1.7 #100

[Apache Jenkins Server]

See 

Build failed in Jenkins: sling-trunk-1.6 #1728

[Apache Jenkins Server]

See 

Changes:

[rombert] SLING-2957 - IT failures in FailingServerTests

Make assertions more precise to prevent false matches from coming up.

[rombert] SLING-2852 - Sling Launchpad Testing WAR - ClassCircularityError when
executed in a reactor

pom.xml cleanups:

- remove unused maven-jetty-plugin
- remove plugin version overrides ( newer versions are inherited )
- use non-deprecated configuration syntax for the cargo-maven2-plugin

--
[...truncated 19685 lines...]
[INFO] Apache Sling Object Content Mapping ... SUCCESS [5.531s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [1:14.635s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [5.033s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [4.143s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [4.308s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [3.367s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [4.734s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [4.090s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [5.713s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [4.531s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [3.362s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [5.151s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [20.327s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [6.502s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [4.146s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [2.948s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [4.057s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [3.104s]
[INFO] Apache Sling Discovery API  SUCCESS [3.332s]
[INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [2:28.736s]
[INFO] Apache Sling Discovery Support Bundle . SUCCESS [3.695s]
[INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [3.769s]
[INFO] Apache Sling Event Support  FAILURE [6:58.881s]
[INFO] Apache Sling Filesystem Resource Provider . SKIPPED
[INFO] Apache Sling javax.activation bundle .. SKIPPED
[INFO] Apache Sling Settings . SKIPPED
[INFO] Apache Sling Thread Dumper  SKIPPED
[INFO] Apache Sling Web Console Branding . SKIPPED
[INFO] Apache Sling Web Console Security Provider  SKIPPED
[INFO] Apache Sling Groovy Extensions  SKIPPED
[INFO] Apache Sling Explorer . SKIPPED
[INFO] Apache Sling Test Tools ... SKIPPED
[INFO] Apache Sling JUnit Core ... SKIPPED
[INFO] Apache Sling JUnit Scriptable Tests Provider .. SKIPPED
[INFO] Apache Sling JUnit Remote Tests Runners ... SKIPPED
[INFO] Apache Sling Testing Resource Resolver Mock ... SKIPPED
[INFO] Apache Sling Installer  SKIPPED
[INFO] Apache Sling Installer WebConsole Plugin .. SKIPPED
[INFO] Apache Sling File Installer ... SKIPPED
[INFO] Apache Sling JCR Installer  SKIPPED
[INFO] Apache Sling Installer Configuration Admin Support  SKIPPED
[INFO] Apache Sling Deployment Package Installer . SKIPPED
[INFO] Apache Sling Installer Integration Tests .. SKIPPED
[INFO] Apache Sling Launchpad API  SKIPPED
[INFO] Apache Sling Launchpad Base ... SKIPPED
[INFO] Apache Sling Launchpad Installer .. SKIPPED
[INFO] Apache Sling Launchpad Content  SKIPPED
[INFO] Apache Sling Launchpad Application Builder  SKIPPED
[INFO] Apache Sling Sample Server-Side Tests . SKIPPED
[INFO] Apache Sling Failing Server-Side Tests  SKIPPED
[INFO] Apache Sling Sample Integration Tests . SKIPPED
[INFO] Apache Sling Launchpad Testing Services ... SKIPPED
[INFO] Apache Sling Launchpad Testing Services WAR ... SKIPPED
[INFO] Apache Sling Launchpad Testing Fragment Bundle  SKIPPED
[INFO] Apache Sling Launchpad Test Bundles ... SKIPPED
[INFO] Apache Sling Integration Tests  SKIPPED
[INFO] Apache Sling Launchpad Testing  SKIPPED
[INFO] Apache Sling Launchpad Testing WAR version  SKIPPED
[INFO] Apache Sling (Builder)  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 17:30.716s
[INFO] Finished at: Tue Jul 09 16:57:22 UTC 2

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1728

[Apache Jenkins Server]

See 


--
[...truncated 8975 lines...]
09.07.2013 16:57:21.078 *INFO* [main] 
org.apache.sling.event.impl.jobs.JobConsumerManager Updating property provider 
with: /
09.07.2013 16:57:21.078 *INFO* [main] 
org.apache.sling.event.impl.jobs.JobManagerImpl Received topology event 
TopologyEvent [type=PROPERTIES_CHANGED, 
oldView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@1c827cf,
 
newView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@1c827cf]
09.07.2013 16:57:21.079 *INFO* [main] 
org.apache.sling.event.impl.jobs.queues.ParallelJobQueue.test Outdating queue 
test, renaming to test(22460222).
09.07.2013 16:57:21.079 *INFO* [main] 
org.apache.sling.event.impl.jobs.TopologyCapabilities Detected capabilities of 
d6161de4-6895-499d-a9c0-c97606edfb6a : /
09.07.2013 16:57:21.080 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b Service [112] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.081 *INFO* [CM Event Dispatcher (Fire ConfigurationEvent: 
pid=org.apache.sling.event.jobs.QueueConfiguration.3adb6885-65fa-4576-a3dd-fb85dee8c617)]
 org.apache.sling.event Service 
[org.apache.sling.event.jobs.QueueConfiguration.3adb6885-65fa-4576-a3dd-fb85dee8c617,111]
 ServiceEvent UNREGISTERING
09.07.2013 16:57:21.083 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b BundleEvent STOPPING
09.07.2013 16:57:21.083 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b Service [82] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.084 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b Service [83] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.084 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b Service [84] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.085 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b Service [85] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.085 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b Service [86] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.085 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b Service [87] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.086 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b Service [88] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.086 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b Service [89] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.086 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b Service [90] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.087 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b BundleEvent STOPPED
09.07.2013 16:57:21.087 *INFO* [main] 
org.ops4j.pax.exam.raw.extender.intern.TestBundleObserver Unregistered testcase 
[org.ops4j.pax.exam.raw.extender.intern.Probe@184d42.]
09.07.2013 16:57:21.087 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b BundleEvent UNRESOLVED
09.07.2013 16:57:21.089 *INFO* [main] 
PAXEXAM-PROBE-1e5b7a24-fe95-410a-bb5e-3f372ba37b0b BundleEvent UNINSTALLED
09.07.2013 16:57:21.089 *INFO* [FelixShutdown] org.apache.felix.framework 
BundleEvent STOPPING
09.07.2013 16:57:21.090 *INFO* [FelixDispatchQueue] org.apache.felix.framework 
FrameworkEvent PACKAGES REFRESHED
09.07.2013 16:57:21.090 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit BundleEvent STOPPING
09.07.2013 16:57:21.090 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit Service [81] ServiceEvent UNREGISTERING
09.07.2013 16:57:21.090 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit BundleEvent STOPPED
09.07.2013 16:57:21.091 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.WebConsolePlugin,100] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.092 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.InventoryPlugin,102] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.093 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.deprecated.JobStatusProviderImpl,101] 
ServiceEvent UNREGISTERING
09.07.2013 16:57:21.093 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.jmx.AllJobStatisticsMBean,104] ServiceEvent 
UNREGISTERING
09.07.2013 16:57:21.093 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobConsumerManager Updating property provider 
with: 
09.07.2013 16:57:21.096 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobManagerImpl Received topology event 
TopologyEvent [type=PROPERTIES_CHANGED, 
oldView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@1c827cf,
 
newView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@1c827cf]
09.07.2013 16:57:21.096 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.q

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Sample Integration Tests #100

[Apache Jenkins Server]

See 

[jira] [Resolved] (SLING-2957) IT failures in FailingServerTests

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-2957.


Resolution: Fixed

Made the assertions more precise in 
http://svn.apache.org/viewvc?view=revision&revision=1501356

> IT failures in FailingServerTests
> -
>
> Key: SLING-2957
> URL: https://issues.apache.org/jira/browse/SLING-2957
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sample Integration Tests 1.0.8
>
>
> I've seen this happen intermitently in testing runs, e.g. [1]
> org.junit.ComparisonFailure: 
> expected:  This JUnit4 test fail]s every time> but 
> was:  This JUnit4 test assert]s every time>
>   at org.junit.Assert.assertEquals(Assert.java:123)
>   at org.junit.Assert.assertEquals(Assert.java:145)
>   at 
> org.apache.sling.testing.samples.integrationtests.serverside.FailingTestsTest.testFailures(FailingTestsTest.java:82)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>   at 
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
>   at $Proxy0.invoke(Unknown Source)
>   at 
> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
>   at 
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> [1]: 
> https://builds.apache.org/job/sling-trunk-1.7/99/org.apache.sling$org.apache.sling.testing.samples.integrationtests/testReport/org.apache.sling.testing.samples.integrationtests.serverside/FailingTestsTest/testFailures/

--
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] [Updated] (SLING-2957) IT failures in FailingServerTests

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2957:
---

Fix Version/s: Sample Integration Tests 1.0.8

> IT failures in FailingServerTests
> -
>
> Key: SLING-2957
> URL: https://issues.apache.org/jira/browse/SLING-2957
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sample Integration Tests 1.0.8
>
>
> I've seen this happen intermitently in testing runs, e.g. [1]
> org.junit.ComparisonFailure: 
> expected:  This JUnit4 test fail]s every time> but 
> was:  This JUnit4 test assert]s every time>
>   at org.junit.Assert.assertEquals(Assert.java:123)
>   at org.junit.Assert.assertEquals(Assert.java:145)
>   at 
> org.apache.sling.testing.samples.integrationtests.serverside.FailingTestsTest.testFailures(FailingTestsTest.java:82)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>   at 
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
>   at $Proxy0.invoke(Unknown Source)
>   at 
> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
>   at 
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> [1]: 
> https://builds.apache.org/job/sling-trunk-1.7/99/org.apache.sling$org.apache.sling.testing.samples.integrationtests/testReport/org.apache.sling.testing.samples.integrationtests.serverside/FailingTestsTest/testFailures/

--
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] [Updated] (SLING-2957) IT failures in FailingServerTests

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2957:
---

Assignee: Robert Munteanu

> IT failures in FailingServerTests
> -
>
> Key: SLING-2957
> URL: https://issues.apache.org/jira/browse/SLING-2957
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> I've seen this happen intermitently in testing runs, e.g. [1]
> org.junit.ComparisonFailure: 
> expected:  This JUnit4 test fail]s every time> but 
> was:  This JUnit4 test assert]s every time>
>   at org.junit.Assert.assertEquals(Assert.java:123)
>   at org.junit.Assert.assertEquals(Assert.java:145)
>   at 
> org.apache.sling.testing.samples.integrationtests.serverside.FailingTestsTest.testFailures(FailingTestsTest.java:82)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>   at 
> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:601)
>   at 
> org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
>   at $Proxy0.invoke(Unknown Source)
>   at 
> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
>   at 
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> [1]: 
> https://builds.apache.org/job/sling-trunk-1.7/99/org.apache.sling$org.apache.sling.testing.samples.integrationtests/testReport/org.apache.sling.testing.samples.integrationtests.serverside/FailingTestsTest/testFailures/

--
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-2852) Sling Launchpad Testing WAR - ClassCircularityError when executed in a reactor

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-2852:


Minor pom.xml cleanups in 
http://svn.apache.org/viewvc?view=revision&revision=1501355 , just to make it 
easier to understand.

> Sling Launchpad Testing WAR - ClassCircularityError when executed in a reactor
> --
>
> Key: SLING-2852
> URL: https://issues.apache.org/jira/browse/SLING-2852
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> The the launchpad/testing-war project is executed as part of a reactor build 
> it fails with a CCE. However, when run standalone does have this problem. The 
> problem can be seen for instance at 
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/1640/consoleText
>  . I don't know about Java 7 tests since they fail earlier.
> 2013-05-02 14:04:54.986:INFO:/:sling: Starting Apache Sling in 
> /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6/trunk/launchpad/testing-war/target/sling-cargo-test/sling
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:597)
>   at 
> org.apache.felix.framework.util.SecureAction.invoke(SecureAction.java:840)
>   at 
> org.apache.felix.framework.URLHandlers.getFrameworkFromContext(URLHandlers.java:722)
>   at 
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.getStreamHandlerService(URLHandlersStreamHandlerProxy.java:574)
>   at 
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:369)
>   at java.net.URL.(URL.java:596)
>   at java.net.URL.(URL.java:464)
>   at sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:674)
>   at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:759)
>   at sun.misc.URLClassPath.getResource(URLClassPath.java:169)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>   at 
> org.apache.sling.launchpad.base.shared.LauncherClassLoader.loadClass(LauncherClassLoader.java:131)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>   at java.lang.Class.getDeclaredMethods0(Native Method)
>   at java.lang.Class.privateGetDeclaredMethods(Class.java:2436)
>   at java.lang.Class.getDeclaredMethod(Class.java:1937)
>   at 
> org.apache.sling.launchpad.base.impl.SlingFelix.getBundle(SlingFelix.java:114)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:597)
>   at 
> org.apache.felix.framework.util.SecureAction.invoke(SecureAction.java:840)
>   at 
> org.apache.felix.framework.URLHandlers.getFrameworkFromContext(URLHandlers.java:722)
>   at 
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.getStreamHandlerService(URLHandlersStreamHandlerProxy.java:574)
>   at 
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:369)
>   at java.net.URL.(URL.java:596)
>   at java.net.URL.(URL.java:464)
>   at sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:674)
>   at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:759)
>   at sun.misc.URLClassPath.getResource(URLClassPath.java:169)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>   at 
> org.apache.sling.launchpad.base.shared.LauncherClassLoader.loadClass(LauncherClassLoader.java:131)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findResourcesByDelegation(BundleWiringImpl.java:1202)
>   at 
> org.apache.felix.framework.BundleWiringImpl.getResourcesByDelegation(BundleWiringImpl.java:1076)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findResourcesByDelegation(BundleWiringImpl.java:1127)
>   at 
> org.apache.felix.framework.BundleWiringImp

Jenkins build is back to stable : sling-trunk-1.6 #1727

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1727

[Apache Jenkins Server]

See 

[jira] [Created] (SLING-2957) IT failures in FailingServerTests

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-2957:
--

 Summary: IT failures in FailingServerTests
 Key: SLING-2957
 URL: https://issues.apache.org/jira/browse/SLING-2957
 Project: Sling
  Issue Type: Bug
  Components: Testing
Reporter: Robert Munteanu


I've seen this happen intermitently in testing runs, e.g. [1]

org.junit.ComparisonFailure: 
expected: but 
was:
at org.junit.Assert.assertEquals(Assert.java:123)
at org.junit.Assert.assertEquals(Assert.java:145)
at 
org.apache.sling.testing.samples.integrationtests.serverside.FailingTestsTest.testFailures(FailingTestsTest.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at 
org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at $Proxy0.invoke(Unknown Source)
at 
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)

[1]: 
https://builds.apache.org/job/sling-trunk-1.7/99/org.apache.sling$org.apache.sling.testing.samples.integrationtests/testReport/org.apache.sling.testing.samples.integrationtests.serverside/FailingTestsTest/testFailures/

--
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

Re: [VOTE] New Module Releases

[Carsten Ziegeler]

+1

Carsten


2013/7/9 Carsten Ziegeler 

> Hi,
>
> this vote is about some important bug fix releases.
>
> So please vote for:
> Parent POM 17
> https://issues.apache.org/jira/browse/SLING/fixforversion/12324381
>
> JCR ClassLoader 3.2.0
> https://issues.apache.org/jira/browse/SLING/fixforversion/12324058
>
> Commons FileSystem ClassLoader 1.0.0
> First Release
>
> Servlets Post 2.3.2
> https://issues.apache.org/jira/browse/SLING/fixforversion/12324380
>
> I18n 2.2.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12323577
>
> Discovery API 1.0.0
> First Release
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-119/
>
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 119 /tmp/sling-staging
>
>
> Please vote to approve this release:
>
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
>
> This vote will be open for 72 hours.
>
> Regards
>
> --
> Carsten Ziegeler
> cziege...@apache.org
>



-- 
Carsten Ziegeler
cziege...@apache.org

[jira] [Updated] (SLING-2852) Sling Launchpad Testing WAR - ClassCircularityError when executed in a reactor

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2852:
---

Assignee: Robert Munteanu

> Sling Launchpad Testing WAR - ClassCircularityError when executed in a reactor
> --
>
> Key: SLING-2852
> URL: https://issues.apache.org/jira/browse/SLING-2852
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> The the launchpad/testing-war project is executed as part of a reactor build 
> it fails with a CCE. However, when run standalone does have this problem. The 
> problem can be seen for instance at 
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/1640/consoleText
>  . I don't know about Java 7 tests since they fail earlier.
> 2013-05-02 14:04:54.986:INFO:/:sling: Starting Apache Sling in 
> /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6/trunk/launchpad/testing-war/target/sling-cargo-test/sling
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:597)
>   at 
> org.apache.felix.framework.util.SecureAction.invoke(SecureAction.java:840)
>   at 
> org.apache.felix.framework.URLHandlers.getFrameworkFromContext(URLHandlers.java:722)
>   at 
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.getStreamHandlerService(URLHandlersStreamHandlerProxy.java:574)
>   at 
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:369)
>   at java.net.URL.(URL.java:596)
>   at java.net.URL.(URL.java:464)
>   at sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:674)
>   at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:759)
>   at sun.misc.URLClassPath.getResource(URLClassPath.java:169)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>   at 
> org.apache.sling.launchpad.base.shared.LauncherClassLoader.loadClass(LauncherClassLoader.java:131)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>   at java.lang.Class.getDeclaredMethods0(Native Method)
>   at java.lang.Class.privateGetDeclaredMethods(Class.java:2436)
>   at java.lang.Class.getDeclaredMethod(Class.java:1937)
>   at 
> org.apache.sling.launchpad.base.impl.SlingFelix.getBundle(SlingFelix.java:114)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:597)
>   at 
> org.apache.felix.framework.util.SecureAction.invoke(SecureAction.java:840)
>   at 
> org.apache.felix.framework.URLHandlers.getFrameworkFromContext(URLHandlers.java:722)
>   at 
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.getStreamHandlerService(URLHandlersStreamHandlerProxy.java:574)
>   at 
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:369)
>   at java.net.URL.(URL.java:596)
>   at java.net.URL.(URL.java:464)
>   at sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:674)
>   at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:759)
>   at sun.misc.URLClassPath.getResource(URLClassPath.java:169)
>   at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>   at 
> org.apache.sling.launchpad.base.shared.LauncherClassLoader.loadClass(LauncherClassLoader.java:131)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findResourcesByDelegation(BundleWiringImpl.java:1202)
>   at 
> org.apache.felix.framework.BundleWiringImpl.getResourcesByDelegation(BundleWiringImpl.java:1076)
>   at 
> org.apache.felix.framework.BundleWiringImpl.findResourcesByDelegation(BundleWiringImpl.java:1127)
>   at 
> org.apache.felix.framework.BundleWiringImpl.getResourcesByDelegation(BundleWiringImpl.java:1076)
>   at 
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5.getResources(BundleWiringImpl.j

Jenkins build is still unstable: sling-trunk-1.7 #99

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #99

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-2923) release org.apache.sling.jcr.jackrabbit.server 2.1.1

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-2923:


I've just updated the tika bundles to version 1.2 for SLING-2924 . Can you try 
this configuration and see if it fixes your problem?

> release org.apache.sling.jcr.jackrabbit.server 2.1.1
> 
>
> Key: SLING-2923
> URL: https://issues.apache.org/jira/browse/SLING-2923
> Project: Sling
>  Issue Type: Task
>  Components: JCR
>Affects Versions: JCR Jackrabbit Server 2.1.0
> Environment: Apache Karaf 3.0.0.RC1
>Reporter: Oliver Lietz
> Attachments: org.apache.sling.jcr.jackrabbit.server.log
>
>
> There are problems with Tika and org.apache.sling.jcr.jackrabbit.server 
> (Caused by: java.lang.ClassNotFoundException: 
> org.apache.tika.parser.xml.DcXMLParser not found by org.apache.tika.core) on 
> Karaf which seem to be solved with 2.1.1-SNAPSHOT. Release 2.1.1-SNAPSHOT as 
> 2.1.1.

--
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] [Updated] (SLING-2924) Full text extraction issue with Tika v1.0 under OSGi environment

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2924:
---

  Component/s: (was: JCR)
   Launchpad
Fix Version/s: Launchpad Builder 7

> Full text extraction issue with Tika v1.0 under OSGi environment
> 
>
> Key: SLING-2924
> URL: https://issues.apache.org/jira/browse/SLING-2924
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Reporter: Anjan
>Assignee: Robert Munteanu
>  Labels: tika,text-extraction
> Fix For: Launchpad Builder 7
>
>
> The latest stable build (I checked out revision 1487628) of Sling is using 
> Jackrabbit version 2.4.2 and it uses Tika version 1.0 for extracting 
> metatdata and text for indexing purpose.  Jackrabbit v2.4.2 deployed as a 
> separate web application extracts metadata and text from the uploaded 
> documents perfectly fine, but when deployed in Sling (OSGi environment), full 
> text extraction doesn't work.
> Updating the Tika dependency to Version 1.2 in Sling resolved the above issue.
> Secondly, if the indexes are deleted from the repository and the server is 
> restarted, indexes are not rebuilt for the existing documents.  The Tika 
> bundles were not ready by the time Jackrabbit starts to rebuild the indexes 
> during the Sling server start up.  Updating the startlevel from 15 to 10 for 
> the Tika bundles helps to resolve the issue.
> The changes related to above fixes are in 
> /launchpad/builder/src/main/bundles/list.xml file.
> Currently Tika bundles are at start level 15 as shown below:
> 
> ..
> 
> org.apache.tika
> tika-core
> 1.0
> 
> 
> org.apache.tika
> tika-bundle
> 1.0
> 
> ..
> 
> Moved the above bundles to start level 10 and also the version is changed to 
> 1.2
> 
> ..
> 
> org.apache.tika
> tika-core
> 1.2
> 
> 
> org.apache.tika
> tika-bundle
> 1.2
> 
> ..
> 

--
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] [Resolved] (SLING-2924) Full text extraction issue with Tika v1.0 under OSGi environment

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-2924.


Resolution: Fixed

I've updated the start levels following your suggestion in 
http://svn.apache.org/viewvc?view=revision&revision=1501298 .

This issue should be completely fixed, thanks for debugging this in detail and 
for providing the fixes.

> Full text extraction issue with Tika v1.0 under OSGi environment
> 
>
> Key: SLING-2924
> URL: https://issues.apache.org/jira/browse/SLING-2924
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Reporter: Anjan
>Assignee: Robert Munteanu
>  Labels: tika,text-extraction
> Fix For: Launchpad Builder 7
>
>
> The latest stable build (I checked out revision 1487628) of Sling is using 
> Jackrabbit version 2.4.2 and it uses Tika version 1.0 for extracting 
> metatdata and text for indexing purpose.  Jackrabbit v2.4.2 deployed as a 
> separate web application extracts metadata and text from the uploaded 
> documents perfectly fine, but when deployed in Sling (OSGi environment), full 
> text extraction doesn't work.
> Updating the Tika dependency to Version 1.2 in Sling resolved the above issue.
> Secondly, if the indexes are deleted from the repository and the server is 
> restarted, indexes are not rebuilt for the existing documents.  The Tika 
> bundles were not ready by the time Jackrabbit starts to rebuild the indexes 
> during the Sling server start up.  Updating the startlevel from 15 to 10 for 
> the Tika bundles helps to resolve the issue.
> The changes related to above fixes are in 
> /launchpad/builder/src/main/bundles/list.xml file.
> Currently Tika bundles are at start level 15 as shown below:
> 
> ..
> 
> org.apache.tika
> tika-core
> 1.0
> 
> 
> org.apache.tika
> tika-bundle
> 1.0
> 
> ..
> 
> Moved the above bundles to start level 10 and also the version is changed to 
> 1.2
> 
> ..
> 
> org.apache.tika
> tika-core
> 1.2
> 
> 
> org.apache.tika
> tika-bundle
> 1.2
> 
> ..
> 

--
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

[VOTE] New Module Releases

[Carsten Ziegeler]

Hi,

this vote is about some important bug fix releases.

So please vote for:
Parent POM 17
https://issues.apache.org/jira/browse/SLING/fixforversion/12324381

JCR ClassLoader 3.2.0
https://issues.apache.org/jira/browse/SLING/fixforversion/12324058

Commons FileSystem ClassLoader 1.0.0
First Release

Servlets Post 2.3.2
https://issues.apache.org/jira/browse/SLING/fixforversion/12324380

I18n 2.2.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12323577

Discovery API 1.0.0
First Release

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-119/


You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 119 /tmp/sling-staging


Please vote to approve this release:

 [ ] +1 Approve the release
 [ ]  0 Don't care
 [ ] -1 Don't release, because ...

This vote will be open for 72 hours.

Regards

-- 
Carsten Ziegeler
cziege...@apache.org

Jenkins build is still unstable: sling-trunk-1.6 #1726

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Installer Integration Tests #1726

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1726

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 #98

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Event Support #98

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #98

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Launchpad Testing #98

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #98

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-2924) Full text extraction issue with Tika v1.0 under OSGi environment

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-2924:


I've updated the bundles to tika-1.2 and verified the behaviour using an 
integration test in http://svn.apache.org/viewvc?view=revision&revision=1501285 
.

> Full text extraction issue with Tika v1.0 under OSGi environment
> 
>
> Key: SLING-2924
> URL: https://issues.apache.org/jira/browse/SLING-2924
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: Anjan
>Assignee: Robert Munteanu
>  Labels: tika,text-extraction
>
> The latest stable build (I checked out revision 1487628) of Sling is using 
> Jackrabbit version 2.4.2 and it uses Tika version 1.0 for extracting 
> metatdata and text for indexing purpose.  Jackrabbit v2.4.2 deployed as a 
> separate web application extracts metadata and text from the uploaded 
> documents perfectly fine, but when deployed in Sling (OSGi environment), full 
> text extraction doesn't work.
> Updating the Tika dependency to Version 1.2 in Sling resolved the above issue.
> Secondly, if the indexes are deleted from the repository and the server is 
> restarted, indexes are not rebuilt for the existing documents.  The Tika 
> bundles were not ready by the time Jackrabbit starts to rebuild the indexes 
> during the Sling server start up.  Updating the startlevel from 15 to 10 for 
> the Tika bundles helps to resolve the issue.
> The changes related to above fixes are in 
> /launchpad/builder/src/main/bundles/list.xml file.
> Currently Tika bundles are at start level 15 as shown below:
> 
> ..
> 
> org.apache.tika
> tika-core
> 1.0
> 
> 
> org.apache.tika
> tika-bundle
> 1.0
> 
> ..
> 
> Moved the above bundles to start level 10 and also the version is changed to 
> 1.2
> 
> ..
> 
> org.apache.tika
> tika-core
> 1.2
> 
> 
> org.apache.tika
> tika-bundle
> 1.2
> 
> ..
> 

--
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] [Updated] (SLING-2924) Full text extraction issue with Tika v1.0 under OSGi environment

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2924:
---

Assignee: Robert Munteanu

> Full text extraction issue with Tika v1.0 under OSGi environment
> 
>
> Key: SLING-2924
> URL: https://issues.apache.org/jira/browse/SLING-2924
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: Anjan
>Assignee: Robert Munteanu
>  Labels: tika,text-extraction
>
> The latest stable build (I checked out revision 1487628) of Sling is using 
> Jackrabbit version 2.4.2 and it uses Tika version 1.0 for extracting 
> metatdata and text for indexing purpose.  Jackrabbit v2.4.2 deployed as a 
> separate web application extracts metadata and text from the uploaded 
> documents perfectly fine, but when deployed in Sling (OSGi environment), full 
> text extraction doesn't work.
> Updating the Tika dependency to Version 1.2 in Sling resolved the above issue.
> Secondly, if the indexes are deleted from the repository and the server is 
> restarted, indexes are not rebuilt for the existing documents.  The Tika 
> bundles were not ready by the time Jackrabbit starts to rebuild the indexes 
> during the Sling server start up.  Updating the startlevel from 15 to 10 for 
> the Tika bundles helps to resolve the issue.
> The changes related to above fixes are in 
> /launchpad/builder/src/main/bundles/list.xml file.
> Currently Tika bundles are at start level 15 as shown below:
> 
> ..
> 
> org.apache.tika
> tika-core
> 1.0
> 
> 
> org.apache.tika
> tika-bundle
> 1.0
> 
> ..
> 
> Moved the above bundles to start level 10 and also the version is changed to 
> 1.2
> 
> ..
> 
> org.apache.tika
> tika-core
> 1.2
> 
> 
> org.apache.tika
> tika-bundle
> 1.2
> 
> ..
> 

--
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] [Resolved] (SLING-2956) Store compiled classes in a cluster aware way

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-2956.
-

Resolution: Fixed

Implemented in revision 1501227 by adding the Sling Id to the path if a flag is 
set. I set the flag to default to true

> Store compiled classes in a cluster aware way
> -
>
> Key: SLING-2956
> URL: https://issues.apache.org/jira/browse/SLING-2956
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Affects Versions: JCR Classloader 3.1.12
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR ClassLoader 3.1.14
>
>
> If e.g. jsp compilation is run in a clustered installation, there might be a 
> race condition of two instances trying to compile the same jsp at the same 
> time. This might result in compiled classes written by one instance, getting 
> removed by another instance or errors due to concurrent modifications etc.

--
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] [Created] (SLING-2956) Store compiled classes in a cluster aware way

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-2956:
---

 Summary: Store compiled classes in a cluster aware way
 Key: SLING-2956
 URL: https://issues.apache.org/jira/browse/SLING-2956
 Project: Sling
  Issue Type: Improvement
  Components: JCR
Affects Versions: JCR Classloader 3.1.12
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: JCR ClassLoader 3.1.14


If e.g. jsp compilation is run in a clustered installation, there might be a 
race condition of two instances trying to compile the same jsp at the same 
time. This might result in compiled classes written by one instance, getting 
removed by another instance or errors due to concurrent modifications etc.

--
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

Jenkins build is unstable: sling-trunk-1.6 #1725

[Apache Jenkins Server]

See 

Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling Event Support #1725

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 #97

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #97

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Event Support #97

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #97

[Apache Jenkins Server]

See 

Jenkins build is unstable: sling-trunk-1.6 » Apache Sling Installer Integration Tests #1725

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #97

[Apache Jenkins Server]

See 

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

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2954:
---

Assignee: (was: Robert Munteanu)

> 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] [Updated] (SLING-2954) Event ITs spuriosly fail on Jenkins

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2954:
---

Assignee: Robert Munteanu

> 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

Build failed in Jenkins: sling-trunk-1.6 #1724

[Apache Jenkins Server]

See 

Changes:

[cziegeler] SLING-2913 :  Issue in AbstractCreateOperation#deepGetOrCreateNode 
. Apply patch from Antonio Sanso

[rombert] SLING-2953 - Healthcheck pax-exam setup does not check for
maven.repo.local

--
[...truncated 20170 lines...]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [3.551s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[4.969s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [3.649s]
[INFO] Apache Sling Object Content Mapping ... SUCCESS [5.180s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [1:59.541s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [6.191s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [4.756s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [4.004s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [2.744s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [4.273s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [4.530s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [6.316s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [4.971s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [3.312s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [5.092s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [26.831s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [6.069s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [5.379s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [3.532s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [3.942s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [3.007s]
[INFO] Apache Sling Discovery API  SUCCESS [3.525s]
[INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [4:02.430s]
[INFO] Apache Sling Discovery Support Bundle . SUCCESS [2.921s]
[INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [5.751s]
[INFO] Apache Sling Event Support  FAILURE [8:07.900s]
[INFO] Apache Sling Filesystem Resource Provider . SKIPPED
[INFO] Apache Sling javax.activation bundle .. SKIPPED
[INFO] Apache Sling Settings . SKIPPED
[INFO] Apache Sling Thread Dumper  SKIPPED
[INFO] Apache Sling Web Console Branding . SKIPPED
[INFO] Apache Sling Web Console Security Provider  SKIPPED
[INFO] Apache Sling Groovy Extensions  SKIPPED
[INFO] Apache Sling Explorer . SKIPPED
[INFO] Apache Sling Test Tools ... SKIPPED
[INFO] Apache Sling JUnit Core ... SKIPPED
[INFO] Apache Sling JUnit Scriptable Tests Provider .. SKIPPED
[INFO] Apache Sling JUnit Remote Tests Runners ... SKIPPED
[INFO] Apache Sling Testing Resource Resolver Mock ... SKIPPED
[INFO] Apache Sling Installer  SKIPPED
[INFO] Apache Sling Installer WebConsole Plugin .. SKIPPED
[INFO] Apache Sling File Installer ... SKIPPED
[INFO] Apache Sling JCR Installer  SKIPPED
[INFO] Apache Sling Installer Configuration Admin Support  SKIPPED
[INFO] Apache Sling Deployment Package Installer . SKIPPED
[INFO] Apache Sling Installer Integration Tests .. SKIPPED
[INFO] Apache Sling Launchpad API  SKIPPED
[INFO] Apache Sling Launchpad Base ... SKIPPED
[INFO] Apache Sling Launchpad Installer .. SKIPPED
[INFO] Apache Sling Launchpad Content  SKIPPED
[INFO] Apache Sling Launchpad Application Builder  SKIPPED
[INFO] Apache Sling Sample Server-Side Tests . SKIPPED
[INFO] Apache Sling Failing Server-Side Tests  SKIPPED
[INFO] Apache Sling Sample Integration Tests . SKIPPED
[INFO] Apache Sling Launchpad Testing Services ... SKIPPED
[INFO] Apache Sling Launchpad Testing Services WAR ... SKIPPED
[INFO] Apache Sling Launchpad Testing Fragment Bundle  SKIPPED
[INFO] Apache Sling Launchpad Test Bundles ... SKIPPED
[INFO] Apache Sling Integration Tests  SKIPPED
[INFO] Apache Sling Launchpad Testing  SKIPPED
[INFO] Apache Sling Launchpad Testing WAR version  SKIPPED
[INFO] Apache Sling (Builder)  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 21:48.620s
[INFO] Finished at: Tue Jul

Jenkins build is still unstable: sling-trunk-1.7 #96

[Apache Jenkins Server]

See 

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

[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

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1724

[Apache Jenkins Server]

See 


--
[...truncated 9465 lines...]
09.07.2013 08:29:58.347 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [112] ServiceEvent 
REGISTERED
09.07.2013 08:30:00.440 *INFO* [Apache Sling Job Background Loader] 
org.apache.sling.event Service [QueueMBean for queue test,113] ServiceEvent 
REGISTERED
09.07.2013 08:30:00.441 *INFO* [Apache Sling Job Queue test] 
org.apache.sling.event.impl.jobs.queues.ParallelJobQueue.test Starting job 
queue test
09.07.2013 08:30:05.678 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [112] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.680 *INFO* [CM Event Dispatcher (Fire ConfigurationEvent: 
pid=org.apache.sling.event.jobs.QueueConfiguration.c0fedfa8-d167-4f71-ace8-7200e7b10643)]
 org.apache.sling.event Service 
[org.apache.sling.event.jobs.QueueConfiguration.c0fedfa8-d167-4f71-ace8-7200e7b10643,111]
 ServiceEvent UNREGISTERING
09.07.2013 08:30:05.681 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc BundleEvent STOPPING
09.07.2013 08:30:05.681 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [82] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.682 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [83] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.682 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [84] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.683 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [85] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.683 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [86] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.684 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [87] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.684 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [88] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.685 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [89] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.685 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc Service [90] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.686 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc BundleEvent STOPPED
09.07.2013 08:30:05.686 *INFO* [main] 
org.ops4j.pax.exam.raw.extender.intern.TestBundleObserver Unregistered testcase 
[org.ops4j.pax.exam.raw.extender.intern.Probe@1131561.]
09.07.2013 08:30:05.686 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc BundleEvent UNRESOLVED
09.07.2013 08:30:05.688 *INFO* [main] 
PAXEXAM-PROBE-84c1acd9-e0b3-4a12-a5a9-59ea2b2928fc BundleEvent UNINSTALLED
09.07.2013 08:30:05.689 *INFO* [FelixShutdown] org.apache.felix.framework 
BundleEvent STOPPING
09.07.2013 08:30:05.689 *INFO* [FelixDispatchQueue] org.apache.felix.framework 
FrameworkEvent PACKAGES REFRESHED
09.07.2013 08:30:05.690 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit BundleEvent STOPPING
09.07.2013 08:30:05.690 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit Service [81] ServiceEvent UNREGISTERING
09.07.2013 08:30:05.691 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit BundleEvent STOPPED
09.07.2013 08:30:05.692 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.WebConsolePlugin,100] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.693 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.InventoryPlugin,102] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.694 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.deprecated.JobStatusProviderImpl,101] 
ServiceEvent UNREGISTERING
09.07.2013 08:30:05.695 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.jmx.AllJobStatisticsMBean,104] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.695 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobConsumerManager Updating property provider 
with: 
09.07.2013 08:30:05.697 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobManagerImpl Received topology event 
TopologyEvent [type=PROPERTIES_CHANGED, 
oldView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@cb2157,
 
newView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@cb2157]
09.07.2013 08:30:05.698 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.queues.ParallelJobQueue.test Outdating queue 
test, renaming to test(16385267).
09.07.2013 08:30:05.699 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.deprecated.EventAdminBridge,105] ServiceEvent 
UNREGISTERING
09.07.2013 08:30:05.699 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.job

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #96

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Sample Integration Tests #96

[Apache Jenkins Server]

See 

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

[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

[jira] [Created] (SLING-2955) Unnecessary errors "TopologyViewImpl addInstance: cannot add same instance twice"

[Stefan Egli (JIRA)]

Stefan Egli created SLING-2955:
--

 Summary: Unnecessary errors "TopologyViewImpl addInstance: cannot 
add same instance twice"
 Key: SLING-2955
 URL: https://issues.apache.org/jira/browse/SLING-2955
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Discovery Impl 1.0.0
Reporter: Stefan Egli
Assignee: Stefan Egli


Apparently, adding/removing/adding/removing of instances to/from the cluster 
cause the following unnecessary (and scary) error - while everything works fine:

08.07.2013 17:09:36.513 *ERROR* [Apche Sling JCR Resource Event Queue Processor 
for path '/'] org.apache.sling.discovery.impl.topology.TopologyViewImpl 
addInstance: cannot add same instance twice: an 
InstanceDescription[slindId=23c62a57-2505-410a-9329-7a7f72bdffb4, 
isLeader=true, isOwn=false, clusterViewId=9249b4de-c6ae-4810-a107-efca0d024a7c, 
properties={com.adobe.granite.offloading.infrastructure.osgiconsole.path=/system/console,
 job.consumermanager.whitelist=*, 
org.apache.sling.instance.endpoints=http://./,http://./}]

--
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-2939) 3rd-party based implementation of discovery.api

[Stefan Egli (JIRA)]

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

Stefan Egli commented on SLING-2939:


Hi [~k4j],

Sure, would be great to get more info on Helix! In comparison to Curator I 
considered Curator a better fit than Helix re the requirements.

Basically the requirements are:
 * liveliness detection: be able to detect if an instance is up or not
 * manage a topology structure consisting of clusters and instances
 * cluster leader election ("stable" leader, ie the leader stays until it 
crashes/shuts down)
 * property propagation: each instance can announce properties to the topology, 
so every other instance can read those properties

Cheers,
Stefan

> 3rd-party based implementation of discovery.api
> ---
>
> Key: SLING-2939
> URL: https://issues.apache.org/jira/browse/SLING-2939
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Affects Versions: Discovery API 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>
> The Sling Discovery API introduces the abstraction of a topology which 
> contains (Sling) clusters and instances, supports liveliness-detection, 
> leader-election within a cluster and property-propagation between the 
> instances. As a default and reference implementation a resource-based, OOTB 
> implementation was created (org.apache.sling.discovery.impl).
> Pros and cons of the discovery.impl
> Although the discovery.impl supports everything required in discovery.api, it 
> has a few limitations. Here's a list of pros and cons:
> Pros
> No additional software required (leverages repository for intra-cluster 
> communication/storage and HTTP-REST calls for cross-cluster communication)
> Very small footprint
> Perfectly suited for a single clusters, instance and for small, rather 
> stable hub-based topologies
> Cons
> Config-/deployment-limitations (aka embedded-limitation): connections 
> between clusters are peer-to-peer and explicit. To span a topology, a number 
> of instances must (be made) know (to) each other, changes in the topology 
> typically requires config adjustments to guarantee high availability of the 
> discovery service
> Except if a natural "hub cluster" exists that can serve as connection 
> point for all "satellite clusters"
> Other than that, it is less suited for large and/or dynamic topologies
> Change propagation (for topology parts reported via connectors) is 
> non-atomic and slow, hop-by-hop based
> No guarantee on order of TopologyEvents sent in individual instances - ie 
> different instances might see different orders of TopologyEvents (ie changes 
> in the topology) but eventually the topology is guaranteed to be consistent
> Robustness of discovery.impl wrt storm situations depends on robustness 
> of underlying cluster (not a real negative but discovery.impl might in theory 
> unveil repository bugs which would otherwise not have been a problem)
> Rather new, little tested code which might have issues with edge cases 
> wrt network problems
> although partitioning-support is not a requirement per se, similar 
> edge-cases might exist wrt network-delays/timing/crashes
> Reusing a suitable 3rd party library
> To provide an additional option as implementation of the discovery.api one 
> idea is to use a suitable 3rd party library.
> Requirements
> The following is a list of requirements a 3rd party library must support:
> liveliness detection: detect whether an instance is up and running
> stable leader election within a cluster: stable describes the fact that a 
> leader will remain leader until it leaves/crashes and no new, joining 
> instance shall take over while a leader exists
> stable instance ordering: the list of instances within a cluster is 
> ordered and stable, new, joining instances are put at the end of the list
> property propagation: propagate the properties provided within one 
> instance to everybody in the topology. there are no timing requirements bound 
> to this but the intention of this is not to be used as messaging but to 
> announce config parameters to the topology
> support large, dynamic clusters: configuration of the new discovery 
> implementation should be easy and support frequent changes in the (large) 
> topology
> no single point of failure: this is obvious, there should of course be no 
> single point of failure in the setup
> embedded or dedicated: this might be a hot topic: embedding a library has 
> the advantages of not having to install anything additional. a dedicated 
> service on the other hand requires additional handling in deployment. 
> embedding implies a peer-to-peer setup: nodes communicate peer-to-peer rather 

Re: Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1723

[Robert Munteanu]

On Tue, Jul 9, 2013 at 10:50 AM, Carsten Ziegeler  wrote:
> Yes, the tests pass - I thought maybe jenkins is scanning the log for an
> ERROR message and finds this?
>

That's a guess as good as any other. The previous build passed and it
did not have this error message [1].

I've created [2] to track this.

Robert

[1]: 
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.event/1722/consoleText
[2]: https://issues.apache.org/jira/browse/SLING-2954


> Carsten
>
>
> 2013/7/9 Robert Munteanu 
>
>> On Tue, Jul 9, 2013 at 10:09 AM, Carsten Ziegeler 
>> wrote:
>> > I'm wondering why this is marked as failed?
>> >
>> > Is it because:
>> >
>> > 09.07.2013 06:43:12.354 *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)
>> >
>> > As the test don't need the http service, this isn't really a problem.
>>
>> No, this isn't the cause. I ran the tests locally with port 8080 busy
>> and the they passed, even though the same error was logged.
>>
>> I'm am really not sure why the build fails though, all tests pass.
>>
>> Robert
>>
>
>
>
> --
> Carsten Ziegeler
> cziege...@apache.org

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

[Robert Munteanu (JIRA)]

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 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

Re: Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1723

[Carsten Ziegeler]

Yes, the tests pass - I thought maybe jenkins is scanning the log for an
ERROR message and finds this?

Carsten


2013/7/9 Robert Munteanu 

> On Tue, Jul 9, 2013 at 10:09 AM, Carsten Ziegeler 
> wrote:
> > I'm wondering why this is marked as failed?
> >
> > Is it because:
> >
> > 09.07.2013 06:43:12.354 *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)
> >
> > As the test don't need the http service, this isn't really a problem.
>
> No, this isn't the cause. I ran the tests locally with port 8080 busy
> and the they passed, even though the same error was logged.
>
> I'm am really not sure why the build fails though, all tests pass.
>
> Robert
>



-- 
Carsten Ziegeler
cziege...@apache.org

Re: Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1723

[Robert Munteanu]

On Tue, Jul 9, 2013 at 10:09 AM, Carsten Ziegeler  wrote:
> I'm wondering why this is marked as failed?
>
> Is it because:
>
> 09.07.2013 06:43:12.354 *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)
>
> As the test don't need the http service, this isn't really a problem.

No, this isn't the cause. I ran the tests locally with port 8080 busy
and the they passed, even though the same error was logged.

I'm am really not sure why the build fails though, all tests pass.

Robert

Jenkins build is back to stable : sling-healthcheck-1.6 #44

[Apache Jenkins Server]

See 

[jira] [Resolved] (SLING-2913) Issue in AbstractCreateOperation#deepGetOrCreateNode

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-2913.
-

Resolution: Fixed

Thanks for the patch, Antonio. I've applied it (but tweaked the exception 
message a little bit)

> Issue in AbstractCreateOperation#deepGetOrCreateNode
> 
>
> Key: SLING-2913
> URL: https://issues.apache.org/jira/browse/SLING-2913
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Reporter: Antonio Sanso
>Assignee: Carsten Ziegeler
> Fix For: Servlets Post 2.3.2
>
> Attachments: SLING-2913-patch.txt
>
>
> While updating the AbstractCreateOperation to use new CRUD support in POST 
> servlet has been some lost in translation.
> The previous code looked like 
> {code}
> protected Node deepGetOrCreateNode(Session session, String path,
> Map reqProperties, List 
> changes,
> VersioningConfiguration versioningConfiguration)
> throws RepositoryException {
> if (log.isDebugEnabled()) {
> log.debug("Deep-creating Node '{}'", path);
> }
> if (path == null || !path.startsWith("/")) {
> throw new IllegalArgumentException("path must be an absolute 
> path.");
> }
> // get the starting node
> String startingNodePath = path;
> Node startingNode = null;
> while (startingNode == null) {
> if (startingNodePath.equals("/")) {
> startingNode = session.getRootNode();
> } else if (session.itemExists(startingNodePath)) {
> startingNode = (Node) session.getItem(startingNodePath);
> updateNodeType(session, startingNodePath, reqProperties, 
> changes, versioningConfiguration);
> updateMixins(session, startingNodePath, reqProperties, 
> changes, versioningConfiguration);
> } else {
> int pos = startingNodePath.lastIndexOf('/');
> if (pos > 0) {
> startingNodePath = startingNodePath.substring(0, pos);
> } else {
> startingNodePath = "/";
> }
> }
> }
> {code}
> while the updated is 
> {code}
> protected Resource deepGetOrCreateNode(final ResourceResolver resolver,
> final String path,
> final Map reqProperties,
> final List changes,
> final VersioningConfiguration versioningConfiguration)
> throws PersistenceException, RepositoryException {
> if (log.isDebugEnabled()) {
> log.debug("Deep-creating resource '{}'", path);
> }
> if (path == null || !path.startsWith("/")) {
> throw new IllegalArgumentException("path must be an absolute 
> path.");
> }
> // get the starting resource
> String startingResourcePath = path;
> Resource startingResource = null;
> while (startingResource == null) {
> if (startingResourcePath.equals("/")) {
> startingResource = resolver.getResource("/");
> } else if (resolver.getResource(startingResourcePath) != null) {
> startingResource = resolver.getResource(startingResourcePath);
> updateNodeType(resolver, startingResourcePath, reqProperties, 
> changes, versioningConfiguration);
> updateMixins(resolver, startingResourcePath, reqProperties, 
> changes, versioningConfiguration);
> } else {
> int pos = startingResourcePath.lastIndexOf('/');
> if (pos > 0) {
> startingResourcePath = startingResourcePath.substring(0, 
> pos);
> } else {
> startingResourcePath = "/";
> }
> }
> }
> {code}
> The main difference is in that the 
>  startingNode = session.getRootNode(); could throw a RepositoryException e.g. 
> if the session did not have enough permission while startingResource = 
> resolver.getResource("/"); would just return null.
> This might cause a theoretical infinite loop.

--
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] [Resolved] (SLING-2953) Healthcheck pax-exam setup does not check for maven.repo.local

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-2953.


Resolution: Fixed

Fixed in http://svn.apache.org/viewvc?view=revision&revision=1501114 . Also 
filed upstream issue https://ops4j1.jira.com/browse/PAXEXAM-543

> Healthcheck pax-exam setup does not check for maven.repo.local
> --
>
> Key: SLING-2953
> URL: https://issues.apache.org/jira/browse/SLING-2953
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> To reproduce, run a build locally with -Dmaven.repo.local=/some/other/place. 
> This is similar to SLING-2847 and SLING-2848.

--
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] [Updated] (SLING-2953) Healthcheck pax-exam setup does not check for maven.repo.local

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2953:
---

Summary: Healthcheck pax-exam setup does not check for maven.repo.local  
(was: Healthcheck pax-exam setup does not check for mave.repo.local)

> Healthcheck pax-exam setup does not check for maven.repo.local
> --
>
> Key: SLING-2953
> URL: https://issues.apache.org/jira/browse/SLING-2953
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> To reproduce, run a build locally with -Dmaven.repo.local=/some/other/place. 
> This is similar to SLING-2847 and SLING-2848.

--
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

Jenkins build became unstable: sling-trunk-1.7 #95

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #95

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #95

[Apache Jenkins Server]

See 

[jira] [Assigned] (SLING-2913) Issue in AbstractCreateOperation#deepGetOrCreateNode

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler reassigned SLING-2913:
---

Assignee: Carsten Ziegeler

> Issue in AbstractCreateOperation#deepGetOrCreateNode
> 
>
> Key: SLING-2913
> URL: https://issues.apache.org/jira/browse/SLING-2913
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Reporter: Antonio Sanso
>Assignee: Carsten Ziegeler
> Fix For: Servlets Post 2.3.2
>
> Attachments: SLING-2913-patch.txt
>
>
> While updating the AbstractCreateOperation to use new CRUD support in POST 
> servlet has been some lost in translation.
> The previous code looked like 
> {code}
> protected Node deepGetOrCreateNode(Session session, String path,
> Map reqProperties, List 
> changes,
> VersioningConfiguration versioningConfiguration)
> throws RepositoryException {
> if (log.isDebugEnabled()) {
> log.debug("Deep-creating Node '{}'", path);
> }
> if (path == null || !path.startsWith("/")) {
> throw new IllegalArgumentException("path must be an absolute 
> path.");
> }
> // get the starting node
> String startingNodePath = path;
> Node startingNode = null;
> while (startingNode == null) {
> if (startingNodePath.equals("/")) {
> startingNode = session.getRootNode();
> } else if (session.itemExists(startingNodePath)) {
> startingNode = (Node) session.getItem(startingNodePath);
> updateNodeType(session, startingNodePath, reqProperties, 
> changes, versioningConfiguration);
> updateMixins(session, startingNodePath, reqProperties, 
> changes, versioningConfiguration);
> } else {
> int pos = startingNodePath.lastIndexOf('/');
> if (pos > 0) {
> startingNodePath = startingNodePath.substring(0, pos);
> } else {
> startingNodePath = "/";
> }
> }
> }
> {code}
> while the updated is 
> {code}
> protected Resource deepGetOrCreateNode(final ResourceResolver resolver,
> final String path,
> final Map reqProperties,
> final List changes,
> final VersioningConfiguration versioningConfiguration)
> throws PersistenceException, RepositoryException {
> if (log.isDebugEnabled()) {
> log.debug("Deep-creating resource '{}'", path);
> }
> if (path == null || !path.startsWith("/")) {
> throw new IllegalArgumentException("path must be an absolute 
> path.");
> }
> // get the starting resource
> String startingResourcePath = path;
> Resource startingResource = null;
> while (startingResource == null) {
> if (startingResourcePath.equals("/")) {
> startingResource = resolver.getResource("/");
> } else if (resolver.getResource(startingResourcePath) != null) {
> startingResource = resolver.getResource(startingResourcePath);
> updateNodeType(resolver, startingResourcePath, reqProperties, 
> changes, versioningConfiguration);
> updateMixins(resolver, startingResourcePath, reqProperties, 
> changes, versioningConfiguration);
> } else {
> int pos = startingResourcePath.lastIndexOf('/');
> if (pos > 0) {
> startingResourcePath = startingResourcePath.substring(0, 
> pos);
> } else {
> startingResourcePath = "/";
> }
> }
> }
> {code}
> The main difference is in that the 
>  startingNode = session.getRootNode(); could throw a RepositoryException e.g. 
> if the session did not have enough permission while startingResource = 
> resolver.getResource("/"); would just return null.
> This might cause a theoretical infinite loop.

--
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] [Updated] (SLING-2913) Issue in AbstractCreateOperation#deepGetOrCreateNode

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler updated SLING-2913:


Fix Version/s: Servlets Post 2.3.2

> Issue in AbstractCreateOperation#deepGetOrCreateNode
> 
>
> Key: SLING-2913
> URL: https://issues.apache.org/jira/browse/SLING-2913
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Reporter: Antonio Sanso
> Fix For: Servlets Post 2.3.2
>
> Attachments: SLING-2913-patch.txt
>
>
> While updating the AbstractCreateOperation to use new CRUD support in POST 
> servlet has been some lost in translation.
> The previous code looked like 
> {code}
> protected Node deepGetOrCreateNode(Session session, String path,
> Map reqProperties, List 
> changes,
> VersioningConfiguration versioningConfiguration)
> throws RepositoryException {
> if (log.isDebugEnabled()) {
> log.debug("Deep-creating Node '{}'", path);
> }
> if (path == null || !path.startsWith("/")) {
> throw new IllegalArgumentException("path must be an absolute 
> path.");
> }
> // get the starting node
> String startingNodePath = path;
> Node startingNode = null;
> while (startingNode == null) {
> if (startingNodePath.equals("/")) {
> startingNode = session.getRootNode();
> } else if (session.itemExists(startingNodePath)) {
> startingNode = (Node) session.getItem(startingNodePath);
> updateNodeType(session, startingNodePath, reqProperties, 
> changes, versioningConfiguration);
> updateMixins(session, startingNodePath, reqProperties, 
> changes, versioningConfiguration);
> } else {
> int pos = startingNodePath.lastIndexOf('/');
> if (pos > 0) {
> startingNodePath = startingNodePath.substring(0, pos);
> } else {
> startingNodePath = "/";
> }
> }
> }
> {code}
> while the updated is 
> {code}
> protected Resource deepGetOrCreateNode(final ResourceResolver resolver,
> final String path,
> final Map reqProperties,
> final List changes,
> final VersioningConfiguration versioningConfiguration)
> throws PersistenceException, RepositoryException {
> if (log.isDebugEnabled()) {
> log.debug("Deep-creating resource '{}'", path);
> }
> if (path == null || !path.startsWith("/")) {
> throw new IllegalArgumentException("path must be an absolute 
> path.");
> }
> // get the starting resource
> String startingResourcePath = path;
> Resource startingResource = null;
> while (startingResource == null) {
> if (startingResourcePath.equals("/")) {
> startingResource = resolver.getResource("/");
> } else if (resolver.getResource(startingResourcePath) != null) {
> startingResource = resolver.getResource(startingResourcePath);
> updateNodeType(resolver, startingResourcePath, reqProperties, 
> changes, versioningConfiguration);
> updateMixins(resolver, startingResourcePath, reqProperties, 
> changes, versioningConfiguration);
> } else {
> int pos = startingResourcePath.lastIndexOf('/');
> if (pos > 0) {
> startingResourcePath = startingResourcePath.substring(0, 
> pos);
> } else {
> startingResourcePath = "/";
> }
> }
> }
> {code}
> The main difference is in that the 
>  startingNode = session.getRootNode(); could throw a RepositoryException e.g. 
> if the session did not have enough permission while startingResource = 
> resolver.getResource("/"); would just return null.
> This might cause a theoretical infinite loop.

--
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

Re: Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1723

[Carsten Ziegeler]

I'm wondering why this is marked as failed?

Is it because:

09.07.2013 06:43:12.354 *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)

As the test don't need the http service, this isn't really a problem.

Carsten


2013/7/9 Apache Jenkins Server 

> See <
> https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.event/1723/changes
> >
>
> Changes:
>
> [cziegeler] SLING-2950 :  Disabling the distribution flag takes only
> effect after bundle restart
>
> --
> [...truncated 9463 lines...]
> 09.07.2013 06:49:26.718 *INFO* [main]
> org.apache.sling.event.impl.jobs.JobConsumerManager Updating property
> provider with: /
> 09.07.2013 06:49:26.718 *INFO* [main]
> org.apache.sling.event.impl.jobs.JobManagerImpl Received topology event
> TopologyEvent [type=PROPERTIES_CHANGED,
> oldView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@fbdc7c,
> newView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@fbdc7c
> ]
> 09.07.2013 06:49:26.719 *INFO* [main]
> org.apache.sling.event.impl.jobs.queues.ParallelJobQueue.test Outdating
> queue test, renaming to test(4379095).
> 09.07.2013 06:49:26.719 *INFO* [main]
> org.apache.sling.event.impl.jobs.TopologyCapabilities Detected capabilities
> of 27cdd24a-1f80-4f79-a115-001521e8d6d6 : /
> 09.07.2013 06:49:26.720 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [112]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.721 *INFO* [CM Event Dispatcher (Fire
> ConfigurationEvent:
> pid=org.apache.sling.event.jobs.QueueConfiguration.13628013-f4b2-403f-969a-8dc98e216560)]
> org.apache.sling.event Service
> [org.apache.sling.event.jobs.QueueConfiguration.13628013-f4b2-403f-969a-8dc98e216560,111]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.723 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 BundleEvent STOPPING
> 09.07.2013 06:49:26.723 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [82]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.724 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [83]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.724 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [84]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.725 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [85]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.725 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [86]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.725 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [87]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.726 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [88]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.726 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [89]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.726 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 Service [90]
> ServiceEvent UNREGISTERING
> 09.07.2013 06:49:26.727 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 BundleEvent STOPPED
> 09.07.2013 06:49:26.727 *INFO* [main]
> org.ops4j.pax.exam.raw.extender.intern.TestBundleObserver Unregistered
> testcase [org.ops4j.pax.exam.raw.extender.intern.Probe@de808a.]
> 09.07.2013 06:49:26.727 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 BundleEvent UNRESOLVED
> 09.07.2013 06:49:26.729 *INFO* [main]
> PAXEXAM-PROBE-2de06db9-b6b3-44d4-955b-db9624005172 BundleEvent UNINSTALLED
> 09.07.2013 06:49:26.730 *INFO* [FelixShutdown] org.apache.felix.framework
> BundleEvent STOPPING
> 09.07.2013 06:49:26.730 *INFO* [FelixDispatchQueue]
> org.apache.felix.framework FrameworkEvent PACKAGES REFRESHED
> 09.07.2013 06

[jira] [Created] (SLING-2953) Healthcheck pax-exam setup does not check for mave.repo.local

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-2953:
--

 Summary: Healthcheck pax-exam setup does not check for 
mave.repo.local
 Key: SLING-2953
 URL: https://issues.apache.org/jira/browse/SLING-2953
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Reporter: Robert Munteanu
Assignee: Robert Munteanu


To reproduce, run a build locally with -Dmaven.repo.local=/some/other/place. 
This is similar to SLING-2847 and SLING-2848.

--
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