Posts tagged "timeout"

CQ5.4: how to force a delay between workflow steps

Information

If you are using workflows in Adobe CQ5.4 you may wish to have a customized delay between certain workflow steps.  It is possible to cause a delay using the timeout functionality which has pre-defined values (immediate, 1h, 2h, 6h etc…), and then select the Auto Advance timeout handler to move the workflow to the next step.

In some cases you may also want to define your own delay intervals rather than use the pre-defined values.  This is possible in CQ5.4 by creating an overlay of:

/libs/cq/workflow/components/model/step/tab_common/items/timeout/items/timeout/options

to:

/apps/cq/workflow/components/model/step/tab_common/items/timeout/items/timeout/options

and then you can make a copy of one of the existing nodes (1h, 2h etc…), and change the values to suit your needs.  The value should be in seconds and not milliseconds.

This new value will then appear in the workflow step configuration dialog, under the list of timeout values, and the step will timeout after the specified interval.

reference: (37175)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 4.0/10 (4 votes cast)

LiveCycle ES: DocumentError submitting a task after migrating to LC ES 8.2.1

Issue

 After you migrate your server from LiveCycle 7 to LiveCycle ES 8.2.1, the following error may appear in the log when you submit a task in Workspace:

javax.ejb.EJBException: EJB Exception: : com.adobe.idp.DocumentError: The document pointing to the file 
"/data/myservermydomain/AdobeDocumentStorage/session_wfattach585520/9084040089345862489" has expired. 
Consider increasing the document disposal timeout.
 at com.adobe.idp.DocumentFileBackend.checkFileExistance(DocumentFileBackend.java:412)
 at com.adobe.idp.DocumentFileBackend.copy(DocumentFileBackend.java:419)
 at com.adobe.idp.Document.passivate(Document.java:1065)
 at com.adobe.idp.Document.passivate(Document.java:1012)
 at com.adobe.idp.Document.<init>(Document.java:565)
 at com.adobe.idp.Document.<init>(Document.java:621)
 at com.adobe.idp.DocumentStorage.persist(DocumentStorage.java:78)
 at com.adobe.idp.taskmanager.dsc.client.task.AttachmentInfoImpl.persistDoc(AttachmentInfoImpl.java:201)
 at com.adobe.idp.taskmanager.dsc.service.CopyAttachments.copyAttachmentsToTask(CopyAttachments.java:326)
 at com.adobe.idp.taskmanager.dsc.service.CopyAttachments.copyAttachmentsForward(CopyAttachments.java:291)
 at com.adobe.idp.taskmanager.dsc.service.TaskManagerServiceImpl.createTask(TaskManagerServiceImpl.java:467)
 at sun.reflect.GeneratedMethodAccessor1968.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)

Reason

The process itself stalls when this error occurs.  The error refers to a task attachment that no longer exists in the DocumentStorage directory. This error can occur if the LiveCycle 7 session referencing the target file was deleted, and LiveCycle 8 references to the target file remained. Deleting the LiveCycle 7 session deleted the session_wfattch…. directory, leaving the LiveCycle 8 references pointing to deleted resources.

Solution

Restore the missing files from a backup of your LiveCycle DocumentStorage directory. Or, delete the source task whose attachments are being copied or delete the attachment itself.

reference: (181609130/2630482)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)