Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Resource Access Security Integration Tests #2730
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/2730/
Jenkins build is unstable: sling-trunk-1.6 #2730
See https://builds.apache.org/job/sling-trunk-1.6/2730/changes
Re: Any Sling 7 + Java 7 Integration Tests bundles with Pax ?
Hi Dragos, if the settings service is not started, I guess a lot of other services won't start as they depend on it - so the settings service seems to be the root cause. The sling.event bundle works perfectly for me, apart from some sporadic problems it run on Jenkins as well. Are you on windows or what errors do you get when running the ITs? Regards Carsten Am 03.11.14 um 08:16 schrieb Dascalita Dragos: Hi, I'm wondering if there's a bundle that I could use as an example to run Sling 7 during integration-tests. I've been trying to use the example from the SlingPaxOptions - [1] wrapper with Sling 7 bundlelist. While most of the bundles are showing as active, a big number of OSGI components don't start. For instance , org.apache.sling.settings doesn't start any service at all. I can't reference JobManager as it doesn't start either. I can register a basic servlet and that works, so some services work, but not all. There are about 40 components showing up as unsatisfied. I'm listing them bellow - [3] I've been also looking at the org.apache.sling.event bundle - [2], but most of the integration tests are failing as well. Thanks for your help, Dragos [1] - https://github.com/apache/sling/blob/trunk/testing/sling-pax-util/src/main/java/org/apache/sling/paxexam/util/SlingPaxOptions.java [2] - https://github.com/apache/sling/tree/trunk/bundles/extensions/event [3] - List with Unsatisfied components in Sling 7 : org.apache.sling.commons.compiler.impl.EclipseJavaCompiler org.apache.sling.discovery.impl.DiscoveryServiceImpl org.apache.sling.discovery.impl.TopologyWebConsolePlugin org.apache.sling.discovery.impl.cluster.ClusterViewServiceImpl org.apache.sling.discovery.impl.cluster.voting.VotingHandler org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler org.apache.sling.discovery.impl.support.StandardPropertyProvider org.apache.sling.discovery.impl.topology.TopologyChangeHandler org.apache.sling.discovery.impl.topology.announcement.AnnouncementRegistryImpl org.apache.sling.discovery.impl.topology.connector.ConnectorRegistryImpl org.apache.sling.discovery.impl.topology.connector.TopologyConnectorServlet org.apache.sling.engine.impl.SlingSettingsServiceImpl org.apache.sling.engine.impl.log.RequestLoggerService org.apache.sling.engine.parameters org.apache.sling.event.impl.DistributingEventHandler org.apache.sling.event.impl.EnvironmentComponent org.apache.sling.event.impl.dea.DistributedEventReceiver org.apache.sling.event.impl.dea.DistributedEventSender org.apache.sling.event.impl.jobs.console.InventoryPlugin org.apache.sling.event.impl.jobs.console.WebConsolePlugin org.apache.sling.event.impl.jobs.deprecated.EventAdminBridge org.apache.sling.event.impl.jobs.deprecated.JobStatusProviderImpl org.apache.sling.event.impl.jobs.jcr.PersistenceHandler org.apache.sling.event.impl.jobs.jmx.AllJobStatisticsMBean org.apache.sling.event.impl.jobs.tasks.HistoryCleanUpTask org.apache.sling.event.impl.jobs.timed.TimedEventConfiguration org.apache.sling.event.impl.jobs.timed.TimedEventReceiver org.apache.sling.event.impl.jobs.timed.TimedEventSender org.apache.sling.event.jobs.QueueConfiguration org.apache.sling.fsprovider.internal.FsResourceProvider org.apache.sling.installer.provider.jcr.impl.JcrInstaller org.apache.sling.jcr.classloader.internal.DynamicClassLoaderProviderImpl org.apache.sling.jcr.contentloader.internal.ContentLoaderService org.apache.sling.jcr.jackrabbit.server.JndiRegistrationSupport org.apache.sling.jcr.jackrabbit.server.RmiRegistrationSupport org.apache.sling.scripting.jsp.JspScriptEngineFactory org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended - -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Updated] (SLING-4114) Reduce amount of log output from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-4114: -- Attachment: SLING-4114-jsedding-v2.patch Patch without API changes. However, the date/time is omitted from the RPT messages. Reduce amount of log output from RequestProgressTrackerLogFilter - Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.6 Reporter: Julian Sedding Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Event Support #398
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/changes
Jenkins build is still unstable: sling-trunk-1.8 #398
See https://builds.apache.org/job/sling-trunk-1.8/changes
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Resource Access Security Integration Tests #398
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/398/
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling SlingRepository Integration Tests #398
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/398/
Re: Improving the flexibility of RequestProgressTrackerLogFilter
Hi Bertrand Thank you for taking a look. As you observed correctly, the API changes were done to allow more flexibility when rendering the logs. The main objective was avoiding the date/time stamp (e.g. (2014-10-28 10:49:20)) in each line. Because it does not add any information, because the granularity is too coarse, and we already have the millisecond durations. I have attached another patch to SLING-4114 that does not change the API. However, it drops the date/time from the message format. If dropping the date/time from the messages is not acceptable, I can create a slightly more complicated patch. WDYT? Regards Julian On Fri, Oct 31, 2014 at 1:57 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Julian, On Wed, Oct 29, 2014 at 9:42 AM, Julian Sedding jsedd...@gmail.com wrote: ...I propose to reduce the size of the log file by doing the following: 1. changing the log format to include less redundant data 2. allow filtering by request duration 3. allow filtering by request extension(s) sounds good to me! ...I created SLING-4114 [0] with a patch attached that implements these changes. Note that I made some additions to the RequestProgressTracker API. These should be compatible for consumers, so I think they should not do any harm Still, I'm not too happy with requiring changes to the API bundle just for this. IIUC your changes to RequestProgressTracker are only about extracting data from the tracker, as opposed to providing data to it, which is what 99% of the code that uses that API does. So one way to avoid those API bundle changes would be to create a SlingEngineRequestProgressTracker interface (exported) in the engine bundle, which is RequestProgressTracker + niceties that the actual engine provides (your changes). The SlingRequestProgressTracker implements this. As all the reporting is currently done in the engine bundle that's not a problem for Sling itself, the engine just gets the tracker and if it implements SlingEngineRequestProgressTracker uses the additional data. If someone wants to access that data they can do the same. WDYT? -Bertrand
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #1112
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/1112/
Jenkins build became unstable: sling-trunk-1.7 #1112
See https://builds.apache.org/job/sling-trunk-1.7/1112/changes
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Event Support #399
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/399/
Jenkins build is back to stable : sling-trunk-1.8 #399
See https://builds.apache.org/job/sling-trunk-1.8/399/changes
[jira] [Commented] (SLING-3984) JSP Compilation failure under heavy load
[ https://issues.apache.org/jira/browse/SLING-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194398#comment-14194398 ] Viktor Adam commented on SLING-3984: [~cziegeler] We've had a few deployment since my last update and we haven't had this problem so I think you can close this ticket. Thank you for your help! JSP Compilation failure under heavy load Key: SLING-3984 URL: https://issues.apache.org/jira/browse/SLING-3984 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting JSP 2.0.28 Reporter: Viktor Adam Assignee: Carsten Ziegeler Fix For: Scripting JSP 2.1.6 Attachments: Sling_scripting__workaround_for_concurrency_issues_when_compiling.patch, jsp_exception.stacktraces.zip We have seen problems with JSP compilation under heavy load. It looks like when multiple threads try to compile the same JSP or tag file the result can be NoClassDefFoundError, ClassNotFoundException or simply compilation failures (saying method return types not match the expected type, etc.) While I was investigating the issue I have found the following things: First: multiple wrapper instances can exist at the same time for a given JSP file because the caching of them (creating/storing) is not atomic. I have verified that multiple threads can execute the compilation inside the prepareServlet method at the same time. This was my initial prime suspect. Synchronizing access for this method didn't solve all the problems so I have looked into the taglib related parts as taglib related exceptions/errors showed up frequently in stack traces. Finally I've found out that the problem (for us) is around the loadTagFile method of the JspServletWrapper class. This method is invoked from the TagFileProcessor.loadTagFile method which - I believe - again, can have different JspServletWrapper instances for the same taglib at the same time and compiling them concurrently can lead to problems (so it seems). By adding a per-file locking around the body of this method I am no longer able to reproduce the compilation errors, JSP files are compiled correctly. I will attach a patch with my changes to the 2.0.28 version (I haven't found any noticeable changes around this area since) which solved the problems, for us at least. I think I may lock for a larger scope than it is absolutely necessary so maybe someone can advise me on this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3959) Donation of the Sightly and XSS modules
[ https://issues.apache.org/jira/browse/SLING-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-3959: --- Summary: Donation of the Sightly and XSS modules (was: Donation proposal for Sightly and XSS modules) Donation of the Sightly and XSS modules --- Key: SLING-3959 URL: https://issues.apache.org/jira/browse/SLING-3959 Project: Sling Issue Type: Task Components: Scripting Reporter: Radu Cotescu Assignee: Bertrand Delacretaz Attachments: org.apache.sling.scripting.sightly.zip, org.apache.sling.scripting.sightly.zip.sha1, org.apache.sling.xss.zip, org.apache.sling.xss.zip.sha1 This task tracks the donation of the Sightly bundles to Apache Sling. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4127) IP clearance of donated Sightly and XSS modules
Bertrand Delacretaz created SLING-4127: -- Summary: IP clearance of donated Sightly and XSS modules Key: SLING-4127 URL: https://issues.apache.org/jira/browse/SLING-4127 Project: Sling Issue Type: Task Components: General Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz This issue tracks the IP clearance for the SLING-3959 donation of Sightly and XSS modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling SlingRepository Integration Tests #1113
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/1113/
Jenkins build is still unstable: sling-trunk-1.7 #1113
See https://builds.apache.org/job/sling-trunk-1.7/changes
[RESULT][VOTE] accept the donation of the SLING-3959 Sightly and XSS modules
On Thu, Oct 30, 2014 at 4:53 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: ...I'd like to start the vote on accepting the donation of the Sightly and XSS modules attached to SLING-3959... The vote passes with +1s from Robert Munteanu, Carsten Ziegeler, Antonio Sanso and myself, and no other votes. I have created SLING-4127 for the IP clearance, will follow up on that. -Bertrand
Jenkins build became unstable: sling-trunk-1.8 » Apache Sling Event Support #400
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/400/changes
Jenkins build became unstable: sling-trunk-1.8 #400
See https://builds.apache.org/job/sling-trunk-1.8/400/changes
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #1113
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/1113/
[jira] [Created] (SLING-4128) Persisting event trigger should automatically create nuggets path
Tommaso Teofili created SLING-4128: -- Summary: Persisting event trigger should automatically create nuggets path Key: SLING-4128 URL: https://issues.apache.org/jira/browse/SLING-4128 Project: Sling Issue Type: Bug Components: Replication Reporter: Tommaso Teofili Assignee: Tommaso Teofili the _PersistingJcrEventReplicationTrigger_ stores events in a certain (nuggets) path, but if that doesn't exist it fails, without trying to create it. The trigger should try to create that path automatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4128) Persisting event trigger should automatically create nuggets path
[ https://issues.apache.org/jira/browse/SLING-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-4128. Resolution: Fixed fixed in r1636311 Persisting event trigger should automatically create nuggets path - Key: SLING-4128 URL: https://issues.apache.org/jira/browse/SLING-4128 Project: Sling Issue Type: Bug Components: Replication Reporter: Tommaso Teofili Assignee: Tommaso Teofili the _PersistingJcrEventReplicationTrigger_ stores events in a certain (nuggets) path, but if that doesn't exist it fails, without trying to create it. The trigger should try to create that path automatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3984) JSP Compilation failure under heavy load
[ https://issues.apache.org/jira/browse/SLING-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3984. - Resolution: Fixed Thanks [~vadam_ig] JSP Compilation failure under heavy load Key: SLING-3984 URL: https://issues.apache.org/jira/browse/SLING-3984 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting JSP 2.0.28 Reporter: Viktor Adam Assignee: Carsten Ziegeler Fix For: Scripting JSP 2.1.6 Attachments: Sling_scripting__workaround_for_concurrency_issues_when_compiling.patch, jsp_exception.stacktraces.zip We have seen problems with JSP compilation under heavy load. It looks like when multiple threads try to compile the same JSP or tag file the result can be NoClassDefFoundError, ClassNotFoundException or simply compilation failures (saying method return types not match the expected type, etc.) While I was investigating the issue I have found the following things: First: multiple wrapper instances can exist at the same time for a given JSP file because the caching of them (creating/storing) is not atomic. I have verified that multiple threads can execute the compilation inside the prepareServlet method at the same time. This was my initial prime suspect. Synchronizing access for this method didn't solve all the problems so I have looked into the taglib related parts as taglib related exceptions/errors showed up frequently in stack traces. Finally I've found out that the problem (for us) is around the loadTagFile method of the JspServletWrapper class. This method is invoked from the TagFileProcessor.loadTagFile method which - I believe - again, can have different JspServletWrapper instances for the same taglib at the same time and compiling them concurrently can lead to problems (so it seems). By adding a per-file locking around the body of this method I am no longer able to reproduce the compilation errors, JSP files are compiled correctly. I will attach a patch with my changes to the 2.0.28 version (I haven't found any noticeable changes around this area since) which solved the problems, for us at least. I think I may lock for a larger scope than it is absolutely necessary so maybe someone can advise me on this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Resource Access Security Integration Tests #2731
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/2731/
[VOTE] Release Apache Sling Scripting JSP 2.1.6
Hi, we fixed one concurrency issue in the jsp scripting: https://issues.apache.org/jira/browse/SLING-3984 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1147/ 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 1147 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Commented] (SLING-4127) IP clearance of donated Sightly and XSS modules
[ https://issues.apache.org/jira/browse/SLING-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194427#comment-14194427 ] Bertrand Delacretaz commented on SLING-4127: I have prepared the IP clearance document at http://incubator.apache.org/ip-clearance/sling-sightly-xss.html [~radu.cotescu] can you take care of the software grant as per https://www.apache.org/licenses/software-grant.txt ? Best is to include the sha1 digests of SLING-3959 on that document so it's clear what it's about. Once that's recorded I'll update the sling-sightly-xss.html and start the vote on the Incubator PMC list - once that passes we can import the code in the Sling svn repository. IP clearance of donated Sightly and XSS modules --- Key: SLING-4127 URL: https://issues.apache.org/jira/browse/SLING-4127 Project: Sling Issue Type: Task Components: General Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz This issue tracks the IP clearance for the SLING-3959 donation of Sightly and XSS modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4114) Reduce amount of log output from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-4114: -- Attachment: SLING-4114-jsedding-v2.patch Reduce amount of log output from RequestProgressTrackerLogFilter - Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.6 Reporter: Julian Sedding Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4114) Reduce amount of log output from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-4114: -- Attachment: (was: SLING-4114-jsedding-v2.patch) Reduce amount of log output from RequestProgressTrackerLogFilter - Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.6 Reporter: Julian Sedding Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Event Support #401
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/401/
Jenkins build is back to stable : sling-trunk-1.8 #401
See https://builds.apache.org/job/sling-trunk-1.8/401/changes
[jira] [Commented] (SLING-4127) IP clearance of donated Sightly and XSS modules
[ https://issues.apache.org/jira/browse/SLING-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194455#comment-14194455 ] Radu Cotescu commented on SLING-4127: - The software grant form needs to be signed by one of our VPs. Once we have that signature we'll send it to ASF. IP clearance of donated Sightly and XSS modules --- Key: SLING-4127 URL: https://issues.apache.org/jira/browse/SLING-4127 Project: Sling Issue Type: Task Components: General Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz This issue tracks the IP clearance for the SLING-3959 donation of Sightly and XSS modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling SlingRepository Integration Tests #1114
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/1114/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #1114
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/1114/
Jenkins build is still unstable: sling-trunk-1.7 #1114
See https://builds.apache.org/job/sling-trunk-1.7/changes
Re: Any Sling 7 + Java 7 Integration Tests bundles with Pax ?
Hi Dragos, On Mon, Nov 3, 2014 at 8:16 AM, Dascalita Dragos ddrag...@gmail.com wrote: ...I've been trying to use the example from the SlingPaxOptions - [1] wrapper with Sling 7 bundlelist. While most of the bundles are showing as active, a big number of OSGI components don't start... I have adapted that module's tests to use the released Launchpad 7, and all bundles start, the tests pass on my macosx system, but they don't currently check the presence of the SlingSettings service. I'll have a look. FWIW to examine the state of the instance I set a breakpoint in SlingSetupTest.testSlingBundles() and look for those lines in the console output: Running org.apache.sling.paxexam.util.SlingSetupTest ... 8356 [main] INFO org.apache.sling.paxexam.util.SlingPaxOptions - osgi.shell.telnet.port=63850 8356 [main] INFO org.apache.sling.paxexam.util.SlingPaxOptions - org.osgi.service.http.port=63851 ... you can then use those ports to connect to the OSGi console and shell. -Bertrand
Re: Any Sling 7 + Java 7 Integration Tests bundles with Pax ?
Hi, On Mon, Nov 3, 2014 at 12:30 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: ... I have adapted that module's tests to use the released Launchpad 7, and all bundles start, the tests pass on my macosx system, but they don't currently check the presence of the SlingSettings service... Here's a patch that allows SlingSettingsService to start with launchpad 7: https://gist.github.com/bdelacretaz/dee49a174147e066b2b4 The root cause is a missing org.apache.sling.launchpad.api.StartupHandler service, which IIRC is usually provided by the launchpad startup code - the org.apache.sling.launchpad.karaf bundle added in my patch provides this, but it's only a temporary solution. -Bertrand
Jenkins build is back to stable : sling-trunk-1.7 #1115
See https://builds.apache.org/job/sling-trunk-1.7/1115/changes
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Launchpad Testing #1115
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/1115/
[jira] [Commented] (SLING-4106) Cleanup Sling Replication APIs
[ https://issues.apache.org/jira/browse/SLING-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194509#comment-14194509 ] Marius Petria commented on SLING-4106: -- In revision 1636343: adding ConsumerType/ProviderType annotations to replication API Cleanup Sling Replication APIs -- Key: SLING-4106 URL: https://issues.apache.org/jira/browse/SLING-4106 Project: Sling Issue Type: Bug Components: Replication Reporter: Tommaso Teofili Assignee: Tommaso Teofili The Sling Replication API has evolved a lot since its inception so, before the first release, it'd be good to perform a proper review and cleanup to remove the methods / classes that are not needed, avoid exported packages that do not need to be exposed. Also a good thing would be to separate the API itself in a separate bundle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Any Sling 7 + Java 7 Integration Tests bundles with Pax ?
On Mon, Nov 3, 2014 at 12:57 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: ...Here's a patch that allows SlingSettingsService to start with launchpad 7: https://gist.github.com/bdelacretaz/dee49a174147e066b2b4 ... I have now integrated a workaround for the missing StartupHandler, the sling-pax-util tests pass including checking that the org.apache.sling.settings.SlingSettingsService is active. If you write you own tests using SlingPaxOptions you'll need the workaround as in SlingSetupTest.setup() [1], for now. -Bertrand [1] https://svn.apache.org/repos/asf/sling/trunk/testing/sling-pax-util/src/test/java/org/apache/sling/paxexam/util/SlingSetupTest.java
[jira] [Updated] (SLING-4114) Compact and more specific logs from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-4114: --- Summary: Compact and more specific logs from RequestProgressTrackerLogFilter (was: Reduce amount of log output from RequestProgressTrackerLogFilter ) Compact and more specific logs from RequestProgressTrackerLogFilter Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.6 Reporter: Julian Sedding Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-4114) Compact and more specific logs from RequestProgressTrackerLogFilter
[
https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194616#comment-14194616
]
Bertrand Delacretaz commented on SLING-4114:
Thanks, I like this variant - the date/time is not really useful in the RPT
messages anyway as the log message itself does have a timestamp, and the RPT
output includes elapsed time since the request started.
I have applied your patch in http://svn.apache.org/r1636373, thanks for your
contribution!
FWIW here's an example output with the compact format active
{code}
03.11.2014 16:12:56.236 *DEBUG* [0:0:0:0:0:0:0:1 [1415027576194] GET
/.explorer.node.html HTTP/1.1]
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
0 TIMER_START{Request Processing}
0 COMMENT timer_end format is {elapsed msec,timer name} optional
message
0 LOG Method=GET, PathInfo=/.explorer.node.html
0 TIMER_START{ResourceResolution}
0 TIMER_END{0,ResourceResolution} URI=/.explorer.node.html resolves to
Resource=JcrNodeResource, type=sling:redirect, superType=null, path=/
0 LOG Resource Path Info: SlingRequestPathInfo: path='/',
selectorString='explorer.node', extension='html', suffix='null'
0 TIMER_START{ServletResolution}
0 TIMER_START{resolveServlet(JcrNodeResource, type=sling:redirect,
superType=null, path=/)}
2 TIMER_END{2,resolveServlet(JcrNodeResource, type=sling:redirect,
superType=null, path=/)} Using servlet
/libs/sling/servlet/default/explorer/node.esp
2 TIMER_END{2,ServletResolution} URI=/.explorer.node.html handled by
Servlet=/libs/sling/servlet/default/explorer/node.esp
2 LOG Applying Requestfilters
2 LOG Calling filter:
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
2 LOG Applying Componentfilters
2 TIMER_START{/libs/sling/servlet/default/explorer/node.esp#0}
36
TIMER_START{resolveIncludedResource(/.explorer.edit.sling_redirect.html)}
37
TIMER_END{0,resolveIncludedResource(/.explorer.edit.sling_redirect.html)}
path=/.explorer.edit.sling_redirect.html resolves to Resource=JcrNodeResource,
type=sling:redirect, superType=null, path=/
37 LOG Including resource JcrNodeResource, type=sling:redirect,
superType=null, path=/ (SlingRequestPathInfo: path='/',
selectorString='explorer.edit.sling_redirect', extension='html', suffix='null')
37 TIMER_START{resolveServlet(JcrNodeResource, type=sling:redirect,
superType=null, path=/)}
38 TIMER_END{1,resolveServlet(JcrNodeResource, type=sling:redirect,
superType=null, path=/)} Using servlet
/libs/sling/servlet/default/explorer/edit/sling_redirect.esp
38 LOG Applying Includefilters
38
TIMER_START{/libs/sling/servlet/default/explorer/edit/sling_redirect.esp#1}
40
TIMER_END{2,/libs/sling/servlet/default/explorer/edit/sling_redirect.esp#1}
41 TIMER_END{39,/libs/sling/servlet/default/explorer/node.esp#0}
41 TIMER_END{41,Request Processing} Request Processing
{code}
Compact and more specific logs from RequestProgressTrackerLogFilter
Key: SLING-4114
URL: https://issues.apache.org/jira/browse/SLING-4114
Project: Sling
Issue Type: Improvement
Components: Engine
Affects Versions: Engine 2.3.6
Reporter: Julian Sedding
Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch
The RequestProgressTracker currently logs each RPT message as a separate log
entry. Considering the potentially large number of log entries this can add
significantly to the size of log files and the I/O involved.
By logging all RPT messages as a single log entry, the overhead can be
reduced. In addition, filtering by extension and request duration (min/max)
can further reduce the log size (and simplify analysis).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4114) Compact and more specific logs from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-4114: --- Fix Version/s: Engine 2.3.10 Compact and more specific logs from RequestProgressTrackerLogFilter Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.8 Reporter: Julian Sedding Fix For: Engine 2.3.10 Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Improving the flexibility of RequestProgressTrackerLogFilter
Hi Julian, On Mon, Nov 3, 2014 at 10:15 AM, Julian Sedding jsedd...@gmail.com wrote: ...I have attached another patch to SLING-4114 that does not change the API. However, it drops the date/time from the message format... Cool, I like it, it's much better without API bundle changes. I have applied your patch and marked SLING-4114 as fixed. -Bertrand
[jira] [Updated] (SLING-4114) Compact and more specific logs from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-4114: --- Affects Version/s: (was: Engine 2.3.6) Engine 2.3.8 Compact and more specific logs from RequestProgressTrackerLogFilter Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.8 Reporter: Julian Sedding Fix For: Engine 2.3.10 Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4114) Compact and more specific logs from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-4114. Resolution: Fixed Assignee: Bertrand Delacretaz Compact and more specific logs from RequestProgressTrackerLogFilter Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.8 Reporter: Julian Sedding Assignee: Bertrand Delacretaz Fix For: Engine 2.3.10 Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is back to stable : sling-oak-it-1.6 » Apache Sling Launchpad Testing #226
See https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/226/
Jenkins build is back to stable : sling-oak-it-1.6 #226
See https://builds.apache.org/job/sling-oak-it-1.6/226/
Jenkins build became unstable: sling-trunk-1.8 #405
See https://builds.apache.org/job/sling-trunk-1.8/405/changes
Jenkins build became unstable: sling-trunk-1.8 » Apache Sling Launchpad Base #405
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.base/405/
Jenkins build became unstable: sling-trunk-1.8 » Apache Sling Event Support #405
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/405/
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Base #1118
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.base/1118/
Jenkins build became unstable: sling-trunk-1.7 #1118
See https://builds.apache.org/job/sling-trunk-1.7/1118/changes
Re: [VOTE] Release Apache Sling Scripting JSP 2.1.6
On Mon, 2014-11-03 at 11:46 +0100, Carsten Ziegeler wrote: Hi, we fixed one concurrency issue in the jsp scripting: https://issues.apache.org/jira/browse/SLING-3984 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1147/ 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 1147 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... +1 Robert This majority vote is open for at least 72 hours. Regards Carsten
Re: Improving the flexibility of RequestProgressTrackerLogFilter
Hi Bertrand Thanks a lot! I'm looking forward to using the new bundle. Regards Julian On Mon, Nov 3, 2014 at 4:26 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Julian, On Mon, Nov 3, 2014 at 10:15 AM, Julian Sedding jsedd...@gmail.com wrote: ...I have attached another patch to SLING-4114 that does not change the API. However, it drops the date/time from the message format... Cool, I like it, it's much better without API bundle changes. I have applied your patch and marked SLING-4114 as fixed. -Bertrand
Re: [VOTE] Release Slingstart Maven Plugin 1.0.2
On Sun, 2014-11-02 at 14:33 +0100, Carsten Ziegeler wrote: Hi, this release fixes two bugs in the plugin https://issues.apache.org/jira/browse/SLING/fixforversion/12328893 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1146/ 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 1146 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... +1 Robert This majority vote is open for at least 72 hours. Regards Carsten
Re: Any Sling 7 + Java 7 Integration Tests bundles with Pax ?
Hi Carsten, thanks a lot for helping. I'm running the tests on a MacOSX 10.9.5 with Java 7. I've tried to investigate what's making the integration-tests fail but I couldn't figure out the root cause. I can see that Pax URL Aether has issues and the rest of the tests fail to load the cached bundle, but by looking at the logs I don't understand what's causing this. I'm pasting bellow the error that I'm getting in case it helps. Thanks, Dragos -- Forking command line: /bin/sh -c cd /Projects/sling-git/bundles/extensions/event /Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/bin/java -Xmx2048m -XX:MaxPermSize=512m -jar /Projects/sling-git/bundles/extensions/event/target/surefire/surefirebooter3647465897455320849.jar /Projects/sling-git/bundles/extensions/event/target/surefire/surefire6539308234963726488tmp /Projects/sling-git/bundles/extensions/event/target/surefire/surefire_05376957598267243956tmp Running org.apache.sling.event.it.ChaosTest 21 [main] INFO org.ops4j.pax.exam.spi.DefaultExamSystem - Pax Exam System (Version: 3.5.0) created. 63 [main] INFO org.ops4j.pax.exam.junit.impl.ProbeRunner - creating PaxExam runner for class org.apache.sling.event.it.ChaosTest 97 [main] INFO org.ops4j.pax.exam.junit.impl.ProbeRunner - running test class org.apache.sling.event.it.ChaosTest 155 [main] INFO org.ops4j.exec.DefaultJavaRunner - DefaultJavaRunner completed successfully 633 [main] INFO org.ops4j.pax.exam.spi.reactors.ReactorManager - suite finished Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.644 sec FAILURE! - in org.apache.sling.event.it.ChaosTest testDoChaos(org.apache.sling.event.it.ChaosTest) Time elapsed: 0.524 sec ERROR! java.lang.NullPointerException: null at org.ops4j.pax.url.mvn.internal.config.MavenConfigurationImpl.getRepositories(MavenConfigurationImpl.java:251) at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.selectRepositories(AetherBasedResolver.java:191) at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:310) at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:296) at org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:131) at java.net.URL.openStream(URL.java:1037) [...] Running org.apache.sling.event.it.ClassloadingTest 634 [main] INFO org.ops4j.pax.exam.junit.impl.ProbeRunner - creating PaxExam runner for class org.apache.sling.event.it.ClassloadingTest 636 [main] INFO org.ops4j.pax.exam.junit.impl.ProbeRunner - running test class org.apache.sling.event.it.ClassloadingTest 643 [main] INFO org.ops4j.exec.DefaultJavaRunner - DefaultJavaRunner completed successfully ERROR: Error reloading cached bundle, removing it: /var/folders/8c/ky5brl215fd08njt72pz9qy0gq/T/1415035146773-0/bundles (java.lang.NumberFormatException: For input string: s) java.lang.NumberFormatException: For input string: s at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Long.parseLong(Long.java:441) at java.lang.Long.parseLong(Long.java:483) at org.apache.felix.framework.cache.BundleArchive.readId(BundleArchive.java:1077) at org.apache.felix.framework.cache.BundleArchive.readBundleInfo(BundleArchive.java:972) at org.apache.felix.framework.cache.BundleArchive.init(BundleArchive.java:182) at org.apache.felix.framework.cache.BundleCache.getArchives(BundleCache.java:247) at org.apache.felix.framework.Felix.init(Felix.java:713) at org.apache.felix.framework.Felix.start(Felix.java:901) at org.ops4j.pax.swissbox.framework.RemoteFrameworkImpl.start(RemoteFrameworkImpl.java:98) at org.ops4j.pax.swissbox.framework.RemoteFrameworkImpl.main(RemoteFrameworkImpl.java:434) 973 [main] INFO org.ops4j.exec.DefaultJavaRunner - DefaultJavaRunner completed successfully
Re: Any Sling 7 + Java 7 Integration Tests bundles with Pax ?
Bertrand, thank you very much ! I wouldn't have guessed the StartupHandler issue by myself. After adding the @Before and @After methods I can now see most of the components resolving. There are only 4 that don't resolve now, but they don't resolve either when I run the launchpad-standalone-[1] on my machine so I can conclude that this issue it's not related to the setup of the test. These components are: - org.apache.sling.engine.impl.log.RequestLoggerService - org.apache.sling.event.jobs.QueueConfiguration - org.apache.sling.fsprovider.internal.FsResourceProvider [Unsatisfied,Service Name: org.osgi.service.event.EventAdmin] - org.apache.sling.jcr.jackrabbit.server.JndiRegistrationSupport AND org.apache.sling.jcr.jackrabbit.server.RmiRegistrationSupport [Unsatisfied,Service Name: javax.jcr.Repository] [Unsatisfied,Service Name: org.osgi.service.log.LogService] But these don't block my integration tests at the moment. Thanks a lot for helping me with this issue, Dragos [1] - http://central.maven.org/maven2/org/apache/sling/org.apache.sling.launchpad/7/org.apache.sling.launchpad-7-standalone.jar On Mon, Nov 3, 2014 at 6:17 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Nov 3, 2014 at 12:57 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: ...Here's a patch that allows SlingSettingsService to start with launchpad 7: https://gist.github.com/bdelacretaz/dee49a174147e066b2b4 ... I have now integrated a workaround for the missing StartupHandler, the sling-pax-util tests pass including checking that the org.apache.sling.settings.SlingSettingsService is active. If you write you own tests using SlingPaxOptions you'll need the workaround as in SlingSetupTest.setup() [1], for now. -Bertrand [1] https://svn.apache.org/repos/asf/sling/trunk/testing/sling-pax-util/src/test/java/org/apache/sling/paxexam/util/SlingSetupTest.java
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling SlingRepository Integration Tests #2733
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/2733/
Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Resource Access Security Integration Tests #2733
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/2733/ -- [INFO] [INFO] [INFO] Building Apache Sling Resource Access Security Integration Tests 0.0.1-SNAPSHOT [INFO] Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.testing.tools/1.0.7-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.testing.tools/1.0.7-SNAPSHOT/maven-metadata.xml (1010 B at 3.8 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.testing.tools/1.0.7-SNAPSHOT/org.apache.sling.testing.tools-1.0.7-20140715.081043-1.pom Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.testing.tools/1.0.7-SNAPSHOT/org.apache.sling.testing.tools-1.0.7-20140715.081043-1.pom (5 KB at 22.4 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-osgi/4.1.2/httpclient-osgi-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-osgi/4.1.2/httpclient-osgi-4.1.2.pom (7 KB at 126.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.1.2/httpcomponents-client-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.1.2/httpcomponents-client-4.1.2.pom (12 KB at 317.7 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.1.2/httpclient-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.1.2/httpclient-4.1.2.pom (6 KB at 153.9 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore/4.1.2/httpcore-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore/4.1.2/httpcore-4.1.2.pom (8 KB at 206.2 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.1.2/httpcomponents-core-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.1.2/httpcomponents-core-4.1.2.pom (10 KB at 265.8 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.1.2/httpmime-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpmime/4.1.2/httpmime-4.1.2.pom (6 KB at 154.2 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-cache/4.1.2/httpclient-cache-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient-cache/4.1.2/httpclient-cache-4.1.2.pom (7 KB at 182.6 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-osgi/4.1.2/httpcore-osgi-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-osgi/4.1.2/httpcore-osgi-4.1.2.pom (4 KB at 66.2 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-nio/4.1.2/httpcore-nio-4.1.2.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore-nio/4.1.2/httpcore-nio-4.1.2.pom (6 KB at 104.2 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/maven-metadata.xml Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/org.apache.sling.launchpad-7-SNAPSHOT.pom [WARNING] The POM for org.apache.sling:org.apache.sling.launchpad:jar:standalone:7-SNAPSHOT is missing, no dependency information available Downloading: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-api/1.7.6/slf4j-api-1.7.6.pom Downloaded: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-api/1.7.6/slf4j-api-1.7.6.pom (3 KB at 71.0 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-parent/1.7.6/slf4j-parent-1.7.6.pom Downloaded: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-parent/1.7.6/slf4j-parent-1.7.6.pom (12 KB at 323.0 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-simple/1.7.6/slf4j-simple-1.7.6.pom Downloaded: http://repo.maven.apache.org/maven2/org/slf4j/slf4j-simple/1.7.6/slf4j-simple-1.7.6.pom (2 KB at 41.1 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/jackrabbit-api/2.7.5/jackrabbit-api-2.7.5.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/jackrabbit/jackrabbit-api/2.7.5/jackrabbit-api-2.7.5.pom (4 KB at 49.1 KB/sec) Downloading:
Build failed in Jenkins: sling-trunk-1.6 #2733
See https://builds.apache.org/job/sling-trunk-1.6/2733/changes Changes: [bdelacretaz] SLING-4114 - Compact and more specific logs from RequestProgressTrackerLogFilter - contributed by Julian Sedding, thanks! [bdelacretaz] Add local StartupHandler so that SlingSettingsService starts [mpetria] SLING-4106: adding ConsumerType/ProviderType annotations to replication API [bdelacretaz] Use released Sling Launchpad 7 and adapt bundle lists -- [...truncated 49809 lines...] [INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [30.188s] [INFO] Apache Sling Commons Java Compiler SUCCESS [21.124s] [INFO] Apache Sling JSON Library . SUCCESS [20.804s] [INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [54.812s] [INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [15.243s] [INFO] Apache Sling MIME type mapping support SUCCESS [17.365s] [INFO] Apache Sling Commons OSGi support . SUCCESS [21.118s] [INFO] Apache Sling Scheduler Support SUCCESS [17.787s] [INFO] Apache Sling Testing Utilities SUCCESS [32.856s] [INFO] Apache Sling Thread Dumper SUCCESS [14.621s] [INFO] Apache Sling Thread Support ... SUCCESS [18.115s] [INFO] Apache Sling Authentication Service ... SUCCESS [18.725s] [INFO] Apache Sling Form Based Authentication Handler SUCCESS [23.974s] [INFO] Apache Sling Engine Implementation SUCCESS [33.390s] [INFO] Apache Sling Repository API Bundle SUCCESS [18.735s] [INFO] Apache Sling JCR Base Bundle .. SUCCESS [18.256s] [INFO] Apache Sling JCR ClassLoader .. SUCCESS [20.400s] [INFO] Apache Sling Initial Content Loader ... SUCCESS [23.601s] [INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [33.601s] [INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [20.351s] [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SUCCESS [17.456s] [INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [14.654s] [INFO] Apache Sling JCR Resource Resolver SUCCESS [53.974s] [INFO] Apache Sling JCR Repository Registration .. SUCCESS [17.818s] [INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [15.513s] [INFO] Apache Sling DavEx Access to repositories . SUCCESS [20.603s] [INFO] Apache Sling JCR WebConsole Bundle SUCCESS [17.762s] [INFO] Apache Sling Oak Repository Server SUCCESS [21.132s] [INFO] Apache Sling SlingRepository Integration Tests SUCCESS [23.658s] [INFO] Apache Sling Servlet Resolver . SUCCESS [21.681s] [INFO] Apache Sling Default GET Servlets . SUCCESS [20.141s] [INFO] Apache Sling Default POST Servlets SUCCESS [23.802s] [INFO] Apache Sling Compat Servlets .. SUCCESS [13.997s] [INFO] Apache Sling Scripting Implementation API . SUCCESS [14.986s] [INFO] Apache Sling Scripting Core implementation SUCCESS [27.116s] [INFO] Apache Sling Scripting JavaScript Support . SUCCESS [27.050s] [INFO] Apache Sling Scripting JSP Support SUCCESS [33.054s] [INFO] Apache Sling JSP Tag Library .. SUCCESS [23.072s] [INFO] Apache Sling JSP Standard Tag Library . SUCCESS [15.352s] [INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [20.595s] [INFO] Apache Sling Bundle Resource Provider . SUCCESS [15.114s] [INFO] Apache Sling Distributed Event Admin .. SUCCESS [20.830s] [INFO] Apache Sling Discovery API SUCCESS [14.930s] [INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [3:15.079s] [INFO] Apache Sling Discovery Support Bundle . SUCCESS [14.951s] [INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [14.906s] [INFO] Apache Sling Event Support SUCCESS [12:21.310s] [INFO] Apache Sling Feature Flags SUCCESS [17.700s] [INFO] Apache Sling Filesystem Resource Provider . SUCCESS [17.819s] [INFO] Apache Sling javax.activation bundle .. SUCCESS [15.074s] [INFO] Apache Sling Service User Mapper .. SUCCESS [23.659s] [INFO] Apache Sling Settings . SUCCESS [17.763s] [INFO] Apache Sling Web Console Branding . SUCCESS [17.811s] [INFO] Apache Sling Web Console Security Provider SUCCESS [18.027s] [INFO] Apache Sling Explorer . SUCCESS [14.942s] [INFO] Apache Sling Health Check Core SUCCESS [24.524s] [INFO] Apache Sling Health Check Annotations . SUCCESS [15.003s] [INFO] Apache Sling Health Check Samples . SUCCESS
Jenkins build is still unstable: sling-trunk-1.8 #406
See https://builds.apache.org/job/sling-trunk-1.8/changes
Jenkins build became unstable: sling-trunk-1.8 » Apache Sling SlingRepository Integration Tests #406
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/406/
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Launchpad Base #406
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.base/406/
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Event Support #406
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/406/
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #1119
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/1119/
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Launchpad Base #1119
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.base/1119/
Jenkins build is still unstable: sling-trunk-1.7 #1119
See https://builds.apache.org/job/sling-trunk-1.7/changes
Build failed in Jenkins: sling-trunk-1.6 #2734
See https://builds.apache.org/job/sling-trunk-1.6/2734/changes Changes: [rombert] Use released version of the launchpad in ITs -- [...truncated 64135 lines...] [INFO] Apache Sling Commons Java Compiler SUCCESS [21.007s] [INFO] Apache Sling JSON Library . SUCCESS [20.826s] [INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [59.606s] [INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [15.152s] [INFO] Apache Sling MIME type mapping support SUCCESS [20.843s] [INFO] Apache Sling Commons OSGi support . SUCCESS [18.050s] [INFO] Apache Sling Scheduler Support SUCCESS [17.191s] [INFO] Apache Sling Testing Utilities SUCCESS [26.879s] [INFO] Apache Sling Thread Dumper SUCCESS [17.953s] [INFO] Apache Sling Thread Support ... SUCCESS [14.762s] [INFO] Apache Sling Authentication Service ... SUCCESS [18.289s] [INFO] Apache Sling Form Based Authentication Handler SUCCESS [21.005s] [INFO] Apache Sling Engine Implementation SUCCESS [34.138s] [INFO] Apache Sling Repository API Bundle SUCCESS [14.133s] [INFO] Apache Sling JCR Base Bundle .. SUCCESS [17.780s] [INFO] Apache Sling JCR ClassLoader .. SUCCESS [14.859s] [INFO] Apache Sling Initial Content Loader ... SUCCESS [17.878s] [INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [33.126s] [INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [17.973s] [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SUCCESS [14.964s] [INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [15.058s] [INFO] Apache Sling JCR Resource Resolver SUCCESS [51.098s] [INFO] Apache Sling JCR Repository Registration .. SUCCESS [14.958s] [INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [17.972s] [INFO] Apache Sling DavEx Access to repositories . SUCCESS [18.064s] [INFO] Apache Sling JCR WebConsole Bundle SUCCESS [15.057s] [INFO] Apache Sling Oak Repository Server SUCCESS [20.759s] [INFO] Apache Sling SlingRepository Integration Tests SUCCESS [29.416s] [INFO] Apache Sling Servlet Resolver . SUCCESS [19.846s] [INFO] Apache Sling Default GET Servlets . SUCCESS [20.187s] [INFO] Apache Sling Default POST Servlets SUCCESS [24.042s] [INFO] Apache Sling Compat Servlets .. SUCCESS [17.216s] [INFO] Apache Sling Scripting Implementation API . SUCCESS [14.095s] [INFO] Apache Sling Scripting Core implementation SUCCESS [32.382s] [INFO] Apache Sling Scripting JavaScript Support . SUCCESS [27.241s] [INFO] Apache Sling Scripting JSP Support SUCCESS [24.266s] [INFO] Apache Sling JSP Tag Library .. SUCCESS [24.213s] [INFO] Apache Sling JSP Standard Tag Library . SUCCESS [15.325s] [INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [20.651s] [INFO] Apache Sling Bundle Resource Provider . SUCCESS [15.118s] [INFO] Apache Sling Distributed Event Admin .. SUCCESS [21.059s] [INFO] Apache Sling Discovery API SUCCESS [14.844s] [INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [3:02.544s] [INFO] Apache Sling Discovery Support Bundle . SUCCESS [15.451s] [INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [12.715s] [INFO] Apache Sling Event Support SUCCESS [11:39.485s] [INFO] Apache Sling Feature Flags SUCCESS [14.458s] [INFO] Apache Sling Filesystem Resource Provider . SUCCESS [15.191s] [INFO] Apache Sling javax.activation bundle .. SUCCESS [15.067s] [INFO] Apache Sling Service User Mapper .. SUCCESS [17.952s] [INFO] Apache Sling Settings . SUCCESS [15.374s] [INFO] Apache Sling Web Console Branding . SUCCESS [14.800s] [INFO] Apache Sling Web Console Security Provider SUCCESS [15.016s] [INFO] Apache Sling Explorer . SUCCESS [15.243s] [INFO] Apache Sling Health Check Core SUCCESS [21.032s] [INFO] Apache Sling Health Check Annotations . SUCCESS [14.838s] [INFO] Apache Sling Health Check Samples . SUCCESS [18.164s] [INFO] Apache Sling Health Check Support Components .. SUCCESS [15.514s] [INFO] Apache Sling Health Check Webconsole Plugin ... SUCCESS [17.427s] [INFO] Apache Sling Health Check JUnit Bridge SUCCESS [17.804s] [INFO] Apache Sling Health Check Integration Tests ... SUCCESS [32.789s] [INFO] Apache Sling Health Check Reactor POM . SUCCESS [9.207s]
Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling Resource Access Security Integration Tests #2734
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.resourceaccesssecurity.it/2734/changes
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling SlingRepository Integration Tests #2734
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/2734/
Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Sample Integration Tests #2734
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.testing.samples.integrationtests/2734/ -- [INFO] [INFO] [INFO] Building Apache Sling Sample Integration Tests 1.0.7-SNAPSHOT [INFO] Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.junit.scriptable/1.0.8/org.apache.sling.junit.scriptable-1.0.8.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.junit.scriptable/1.0.8/org.apache.sling.junit.scriptable-1.0.8.pom (5 KB at 42.9 KB/sec) Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.servlets.post/2.3.4/org.apache.sling.servlets.post-2.3.4.pom Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.servlets.post/2.3.4/org.apache.sling.servlets.post-2.3.4.pom (7 KB at 77.6 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/maven-metadata.xml Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/org.apache.sling.launchpad-7-SNAPSHOT.pom [WARNING] The POM for org.apache.sling:org.apache.sling.launchpad:jar:standalone:7-SNAPSHOT is missing, no dependency information available Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.servlets.post/2.3.4/org.apache.sling.servlets.post-2.3.4.jar Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.servlets.post/2.3.4/org.apache.sling.servlets.post-2.3.4.jar (139 KB at 755.1 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/org.apache.sling.launchpad-7-SNAPSHOT-standalone.jar [JENKINS] Archiving disabled
Re: [VOTE] Release Apache Sling Scripting JSP 2.1.6
+1 On 3 Nov 2014 05:46, Carsten Ziegeler cziege...@apache.org wrote: Hi, we fixed one concurrency issue in the jsp scripting: https://issues.apache.org/jira/browse/SLING-3984 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1147/ 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 1147 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
