No ManagedConnections available within the configured blocking timeout

book

Article ID: 5900

calendar_today

Updated On:

Products

CA Virtual Privilege Manager CA Privileged Identity Management Endpoint (PIM) CA Privileged Access Manager (PAM)

Issue/Introduction

When logging into the ENTM a users get: 

"The server is currently not responding. You may wait for the server to respond or try again later." 

 

When a user eventually logged in the get the following message: 

"No ManagedConnections available within the configured blocking timeout ( 175000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within the configured blocking timeout ( 175000 [ms] )) " 

Environment

Release: ACP1M005900-12.9-Privileged Identity Manager
Component:

Resolution

The following error means that jboss has run out of connections to the database. Below are instructions to make more connections available in jboss. This requires jboss to be restarted. 

 

No ManagedConnections available within the configured blocking timeout ( 175000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within the configured blocking timeout ( 175000 [ms] )) 

 

Assuming that the ENTM is using SQL Server:

1. Stop the jboss service 

2. Make a backup of <jboss>/server/default/deploy/imtaskpersistencedb-ds.xml outside of of the <jboss> folder tree. It is important that the backup is outside of the jboss folder tree. 

3. Edit <jboss>/server/default/deploy/imtaskpersistencedb-ds.xml 

4. Find: 

<max-pool-size>20</max-pool-size> 

And set it to: 

<max-pool-size>40</max-pool-size> 

5. Find: 

<idle-timeout-minutes>5</idle-timeout-minutes> 

And set it to: 

<idle-timeout-minutes>1</idle-timeout-minutes> 

6. Find: 

<blocking-timeout-millis>175000</blocking-timeout-millis> 

And comment it out: 

<!-- <blocking-timeout-millis>175000</blocking-timeout-millis> --> 

7. Save and close the file 

8. Delete <jboss>/server/default/work and <jboss>/server/default/tmp 

9. Start the jboss service