Could you retry with a more recent mod_jk 1.2.0 (jtc/native) from jakarta-tomcat-connectors ?
- Henri Gomez ___[_]____ EMAIL : [EMAIL PROTECTED] (. .) PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-----Original Message----- >From: Nick Wesselman [mailto:[EMAIL PROTECTED]] >Sent: Thursday, June 13, 2002 4:09 PM >To: [EMAIL PROTECTED] >Subject: Error 500, mod_jk issues > > >We're running Tomcat 4.0.3 on RedHat w/ Apache 1.3 via the mod_jk >connector. > >We received an Error 500, which usually indicates that Tomcat is no >longer running. However in this case it was, it hadn't >crashed. A quick >survey of the logs found these... > >In catalina.out: >Ajp13Connector[8011] No processor available, rejecting this connection > >In mod_jk.log: >[Wed Jun 12 13:37:04 2002] [jk_ajp13_worker.c (381)]: Error >ajp13_process_callback - write failed > >Anyone seen this before? Is it related to this: >http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6068 ? Our native >connector binary might be a bit old. The name of the >precompiled binary >we're using is "mod_jk-3.3-ap13-eapi.so". > >Any ideas? Should we be using the mod_jk-01.so binary from the >4.0.3 build? > >Thanks, >Nick Wesselman >Digital Visions, Inc. > > > >-- >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]>
