You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Multiple Workflow Users sessions??

Laserfiche Workflow
Updated November 11, 2015
posted on September 23, 2014

Customer just sent me an email showing that they have multiple sessions running with the Workflow User and the WFUser$, and no FTUser$.  We created the workflow user for the connection profile...what would cause this and is this normal? (See below).

 

 

Thanks!!

0 0
replied on November 9, 2015 • Show version history

We have a situation similar to the one Daryl described, except in checking Sessions in the Admin Console, we have multiples of the same account in the Workflow connection profile, with inactivity periods measuring in days.  They all come from the workflow server, so appear to be using a single license, but the sessions are definitely not releasing themselves. 

 

Our rules do not use Wait States, so they are not waiting for something to complete.  This is 8.3.1, with Classic Licensing.  We also do not want to use inactivity logouts, as this has been unpredictable in our experience.  Nor can we use a Device License, as this is not Avante.

 

Is this considered to be normal behavior?

 

PS:  Sorting by Inactivity Duration in Admin Console gives you an alpha sort, and not a numeric sort.  A session inactive for 5 minutes shows up right next to one inactive for five days.

0 0
replied on November 10, 2015

8.3.1 had some known issues with releasing connections that have been fixed since. Wait conditions do not keep connections open while in the wait state. Even in Classic licensing setups, the Workflow connections to the repository don't use licenses, so the extra connections can be ignored.

1 0
replied on November 11, 2015

Thanks, Miruna.  We'll be upgrading to 9.2 soon.

0 0
replied on September 23, 2014

Yes, seeing multiple sessions is normal as Workflow does its job in the repository. Workflow is multi-threaded, so multiple instances are executing at the same time. You'll note that all the sessions in your screenshot show an inactive duration of 0min, so they're actively working.

If you don't think there should be that much activity from Workflow in  your repository, you should run a statistics report on your server to check that you don't have any runaway workflows.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...