ApacheConfig returns ClassCastException for mod_jk
Hi, We want to configure tomcat 5.5.17 with mod_jk and change server.xml as below: Engine name=Catalina defaultHost=localhost className=org.apache.jk.config.ApacheConfig The above changed was mentioned at http://tomcat.apache.org/connectors-doc/howto/apache.html; to create a mod_jk.conf-auto file. But, we get an error which sayes: java.lang.ClassCastException: org.apache.jk.config.ApacheConfig at org.apache.catalina.startup.LifecycleListenerRule.begin(LifecycleListenerRule.java:96) at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1275) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:533) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:878) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) Any comments! Regards, Alireza Fattahi - All new Yahoo! Mail The new Interface is stunning in its simplicity and ease of use. - PC Magazine
ApacheConfig returns ClassCastException for mod_jk
Hi, We want to configure tomcat 5.5.17 with mod_jk and change server.xml as below: Engine name=Catalina defaultHost=localhost className=org.apache.jk.config.ApacheConfig The above was mentioned at http://tomcat.apache.org/connectors-doc/howto/apache.html; to create a mod_jk.conf-auto file. But, we get an error which sayes: java.lang.ClassCastException: org.apache.jk.config.ApacheConfig at org.apache.catalina.startup.LifecycleListenerRule.begin(LifecycleListenerRule.java:96) at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1275) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:533) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:878) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) Any comments! Regards, Alireza Fattahi - All New Yahoo! Mail Tired of [EMAIL PROTECTED]@! come-ons? Let our SpamGuard protect you.
Re: ApacheConfig returns ClassCastException for mod_jk
On 7/9/06, Mr Alireza Fattahi [EMAIL PROTECTED] wrote: Hi, We want to configure tomcat 5.5.17 with mod_jk and change server.xml as below: Engine name=Catalina defaultHost=localhost className=org.apache.jk.config.ApacheConfig The above was mentioned at http://tomcat.apache.org/connectors-doc/howto/apache.html; to create a mod_jk.conf-auto file. Alireza, I just read the page you referred to and it said: Engine ... Listener className=org.apache.jk.config.ApacheConfig modJk=/path/to/mod_jk.so / /Engine So you need to add a Listener / element and not add it as an attribute to Engine Also, did you modify your httpd.conf file? Include $TOMCAT_HOME/conf/jk/mod_jk.conf-auto -- brian - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: URGENT HELP NEEDED: mod_jk loadbalancing issues
Hi, First of all - thanks Rainer for willing to look into this issue. Environment description: Web Server: Apache 2.0.52 mod_jk: 1.2.15 OS: RedHat ES 4.2 App. Server: Tomcat 5.5.15 Cluster topology: 4 webservers with mod_jk doing sticky loadbalancing into 10 tomcats MOD_JK Configuration: Pretty much basic mod_jk and Tomcat settings for AJP13 Description of the issue: Under very heavy loads for our standards (about thousand of concurrent users) we start seeing errors (listed at end botton of this e-mail) in the mod_jk error log. Our concern is mod_jk behavior on the web server. We closely monitor apache and Apache itself is not under heavy stress. However, shortly after we start seeing these messages in the mod_jk's error log, web server becomes unresponsive and we have to re-start it. While the web server server is unresponsive we monitor 8009 port - nothing is going on it. We monitor Tomcats and they are fine. As soon as we re-start web servers traffic resumes. Then under heavy loads things break again We are planning on increasing the number of max threads on the Tomcats' AJP connector to imrpove the throughput of the Tomcats. However, our concern is with the web server side lock ups. It seems that mod_jk cannot recover after this oversaturation. TAIL -F FROM THE MOD_JK LOG RIGHT BEFORE IT DIES __ [Fri Jul 07 09:59:43 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:43 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:44 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (IP REMOVED:8009), err=-110 [Fri Jul 07 09:59:44 2006] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:44 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (IP REMOVED:8009), err=-110 [Fri Jul 07 09:59:44 2006] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:44 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (IP REMOVED:8009), err=-110 [Fri Jul 07 09:59:44 2006] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:45 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (IP REMOVED:8009), err=-110 [Fri Jul 07 09:59:45 2006] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) [Fri Jul 07 09:59:45 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:45 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:46 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (IP REMOVED:8009), err=-110 [Fri Jul 07 09:59:46 2006] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) [Fri Jul 07 09:59:46 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:46 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:46 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems
Re: URGENT HELP NEEDED: mod_jk loadbalancing issues
What is your load average under these circumstance? Is each of the 10 tomcats on a seperate physical machine? What are your max thread settings in Tomcat? Are your tomcat machines CPU bound or I/O bound under full load? Alex On 7/9/06, Edmon Begoli [EMAIL PROTECTED] wrote: Hi, First of all - thanks Rainer for willing to look into this issue. Environment description: Web Server: Apache 2.0.52 mod_jk: 1.2.15 OS: RedHat ES 4.2 App. Server: Tomcat 5.5.15 Cluster topology: 4 webservers with mod_jk doing sticky loadbalancing into 10 tomcats MOD_JK Configuration: Pretty much basic mod_jk and Tomcat settings for AJP13 Description of the issue: Under very heavy loads for our standards (about thousand of concurrent users) we start seeing errors (listed at end botton of this e-mail) in the mod_jk error log. Our concern is mod_jk behavior on the web server. We closely monitor apache and Apache itself is not under heavy stress. However, shortly after we start seeing these messages in the mod_jk's error log, web server becomes unresponsive and we have to re-start it. While the web server server is unresponsive we monitor 8009 port - nothing is going on it. We monitor Tomcats and they are fine. As soon as we re-start web servers traffic resumes. Then under heavy loads things break again We are planning on increasing the number of max threads on the Tomcats' AJP connector to imrpove the throughput of the Tomcats. However, our concern is with the web server side lock ups. It seems that mod_jk cannot recover after this oversaturation. TAIL -F FROM THE MOD_JK LOG RIGHT BEFORE IT DIES __ [Fri Jul 07 09:59:43 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:43 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:44 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (IP REMOVED:8009), err=-110 [Fri Jul 07 09:59:44 2006] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:44 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (IP REMOVED:8009), err=-110 [Fri Jul 07 09:59:44 2006] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:44 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (IP REMOVED:8009), err=-110 [Fri Jul 07 09:59:44 2006] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:44 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:45 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (IP REMOVED:8009), err=-110 [Fri Jul 07 09:59:45 2006] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) [Fri Jul 07 09:59:45 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07 09:59:45 2006] [info] ajp_service::jk_ajp_common.c (1749): Sending request to tomcat failed, recoverable operation attempt=1 [Fri Jul 07 09:59:46 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common.c (961): Can't receive the response message from tomcat, network problems or tomcat is down (IP REMOVED:8009), err=-110 [Fri Jul 07 09:59:46 2006] [error] ajp_get_reply::jk_ajp_common.c (1503): Tomcat is down or refused connection. No response has been sent to the client (yet) [Fri Jul 07 09:59:46 2006] [info] ajp_service::jk_ajp_common.c (1721): Receiving from tomcat failed, recoverable operation attempt=0 [Fri Jul 07
users digest attachment problem
Hi, I've subscribed the tomcat users digest mailing list, so that I regulary receive one mail containing the single messages as attachments. Now since the 26.06.2006 the attachments do neither show the subject, nor the from-address any more. All attachments are listed as Unbenannte Anlage (unnamed attachment). The last digest I received where this was working correctly is dated 24 Jun 2006 16:42:08. I'm using Windows 2000, MS Outlook 2003. Did something change within the tomcats mailing list around that date? All other digests I receive like jakarta commons or struts are just working fine. Bjoern Eickvonder Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail bzw. Inhalte hieraus ist nicht gestattet. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
