Hi All, We are having a ticket open on production right now. All the

anagha_abhyankar over 9 years ago

Hi All,

We are having a ticket open on production right now. All the problems are because of Closed connection and a typical alert is as below:

There is a problem with task “Fetch Claim Notes” in the process “Fetch Claim Notes-186919456-001 - 3258”. [An error occured: $Closed Connection]

The DB is up and running. The connectivity between the servers looks good. May be something hung up and those connections were not being released, it could be causing a shortage of available connections from the appian/app server side.

MAX_POOL_SIZE set is 100 on Appian server.

Server restart resolved the issue , however, we wanted to know the root cause and what can we do to not let this happen in future.

Thanks in advance!

Discussion posts and replies are publicly visible

0 anagha_abhyankar over 9 years ago

Forgot to mention, we do have a lot of stored procedure calls and query rules to fetch the data from external DB. The solution is completely entity- based. And we see around 150-200 users launching the app per day. Is it something that the stored proc is causing a problem?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

If the error doesn't explicitly mention there are no more connections from the pool then that's not the issue.

This could be a network glitch communicating with the database. Make sure your appian-ds.xml uses <check-valid-connection-sql> under <validation> to force the app server (assuming you're using JBoss) to reconnect if it loses connectivity with the DB.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel