Burt Alexander wrote:
> I've submitted this as a bug (mod_jserv 4460) but I'd like to know if
> anyone else has seen this problem.
>
> Using InstantDB (www.instantdb.co.uk), a Java relational database, a
> FileNotFoundException gets thrown when a connection is attempted under
> JServ. The URL for the driver is of the form
> jdbc:idb:/path/to/property_file . The property file is found - thats
> not the problem. Within this property file are properties specifying
> other directories & files. These are what cause the
> FileNotFoundException to be thrown. I'm running this under RH 6.0 &
> Apache 1.3.6 & I've tried it with the b5, b4 & b3 release of JServ with
> the same results. Using the Java tools that come with InstantDB, I can
> make a connection no prob.
>
> It took me a while, but I remembered that we had a similar problem at
> work. There, we were using IBM's UDB with our servlet product & it was
> working successfully with JRun, Websphere & Domino. I attempted to
> install JServ on my laptop since the servlet engine(s) was constantly up
> & down. An UnsatisfiedLinkError got thrown - the IBM driver could not
> locate native code in the path necessary to establish a connection to
> the database, even tho my paths were exactly the same as the servers'.
> I thot it was a configuration thing until it was duplicated several
> weeks later when they attempted to use JServ on the server.
>
> Sound familiar to anyone? Thanx.
>
> Burt.
>
This sounds like it might be related to things like current working
directories and class paths, more than anything in particular about JServ.
However, there's no way to really help find out what's going on without
more detailed information. For example, can you get a stack trace when the
exception occurs? Can you identify the source code that is receiving the
exception, so we can see exactly what it's trying to do? Have you followed
all the installation instructions that InstantDB requires in terms of class
pathc and paths? Have you asked the InstantDB folks for help?
If you're running drivers that require native code, you also have to make
sure that the appropriate shared libraries (DLL files under Windows, SO
files under Unix) are in the right places, and defined in the right
environment variables (PATH under Windows, LD_LIBRARY_PATH under Unix).
Thjis kind of thing trips up lots of people installing stuff in servlet
engines (not just JServ).
The environment under which JServ runs is under your control, because you
can set up environment variables and things like that, but it is not
necessarily the same as the environment that your stand-alone Java apps run
under.
Craig McClanahan
-- --------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
