Hi, I just posted a new bug report (518 in the Bugrat interim bug track system) regarding an apparent bug in Tomcat 3.2's JNI support... I was just wondering if folks were already aware of any JNI problems, or could offer any suggestions for work-arounds. Basically, this bug happens when there are two servlets trying to communicate. As I said in the bug report: >>> The first servlet (BadClient.java) opens a URLConnection to the second servlet (BadServer.java). BadClient uses the URLConnection to open an output stream, then uses the output stream to print some text, which will be read by BadServer. The BadServer servlet then calls request.getReader to get a reader object, to read the text that was sent by BadClient. This all works fine under Tomcat 3.2, when Tomcat is running stand-alone. But if Tomcat 3.2 is running inside IIS, using the JNI connector, there's a problem. BadServer is never able to read any of the text sent by BadClient. The whole process just seems to hang for exactly 1 minute... apparently, something times out after 1 minute, and BadClient stops trying to read the text. Under JNI, the read call returns -1. <<< If anyone has any workarounds, I'd love to know of them. Or for that matter, if this is just a known limitation, I'd like to know. If anyone wants I can mail you two simple servlets that demonstrate the problem. (I included the source code in my bug report, but it looks like the formatting got lost...) Feel free to email me if you'd like source code. Thanks Dave Smith Sr. Software Engineer MapInfo Corp. [EMAIL PROTECTED]
