[jira] [Updated] (SLING-5805) Eventing: NPE in JobSchedulerImpl when shutting down instance
[
https://issues.apache.org/jira/browse/SLING-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-5805:
Fix Version/s: Event 4.1.0
> Eventing: NPE in JobSchedulerImpl when shutting down instance
> -
>
> Key: SLING-5805
> URL: https://issues.apache.org/jira/browse/SLING-5805
> Project: Sling
> Issue Type: Bug
> Components: Extensions
>Affects Versions: Event 4.0.2
>Reporter: Stefan Seifert
>Priority: Minor
> Fix For: Event 4.1.0
>
>
> when shutting down a sling instance (part of a cluster) with ~30.000
> scheduled jobs, i get thousands of error logs like this in the logs:
> {noformat}
> 22.06.2016 17:25:07.174 *ERROR*
> [sling-default-593-org.apache.sling.event.jobs.Job:03eb3d10-952e-4b1b-83c8-e7e092495c09-0]
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job
> execution of
> org.apache.sling.event.impl.jobs.scheduling.JobSchedulerImpl@407bb6e7 : null
> java.lang.NullPointerException: null
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJobInteral(JobManagerImpl.java:537)
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJob(JobManagerImpl.java:704)
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJob(JobManagerImpl.java:267)
> at
> org.apache.sling.event.impl.jobs.scheduling.JobSchedulerImpl.execute(JobSchedulerImpl.java:280)
> at
> org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:116)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5805) Eventing: NPE in JobSchedulerImpl when shutting down instance
[
https://issues.apache.org/jira/browse/SLING-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347702#comment-15347702
]
Carsten Ziegeler commented on SLING-5805:
-
I think the fix in rev 1750042 should solve the problem.
[~sseif...@pro-vision.de] Can you give this a try?
> Eventing: NPE in JobSchedulerImpl when shutting down instance
> -
>
> Key: SLING-5805
> URL: https://issues.apache.org/jira/browse/SLING-5805
> Project: Sling
> Issue Type: Bug
> Components: Extensions
>Affects Versions: Event 4.0.2
>Reporter: Stefan Seifert
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: Event 4.1.0
>
>
> when shutting down a sling instance (part of a cluster) with ~30.000
> scheduled jobs, i get thousands of error logs like this in the logs:
> {noformat}
> 22.06.2016 17:25:07.174 *ERROR*
> [sling-default-593-org.apache.sling.event.jobs.Job:03eb3d10-952e-4b1b-83c8-e7e092495c09-0]
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job
> execution of
> org.apache.sling.event.impl.jobs.scheduling.JobSchedulerImpl@407bb6e7 : null
> java.lang.NullPointerException: null
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJobInteral(JobManagerImpl.java:537)
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJob(JobManagerImpl.java:704)
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJob(JobManagerImpl.java:267)
> at
> org.apache.sling.event.impl.jobs.scheduling.JobSchedulerImpl.execute(JobSchedulerImpl.java:280)
> at
> org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:116)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SLING-5805) Eventing: NPE in JobSchedulerImpl when shutting down instance
[
https://issues.apache.org/jira/browse/SLING-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-5805:
---
Assignee: Carsten Ziegeler
> Eventing: NPE in JobSchedulerImpl when shutting down instance
> -
>
> Key: SLING-5805
> URL: https://issues.apache.org/jira/browse/SLING-5805
> Project: Sling
> Issue Type: Bug
> Components: Extensions
>Affects Versions: Event 4.0.2
>Reporter: Stefan Seifert
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: Event 4.1.0
>
>
> when shutting down a sling instance (part of a cluster) with ~30.000
> scheduled jobs, i get thousands of error logs like this in the logs:
> {noformat}
> 22.06.2016 17:25:07.174 *ERROR*
> [sling-default-593-org.apache.sling.event.jobs.Job:03eb3d10-952e-4b1b-83c8-e7e092495c09-0]
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job
> execution of
> org.apache.sling.event.impl.jobs.scheduling.JobSchedulerImpl@407bb6e7 : null
> java.lang.NullPointerException: null
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJobInteral(JobManagerImpl.java:537)
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJob(JobManagerImpl.java:704)
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJob(JobManagerImpl.java:267)
> at
> org.apache.sling.event.impl.jobs.scheduling.JobSchedulerImpl.execute(JobSchedulerImpl.java:280)
> at
> org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:116)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5805) Eventing: NPE in JobSchedulerImpl when shutting down instance
[
https://issues.apache.org/jira/browse/SLING-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347696#comment-15347696
]
Carsten Ziegeler commented on SLING-5805:
-
There is a problem with deactivate of the JobSchedulerImpl and
stopScheduledJob. deactivate first sets the active flag to false and then calls
stopScheduledJob which checks the active flag and therefore does not unschedule
> Eventing: NPE in JobSchedulerImpl when shutting down instance
> -
>
> Key: SLING-5805
> URL: https://issues.apache.org/jira/browse/SLING-5805
> Project: Sling
> Issue Type: Bug
> Components: Extensions
>Affects Versions: Event 4.0.2
>Reporter: Stefan Seifert
>Priority: Minor
> Fix For: Event 4.1.0
>
>
> when shutting down a sling instance (part of a cluster) with ~30.000
> scheduled jobs, i get thousands of error logs like this in the logs:
> {noformat}
> 22.06.2016 17:25:07.174 *ERROR*
> [sling-default-593-org.apache.sling.event.jobs.Job:03eb3d10-952e-4b1b-83c8-e7e092495c09-0]
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job
> execution of
> org.apache.sling.event.impl.jobs.scheduling.JobSchedulerImpl@407bb6e7 : null
> java.lang.NullPointerException: null
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJobInteral(JobManagerImpl.java:537)
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJob(JobManagerImpl.java:704)
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJob(JobManagerImpl.java:267)
> at
> org.apache.sling.event.impl.jobs.scheduling.JobSchedulerImpl.execute(JobSchedulerImpl.java:280)
> at
> org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:116)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5805) Eventing: NPE in JobSchedulerImpl when shutting down instance
[
https://issues.apache.org/jira/browse/SLING-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347093#comment-15347093
]
Stefan Seifert commented on SLING-5805:
---
it seems that {{this.configuration}} (JobManagerConfiguration) in
{{JobManagerImpl}} is null - this leads to the NPE when shutting down the
instance.
> Eventing: NPE in JobSchedulerImpl when shutting down instance
> -
>
> Key: SLING-5805
> URL: https://issues.apache.org/jira/browse/SLING-5805
> Project: Sling
> Issue Type: Bug
> Components: Extensions
>Affects Versions: Event 4.0.2
>Reporter: Stefan Seifert
>Priority: Minor
>
> when shutting down a sling instance (part of a cluster) with ~30.000
> scheduled jobs, i get thousands of error logs like this in the logs:
> {noformat}
> 22.06.2016 17:25:07.174 *ERROR*
> [sling-default-593-org.apache.sling.event.jobs.Job:03eb3d10-952e-4b1b-83c8-e7e092495c09-0]
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job
> execution of
> org.apache.sling.event.impl.jobs.scheduling.JobSchedulerImpl@407bb6e7 : null
> java.lang.NullPointerException: null
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJobInteral(JobManagerImpl.java:537)
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJob(JobManagerImpl.java:704)
> at
> org.apache.sling.event.impl.jobs.JobManagerImpl.addJob(JobManagerImpl.java:267)
> at
> org.apache.sling.event.impl.jobs.scheduling.JobSchedulerImpl.execute(JobSchedulerImpl.java:280)
> at
> org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:116)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLING-5809) Provide Sling's Launchpad Karaf Features as Options for Pax Exam
[ https://issues.apache.org/jira/browse/SLING-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347011#comment-15347011 ] Oliver Lietz commented on SLING-5809: - [r1749897|https://svn.apache.org/r1749897] [r1749903|https://svn.apache.org/r1749903] > Provide Sling's Launchpad Karaf Features as Options for Pax Exam > > > Key: SLING-5809 > URL: https://issues.apache.org/jira/browse/SLING-5809 > Project: Sling > Issue Type: New Feature > Components: Testing >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Fix For: Testing Pax Exam 0.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5809) Provide Sling's Launchpad Karaf Features as Options for Pax Exam
Oliver Lietz created SLING-5809: --- Summary: Provide Sling's Launchpad Karaf Features as Options for Pax Exam Key: SLING-5809 URL: https://issues.apache.org/jira/browse/SLING-5809 Project: Sling Issue Type: New Feature Components: Testing Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Testing Pax Exam 0.0.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-5808) Update Tika to 1.13
[ https://issues.apache.org/jira/browse/SLING-5808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-5808. - Resolution: Done [r1749884|https://svn.apache.org/r1749884] [r1749885|https://svn.apache.org/r1749885] [r1749886|https://svn.apache.org/r1749886] > Update Tika to 1.13 > --- > > Key: SLING-5808 > URL: https://issues.apache.org/jira/browse/SLING-5808 > Project: Sling > Issue Type: Task > Components: Launchpad >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Fix For: Launchpad Karaf Features 0.2.0, Launchpad Builder 9 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5808) Update Tika to 1.13
Oliver Lietz created SLING-5808: --- Summary: Update Tika to 1.13 Key: SLING-5808 URL: https://issues.apache.org/jira/browse/SLING-5808 Project: Sling Issue Type: Task Components: Launchpad Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: Launchpad Karaf Features 0.2.0, Launchpad Builder 9 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5807) [HApi] Annotate the html rendering a type with HApi
Andrei Dulvac created SLING-5807: Summary: [HApi] Annotate the html rendering a type with HApi Key: SLING-5807 URL: https://issues.apache.org/jira/browse/SLING-5807 Project: Sling Issue Type: Improvement Affects Versions: HApi 1.0.0 Reporter: Andrei Dulvac Assignee: Andrei Dulvac Fix For: HApi 1.0.2 The default resource type of a hapi type is /libs/sling/hapi/components/type. This HTML should also be annotated with hapi so it can be understood by machines (eat your own dog food) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Sling Rewriter 1.1.4
On Thursday 23 June 2016 09:45:58 Carsten Ziegeler wrote: > Hi, > > We solved 1 issue: > > https://issues.apache.org/jira/browse/SLING/fixforversion/12334894 +1 O.
Re: [VOTE] Release Apache Sling Adapter Manager Implementation 2.1.8
On Wednesday 22 June 2016 14:23:03 Antonio Sanso wrote: > Hi, > > We solved 2 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12333853 +1 O.
[jira] [Commented] (SLING-5803) FilterRuleExcludeCategoryIgnoreIfTest fails on Jenkins
[ https://issues.apache.org/jira/browse/SLING-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346202#comment-15346202 ] Bertrand Delacretaz commented on SLING-5803: As per http://wiki.apache.org/general/Jenkins you need to ask the Sling PMC chair (that's Carsten) to request access, just ask on our dev list. > FilterRuleExcludeCategoryIgnoreIfTest fails on Jenkins > -- > > Key: SLING-5803 > URL: https://issues.apache.org/jira/browse/SLING-5803 > Project: Sling > Issue Type: Bug > Components: Testing >Reporter: Bertrand Delacretaz >Assignee: Andrei Dulvac >Priority: Minor > Labels: sling-IT > > These tests are consistently failing on Jenkins as in [1] for example: > * FilterRuleExcludeCategoryIgnoreIfTest.testExcludedCategoryExists > * FilterRuleExcludeCategoryTest.testExcludedCategoryExists > both with "java.lang.AssertionError: Test should be Ignored" > Andrei, as you wrote those tests, could you have a look? > [1] https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/4145/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release o.a.s.jcr.api 2.4.0 and o.a.s.jcr.base 2.4.0
On Tuesday 21 June 2016 16:05:30 Bertrand Delacretaz wrote: > Hi, > > We solved 4 distinct issues in these related releases: > > org.apache.sling.jcr.api 2.4.0 > https://issues.apache.org/jira/browse/SLING/fixforversion/12333247 +1 > org.apache.sling.jcr.base 2.4.0 > https://issues.apache.org/jira/browse/SLING/fixforversion/12334904 +1 O.
Re: [VOTE] Release o.a.s.repoinit.parser 1.0.0 and o.a.s.repoinit.oak.jcr 1.0.0
On Tuesday 21 June 2016 16:58:30 Bertrand Delacretaz wrote: > Hi, > > This is the first release of these new modules. > > Note that building these requires the o.a.s.jcr.api 2.4.0 and > o.a.s.jcr.base 2.4.0 releases from staging repository 1465, so this > release will only happen if the 1465 vote passes. o.a.s.repoinit.oak.jcr should not contain oak but jackrabbit in its name (no Oak API used). Why are JcrRepoInitOpVisitor and RepositoryInitializer public? Shouldn't they live in impl (internal) also? The package webconsole and resources seem to be obsolete and should be removed. Regards, O.
Re: Build failed in Jenkins: sling-contrib-1.7 #961
Apache Jenkins Server wrote > # There is insufficient memory for the Java Runtime Environment to continue. > # Cannot create GC thread. Out of system resources. Looks like a jenkins problem -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Sling Rewriter 1.1.4
+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[VOTE] Release Apache Sling Rewriter 1.1.4
Hi, We solved 1 issue: https://issues.apache.org/jira/browse/SLING/fixforversion/12334894 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1468 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 1468 /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-5803) FilterRuleExcludeCategoryIgnoreIfTest fails on Jenkins
[ https://issues.apache.org/jira/browse/SLING-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345985#comment-15345985 ] Andrei Dulvac commented on SLING-5803: -- [~bdelacretaz], sorry for that. Thing is they pass locally just fine and the jenkins logs don't tell me enough about what's going on. I'll try and run with the same openjdk version on the slaves. Could I possibly have access to inspect/configure the jenkins job? > FilterRuleExcludeCategoryIgnoreIfTest fails on Jenkins > -- > > Key: SLING-5803 > URL: https://issues.apache.org/jira/browse/SLING-5803 > Project: Sling > Issue Type: Bug > Components: Testing >Reporter: Bertrand Delacretaz >Assignee: Andrei Dulvac >Priority: Minor > Labels: sling-IT > > These tests are consistently failing on Jenkins as in [1] for example: > * FilterRuleExcludeCategoryIgnoreIfTest.testExcludedCategoryExists > * FilterRuleExcludeCategoryTest.testExcludedCategoryExists > both with "java.lang.AssertionError: Test should be Ignored" > Andrei, as you wrote those tests, could you have a look? > [1] https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/4145/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-5806) No service returned if several services for same type
[ https://issues.apache.org/jira/browse/SLING-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5806. - Resolution: Fixed The services of the same type are now ordered by service ranking (highest wins) Refactored the code and moved the tracker customizers into separate classes for easier testing I've also added a test which shows that the old code was broken, and succeeds with the new code > No service returned if several services for same type > - > > Key: SLING-5806 > URL: https://issues.apache.org/jira/browse/SLING-5806 > Project: Sling > Issue Type: Bug > Components: Extensions >Affects Versions: Rewriter 1.1.2 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Critical > Fix For: Rewriter 1.1.4 > > > If there is more than one plugin service (generator, transformer, serializer, > processor) for the same type, and just one of them is unregistered, the > factory cache will return null - although there are still other services for > the same type. > In addition, there is no rule on which service to pick if there are multiple > for the same type -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-5806) No service returned if several services for same type
Carsten Ziegeler created SLING-5806: --- Summary: No service returned if several services for same type Key: SLING-5806 URL: https://issues.apache.org/jira/browse/SLING-5806 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Rewriter 1.1.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Priority: Critical Fix For: Rewriter 1.1.4 If there is more than one plugin service (generator, transformer, serializer, processor) for the same type, and just one of them is unregistered, the factory cache will return null - although there are still other services for the same type. In addition, there is no rule on which service to pick if there are multiple for the same type -- This message was sent by Atlassian JIRA (v6.3.4#6332)
