Thanks for reporting, yes this is in fact a problem of the notification
which is sent by the job handling - it shouldn't contain the async handler.

Carsten


2013/5/18 Amit.. Gupta. <[email protected]>

> Minor correction in the mail
>
> -----Original Message-----
> From: Amit.. Gupta.
> Sent: 19 May 2013 02:53
> To: [email protected]
> Subject: RE: JcrResourceProvider.create/JobMangerImpl.writeJob can cause
> inconsistent behavior
>
> Hi Carsten,
>
> I think that change has surfaced one more bug that was perhaps working as
> a side effect, after I used the latest changed JcrResourceProvider, I get
> following error in logs
> 19.05.2013 02:40:37.421 *ERROR* [Thread-33]
> org.apache.sling.event.impl.dea.DistributedEventReceiver Exception during
> writing the event to the resource tree.
> org.apache.sling.api.resource.PersistenceException: Unable to create
> resource with path
> /var/eventing/distribution/826cd21a-6a8f-48cb-b112-768b421af572/2013/5/19/2/40/event-372
>         at
> org.apache.sling.event.impl.support.ResourceHelper.getOrCreateResource(ResourceHelper.java:230)
>         at
> org.apache.sling.event.impl.dea.DistributedEventReceiver.writeEvent(DistributedEventReceiver.java:208)
>         at
> org.apache.sling.event.impl.dea.DistributedEventReceiver.processWriteQueue(DistributedEventReceiver.java:158)
>         at
> org.apache.sling.event.impl.dea.DistributedEventReceiver.access$500(DistributedEventReceiver.java:75)
>         at
> org.apache.sling.event.impl.dea.DistributedEventReceiver$1.run(DistributedEventReceiver.java:115)
>         at java.lang.Thread.run(Thread.java:662)
>
> on debugging I found that this event has following property
> ":sling:jobs:asynchandler" which jcr wont allow
>
> This property is coming from JobConsumer.
>
> Thanks,
> -Amit
>



-- 
Carsten Ziegeler
[email protected]

Reply via email to