[Log4plsql] JDBC to stored procedure using LOG4PLSQL: How to avoid file handles being closed?

[<log...@li...>]

Hi there.

Half a year ago I built a PL/SQL wrapper around Log4J that was loaded into
an 8.1.6 database. I had the following severe problem with that solution:
When calling a stored procedure (that used the PL/SQL wrapper) from Java
through JDBC it turned out that the Oracle VM closed all open file handles
(and also sockets) on purpose when the JDBC call finished even though static
objects that could survive the call were used. Oracle explained that this is
by design and documented in the section "Operating System Resources Affected
Across Calls" at
http://technet.oracle.com/doc/oracle8i_816/java.816/a81353/03writed.htm.

Have you been able to find a workaround with LOG4PLSQL for this serious
issue?

Cheers,

Finn

---------------------------------------------------------------------------
 Finn Ellebaek Nielsen                           ChangeGroup ApS
 Product Manager, Principal Consultant, Partner  Kronprinsessegade 54, 4.
 E-mail: fe...@ch...                      DK-1306  Koebenhavn K
 Mobile: +45 20 32 49 25                         Denmark
 Phone:  +45 33 32 77 78                         http://www.changegroup.dk
---------------------------------------------------------------------------
                      "Where do you want to GPF today?"