Portal sessions not closing after publish causing exceeding limit error
Article ID: 8684
Updated On:
Products
Issue/Introduction
We are trying to publish tables to a Data Target containing multiple schemas using the TDM Portal. Before run time, we have zero active JDBC connections. At runtime, when the job is submitted, we received an error due to the session limit exceeding the set number. We have set a hard limit of 6 sessions per user ID. Does the TDM Portal create one session per publish job or does it create multiple sessions per publish? Also, TDM Portal is not closing the session when the job is over, which is an issue for us due to the set limit.
Environment
Cause
By design we keep the connections open after publishes for a certain amount of time. We do this because closing and opening after each session can be expensive on resources. The Portal uses a connection pool. The size of the connection pool is setup in the application.properties file, which is by default located at C:\Program Files\CA\CA Test Data Manager Portal\conf. When a connection is used, then a session is created and activated. It becomes inactive between queries or when the connection is put back into the connection pool.
Resolution
The product is working as designed. If you are setting a specific limit to connections, we recommend working with your DBA to increase the number of sessions. In this specific case, we would recommend unlimited sessions for specific users.
If you have certain restrictions that do not allow you to increase the sessions, we recommend submitting an enhancement request, which our product management team will then review. You can do this by following the directions in this document: https://knowledge.broadcom.com/external/article?articleId=9611.
Additional Information
If you experience any further issues, please open a support case by going to https://support.broadcom.com.
Feedback
