-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
tnsnames?? You must be using the THICK-driver, while on th eLinux box you
are using the thin-driver. It works for me on my Solaris, NT, etc boxes.
Are you trying to rebuild the connection object, or setting it to null and
replacing it with a new one?
BTW: If you are using pre 8.1.5 jdbc drivers, DON'T!!!!!
Thor HW
----- Original Message -----
From: Mader, Cary J <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 05, 1999 1:18 PM
Subject: corruption of environment variables?
> -----------------------------
> Please read the FAQ!
> <http://java.apache.org/faq/>
> -----------------------------
>
> I have a servlet which manages a pool of oracle db connections which is
> having problems re-establishing the connections when they are closed (i.e.
> datbase comes down for backups) because the Oracle client software
suddenly
> doesn't like the connect string that was originally used to connect to the
> db.
>
> After doing a lot of research it appears the only possible explanation
left
> is that the environment variable(s) that were defined in the wrapper.env
> lines are somehow getting wiped out or corrupted. The variables are used
by
> the oracle software to find the tnsnames.ora file (ORACLE_HOME,
ORACLE_BASE,
> etc) that defines the connect string being used. Stopping and starting
the
> web server (and the jserv module) always fixes the problem. Also, I can
get
> around the problem by using a tnsnames-entry style connect string that
> avoids the lookup to the tnsnames.ora file.
>
> I have several questions:
>
> - Has anyone heard of variables defined in the jserv.properties file using
> the wrapper.env statements getting corrupted?
>
> - Is there any way to force jserv to redefine these variables?
>
> - Is there any way to access the value of these variables from within a
> servlet for debug purposes?
>
> - Are there any logging parameters I can set that might be of help in
trying
> to figure out what is going on?
>
> The funny thing is that we have a linux box using the last beta release of
> jserv that does not have this problem, while the 1.0 release of jserv
> running on another box does.
>
> I think the version of Apache is 1.3.6, and the OS is the latest SuSe
> distribution of Linux.
>
> Thanks.
>
> Cary Mader
> email: [EMAIL PROTECTED]
>
>
> Cary Mader
> Phoenix Development Center
> Cell Phone: 602-770-0241
> Pager: 602-440-0008
> PDC Phone: 602-952-4731 (8-695)
> DPG Phone: 602-827-5031
> email: [EMAIL PROTECTED]
>
>
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://java.apache.org/main/mail.html/>
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
