MetaSolv Solution - JDBC Connection Leak in the Service Request Search Window
(Doc ID 2000127.1)
Last updated on MARCH 14, 2019
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
The Service Request Search window has a connection leak as it uses the MetaSolv.utilities.powerbuilder.Update framework to issue a SELECT statement instead of MetaSolv.utilities.powerbuilder.Populate. There is no call to MetaSolv.utilities.powerbuilder.Commit within the process so the tbs.exe client holds a reference to the connection for reuse.
Below is an image of the tbs,exe client and its SQL Spy session showing usage of the MetaSolv.utilities.powerbuilder.Update framework.
Below is an image showing the client holding a reference to the connection on the v$session table as its client_identifier value remains populated because the client has not given it back to the pool. Reference Doc ID 2018598.1 for information regarding "MetaSolv Solution - How to Configure WebLogic Server Data Sources to Identify/Monitor JDBC Connections on the Oracle Database". Reference Doc ID 952202.1 and Doc ID 1577030.1 for information about the JDBC Data Sources used by the MetaSolv Solution application and their installed default parameters.
Below is an image of the WebLogic Administration Console's Data Source monitoring Settings for mslvNoneTxDataSource showing the connection as an Active Connections Current Count even though the session status is INACTIVE on the database. Note that the example shows 3 which it is one of.
The issue can be reproduced at will using the following steps:
1. Access MetaSolv Solution (tbs.exe)
2. Order Management
3. Service Requests
4. Query for 100 In Progress PSR orders
Due to this issue, the application server may eventually need to be restarted.
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