02-21-2019 11:07 AM
We have some contractors that are working really early morning hours. They are reporting they are getting logged out. Could the (staggered) recycling of the application pools (during this time frame) cause this? I would think that the Onbase (Thick) Client (V17) would be resilient and automatically establish a connection to another available app pool. I tried finding documentation on the effects of recycling app pools but could not find any. I did see that it would not remove locks incurred by users. However is there anything that it would affect?
02-21-2019 12:00 PM
Hello Peter,
While the Thick Client is fairly resilient to most things, if the user in the Thick Client is using Core Based Workflow and the Application Pool they are connected to is recycled, they would need to close and re-open the client to use these functions. The thick client will not automatically grab a new session. Clients like the Unity Client, OBA, and other Unity Foundation modules will do this.
Thanks,
02-21-2019 12:00 PM
Hello Peter,
While the Thick Client is fairly resilient to most things, if the user in the Thick Client is using Core Based Workflow and the Application Pool they are connected to is recycled, they would need to close and re-open the client to use these functions. The thick client will not automatically grab a new session. Clients like the Unity Client, OBA, and other Unity Foundation modules will do this.
Thanks,
02-22-2019 05:18 AM
That's helpful, thank you!!!!
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.