Ok, If I make the channel.socket as a first call to the TC then JNI works OK. After the first call through socket, I can disable the channel.socket, and the channel.jni works after that without problems.
Are there any special classes that are loaded during initial socket accept on the TC side, or something similar? > -----Original Message----- > From: Mladen Turk [mailto:[EMAIL PROTECTED]] > > From: jean-frederic clere > > > > > > > > Any clues? > > > > Not yet. > > I have problems with the classloader in an earlier state (and > > I am using the CVS > > head of 4.1). > > > > Well, the jni is working _only_ if I setup the channel.socket before > channel.jni in the workers2.properties. > The load balancer then calls the socket and this seems somehow > 'initializes' TC cause after that the jni calls are working normally, > but they are switched with the socket channel, so it's not a proper > solution. > > Right now I'm not sure If It ever worked :(. I will try to make the > socket channel as single shot to see if this is the true reason or the > mod_jk2 is faulty. > > MT. > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For > additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
