There's no need to change connectors.
Your existing JK configuration would have worked fine with Tomcat 4.1.27. The CoyoteConnector is perfectly happy with either JK or JK2.
All you need to do is put your pre-.27 redirector configuration back in place and make sure the ports are correct in server.xml.
John
Thomas Nybro Bolding wrote:
Having just upgraded to Tomcat 4.1.27 I also upgraded from jk to the jk2 redirector as I (has to!) use IIS to validate users etc.
Thing is that with the jk2 connector (isapi_redirector2.dll) my JSP pages are CONSIDERABLY slower, i.e. way to slow to be acceptable.
Does anyone has any experiences with IIS+jk2 or perhaps a few comments to the settings used by http://reynir.net/tomcat/tomcat_IIS_service_jk2.html?
Is it possible to use the old jk (isapi_redirect.dll) under Tomcat 4.1.27 and what needs to be done to accomplish this?
Regards Thomas
<FONT SIZE=1 FACE="Arial">_______________ Vi goer opmaerksom paa, at denne e-mail kan indeholde fortrolig information. Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst informere afsender om fejlen ved at bruge svar-funktionen. Samtidig beder vi dig slette e-mailen i dit system uden at videresende eller kopiere den. Selv om e-mailen og ethvert vedhaeftet bilag efter vores overbevisning er fri for virus og andre fejl, som kan paavirke computeren eller it-systemet, hvori den modtages og laeses, aabnes den paa modtagerens eget ansvar. Vi paatager os ikke noget ansvar for tab og skade, som er opstaaet i forbindelse med at modtage og bruge e-mailen. _______________ Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by sending a reply, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message. </FONT>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
