Re: Connection.close() failed, message was Exception d'E/S: Socket closed

[Martin Kal�n]

Emmanuel Dupont wrote:

I'm using OJBRC4 with Oracle.
Often I have this error message : 
0                    WARN  [Finalizer]
accesslayer.ConnectionFactoryNotPooledImpl - Connection.close() failed,
message was Exception d'E/S: Socket closed
I've seen Oracle servers with a very short connection-timeout if the 
connection is passive.

If this is the case at your end you could tweak the server settings (out 
of my league) or try to remedy holding your connections longer than 
neccesary. If your are using the PersistenceBroker API, make sure you 
call broker.close() (or the more violent and terminal "destroy") after 
using your broker.

If you have to hold on to your connections for longer than the server 
would allow you, or for more robust operations in gereal -- consider 
using a connection pool and the validation query "SELECT 1 FROM DUAL" 
(this will revive any dead connections if Oracle kicked you out).

Cheers,
 Martin
--
Martin Kal�n
Curalia AB              Web:  http://www.curalia.se
Orrspelsv�gen 2B        Mail: [EMAIL PROTECTED]
SE-182 79  Stocksund    Tel:  +46-8-410 064 40
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]