Java Database Connection Disclosure workaround-based on WebLogic server

Temporarily resolve connection leak scenarios

When a connection leak really happens, inevitably, we take the following scenario to temporarily resolve the connection issue to try to change the code time.

Step 1: Select theJNDIData Source

Steps2(optional): Maximum number of data connections can be configured

Steps3:Connection Leak Auto-shutdown

Click on the icon, expand, set when there is a connection leak, WEBLOGIC10 automatically shuts down automatically. The timeout number of seconds is set by the property inactive connection timeout. 0 for disable, set greater than 1.

For example: Set - seconds, the connection to the leak is automatically closed. Once set up here, you can view the logs of the connection auto-shutdown and the connection leak point in the weblogic10 log . See the log section for descriptions.

Monitoring connection Leak settings connection Leak profile

Check "Profile connection leak" option

Monitor connection Usage

Increase the leak connection count in the Customize this table column to count the number of connection leaks.

Find Java connection leak points

Copy the exception information and you can see where the code is leaking.

Java Database Connection Disclosure workaround-based on WebLogic server