[
https://issues.apache.org/jira/browse/SLING-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540199
]
Philipp Koch commented on SLING-96:
-----------------------------------
even if i create anew timed event i get following exception which is thrown
when the event is processed(note: i did restart sling and the repository
before):
05.11.2007 15:39:11 *ERROR* o.a.s.e.i.TimedEventHandler: Exception during
writing new job to repository.
javax.jcr.InvalidItemStateException: Unable to unlock node. Node has pending
changes: /sling/timed-events
at com.day.crx.core.NodeImpl.unlock(NodeImpl.java:4097)
at org.apache.jackrabbit.util.Locked.runAndUnlock(Locked.java:234)
at org.apache.jackrabbit.util.Locked.with(Locked.java:148)
at org.apache.jackrabbit.util.Locked.with(Locked.java:104)
at
org.apache.sling.event.impl.TimedEventHandler.persistEvent(TimedEventHandler.java:172)
at
org.apache.sling.event.impl.TimedEventHandler.runInBackground(TimedEventHandler.java:127)
at
org.apache.sling.event.impl.AbstractRepositoryEventHandler$1.run(AbstractRepositoryEventHandler.java:114)
> persisted timed events should be removed from the repository after they got
> successfully executed
> -------------------------------------------------------------------------------------------------
>
> Key: SLING-96
> URL: https://issues.apache.org/jira/browse/SLING-96
> Project: Sling
> Issue Type: Bug
> Components: Event
> Reporter: Philipp Koch
> Assignee: Carsten Ziegeler
> Priority: Minor
>
> the persisted timed events keep staying in the repository also after being
> executed/fired successfully. this is from my point of view not correct. the
> nodes should be deleted so that it would be possible to register a timed
> event again with the same id. if the current behaviour is thought to keep
> kind of a history than it would make more sense to keep such a history in a
> "history" tree.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
