Understood. My point was to encourage you to file a bug...it wasn't clear in your original post if you had done it already or were planning to do it, so I erred on the side of caution. I didn't want your information to go to waste, which is what would have happened if it hadn't gotten into bugzilla.
John > -----Original Message----- > From: Rahul Bhargava [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 11, 2003 2:44 PM > To: Tomcat Users List > Subject: Re: Beware: Don't use JNI inprocess mode with JK2, it's badly > broken > > > I have filed a bug John already. I think it helps a great > deal as folks here > can > avoid walking into the land mine called Jk2 JNI. Sure most > people may not > want to know the innards of the codebase that causes JNI to fail, but > knowing it > won't work can save time - it would have saved me a week as I > struggled with > the > config thinking I must have screwed up .... > _________________________________ > Rahul Bhargava > ----- Original Message ----- > From: "Turner, John" <[EMAIL PROTECTED]> > To: "'Tomcat Users List'" <[EMAIL PROTECTED]> > Sent: Tuesday, February 11, 2003 11:37 AM > Subject: RE: Beware: Don't use JNI inprocess mode with JK2, it's badly > broken > > > | > | Thanks for the info. BEST PLACE for this is BUGZILLA, and > a post to the > | tomcat-dev list. Folks here are Tomcat users, and this information > doesn't > | help us that much aside from an overview. > | > | John > | > | > | > -----Original Message----- > | > From: Rahul Bhargava [mailto:[EMAIL PROTECTED]] > | > Sent: Tuesday, February 11, 2003 2:35 PM > | > To: Tomcat Users List > | > Subject: Beware: Don't use JNI inprocess mode with JK2, it's badly > | > broken > | > > | > > | > There is no way in hell JNI can ever work with JK2. > | > jk_channel_jni.c::jk2_channel_jni_open invokes > | > the java static method createJavaContext() which in turns > | > tries to return a registered JkHandler for > | > Jni (ChannelJni) from the underlying hashtable. However when > | > the in-process mode is enabled, there > | > is nobody registering any handlers! As a result null is > | > trurned into c land from Java when createJavaContext > | > returns causing the JNI invocation to fail. > | > > | > Tried this with Apache 2.0.43/44. With the out of process > | > mode the declaration in server.xml cause a JkCoyoteHandler to > | > be registered but with the in-process mode, this was suppose > | > to happen automatically. Nobody seems to trigger a call to > | > AprImpl.addJkHandler() - not in java land not in c land! > | > > | > This convince me that JNI mode never really worked with JK2. > | > If you look at the tomcat-user archive > | > you can see people falling on their faces trying to get this > | > to work,but nobody has succedded now > | > I know why. > | > > | > Someone should fix the Jk2 web site which lures naive users > | > to believe that JNI mode is working with > | > Jk2! I did try to fix the problem by tring to instantiate a > | > ChannelJni instance in the ctor of AprImpl and register > | > it into the jkHandlers table but was getting NPE...don't > | > know the code that well to know what assumptions are built > | > into ChannelJni. Will continue to debug. But in the meatime > | > stay away from JNI. > | > _________________________________ > | > Rahul Bhargava > | > > | > | > --------------------------------------------------------------------- > | To unsubscribe, e-mail: [EMAIL PROTECTED] > | For additional commands, e-mail: [EMAIL PROTECTED] > | > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
