head	1.7;
access;
symbols;
locks
	nobody:1.7; strict;
comment	@# @;


1.7
date	99.09.30.08.15.30;	author nobody;	state Exp;
branches;
next	1.6;

1.6
date	99.09.28.23.38.16;	author nobody;	state Exp;
branches;
next	1.5;

1.5
date	99.09.26.06.36.16;	author nobody;	state Exp;
branches;
next	1.4;

1.4
date	99.09.23.04.55.32;	author nobody;	state Exp;
branches;
next	1.3;

1.3
date	99.09.23.04.42.25;	author nobody;	state Exp;
branches;
next	1.2;

1.2
date	99.09.23.04.41.28;	author nobody;	state Exp;
branches;
next	1.1;

1.1
date	99.09.23.04.40.55;	author nobody;	state Exp;
branches;
next	;


desc
@null
@


1.7
log
@null
@
text
@IDependOn-Set: 1
IDependOn-Set: 119
IDependOn-Set: 2
IDependOn-Set: 305
IDependOn-Set: 306
IDependOn-Set: 312
LastModifiedSecs: 938561896
Parent: 119
SequenceNumber: 3
Title: JServ & JDBC drivers dependant on native code
Part: 0
Author-Set: ba@@sentor.com.au
LastModifiedSecs: 938561896
Type: 
Lines: 7
I had attempted to use JServ in conjunction with DB2 access on NT.  In spite of the best configuration efforts, I was unable to get it to work - an UnsatisfiedLinkError exception was being thrown.

This is because the JDBC drivers for DB2 require native code to execute - db2jdbc.dll specifically, whose directory must be (and was) in the path.  After trying to debug classes locally, I discovered (buried) in the Sun documentation that in order to debug drivers dependant on dll's, the dll must be copied with an '_g' appended to the end of the name ie. db2jdbc_g.dll.

Having done this separately, I started up Apache/JServ, and things worked the first time.  JServ must require debug names for dependant native dll's.

Also, set the wrapper.env.copyall=true in jserv.properties. This copies all system environment variables for use by JServ.
EndPart: 0
@


1.6
log
@null
@
text
@d14 1
@


1.5
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938062532
d9 1
a9 1
SequenceNumber: 2
d13 2
a14 3
LastModifiedSecs: 938062532
Type: 
Lines: 5
d17 1
a17 1
This is because the JDBC drivers for DB2 require native code to execute - db2java.dll specifically, whose directory must be (and was) in the path.  After trying to debug classes locally, I discovered (buried) in the Sun documentation that in order to debug drivers dependant on dll's, the dll must be copied with an '_g' appended to the end of the name ie. db2java_g.dll.
d20 2
@


1.4
log
@null
@
text
@d6 1
d14 1
@


1.3
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 938061745
d8 1
a8 1
SequenceNumber: 1
d10 10
@


1.2
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 938061655
d8 2
a9 2
SequenceNumber: 0
Title: New Item
@


1.1
log
@null
@
text
@d4 1
@
