Remove from Workflow Takes a Long Time for Assets in Workflow Group with Initial State Step Action that Calls the SendEmailToAssignees Element (Doc ID 2468647.1)

Last updated on APRIL 03, 2023

Applies to:

Oracle WebCenter Sites - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

Remove From Workflow Takes a Long Time for Assets In Workflow Group with Initial State Step Action That Calls SendEmailToAssignees Element

Description:
- Workflow Group with many assets (~25-50) added to it
- Workflow Process has Step Action in initial step (Start of Workflow) that calls the OpenMarket/Xcelerate/Actions/Workflow/StepActions/SendEmailToAssignees element.
- When attempting to remove one of these assets from workflow, it takes a very long time, and threads get STUCK.
- Additionally, can contribute to UI becoming slow waiting on workflow operations.

The following thread is seen in the thread dumps while this process is taking a long time:

[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" #29 daemon prio=1 os_prio=0 tid=0x00000000027aa800 nid=0x6915 runnable [0x00007fb3c973e000]
java.lang.Thread.State: RUNNABLE
at COM.FutureTense.Util.FStringBuffer.safeIndexOf(FStringBuffer.java:613)
at COM.FutureTense.Util.FStringBuffer.indexOf(FStringBuffer.java:538)
at COM.FutureTense.Util.FStringBuffer.indexOf(FStringBuffer.java:526)
at COM.FutureTense.Util.FStringBuffer.indexOf(FStringBuffer.java:521)
at COM.FutureTense.Common.ftAppLogic.replaceQueryinfo(ftAppLogic.java:576)
at COM.FutureTense.Common.ftAppLogic.doReplaces(ftAppLogic.java:244)
at COM.FutureTense.Common.ftAppLogic.doStandardReplace(ftAppLogic.java:174)
at COM.FutureTense.XML.Template.CArgument.execute(CArgument.java:185)
at COM.FutureTense.XML.Template.Variable.execute(Variable.java:88)
at COM.FutureTense.XML.Template.BlockTag.execute(BlockTag.java:144)
at COM.FutureTense.XML.Template.BlockTag.execute(BlockTag.java:120)
at COM.FutureTense.XML.Template.LoopTag.execute(BlockTag.java:757)
at COM.FutureTense.XML.Template.BlockTag.execute(BlockTag.java:144)
at COM.FutureTense.XML.Template.BlockTag.execute(BlockTag.java:120)
at COM.FutureTense.XML.Template.LoopTag.execute(BlockTag.java:757)
at COM.FutureTense.XML.Template.BlockTag.execute(BlockTag.java:144)
at COM.FutureTense.XML.Template.BlockTag.execute(BlockTag.java:120)
at COM.FutureTense.XML.Template.IfChild.execute(BlockTag.java:398)
at COM.FutureTense.XML.Template.IFTag.execute(BlockTag.java:497)
at COM.FutureTense.XML.Template.BlockTag.execute(BlockTag.java:144)
at COM.FutureTense.XML.Template.BlockTag.execute(BlockTag.java:120)
at COM.FutureTense.XML.Template.Root.execute(BlockTag.java:366)
at COM.FutureTense.XML.Template.XMLEval.run(XMLEval.java:345)
at COM.FutureTense.Common.ContentServer.evalTheXML(ContentServer.java:3665)
at COM.FutureTense.Common.ContentServer.evalTemplate(ContentServer.java:2909)
at COM.FutureTense.Common.ContentServer.processElement(ContentServer.java:2312)
at COM.FutureTense.Common.CS.CallElement(CS.java:1612)
at com.openmarket.xcelerate.workflow.WorkflowAction.callElement(WorkflowAction.java:183)
at com.openmarket.xcelerate.workflow.WorkflowStepAction.executeAction(WorkflowStepAction.java:47)
at com.openmarket.xcelerate.workflow.WorkflowEngine.fireStepActions(WorkflowEngine.java:2361)
at com.openmarket.xcelerate.workflow.WorkflowEngine.defineNewAssignments(WorkflowEngine.java:2302)
at com.openmarket.xcelerate.workflow.WorkflowEngine.checkGroupDeadlockResolution(WorkflowEngine.java:7084)
at com.openmarket.xcelerate.workflow.WorkflowEngine.cancelObjectAssignments(WorkflowEngine.java:2049)
at com.openmarket.xcelerate.workflow.WorkflowEngine.closeAssignments(WorkflowEngine.java:5436)
at com.openmarket.xcelerate.commands.WorkflowEngineDispatcher.CloseAssignments(WorkflowEngineDispatcher.java:2536)

Additionally, if attempting to load the Contributor UI with another user, the UI hangs attempting to load the Assignments widget and the following STUCK thread is seen in the thread dumps:

[STUCK] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)'" #120 daemon prio=1 os_prio=0 tid=0x00007fb3c4d64800 nid=0x6977 in Object.wait() [0x00007fb3a6184000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at com.openmarket.xcelerate.locks.LockObject.enterReadLock(LockObject.java:326)
- locked <0x0000000710d620e8> (a com.openmarket.xcelerate.locks.LockObject)
at com.openmarket.xcelerate.locks.LockManager.enterReadLock(LockManager.java:322)
at com.openmarket.xcelerate.workflow.WorkflowEngine.getFilteredAssignments(WorkflowEngine.java:3172)
at com.openmarket.xcelerate.workflow.WorkflowEngine.getFilteredAssignments(WorkflowEngine.java:3135)
at com.fatwire.services.WorkflowServiceImpl$1.run(WorkflowServiceImpl.java:59)
at com.fatwire.services.WorkflowServiceImpl$1.run(WorkflowServiceImpl.java:48)
at com.fatwire.services.helper.ServiceWrapper.run(ServiceWrapper.java:69)
at com.fatwire.services.WorkflowServiceImpl.getAssignments(WorkflowServiceImpl.java:122)
at jsp_servlet._jsp._cs_deployed._ui._data._dashboard.__workflowaction._jspService(__workflowaction.java:117)

Changes

Cause

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Remove from Workflow Takes a Long Time for Assets in Workflow Group with Initial State Step Action that Calls the SendEmailToAssignees Element (Doc ID 2468647.1)

Applies to:

Symptoms

Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!