On Fri, May 19, 2006 at 02:30:54PM -0700, dhogaza@PACIFIER.COM wrote:
> > (which I think was done to work around some ancient bug in an ancient
> > version of the nsoracle driver) then you get the problem.
> 
> I think the problem was in the oracle library (OCI), but it's been a long,
> long time.

Yep.  For those interested in ancient trivia, I think it was TWO bugs,
one in the Oracle driver and/or OCI libraries (most likely OCI), and
one in AOLserver.  I think the workaround dates from before I ever
used AOLserver, but I have these old comments in my AOLserver config
file:

# MaxIdle and MaxOpen: 
# 
# Settings these to 1000000000 is a historical bug workaround.  Could 
# now probably set this to some normal number, or set to 0 to disable 
# entirely.  E.g., in this thread Rob Mayoff <[EMAIL PROTECTED]> says: 
# 
# http://www.arsdigita.com/bboard/q-and-a-fetch-msg?msg%5fid=000Ibq 
# 
#   It is a bug workaround. Many Linux users (including me) saw that 
#   when AOLserver tried to close a database connection, it would hang 
#   in the Oracle driver. So people started setting and MaxIdle to a 
#   very large number to keep connections from closing. You can also set 
#   them to zero, but at the time the bug was discovered, AOLserver had 
#   a bug that prevented you from setting them to zero. 
# 
#   I believe the bug was also seen, very rarely, on Solaris. 
# 
#   Curtis Galloway managed to get Oracle to investigate. They suggested 
#   to workarounds: use IPC or TCP to connect (which is what I do on my 
#   system), or set bequeath_detach=yes in sqlnet.ora. 
# 
# [EMAIL PROTECTED], 2002/01/10 14:22 EST 

-- 
Andrew Piskorski <[EMAIL PROTECTED]>
http://www.piskorski.com/


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to