[Qgis-user] Oracle connection Timeout

[Heather Hillers]

We have looked closer at the Network activity during the Connection process.

1.  We have no Firewall between the Oracle Server and the Client.

We can reproduce the error most easily by

1. Opening a Connection to the database without saving the username and
Password.
2. Adding any table to the Project from the Connection. 
3. Save the Project
4. Close Qgis
5. Open Qgis
6. Load the Project.

Behavior on load:

The user gets a credentials request immediately with a normal failed to
Login with username/Password error.  In the logs, we see that a Connection
is opened (We'll call it ConnA) and recieves the Login error.
There is no Termination of the Connection from the Client side.

The user gives the correct username and Password.  A second Connection,
ConnB, is created.  The table is loaded and this ConnB is closed by the
Client.

Exactly one Minute after ConnA was opened, ConnA, which was never explicitly
closed by the Client, gets a reset Signal from the Oracle Server.  This is
the Point at which Oracle gets the Connection timeout error, leading to the
eventual overload of the error logs and the required restart of the TNS
Listener.

Should not QGIS be explicitly cutting the dead Connection after the Login
denial? Is there a Workaround for this?  

Heather



 



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Oracle-connection-Timeout-tp5193601p5193783.html
Sent from the Quantum GIS - User mailing list archive at Nabble.com.