Burt Alexander wrote:
> "Craig R. McClanahan" wrote:
>
> > 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?
>
> Yep. The trace looks like so:
>
> java.sql.SQLException: IO problem: java.io.FileNotFoundException: ./trace.log
> at db.Trace.setExport(Trace.java)
> at db.Database.initialise(Database.java)
> at db.Database.dbOpen(Database.java)
> at jdbc.idbConnection.<init>(idbConnection.java)
> at jdbc.idbDriver.connect(idbDriver.java)
> at java.sql.DriverManager.getConnection(DriverManager.java:83)
> at java.sql.DriverManager.getConnection(DriverManager.java:126)
>
> where ./trace.log is a property in that properties file, and does exist. I've
> tried specifying the absolute path too with the same result. The tools that
> come with IDB work (establish connections) with both relative & absolute
> paths.
>
> I have successfully used InstantDB on NT with JRun. I'll be trying JRun on my
> Linux config shortly. Will let U know.
>
> > Can you identify the source code that is receiving the
> > exception, so we can see exactly what it's trying to do?
>
> Yep. Its happening when a connection is being attempted.
>
> > Have you followed
> > all the installation instructions that InstantDB requires in terms of class
> > pathc and paths?
>
> Yep. As I said, had it working with different configurations.
>
> > Have you asked the InstantDB folks for help?
> >
>
> Yep, I'm waiting for feedback, but I doubt its an InstantDB problem.
>
> >
> > 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).
>
> Yep. All these things are set up & working fine for other servlet engines.
> Its only JServ that has the problem.
>
> >
> > 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.
> >
>
> Yep. However I'm not able to control how JServ handles the paths that the
> JDBC drivers use/need. This is what is causing the errors (I think). And I'm
> 99.9999% sure its not a config problem. Thanx for the double check - please
> let me know if you can think of anything else. If you'd like to duplicate the
> problem, InstantDB comes with a sample db. You just run the java program
> sample.java, & create a quick servlet that tries to establish a connection to
> the db. You can get it at www.instantdb.co.uk. Thanx again.
>
> Burt.
>
> >
> > 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]
>
> -- --------------------------------------------------------------
> 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]
I just install JRun on my linux box. Without modifying anything but my
httpd.conf file to accomodate JRun, I am now accessing my InstantDB database.
Please let me know if anyone can reproduce this. Thanx.
Burt.
-- --------------------------------------------------------------
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]
