Skip to main content
P
PreetiGupta15-Moonstone
15-Moonstone
April 20, 2010
Question

Winchill 9.1 Workflow Queue Issue

  • April 20, 2010
  • 3 replies
  • 708 views
Hi ,

We upgraded our Windchill instance to 9.1 M040 from 9 M050 three weeks back.

We have been seeing WFWorkqueue problems. The entries get severe and setting them back to ready clears them off. Sometimes it gets stuck on the custom codes we wrote and sometimes it gets stuck for set state robot as well...unusual pattern. We are not able reproduce it on any test server. So far PTC tech support could not give us a clue as to why it is happening. Have you seen this behavior on your 9.1 system?

For now one of us constantly has to baby sit the system to clear these queues entries manually. Same workflows were running just fine on 9 but giving us such weird problems in 9.1

Thanks,
Preeti


3 replies

R
rnkennedy31-Visitor
1-Visitor
April 21, 2010
Preeti,

It could be that you are missing some custom states in the StateRB.rbInfo file. If you have custom workflows then it makes sense that you have custom states.

The maintenance update will overwrite any of the customizations and they will need to be reinstalled - take a look in the <windchill home=">/src or <windchill home=">/wtCustom folder.


Regards,

Robert Kennedy
Eccellent Solutions
robert.kennedy@eccellent.com
I
iwebb1-Visitor
1-Visitor
July 19, 2010

I would be interested if there any more details of a solution/workaround for this...

Regards

Ian

P
ptc-5685931-Visitor
1-Visitor
July 19, 2010

Logs normally show causes for the failures, look in the background method server log for details. The queue manager may show some exception traces as well. The custom code is always a potential problem, you should <u>always</u> write the code in external classes and call it from within the workflow. The code should be wrapped in atry..catch and be especially careful putting code into conditionals these have some weaknesses especially with transaction handling, we normally write the code to execute in a block before the conditional and set a variable. As far a I know the workflow engine has not fundamentally changed fora while so the cause of your problems are more likely to be environmental, missing classes, soft types etc.

Ideally all developers should develop workflow code in external classes, with compehensive junit testing.

Terms & ConditionsCookie settingsAccessibility statement