-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------

Urban Widmark wrote:
> 
> On Fri, 3 Sep 1999, Raimee Stevens wrote:
> 
> > >
> > > I believe the vm will only load native libraries (dlls) for classes in the
> > > vm classpath, and not for classes in the zone "repository". At least that
> > > is true for jdk1.1.x.
> >
> > I did set wrapper.classpath=path_to_dll in jserv.properties.
> > That had no effect.
> >
> 
> But the dll is not a java class. You need to have your servlet class(es)
> in the wrapper.classpath (pointing to the zip, jar, "base directory", or
> whatever you use).
Yeh, but I was desperate.  I didn't have a problem loading the JDBC
driver, the problem
was that the driver class file couldn't located it's native
counter-part.


> The dll has to be in whatever search path NT uses for dlls (the PATH
> variable? I think the db2 installation sets that).
Not which path NT uses, but which path the vm uses.  The DriverManager
loads a db2 class file
which needs to find it's native interface to the database.

setting wrapper.path=java.library.path=h:\sqllib\bin in my
jserv.properties has the following effect:

//DriverManager.setLogStream(outFile) output

DriverManager.initialize: jdbc.drivers = null
JDBC DriverManager initialized
registerDriver:
driver[className=COM.ibm.db2.jdbc.app.DB2Driver,COM.ibm.db2.jdbc.app.DB2Driver@e39d4957]
registerDriver:
driver[className=COM.ibm.db2.jdbc.net.DB2Driver,COM.ibm.db2.jdbc.net.DB2Driver@3d54957]
DriverManager.getConnection("jdbc:db2://elderlyone:6790/DBTTR")
    trying
driver[className=COM.ibm.db2.jdbc.app.DB2Driver,COM.ibm.db2.jdbc.app.DB2Driver@e39d4957]
    trying
driver[className=COM.ibm.db2.jdbc.net.DB2Driver,COM.ibm.db2.jdbc.net.DB2Driver@3d54957]
Server elderlyone port 6790 source DBTTR
getConnection returning
driver[className=COM.ibm.db2.jdbc.net.DB2Driver,COM.ibm.db2.jdbc.net.DB2Driver@3d54957]

//Notice that both  ...jdbc.net and ...jdbc.app drivers are tried.  This
is documented in an IBM Quick Book as
//required for trusted applets.  The connection to the app driver
_alone_ fails for some reason but waorks when 
//drivers both are registered.

This is a step forward, but actually things don't work yet.  I am
working on trace outputa from DB2 to isolate
the problem.  It looks as though I am making a connection, but I still
don't get any output to my ResultSet.
The trace files are a little cryptic.

mod_jserv.log:
ajp11: Servlet Error: GET is not supported by this URL

now what does this mean?


--
--------------------------------------------------------------
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]

Reply via email to