Skip to main content
S
sad1-Visitor
1-Visitor
March 13, 2014
Solved

Workflow hanging at set state robot

  • March 13, 2014
  • 2 replies
  • 6418 views

For particular workflow processes, it is hanging at the Set State Robot, and throwing the following error. I could not find any root cause for this issue.

A nested transaction cannot be started when a rollback is in progress. The following is the rollback stacktrace.
ROLLBACK: java.lang.Thread.getStackTraceImpl(Native Method)
ROLLBACK: java.lang.Thread.getStackTrace(Thread.java:1042)
ROLLBACK: wt.pom.TransactionManager.rollbackTransaction(TransactionManager.java:624)
ROLLBACK: wt.pom.BasicTransactionMonitor.rollbackTransaction(BasicTransactionMonitor.java:77)
ROLLBACK: wt.pom.PersistentObjectManager.rollbackTransaction(PersistentObjectManager.java:447)
ROLLBACK: wt.pom.Transaction.rollback(Transaction.java:566)
ROLLBACK: wt.workflow.engine.StandardWfEngineService.synchRobotToEvent(StandardWfEngineService.java:8959)
ROLLBACK: wt.workflow.engine.StandardWfEngineService$SynchEventListener.notifyVetoableEvent(StandardWfEngineService.java:429)
ROLLBACK: wt.events.StandardKeyedEventBranch.intDispatchEvent(StandardKeyedEventBranch.java:320)
ROLLBACK: wt.events.StandardKeyedEventBranch.dispatchVetoableEvent(StandardKeyedEventBranch.java:229)
ROLLBACK: wt.events.StandardKeyedEventDispatcher.intDispatchEvent(StandardKeyedEventDispatcher.java:286)
ROLLBACK: wt.events.StandardKeyedEventDispatcher.dispatchVetoableEvent(StandardKeyedEventDispatcher.java:215)
ROLLBACK: wt.services.StandardManagerService.intDispatchVetoableEvent(StandardManagerService.java:406)
ROLLBACK: wt.services.StandardManagerService.dispatchVetoableEvent(StandardManagerService.java:302)
ROLLBACK: wt.lifecycle.StandardLifeCycleService.dispatchVetoableEvent(StandardLifeCycleService.java:571)
ROLLBACK: wt.lifecycle.StandardLifeCycleService.doSetState(StandardLifeCycleService.java:9981)
ROLLBACK: wt.lifecycle.StandardLifeCycleService.doSetState(StandardLifeCycleService.java:7449)
ROLLBACK: wt.lifecycle.StandardLifeCycleService.setState(StandardLifeCycleService.java:7256)
ROLLBACK: wt.lifecycle.StandardLifeCycleService.setState(StandardLifeCycleService.java:7587)

If somebody throws some light on this issue, will be very much appreciated.

Thanks

Suresh

Attributes

Best answer by sad

Actually this issue was started appearing in all workflows for the past two days. Clearing queue also failed.

Then as per the PTC suggestion, we cleared all the tomcat cache & task cache and retstarted method server. The issue is resolved now.

2 replies

P
ptc-14203601-Visitor
1-Visitor
March 13, 2014

Hi, may be this article would help

https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS68591

M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
March 13, 2014

Not a very helpful error message - like most...

Did you check the obvious - the state being set to is not in the current lifecycle? Maybe made an iteration to the lifecycle since this object was created?

S
sad1-VisitorAuthorAnswer
1-Visitor
March 14, 2014

Actually this issue was started appearing in all workflows for the past two days. Clearing queue also failed.

Then as per the PTC suggestion, we cleared all the tomcat cache & task cache and retstarted method server. The issue is resolved now.

T
tanose1-Visitor
1-Visitor
January 2, 2015

Hello AD,

Where is the windchill Task cache? I am having this issue in our windchill system so often?

Thanks

Tem

Terms & ConditionsCookie settingsAccessibility statement