Re: mod_jk and EAPI
If I had to guess, I'd say that you have incorrectly inserted a Valve/Realm into your server.xml that is not really a Valve/Realm. This error is way too far down the pipeline to have anything to do with mod_jk. My guess is that if you enable the stand-alone Connector and attempt to connect on port 8080, you will get the same error. Jill Veronda [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]. .. I am getting the mod_jk EAPI warning message on apache start. What might be the results of running with this version of mod_jk? I realize I can try to rebuild mod_jk but would like to know if the error I am seeing is due to this problem or not. The error is that jsp pages do not run and in the log file I get: 2002-08-28 11:51:50 Ajp13Processor[8009][4] process: invoke java.lang.NoSuchMethodError at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase .java:436) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:2 46) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) -Jill -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: mod_jk and EAPI
The problem had to do with having old jar files on my classpath. Thanks for your help! -jill -Original Message- From: Bill Barker [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 29, 2002 11:38 PM To: [EMAIL PROTECTED] Subject: Re: mod_jk and EAPI If I had to guess, I'd say that you have incorrectly inserted a Valve/Realm into your server.xml that is not really a Valve/Realm. This error is way too far down the pipeline to have anything to do with mod_jk. My guess is that if you enable the stand-alone Connector and attempt to connect on port 8080, you will get the same error. Jill Veronda [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]. .. I am getting the mod_jk EAPI warning message on apache start. What might be the results of running with this version of mod_jk? I realize I can try to rebuild mod_jk but would like to know if the error I am seeing is due to this problem or not. The error is that jsp pages do not run and in the log file I get: 2002-08-28 11:51:50 Ajp13Processor[8009][4] process: invoke java.lang.NoSuchMethodError at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase .java:436) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:2 46) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) -Jill -- 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]
mod_jk and EAPI
I am getting the mod_jk EAPI warning message on apache start. What might be the results of running with this version of mod_jk? I realize I can try to rebuild mod_jk but would like to know if the error I am seeing is due to this problem or not. The error is that jsp pages do not run and in the log file I get: 2002-08-28 11:51:50 Ajp13Processor[8009][4] process: invoke java.lang.NoSuchMethodError at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:436) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551) at java.lang.Thread.run(Thread.java:479) -Jill -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
mod_jk and EAPI
Hi. I'm trying to compile the mod_jk module on Win32. The version using standard Apache API went right through, and is working perfectly. The I tried to make a version that should use the Apache EAPI, and this is where my problems started. Using the standard Apache source, I get the C:\ApacheGroup\mod_jk\apache1.3\mod_jk.c(1105) : error C2078: too many initializers error when I try to compile with the EAPI option. So I tried first compiling the Apache source with the EAPI option ant the compile mod_jk, but this doesn't seem to change anything. I still get the same error. Has anybody compiled mod_jk on win32 using EAPI? What am I doing wrong? Does anybody, as a last resort, have a win32 mod_jk binary for Apache 1.3.20 that uses EAPI? /Rasmus
mod_jk with EAPI problems
I am using Tomcat with mod_jk in Apache+mod_ssl in Win32. Upon receiving the warning : Loaded DSO modules/mod_jk.dll uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI) I opened mod_jk.dsp into Visual C++, and added /D "EAPI". Upon compiling, I got a "too many initializers" error. Investigating the typedef for module, there was no preprocessor instruction to extend the def for module for EAPI. Grabbing the typedef from the Apache source, I added #ifdef EAPI #ifdef ULTRIX_BRAIN_DEATH void (*add_module) (); void (*remove_module) (); char *(*rewrite_command) (); void (*new_connection) (); void (*close_connection) ();#else void (*add_module) (struct module_struct *); void (*remove_module) (struct module_struct *); char *(*rewrite_command) (cmd_parms *, void *config, const char *); void (*new_connection) (conn_rec *); void (*close_connection) (conn_rec *);#endif The module then compiled without problem. However, when I attempted to use it, the warning persisted! Any help would be appreciated. Bob.
mod_jk for EAPI?
hi, i use apache 1.3.14 + mod-ssl 2.7.2 + openSSL 0.96 on NT 4.0 SP 5, everything works fine. now i want to use tomcat 3.2 and therfor i use mod_jk.dll to enable apache communicating with tomcat. This works fine as well but leavs the errormessage [Mon Dec 04 14:26:45 2000] [warn] Loaded DSO modules/mod_jk.dll uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI) in apache's error.log everytime apache is starting. (it doesn't crash til now, but it isn't the correct solution, right?, and btw, i could imagine, i'am not the only one having this problem) now my question: is it possible to make some -DEAPI-Binary-Version of mod_ssl.dll available at tomcats download-site? or is there any howto on integrating an ssl-aware apache with tomcat on win32? i recompiled for instance mod_jserv for win32 (ApacheModuleJServ.dll) with MS Visual C++ 6.0 with no problems, but the normal version, not the -deapi one. a little recommendation, how to recompile mod_jk for the EAPI wold probably allready help me! so i would be really grateful for all recommendations or hints, many thanks in advance! basti
