You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2015/07/23 09:57:04 UTC

[jira] [Created] (SLING-4899) Background servlet not cluster aware

Marcel Reutegger created SLING-4899:
---------------------------------------

             Summary: Background servlet not cluster aware
                 Key: SLING-4899
                 URL: https://issues.apache.org/jira/browse/SLING-4899
             Project: Sling
          Issue Type: Bug
          Components: Extensions
    Affects Versions: Background Servlets 1.0.0
            Reporter: Marcel Reutegger


The background servlet creates stream nodes under a configurable path with a local counter. When running in a cluster, it may happen that background servlets on multiple cluster nodes try to create the same stream node.

{noformat}
java.lang.IllegalArgumentException: Stream node already exists: /var/bg/jobs/2015/07/17/15/51/82/stream
	at org.apache.sling.bgservlets.impl.storage.JobDataImpl.getOutputStream(JobDataImpl.java:74)
	at org.apache.sling.bgservlets.impl.BackgroundRequestExecutionJob.<init>
{noformat}

It would probably be good to include the slingId in the path prefix to separate streams from different cluster nodes. A similar approach is implemented already for sling jobs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)