This means that Oracle terminated your connection. It normally occurs due to a timeout or a restart. You can check your connection pool parameters.
For example set your initial connections to zero. This ensures that stale connections are not left in the pool.
Thanks for the input.These are the parameters and their corresponding values that are currently set for the connection pool.
Can you please specifically suggest which parameter to be changed?
(The number of physical database connections (between 0 and a positive 32-bit integer)
to create when creating this JDBC connection pool. )
(The maximum number of physical database connections (between 0 and a positive 32-bit integer)
that this JDBC connection pool can contain.)
(The increment (between 0 and a positive 32-bit integer) by which this JDBC connection pool's capacity is expanded.)
Statement Cache Type:LRU
(The algorithm used for maintaining the prepared statements stored in the cache.)
Statement Cache Size: 10
(The number of prepared and callable statements stored in the cache.
Remove Infected Connections: Enabled
(Controls whether a connection will be removed from the connection pool
when the application asks for the underlying vendor connection object)
Allow Shrinking: YES
Shrink Frequency:900 SEC
(The number of seconds (between 0 and a positive 32-bit integer) before WebLogic Server shrinks the connection pool
to the original number of connections or number of connections currently in use.)
Test Reserved Connections: true
Connection Reserve Timeout: 10 SEC
Connection Creation Retry Frequency:3000 SEC
Inactive Connection Timeout:3000 SEC
Maximum Waiting for Connection:100
Test Table Name:SQL SELECT 1 FROM DUAL
(The name of the database table to use when testing physical database connections.
This field is required when you specify a Test Frequency and enable Test Reserved Connections,
Test Created Connections, and Test Released Connections.)
Initial Capacity: 0
The main reason you are getting the errors is due to option Test Connections On Reserve. In this
case WebLogic first tests the connection before it is gven to the client. Which is a good thing.
Note that also the shrinkng frequency is set to 900 seconds. So every 900 seconds the connection
pool is reduced in size if necessary.
It won't. That was an erroneous suggestion. If you need 5 connections in the pool, set the initial capacity to 5
so it makes all it's going to need at boot time, and leave them there. No need to shrink. Tell us what happens.
As I said, the DBMS or network is just killing an established connection. This is nothing WebLogic or the driver
can cause or fix.