OK this is a release showstopper!
Now I'm convinced that JNI doesn't work as it should :(
Done some serious tests with various JDK's and TC versions from 4.0.4
through 4.1.10
The jni works _only_ and ONLY if preceded by socket call meaning
[channel.socket]
[channel.jni]
works, but
[channel.jni]
[channel.socket]
doesn't work
I've traced the problem down to the MsgAjp constructor called from
JniHandler's createMsgContext member:
...
public MsgContext createMsgContext() {
if( nativeJkHandlerP==0 || apr==null )
return null;
try {
MsgContext msgCtx=new MsgContext();
// THIS IS PASSED
System.err.println("JniHandler OK createMsgContext
MsgContext");
MsgAjp msg=new MsgAjp();
// NEWER GETS HERE
System.err.println("JniHandler OK createMsgContext MsgAjp");
....
} catch( Exception ex ) {
// DISPLAYS NOTHING!
ex.printStackTrace();
return null;
}
...
IMHO the reason is missing org.apache.commons.logging.LogFactory,
perhaps not loaded by the jni channel.
If someone more familiar with that can dig into and trace the problem it
would be great, or I'll simply delete all that 'unnecessary' *.Log
stuff, and use the System.err.
MT.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
