Web Service Manager Request Throws an Error before Connecting to Connection Manager
(Doc ID 2437579.1)
Last updated on AUGUST 08, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.20.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
-----------------------
When using Web Service Manager, web-service request throws an error before connecting to CM (Connection Manager) even when connection pool is enabled with below Infranet.properties configuration :
infranet.connectionpool.minsize=5
infranet.connectionpool.maxsize=15
infranet.connectionpool.timeout=30000
infranet.connectionpool.maxidletime=90000
For each web-service successful request, the web-service log shows an error as below:
EXPECTED BEHAVIOR
-----------------------
It is expected that the web service manager will connect successfully to the CM without generating any errors.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
a. Install Web Service Manager, and deploy the BrmWebServices.war file on Tomcat.
b. From SOAP UI, try to execute any of the service, say BRMReadServices, from the second request onward you would start seeing the Error "Could not create Connection pool instance"
c. Below are the parameters set for the log file generation in the Infranet.properties
infranet.log.logallebuf=true
infranet.pcp.debug.flags=0x3FFFFFFF
infranet.pcp.debug.enabled=true
d. Below are the connection pool settings
infranet.connectionpool.minsize=5
infranet.connectionpool.maxsize=15
infranet.connectionpool.timeout=30000
infranet.connectionpool.maxidletime=90000
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |