[jira] [Updated] (SLING-3699) [Job Scheduling] A job scheduled using JobBuilder does not get removed if the JobConsumer returns JobResult.OK
[ https://issues.apache.org/jira/browse/SLING-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshika Agarwal updated SLING-3699: --- Description: Behavior: If we schedule a job to be executed at a specific time for a topic using: JobBuilder jobBuilder = jobManager.createJob(EVENT_TOPIC); jobBuilder.properties(props).schedule().at(activationTime).add(); It first creates a node of type slingevent:TimedEvent in crx repository under /var/eventing/scheduled-jobs and when the exact time arrives (in this case activationTime), a node of type slingevent:Job gets created under assigned jobs and posts an event to the JobConsumer. Issue: When the JobConsumer returns JobResult.OK the node of type slingevent:TimedEvent (scheduled job) does not get removed from the list. Due to this issue, when the server restarts, all the jobs that were earlier scheduled and had finished with their execution, get executed again to become nodes of type slingevent:Job and again post an event to the JobConsumer. This happens for all the jobs scheduled for a time that is before the current time (when the server restarts) Desired: Although, we wish to have the scheduled jobs to persist even after the server restarts, but only the jobs that have not yet been executed should be executed after restart. This implies that all the jobs that are executed should be removed from the list of scheduled jobs once the JobConsumer gets the control. was: Behavior: If we schedule a job to be executed at a specific time for a topic using: JobBuilder jobBuilder = jobManager.createJob(EVENT_TOPIC); jobBuilder.properties(props).schedule().at(activationTime).add(); It first creates a node of type slingevent:TimedEvent in crx repository under /var/eventing/scheduled-jobs and when the exact time arrives (in this case activationTime), a node of type slingevent:Job gets created under assigned jobs and posts an event to the JobConsumer. Issue: When the JobConsumer returns JobResult.OK the node of type slingevent:TimedEvent (scheduled job) does not get removed from the list. Due to this issue, when the server restarts, all the jobs that were earlier scheduled and had finished with their execution, get executed again to become nodes of type slingevent:Job and again post an event to the JobConsumer. This happens for all the jobs scheduled for a time that is before the current time (when the server restarts) Desired: Although, we wish to have the scheduled jobs to persist even after the server restarts, but only the jobs that have not yet been executed should be executed after restart. This implies that all the jobs that are executed should be removed from the list of scheduled jobs once the JobConsumer returns JobResult.OK [Job Scheduling] A job scheduled using JobBuilder does not get removed if the JobConsumer returns JobResult.OK -- Key: SLING-3699 URL: https://issues.apache.org/jira/browse/SLING-3699 Project: Sling Issue Type: Bug Components: API Reporter: Anshika Agarwal Priority: Critical Labels: scheduler, scheduling Behavior: If we schedule a job to be executed at a specific time for a topic using: JobBuilder jobBuilder = jobManager.createJob(EVENT_TOPIC); jobBuilder.properties(props).schedule().at(activationTime).add(); It first creates a node of type slingevent:TimedEvent in crx repository under /var/eventing/scheduled-jobs and when the exact time arrives (in this case activationTime), a node of type slingevent:Job gets created under assigned jobs and posts an event to the JobConsumer. Issue: When the JobConsumer returns JobResult.OK the node of type slingevent:TimedEvent (scheduled job) does not get removed from the list. Due to this issue, when the server restarts, all the jobs that were earlier scheduled and had finished with their execution, get executed again to become nodes of type slingevent:Job and again post an event to the JobConsumer. This happens for all the jobs scheduled for a time that is before the current time (when the server restarts) Desired: Although, we wish to have the scheduled jobs to persist even after the server restarts, but only the jobs that have not yet been executed should be executed after restart. This implies that all the jobs that are executed should be removed from the list of scheduled jobs once the JobConsumer gets the control. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3693) Repository import wizard blocks UI thread and is not cancellable
[ https://issues.apache.org/jira/browse/SLING-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3693: --- Fix Version/s: (was: Sling Eclipse IDE 1.0.2) Sling Eclipse IDE 1.0.0 Repository import wizard blocks UI thread and is not cancellable Key: SLING-3693 URL: https://issues.apache.org/jira/browse/SLING-3693 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 For large import jobs, the import wizard dialog looks unresponsive, since it is executed in the UI thread and it does not allow cancellation. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3687) The selected project is not configured with/added to any Sling server during Sling Import or Export
[
https://issues.apache.org/jira/browse/SLING-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-3687:
---
Fix Version/s: (was: Sling Eclipse IDE 1.0.2)
Sling Eclipse IDE 1.0.0
The selected project is not configured with/added to any Sling server
during Sling Import or Export
-
Key: SLING-3687
URL: https://issues.apache.org/jira/browse/SLING-3687
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.0
Reporter: Konrad Windszus
Assignee: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.0
Attachments: SLING-3687.png
Although the module was already added to the Sling Server (and was even
synchronized and therefore obviously has the right facets), I can neither
user Export nor Import because both wizards fail with the message
{code}
The selected project is not configured with/added to any Sling server
{code}
Please compare with the attached screenshot. Enabling the tracing does not
reveal any other log statements related to that.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (SLING-3694) Full coverage nodes are imported without the XML extension
[
https://issues.apache.org/jira/browse/SLING-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-3694:
---
Fix Version/s: (was: Sling Eclipse IDE 1.0.2)
Sling Eclipse IDE 1.0.0
Full coverage nodes are imported without the XML extension
--
Key: SLING-3694
URL: https://issues.apache.org/jira/browse/SLING-3694
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.0.0
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.0
When importing content from the repository full coverage nodes ( e.g. those
with primary type {{sling:OsgiConfig}} ) are imported without extension.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 6/26/14 8:25 AM:
-
For reference, this is the current release process:
Some notes:
* force build a qualifier by adding the followin in the reactor pom (
pluginManagement )
{code}
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-packaging-plugin/artifactId
version${tycho.version}/version
configuration
format'RELEASE'/format
/configuration
/plugin
{code}
* manually tag in svn {{svn copy
https://svn.apache.org/repos/asf/sling/trunk/tooling/ide
https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.0}}
* build the project with p2 signing enabled {{mvn clean install -Psign}} . This
also runs all the integration tests and checks the licenses on all files
* build only a src archive {{mvn -Psource-release assembly:single antrun:run
-Dtycho.mode=maven -Dusername=rombert -Djira.fixVersion=12324873
-Djira.fixedIssues=140}}
* manually gpg-sign the src archive and the checksums
* upload for testing on the dist/dev tree ( see
https://www.apache.org/dev/release.html#host-rc ).
** src zip file
* call the vote ( updated email template )
* remove the build qualifier from trunk
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.2-SNAPSHOT}}
* if the vote is successful
** remove the files drom dist/dev
** move the files to dist/dev
** upload the p2 update site (exploded/archived ) to
https://dist.apache.org/repos/dist/release/sling/eclipse ( *.zip, /update )
was (Author: rombert):
For reference, this is the current release process:
Some notes:
* force build a qualifier by adding the followin in the reactor pom (
pluginManagement )
{code}
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-packaging-plugin/artifactId
version${tycho.version}/version
configuration
format'RELEASE'/format
/configuration
/plugin
{code}
* manually tag in svn {{svn copy
https://svn.apache.org/repos/asf/sling/trunk/tooling/ide
https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.0}}
* build the file with p2 signing enabled {{mvn clean install -Psign}}
* build only a src archive {{mvn -Psource-release assembly:single antrun:run
-Dtycho.mode=maven -Dusername=rombert -Djira.fixVersion=12324873
-Djira.fixedIssues=140}}
** the build might fail ... but it's only required for the reactor to be built
* manually gpg-sign the src archive and the checksums
* upload for testing on the dist/dev tree ( see
https://www.apache.org/dev/release.html#host-rc ).
** src zip file
* call the vote ( updated email template )
* remove the build qualifier from trunk
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.2-SNAPSHOT}}
* if the vote is successful
** remove the files drom dist/dev
** move the files to dist/dev
** upload the p2 update site (exploded/archived ) to
https://dist.apache.org/repos/dist/release/sling/eclipse ( *.zip, /update )
Document and further automate the IDE tooling release process
-
Key: SLING-3685
URL: https://issues.apache.org/jira/browse/SLING-3685
Project: Sling
Issue Type: Task
Components: IDE
Reporter: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.2
The current release process is very much manual, due to some of tycho's
peculiarities ( see also SLING-3620 ). This task tracks the documentation of
this release process and possible automation enhancements.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (SLING-3697) Incorrect handling of deeply nested aggregates
[ https://issues.apache.org/jira/browse/SLING-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3697: --- Fix Version/s: (was: Sling Eclipse IDE 1.0.2) Sling Eclipse IDE 1.0.0 Incorrect handling of deeply nested aggregates -- Key: SLING-3697 URL: https://issues.apache.org/jira/browse/SLING-3697 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 With SLING-3656 we now have improved handling of structures serialized under nt:file/nt:resource nodes. For such derived nodes, Vault uses a concept called leaf aggregates, tied to a main aggregate. It has become apparent that our handling of leaf aggregates is insufficient, for two reasons: * when looking for a leaf aggregate, we don't descend into nested leaf aggregates * when calculating the filesystem path of an aggregate which is built from a leaf, we always assume that it has a single parent -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (SLING-3685) Document and further automate the IDE tooling release process
[
https://issues.apache.org/jira/browse/SLING-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040663#comment-14040663
]
Robert Munteanu edited comment on SLING-3685 at 6/26/14 8:26 AM:
-
For reference, this is the current release process:
Some notes:
* force build a qualifier by adding the followin in the reactor pom (
pluginManagement )
{code}
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-packaging-plugin/artifactId
version${tycho.version}/version
configuration
format'RELEASE'/format
/configuration
/plugin
{code}
* manually tag in svn {{svn copy
https://svn.apache.org/repos/asf/sling/trunk/tooling/ide
https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.0}}
* build the project with p2 signing enabled {{mvn clean install -Psign}} . This
also runs all the integration tests and checks the licenses on all files
* build only a src archive {{mvn -Psource-release assembly:single antrun:run
-Dtycho.mode=maven -Dusername=rombert -Djira.fixVersion=12324873
-Djira.fixedIssues=140}}
* manually gpg-sign the src archive and the checksums
* upload the src zip file with checksums and signatures for testing on the
dist/dev tree ( see https://www.apache.org/dev/release.html#host-rc ).
* call the vote ( updated email template )
* remove the build qualifier from trunk
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.2-SNAPSHOT}}
* if the vote is successful
** remove the files from dist/dev
** move the files to dist/dev
** upload the p2 update site (exploded/archived ) to
https://dist.apache.org/repos/dist/release/sling/eclipse ( *.zip, /update )
* if the vote is not successful
** remove the files from dist/dev
** remove the tag from SVN
was (Author: rombert):
For reference, this is the current release process:
Some notes:
* force build a qualifier by adding the followin in the reactor pom (
pluginManagement )
{code}
plugin
groupIdorg.eclipse.tycho/groupId
artifactIdtycho-packaging-plugin/artifactId
version${tycho.version}/version
configuration
format'RELEASE'/format
/configuration
/plugin
{code}
* manually tag in svn {{svn copy
https://svn.apache.org/repos/asf/sling/trunk/tooling/ide
https://svn.apache.org/repos/asf/sling/tags/sling-ide-tooling-1.0.0}}
* build the project with p2 signing enabled {{mvn clean install -Psign}} . This
also runs all the integration tests and checks the licenses on all files
* build only a src archive {{mvn -Psource-release assembly:single antrun:run
-Dtycho.mode=maven -Dusername=rombert -Djira.fixVersion=12324873
-Djira.fixedIssues=140}}
* manually gpg-sign the src archive and the checksums
* upload for testing on the dist/dev tree ( see
https://www.apache.org/dev/release.html#host-rc ).
** src zip file
* call the vote ( updated email template )
* remove the build qualifier from trunk
* Update to next version, e.g. {{mvn tycho-versions:set-version
-DnewVersion=1.0.2-SNAPSHOT}}
* if the vote is successful
** remove the files drom dist/dev
** move the files to dist/dev
** upload the p2 update site (exploded/archived ) to
https://dist.apache.org/repos/dist/release/sling/eclipse ( *.zip, /update )
Document and further automate the IDE tooling release process
-
Key: SLING-3685
URL: https://issues.apache.org/jira/browse/SLING-3685
Project: Sling
Issue Type: Task
Components: IDE
Reporter: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.2
The current release process is very much manual, due to some of tycho's
peculiarities ( see also SLING-3620 ). This task tracks the documentation of
this release process and possible automation enhancements.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[VOTE] Release Apache Sling IDE Tooling 1.0.0
Hi, We solved 144 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12324873 There are still some outstanding issues: https://issues.apache.org/jira/browse/SLING/component/12320908 The release candidate has been uploaded at https://dist.apache.org/repos/dist/dev/sling, and can be built using mvn clean package The resulting binaries can be installed into an Eclipse instance by installing from the update site which is found at p2update/target/repository after building the project. 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.
Re: [VOTE] Release Apache Sling Models API 1.0.2 Implementation 1.0.6
On Wed, Jun 25, 2014 at 11:21 PM, Robert Munteanu romb...@apache.org wrote: ...Hopefully the combined changes will fix the Jenkins build as well... Looks like it did, at [1] I seee only the launchpad testing failing, probably due to not waiting long enough for the Sling instance to start. Note that I recently added the -fae option to that build, so it runs to the end even if some tests fail along the way. -Bertrand [1] http://ci.apache.org/builders/sling-trunk/builds/434/steps/compile/logs/stdio
[jira] [Created] (SLING-3702) ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 10000 msec
Robert Munteanu created SLING-3702:
--
Summary: ResourceResolverTest.testResolveRemovedResourceAlias
fails: Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec
Key: SLING-3702
URL: https://issues.apache.org/jira/browse/SLING-3702
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Reporter: Robert Munteanu
The mentioned test fails on Jenkins consistently.
*Error Message*
{noformat}1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]{noformat}
*Stacktrace*
{noformat}java.lang.AssertionError: 1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:109)
at
org.apache.sling.launchpad.webapp.integrationtest.ResourceResolverProxyTest.runWriteableResourcesTest(ResourceResolverProxyTest.java:26){noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Re: [VOTE] Release Apache Sling Models API 1.0.2 Implementation 1.0.6
On Thu, Jun 26, 2014 at 11:37 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Wed, Jun 25, 2014 at 11:21 PM, Robert Munteanu romb...@apache.org wrote: ...Hopefully the combined changes will fix the Jenkins build as well... Looks like it did, at [1] I seee only the launchpad testing failing, probably due to not waiting long enough for the Sling instance to start. Not waiting long is enough is probably the root cause. The same changeset passes all tests but one on Jenkins I've reported SLING-3702 - ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 1 msec https://issues.apache.org/jira/browse/SLING-3702 to track that particular failures failure. Robert
[jira] [Commented] (SLING-3702) ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 10000 msec
[
https://issues.apache.org/jira/browse/SLING-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044478#comment-14044478
]
Robert Munteanu commented on SLING-3702:
[~cziegeler], [~justinedelson], [~asanso] - you're the main contributors to the
ResourceResolver mapping area, maybe you can take a look at this failing test?
ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting
for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event,
after 1 msec
-
Key: SLING-3702
URL: https://issues.apache.org/jira/browse/SLING-3702
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Reporter: Robert Munteanu
The mentioned test fails on Jenkins consistently.
*Error Message*
{noformat}1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]{noformat}
*Stacktrace*
{noformat}java.lang.AssertionError: 1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:109)
at
org.apache.sling.launchpad.webapp.integrationtest.ResourceResolverProxyTest.runWriteableResourcesTest(ResourceResolverProxyTest.java:26){noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3702) ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 10000 msec
[
https://issues.apache.org/jira/browse/SLING-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044487#comment-14044487
]
Antonio Sanso commented on SLING-3702:
--
thanks [~rombert] I am on it
ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting
for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event,
after 1 msec
-
Key: SLING-3702
URL: https://issues.apache.org/jira/browse/SLING-3702
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Reporter: Robert Munteanu
Assignee: Antonio Sanso
The mentioned test fails on Jenkins consistently.
*Error Message*
{noformat}1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]{noformat}
*Stacktrace*
{noformat}java.lang.AssertionError: 1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:109)
at
org.apache.sling.launchpad.webapp.integrationtest.ResourceResolverProxyTest.runWriteableResourcesTest(ResourceResolverProxyTest.java:26){noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (SLING-3702) ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 10000 msec
[
https://issues.apache.org/jira/browse/SLING-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso reassigned SLING-3702:
Assignee: Antonio Sanso
ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting
for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event,
after 1 msec
-
Key: SLING-3702
URL: https://issues.apache.org/jira/browse/SLING-3702
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Reporter: Robert Munteanu
Assignee: Antonio Sanso
The mentioned test fails on Jenkins consistently.
*Error Message*
{noformat}1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]{noformat}
*Stacktrace*
{noformat}java.lang.AssertionError: 1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:109)
at
org.apache.sling.launchpad.webapp.integrationtest.ResourceResolverProxyTest.runWriteableResourcesTest(ResourceResolverProxyTest.java:26){noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-920) Sling Jenkins setup
[
https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044498#comment-14044498
]
Robert Munteanu commented on SLING-920:
---
Tried to cut down the number of spurious builds by updating the Ignored
Patterns for the sling-trunk-1.{6,7} builds to be
{code}/trunk/tooling/ide/.*
/trunk/contrib/.*
/trunk/samples/.*{code}
The previous exclusions did not work.
Sling Jenkins setup
---
Key: SLING-920
URL: https://issues.apache.org/jira/browse/SLING-920
Project: Sling
Issue Type: Task
Components: Testing
Reporter: Bertrand Delacretaz
Use this issue to record changes to the Hudson continuous environment setup
at http://hudson.zones.apache.org/hudson/view/Sling/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SLING-3702) ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 10000 msec
[
https://issues.apache.org/jira/browse/SLING-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso resolved SLING-3702.
--
Resolution: Fixed
Fix Version/s: Resource Resolver 1.1.2
fixed in rev. r1605714
ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting
for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event,
after 1 msec
-
Key: SLING-3702
URL: https://issues.apache.org/jira/browse/SLING-3702
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Reporter: Robert Munteanu
Assignee: Antonio Sanso
Fix For: Resource Resolver 1.1.2
The mentioned test fails on Jenkins consistently.
*Error Message*
{noformat}1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]{noformat}
*Stacktrace*
{noformat}java.lang.AssertionError: 1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:109)
at
org.apache.sling.launchpad.webapp.integrationtest.ResourceResolverProxyTest.runWriteableResourcesTest(ResourceResolverProxyTest.java:26){noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #604
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/604/
[jira] [Commented] (SLING-3650) Logging in to sling ftpserver throws IllegalStateException
[
https://issues.apache.org/jira/browse/SLING-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044514#comment-14044514
]
Amit Gupta commented on SLING-3650:
---
attached patch At revision: 1605719
Logging in to sling ftpserver throws IllegalStateException
--
Key: SLING-3650
URL: https://issues.apache.org/jira/browse/SLING-3650
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Amrit Verma
Assignee: Amit Gupta
Fix For: FTP Server 1.0.0
Attachments: slingUserManagerDiff.txt
Steps:
{code}
ftpopen some_server some_port
User (some_server:(none)): some_existing_user
{code}
After the second step the following exception is thrown:
{code}
java.lang.IllegalStateException: This session has been closed
at
com.google.common.base.Preconditions.checkState(Preconditions.java:150)
at
org.apache.jackrabbit.oak.core.ContentSessionImpl.checkLive(ContentSessionImpl.java:85)
at
org.apache.jackrabbit.oak.core.MutableRoot.checkLive(MutableRoot.java:172)
at
org.apache.jackrabbit.oak.core.MutableRoot.hasPendingChanges(MutableRoot.java:295)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.hasPendingChanges(SessionDelegate.java:533)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.refresh(SessionDelegate.java:562)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:299)
at
org.apache.jackrabbit.oak.jcr.delegate.AuthorizableDelegator.getProperty(AuthorizableDelegator.java:204)
at
org.apache.sling.ftpserver.impl.SlingUserManager.getProperty(SlingUserManager.java:252)
at
org.apache.sling.ftpserver.impl.SlingUserManager.createUser(SlingUserManager.java:220)
at
org.apache.sling.ftpserver.impl.SlingUserManager.getUserByName(SlingUserManager.java:133)
at
org.apache.ftpserver.command.impl.USER.execute(USER.java:161)
at
org.apache.ftpserver.impl.DefaultFtpHandler.messageReceived(DefaultFtpHandler.java:210)
at
org.apache.ftpserver.listener.nio.FtpHandlerAdapter.messageReceived(FtpHandlerAdapter.java:61)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:716)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
at
org.apache.ftpserver.listener.nio.FtpLoggingFilter.messageReceived(FtpLoggingFilter.java:85)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
at
org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:75)
at
org.apache.mina.filter.logging.MdcInjectionFilter.filter(MdcInjectionFilter.java:136)
at
org.apache.mina.filter.util.CommonEventFilter.messageReceived(CommonEventFilter.java:70)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
at
org.apache.mina.filter.codec.ProtocolCodecFilter$ProtocolDecoderOutputImpl.flush(ProtocolCodecFilter.java:427)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:245)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
at
org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:75)
at
[jira] [Resolved] (SLING-3650) Logging in to sling ftpserver throws IllegalStateException
[
https://issues.apache.org/jira/browse/SLING-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Gupta resolved SLING-3650.
---
Resolution: Fixed
Fix Version/s: FTP Server 1.0.0
Logging in to sling ftpserver throws IllegalStateException
--
Key: SLING-3650
URL: https://issues.apache.org/jira/browse/SLING-3650
Project: Sling
Issue Type: Bug
Components: Extensions
Reporter: Amrit Verma
Assignee: Amit Gupta
Fix For: FTP Server 1.0.0
Attachments: slingUserManagerDiff.txt
Steps:
{code}
ftpopen some_server some_port
User (some_server:(none)): some_existing_user
{code}
After the second step the following exception is thrown:
{code}
java.lang.IllegalStateException: This session has been closed
at
com.google.common.base.Preconditions.checkState(Preconditions.java:150)
at
org.apache.jackrabbit.oak.core.ContentSessionImpl.checkLive(ContentSessionImpl.java:85)
at
org.apache.jackrabbit.oak.core.MutableRoot.checkLive(MutableRoot.java:172)
at
org.apache.jackrabbit.oak.core.MutableRoot.hasPendingChanges(MutableRoot.java:295)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.hasPendingChanges(SessionDelegate.java:533)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.refresh(SessionDelegate.java:562)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:299)
at
org.apache.jackrabbit.oak.jcr.delegate.AuthorizableDelegator.getProperty(AuthorizableDelegator.java:204)
at
org.apache.sling.ftpserver.impl.SlingUserManager.getProperty(SlingUserManager.java:252)
at
org.apache.sling.ftpserver.impl.SlingUserManager.createUser(SlingUserManager.java:220)
at
org.apache.sling.ftpserver.impl.SlingUserManager.getUserByName(SlingUserManager.java:133)
at
org.apache.ftpserver.command.impl.USER.execute(USER.java:161)
at
org.apache.ftpserver.impl.DefaultFtpHandler.messageReceived(DefaultFtpHandler.java:210)
at
org.apache.ftpserver.listener.nio.FtpHandlerAdapter.messageReceived(FtpHandlerAdapter.java:61)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:716)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
at
org.apache.ftpserver.listener.nio.FtpLoggingFilter.messageReceived(FtpLoggingFilter.java:85)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
at
org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:75)
at
org.apache.mina.filter.logging.MdcInjectionFilter.filter(MdcInjectionFilter.java:136)
at
org.apache.mina.filter.util.CommonEventFilter.messageReceived(CommonEventFilter.java:70)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
at
org.apache.mina.filter.codec.ProtocolCodecFilter$ProtocolDecoderOutputImpl.flush(ProtocolCodecFilter.java:427)
at
org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:245)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:796)
at
org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:75)
at org.apache.mina.core.session.IoEvent.run(IoEvent.java:63)
Jenkins build is still unstable: sling-trunk-1.7 #604
See https://builds.apache.org/job/sling-trunk-1.7/changes
[jira] [Commented] (SLING-3700) Add a simple injector to get the resource resolver
[ https://issues.apache.org/jira/browse/SLING-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044519#comment-14044519 ] Konrad Windszus commented on SLING-3700: I don't get why we need this. The ResourceResolver should be available (in JSPs) through a scripting variable: https://cwiki.apache.org/confluence/display/SLING/Scripting+variables#Scriptingvariables-Commonscriptingvariables. Isn't that enough in that case? Add a simple injector to get the resource resolver -- Key: SLING-3700 URL: https://issues.apache.org/jira/browse/SLING-3700 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Justin Edelson Assignee: Justin Edelson Fix For: Sling Models Implementation 1.0.6 Currently, injecting a ResourceResolver into a model class which is adapted from a resource is not possible - you have to use constructor injection of the Resource and then get the Resource Resolver from the Resource. This is non-intuitive and should be fixed. -- This message was sent by Atlassian JIRA (v6.2#6252)
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2229
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2229/
Jenkins build is still unstable: sling-trunk-1.6 #2229
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is back to normal : sling-contrib-1.6 » Apache Sling Replication Integration Tests #1159
See https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/1159/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #605
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/605/
Jenkins build is still unstable: sling-trunk-1.7 #605
See https://builds.apache.org/job/sling-trunk-1.7/changes
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2230
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2230/
Jenkins build is still unstable: sling-trunk-1.6 #2230
See https://builds.apache.org/job/sling-trunk-1.6/changes
[jira] [Commented] (SLING-3702) ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 10000 msec
[
https://issues.apache.org/jira/browse/SLING-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044586#comment-14044586
]
Robert Munteanu commented on SLING-3702:
Thanks for looking into this. Do the tests pass locally for you? They still
fail on Jenkins, see
*
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2230/testReport/org.apache.sling.launchpad.webapp.integrationtest/ResourceResolverProxyTest/runWriteableResourcesTest/
*
https://builds.apache.org/job/sling-trunk-1.7/605/org.apache.sling$org.apache.sling.launchpad.testing/testReport/org.apache.sling.launchpad.webapp.integrationtest/ResourceResolverProxyTest/runWriteableResourcesTest/
ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting
for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event,
after 1 msec
-
Key: SLING-3702
URL: https://issues.apache.org/jira/browse/SLING-3702
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Reporter: Robert Munteanu
Assignee: Antonio Sanso
Fix For: Resource Resolver 1.1.2
The mentioned test fails on Jenkins consistently.
*Error Message*
{noformat}1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]{noformat}
*Stacktrace*
{noformat}java.lang.AssertionError: 1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:109)
at
org.apache.sling.launchpad.webapp.integrationtest.ResourceResolverProxyTest.runWriteableResourcesTest(ResourceResolverProxyTest.java:26){noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3702) ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 10000 msec
[
https://issues.apache.org/jira/browse/SLING-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044592#comment-14044592
]
Antonio Sanso commented on SLING-3702:
--
@robert munteanu actually yes
ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting
for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event,
after 1 msec
-
Key: SLING-3702
URL: https://issues.apache.org/jira/browse/SLING-3702
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Reporter: Robert Munteanu
Assignee: Antonio Sanso
Fix For: Resource Resolver 1.1.2
The mentioned test fails on Jenkins consistently.
*Error Message*
{noformat}1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]{noformat}
*Stacktrace*
{noformat}java.lang.AssertionError: 1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:109)
at
org.apache.sling.launchpad.webapp.integrationtest.ResourceResolverProxyTest.runWriteableResourcesTest(ResourceResolverProxyTest.java:26){noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (SLING-3702) ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 10000 ms
[
https://issues.apache.org/jira/browse/SLING-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044592#comment-14044592
]
Antonio Sanso edited comment on SLING-3702 at 6/26/14 11:55 AM:
[~rombert] actually yes :) :S
was (Author: asanso):
@robert munteanu actually yes
ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting
for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event,
after 1 msec
-
Key: SLING-3702
URL: https://issues.apache.org/jira/browse/SLING-3702
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Reporter: Robert Munteanu
Assignee: Antonio Sanso
Fix For: Resource Resolver 1.1.2
The mentioned test fails on Jenkins consistently.
*Error Message*
{noformat}1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]{noformat}
*Stacktrace*
{noformat}java.lang.AssertionError: 1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:109)
at
org.apache.sling.launchpad.webapp.integrationtest.ResourceResolverProxyTest.runWriteableResourcesTest(ResourceResolverProxyTest.java:26){noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3702) ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after 10000 msec
[
https://issues.apache.org/jira/browse/SLING-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044624#comment-14044624
]
Robert Munteanu commented on SLING-3702:
Hm, do think it's possible that the test fails due to a timeout?
ResourceResolverTest.testResolveRemovedResourceAlias fails: Timeout waiting
for org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event,
after 1 msec
-
Key: SLING-3702
URL: https://issues.apache.org/jira/browse/SLING-3702
Project: Sling
Issue Type: Bug
Components: ResourceResolver
Reporter: Robert Munteanu
Assignee: Antonio Sanso
Fix For: Resource Resolver 1.1.2
The mentioned test fails on Jenkins consistently.
*Error Message*
{noformat}1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]{noformat}
*Stacktrace*
{noformat}java.lang.AssertionError: 1 tests
failed:[testResolveRemovedResourceAlias(org.apache.sling.launchpad.testservices.serversidetests.ResourceResolverTest):
Timeout waiting for
org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event, after
1 msec]
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.sling.launchpad.webapp.integrationtest.util.ServerSideTestClient.assertTestsPass(ServerSideTestClient.java:109)
at
org.apache.sling.launchpad.webapp.integrationtest.ResourceResolverProxyTest.runWriteableResourcesTest(ResourceResolverProxyTest.java:26){noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (SLING-3703) Dependency on org.apache.sling.commons.osgi in version 2.2
Konrad Windszus created SLING-3703: -- Summary: Dependency on org.apache.sling.commons.osgi in version 2.2 Key: SLING-3703 URL: https://issues.apache.org/jira/browse/SLING-3703 Project: Sling Issue Type: Improvement Affects Versions: Sling Models Implementation 1.0.4, Sling Models Implementation 1.0.6 Reporter: Konrad Windszus Priority: Minor Currently it is not possible to start the bundle org.apache.sling.models.impl in version 5.5 of Adobe CQ 5.5 due to the dependency on org.apache.sling.commons.osgi in version 2.2. Can you lower the dependency to version 2.1? To me it doesn't look that you actually rely on functionality being introduced with version 2.2 (https://issues.apache.org/jira/browse/SLING/fixforversion/12317581). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3505) Improve handling of updates to mapping (alias, vanity path)
[
https://issues.apache.org/jira/browse/SLING-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044794#comment-14044794
]
Andrei Dulvac commented on SLING-3505:
--
OK, I debugged this and there is a null resource in MapEntries.java:291 if I
trigger the method quasi-concurrently. I guess the event hadle is triggered
before the resolver is able to resolve that path. can't tell you why, though.
before, this wasn't working either, but now there's a NPE to show it too :(
{code}
private void doAddVanity(String path) {
Resource resource = resolver.getResource(path);
loadVanityPath(resource, resolveMapsMap, vanityTargets);
}
{code}
Improve handling of updates to mapping (alias, vanity path)
---
Key: SLING-3505
URL: https://issues.apache.org/jira/browse/SLING-3505
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Affects Versions: Resource Resolver 1.1.0
Reporter: Carsten Ziegeler
Assignee: Antonio Sanso
Fix For: Resource Resolver 1.1.2
Attachments: MapEntry.java.rej, SLING-3505-patch.txt,
SLING-3505-patch2.txt, SLING-3505-patch2.txt, SLING-3505-patch3-je.txt,
SLING-3505-patch3.txt, SLING-3505-patch3.txt
The update handling for the mapping including aliases and vanity path is a
simple algorithm which simply updates the whole mapping. Especially with
large mapping info spread across the repository, a simple update of a single
property results in the whole mapping info to be recreated.
It would be great if this could be improved.
Right now, only the active mapping is hold in memory - as a change of a
single property might cause to activate a totally different mapping than the
one which was changed (e.h. when the ordering is changed), the update needs
to be more complex or more information needs to be hold in memory.
In addition there is more to consider, like if the vanity path info is
changed, only the new value is available - but the old is gone.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Comment Edited] (SLING-3505) Improve handling of updates to mapping (alias, vanity path)
[
https://issues.apache.org/jira/browse/SLING-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044794#comment-14044794
]
Andrei Dulvac edited comment on SLING-3505 at 6/26/14 4:01 PM:
---
[~asanso], OK, I debugged this and there is a null resource in
MapEntries.java:291 if I trigger the method quasi-concurrently. I guess the
event hadle is triggered before the resolver is able to resolve that path.
can't tell you why, though.
before, this wasn't working either, but now there's a NPE to show it too :(
{code}
private void doAddVanity(String path) {
Resource resource = resolver.getResource(path);
loadVanityPath(resource, resolveMapsMap, vanityTargets);
}
{code}
I'll investigate this further if needed, but maybe you can spot the problem
directly...
was (Author: andrei.dulvac):
OK, I debugged this and there is a null resource in MapEntries.java:291 if I
trigger the method quasi-concurrently. I guess the event hadle is triggered
before the resolver is able to resolve that path. can't tell you why, though.
before, this wasn't working either, but now there's a NPE to show it too :(
{code}
private void doAddVanity(String path) {
Resource resource = resolver.getResource(path);
loadVanityPath(resource, resolveMapsMap, vanityTargets);
}
{code}
Improve handling of updates to mapping (alias, vanity path)
---
Key: SLING-3505
URL: https://issues.apache.org/jira/browse/SLING-3505
Project: Sling
Issue Type: Improvement
Components: ResourceResolver
Affects Versions: Resource Resolver 1.1.0
Reporter: Carsten Ziegeler
Assignee: Antonio Sanso
Fix For: Resource Resolver 1.1.2
Attachments: MapEntry.java.rej, SLING-3505-patch.txt,
SLING-3505-patch2.txt, SLING-3505-patch2.txt, SLING-3505-patch3-je.txt,
SLING-3505-patch3.txt, SLING-3505-patch3.txt
The update handling for the mapping including aliases and vanity path is a
simple algorithm which simply updates the whole mapping. Especially with
large mapping info spread across the repository, a simple update of a single
property results in the whole mapping info to be recreated.
It would be great if this could be improved.
Right now, only the active mapping is hold in memory - as a change of a
single property might cause to activate a totally different mapping than the
one which was changed (e.h. when the ordering is changed), the update needs
to be more complex or more information needs to be hold in memory.
In addition there is more to consider, like if the vanity path info is
changed, only the new value is available - but the old is gone.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #606
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/606/
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #606
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/606/
Jenkins build is still unstable: sling-trunk-1.7 #606
See https://builds.apache.org/job/sling-trunk-1.7/changes
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Installer Integration Tests #2231
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.it/2231/
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Models Integration Tests #2231
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.models.integration-tests/2231/
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2231
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2231/
Jenkins build is still unstable: sling-trunk-1.6 #2231
See https://builds.apache.org/job/sling-trunk-1.6/changes
[jira] [Commented] (SLING-3512) All dependencies referenced from TEI classes should have compile scope
[ https://issues.apache.org/jira/browse/SLING-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045358#comment-14045358 ] Dan Klco commented on SLING-3512: - Justin Konrad, is this issue ready to be resolved? All dependencies referenced from TEI classes should have compile scope Key: SLING-3512 URL: https://issues.apache.org/jira/browse/SLING-3512 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting JSP-Taglib 2.2.0 Reporter: Konrad Windszus Assignee: Justin Edelson Fix For: Scripting JSP-Taglib 2.2.2 Currently some classes which are referenced from TEI classes (e.g. DefineObjectsTEI) cannot be resolved within an IDE, because the according dependency is given with scope provided. Since provided dependencies are not evaluated if given in a transitive way [0], the classpath of the referencing JSP does not necessarily contain those transitive dependencies, but they are necessary for the TEI to be instanciated within the IDE. For example the DefineObjectsTEI references classes from org.apache.sling.api and slf4j-api. Therefore both dependencies should have the compile scope. [0] - http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3512) All dependencies referenced from TEI classes should have compile scope
[ https://issues.apache.org/jira/browse/SLING-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-3512. --- Resolution: Fixed All dependencies referenced from TEI classes should have compile scope Key: SLING-3512 URL: https://issues.apache.org/jira/browse/SLING-3512 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting JSP-Taglib 2.2.0 Reporter: Konrad Windszus Assignee: Justin Edelson Fix For: Scripting JSP-Taglib 2.2.2 Currently some classes which are referenced from TEI classes (e.g. DefineObjectsTEI) cannot be resolved within an IDE, because the according dependency is given with scope provided. Since provided dependencies are not evaluated if given in a transitive way [0], the classpath of the referencing JSP does not necessarily contain those transitive dependencies, but they are necessary for the TEI to be instanciated within the IDE. For example the DefineObjectsTEI references classes from org.apache.sling.api and slf4j-api. Therefore both dependencies should have the compile scope. [0] - http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope -- This message was sent by Atlassian JIRA (v6.2#6252)
