We've had a few issues when jboss stops working and we've found the foll

Hello Karla,

It seems like the Work Poller has run out of threads.

In order to fix this issue temporarily, please restart the Application server.

Alok,

We restarted jboss and things seemed to be running well now. We're really not sure what is causing the issue, but it has happened around the same time of the morning of at least 3 days in the last couple of months. Is there anything we should look at to try to determine what causes the error? I've looked through many of the logs and nothing is jumping out at me for what happened at the time the error happened.

Thanks,
Karla

Karla, what version of Appian are you running?

These errors on 6.6.1 we are currently testing our 7.5 upgrade, hoping to move that to production in a month. We have 3 production servers, 1 runs jboss, the other 2 have 3 engines each, we have multiple gateways for each analytic and execution engine.

Karla, this issue has been addressed in a more current release of Appian.

The upgrade to Appian 7.5 should definitely resolve this permanently and stop this from occurring in the future.

Thanks Alok. We are just bringing up our 7.5 QA servers this week. Does 7.5 reduce the need for multiple gateways? We are still on the original portal, we won't have anything moved over to SAIL with the new 7.5 upgrade this year.

Regression testing on 7.5 should give you a good insight as to what the Performance looks like with the existing Application on the upgraded system. Appian 7.5 does have several performance improvements, but I wouldn't know if that necessarily applies to your Application.