Hijacking the coyote connector
In tomcat 5.0.28, we were able to replace the coyote connector using a className setting in the connector in server.xml. In tomcat 5.5.9 it looks like className is ignored. Looking at the source, it looks like the Connector is hardcoded in. Is this the case or am I missing something? My next attempt, I repackaged our connector to replace the org.apache.catalina.connector package and put that in the -Xbootclasspath to override the released version. With -verbose:class set I can see my Connector being loaded, but the next class loaded is java/lang/reflect/InvocationTargetException and the JVM terminates. The documentation says that this is used to wrap an exception when a method or constructor is called by reflection. As I said above it looks to me like the constructor is called directly not via reflection. Am I missing something obvious? I know that using the AJP connector is a cleaner way, but we estimate the serialization overhead will cost us about 5% on our platform. Thanks mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Hijacking the coyote connector
From: Dobbins, Michael G [mailto:[EMAIL PROTECTED] Subject: Hijacking the coyote connector My next attempt, I repackaged our connector to replace the org.apache.catalina.connector package and put that in the -Xbootclasspath I don't think that's the right place. -Xbootclasspath should be used only to override or augment the jars in JAVA_HOME/jre/lib (e.g., rt.jar, jsse.jar), not classes that come out of Tomcat's server/lib. I suspect things ended up under the wrong classloader, making life difficult for all concerned. You will probably have to just replace server/lib/catalina.jar with your modified version. I don't see where className was ever a documented attribute for a Connector element in 5.0 (although it apparently was in 4.1); it is a valid attribute for Service though. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
http connector secure=true
Hi, I'm trying to have one connector on tomcat open with secure=true with out it being SSL or https. I just want request.isSecure() return true. This is the setup for the connector : Connector port=9020 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=99 connectionTimeout=2 disableUploadTimeout=true secure=true scheme=http / The port is opened with out errors, but does never return anything, and I see no errors in my log. Am I missing out on something or is this a bug ?, It works fine with tomcat 4.1.x. Any suggestions ? thanx [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: http connector secure=true
When starting a new thread (ie sending a message to the list about a new topic) please do not reply to an existing message and change the subject line. To many of the list archiving services and mail clients used by list subscribers this makes your new message appear as part of the old thread. This makes it harder for other users to find relevant information when searching the lists. This is known as thread hijacking and is behaviour that is frowned upon on this list. Frequent offenders will be removed from the list. It should also be noted that many list subscribers automatically ignore any messages that hijack another thread. The correct procedure is to create a new message with a new subject. This will start a new thread. Mark tomcat-user-owner Reynir Hubner wrote: Hi, I'm trying to have one connector on tomcat open with secure=true with out it being SSL or https. I just want request.isSecure() return true. This is the setup for the connector : Connector port=9020 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 debug=99 connectionTimeout=2 disableUploadTimeout=true secure=true scheme=http / The port is opened with out errors, but does never return anything, and I see no errors in my log. Am I missing out on something or is this a bug ?, It works fine with tomcat 4.1.x. Any suggestions ? thanx [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Vexing Problem with Tomcat connector
Hello, I have a website that I am migrating to a new server. Server is Redhat ES3 2.4.21-20.0.1.ELsmp. Server version: Apache/2.0.46 I have jakarta-tomcat-5.5.9 installed and working properly on the new server. It is perfectly accessible from the legacy web server. On the Website on the new server, access to jsp based pages give a 503 error. The main page, home.jsp, loads fine in the servlet if no page is given. http://webserver/PI/ The home.jsp spawns a 503 if is in the URL. http://webserver/PI/home.jsp I can successfully get images from the page from the tomcat instance. It does not like the .jsp extension. In the mod_jk log i can see the match made: [Wed Sep 28 10:29:14 2005] [18841:2816] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/PI/*' [Wed Sep 28 10:29:14 2005] [18841:2816] [debug] map_uri_to_worker::jk_uri_worker_map.c (475): Found a wildchar match worker3 - /PI/* However, in the apache access log is the 503. xxx.89.23.173 - - [28/Sep/2005:10:29:14 -0400] GET /PI/home.jsp HTTP/1.1 503 412 - Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 SESSIONID=128F9AD992A16BC3D3EB1ED0AD5549C1 I have watched in Ethereal as no traffic goes from the apache to the tomcat. I have tried using the loopback and local network address. I have tried adding a *.jsp directive to the mod_jk config for the servlet. Any help would be appreciated. I have a dent in my desk from hitting it with my forehead. Apache Config: #INSERT OF TOMCAT CONF PARAMETERS # Load mod_jk module # LoadModule jk_module modules/mod_jk.so LoadModule jk_module /etc/httpd/modules/mod_jk.so # Declare the module for IfModule directive #AddModule mod_jk.c # Where to find workers.properties JkWorkersFile /etc/httpd/conf/workers.properties # Where to put jk logs JkLogFile /var/log/httpd/mod_jk.log # Set the jk log level [debug/error/info] JkLogLevel debug # Select the log format JkLogStampFormat [%a %b %d %H:%M:%S %Y] # JkOptions indicate to send SSL KEY SIZE, JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories # JkRequestLogFormat set the request format JkRequestLogFormat %w %V %T # Send servlet for context /examples to worker named worker1 JkMount /examples/servlet/* worker1 JkMount /PI/* worker3 #JkMount /PI/*.jsp worker3 # Send JSPs for context /examples to worker named worker1 JkMount /examples/*.jsp worker1 JkMount /journals/*.jsp worker1 Worker Properties /etc/httpd/conf/workers.properties # Define some properties workers.apache_log=/var/log/httpd/ workers.tomcat_home=/usr/local/tomcat/jakarta-tomcat-5.5.9 workers.java_home=/usr/bin/java ps=/ # worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=172.20.1.19 worker.worker1.port=8009 # worker.list=worker2 # Set properties for worker2 (ajp13) worker.worker2.type=ajp13 worker.worker2.host=172.20.1.19 worker.worker2.port=10009 # worker.list=worker3 # Set properties for worker3 (ajp13) worker.worker3.type=ajp13 worker.worker3.host=127.0.0.1 worker.worker3.port=8099 # worker.list=worker4 # Set properties for worker4 (ajp13) worker.worker4.type=ajp13 worker.worker4.host=172.20.1.19 worker.worker4.port=8099 _ Tim Pickard CrossRef Systems Support Analyst and Administrator 40 Salem Street Lynnfield, MA 01940 tpickard at crossref dot org 781 295 0072 x27 __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Vexing Problem with Tomcat connector
When starting a new thread (ie sending a message to the list about a new topic) please do not reply to an existing message and change the subject line. To many of the list archiving services and mail clients used by list subscribers this makes your new message appear as part of the old thread. This makes it harder for other users to find relevant information when searching the lists. This is known as thread hijacking and is behaviour that is frowned upon on this list. Frequent offenders will be removed from the list. It should also be noted that many list subscribers automatically ignore any messages that hijack another thread. The correct procedure is to create a new message with a new subject. This will start a new thread. Mark tomcat-user-owner [EMAIL PROTECTED] wrote: Hello, I have a website that I am migrating to a new server. Server is Redhat ES3 2.4.21-20.0.1.ELsmp. Server version: Apache/2.0.46 I have jakarta-tomcat-5.5.9 installed and working properly on the new server. It is perfectly accessible from the legacy web server. On the Website on the new server, access to jsp based pages give a 503 error. The main page, home.jsp, loads fine in the servlet if no page is given. http://webserver/PI/ The home.jsp spawns a 503 if is in the URL. http://webserver/PI/home.jsp I can successfully get images from the page from the tomcat instance. It does not like the .jsp extension. In the mod_jk log i can see the match made: [Wed Sep 28 10:29:14 2005] [18841:2816] [debug] map_uri_to_worker::jk_uri_worker_map.c (461): Attempting to map context URI '/PI/*' [Wed Sep 28 10:29:14 2005] [18841:2816] [debug] map_uri_to_worker::jk_uri_worker_map.c (475): Found a wildchar match worker3 - /PI/* However, in the apache access log is the 503. xxx.89.23.173 - - [28/Sep/2005:10:29:14 -0400] GET /PI/home.jsp HTTP/1.1 503 412 - Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 SESSIONID=128F9AD992A16BC3D3EB1ED0AD5549C1 I have watched in Ethereal as no traffic goes from the apache to the tomcat. I have tried using the loopback and local network address. I have tried adding a *.jsp directive to the mod_jk config for the servlet. Any help would be appreciated. I have a dent in my desk from hitting it with my forehead. Apache Config: #INSERT OF TOMCAT CONF PARAMETERS # Load mod_jk module # LoadModule jk_module modules/mod_jk.so LoadModule jk_module /etc/httpd/modules/mod_jk.so # Declare the module for IfModule directive #AddModule mod_jk.c # Where to find workers.properties JkWorkersFile /etc/httpd/conf/workers.properties # Where to put jk logs JkLogFile /var/log/httpd/mod_jk.log # Set the jk log level [debug/error/info] JkLogLevel debug # Select the log format JkLogStampFormat [%a %b %d %H:%M:%S %Y] # JkOptions indicate to send SSL KEY SIZE, JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories # JkRequestLogFormat set the request format JkRequestLogFormat %w %V %T # Send servlet for context /examples to worker named worker1 JkMount /examples/servlet/* worker1 JkMount /PI/* worker3 #JkMount /PI/*.jsp worker3 # Send JSPs for context /examples to worker named worker1 JkMount /examples/*.jsp worker1 JkMount /journals/*.jsp worker1 Worker Properties /etc/httpd/conf/workers.properties # Define some properties workers.apache_log=/var/log/httpd/ workers.tomcat_home=/usr/local/tomcat/jakarta-tomcat-5.5.9 workers.java_home=/usr/bin/java ps=/ # worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=172.20.1.19 worker.worker1.port=8009 # worker.list=worker2 # Set properties for worker2 (ajp13) worker.worker2.type=ajp13 worker.worker2.host=172.20.1.19 worker.worker2.port=10009 # worker.list=worker3 # Set properties for worker3 (ajp13) worker.worker3.type=ajp13 worker.worker3.host=127.0.0.1 worker.worker3.port=8099 # worker.list=worker4 # Set properties for worker4 (ajp13) worker.worker4.type=ajp13 worker.worker4.host=172.20.1.19 worker.worker4.port=8099 _ Tim Pickard CrossRef Systems Support Analyst and Administrator 40 Salem Street Lynnfield, MA 01940 tpickard at crossref dot org 781 295 0072 x27 __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR
hi, I know the way to access Tomcat JMX support via http adaptor. I also know how to monitor an application via JMX by registering an mbeanserver. But I really confused about accessing Tomcat JMX support via RMI connector: 1. how to configure Mx4j RMI connector with Tomcat 5.5, since only Activating JMX MX4J Http Adaptor could be found in the Tomcat website. 2. after configuring RMI connector, how can I access Tomcat JMX support programmatically? I am not clear about the mbeanserver that tomcat mbeans has been registed. How can I make use of the connector, thread pool, servlet information that Tomcat has already monitored and controlled. Thank you. :) _ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR
Hi, --- Ursprüngliche Nachricht --- Von: jiang ying [EMAIL PROTECTED] An: tomcat-user@jakarta.apache.org Betreff: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR Datum: Wed, 21 Sep 2005 16:26:00 +0800 hi, I know the way to access Tomcat JMX support via http adaptor. I also know how to monitor an application via JMX by registering an mbeanserver. But I really confused about accessing Tomcat JMX support via RMI connector: 1. how to configure Mx4j RMI connector with Tomcat 5.5, since only Activating JMX MX4J Http Adaptor could be found in the Tomcat website. 2. after configuring RMI connector, how can I access Tomcat JMX support programmatically? I am not clear about the mbeanserver that tomcat mbeans has been registed. How can I make use of the connector, thread pool, servlet information that Tomcat has already monitored and controlled. Thank you. :) Have a look at http://jakarta.apache.org/tomcat/tomcat-5.5-doc/monitoring.html. You can then use e.g. MC4J (http://mc4j.org/confluence/display/MC4J/Home?) for monitoring Tomcat. Regards Dirk -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR
Dirk is correct you need to check out the doc in order to understand your options. To add a little specificity to your challenge, you need to do at least the following to get going: 1) set remote monitoring options when you are starting the JVM. This can be accomplished multiple ways. One place is in catalina.bat 1) set remote monitoring port -Dcom.sun.management.jmxremote.port= 2) turn on remote monitoring-Dcom.sun.management.jmxremote there are others for SSL and authentication and you have to decide if they are needed. 2) create the RMI connector client in a very small bit of java code as well as establish as use the MBeanServerConnection class to access TOMCAT domains and MBeans. THis is probably about a 1/2 dozen LOC to gain access and there are examples to be found. You can use JConsole (JMX monitoring from SUN) which is located in the JDK 1.5 BIN directory to validate configuration tasks without any coding or installing any other software. hope this helps. - andy Dirk Weigenand [EMAIL PROTECTED] wrote: Hi, --- Ursprüngliche Nachricht --- Von: jiang ying An: tomcat-user@jakarta.apache.org Betreff: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR Datum: Wed, 21 Sep 2005 16:26:00 +0800 hi, I know the way to access Tomcat JMX support via http adaptor. I also know how to monitor an application via JMX by registering an mbeanserver. But I really confused about accessing Tomcat JMX support via RMI connector: 1. how to configure Mx4j RMI connector with Tomcat 5.5, since only Activating JMX MX4J Http Adaptor could be found in the Tomcat website. 2. after configuring RMI connector, how can I access Tomcat JMX support programmatically? I am not clear about the mbeanserver that tomcat mbeans has been registed. How can I make use of the connector, thread pool, servlet information that Tomcat has already monitored and controlled. Thank you. :) Have a look at http://jakarta.apache.org/tomcat/tomcat-5.5-doc/monitoring.html. You can then use e.g. MC4J (http://mc4j.org/confluence/display/MC4J/Home?) for monitoring Tomcat. Regards Dirk -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Yahoo! for Good Click here to donate to the Hurricane Katrina relief effort.
Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR
Thank you. Before posting my question, I have studied http://jakarta.apache.org/tomcat/tomcat-5.5-doc/monitoring.html. It explains the way to activate HTTP adaptor. I have also browsed the mx4j website and found little information. MC4j(http://mc4j.org/confluence/display/MC4J/Home?) that you suggest really do me a lot. Finally I am able to monitor the tomcat via RMI connector. Thanks a lot. cylinder From: Dirk Weigenand [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: Tomcat Users List tomcat-user@jakarta.apache.org Subject: Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR Date: Wed, 21 Sep 2005 11:49:58 +0200 (MEST) Hi, --- Urspr�ngliche Nachricht --- Von: jiang ying [EMAIL PROTECTED] An: tomcat-user@jakarta.apache.org Betreff: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR Datum: Wed, 21 Sep 2005 16:26:00 +0800 hi, I know the way to access Tomcat JMX support via http adaptor. I also know how to monitor an application via JMX by registering an mbeanserver. But I really confused about accessing Tomcat JMX support via RMI connector: 1. how to configure Mx4j RMI connector with Tomcat 5.5, since only Activating JMX MX4J Http Adaptor could be found in the Tomcat website. 2. after configuring RMI connector, how can I access Tomcat JMX support programmatically? I am not clear about the mbeanserver that tomcat mbeans has been registed. How can I make use of the connector, thread pool, servlet information that Tomcat has already monitored and controlled. Thank you. :) Have a look at http://jakarta.apache.org/tomcat/tomcat-5.5-doc/monitoring.html. You can then use e.g. MC4J (http://mc4j.org/confluence/display/MC4J/Home?) for monitoring Tomcat. Regards Dirk -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR
Hi, Before posting my question, I have studied http://jakarta.apache.org/tomcat/tomcat-5.5-doc/monitoring.html. It explains the way to activate HTTP adaptor. Well it explains how to activate jmx remote monitoring right at the start of the page. Did you follow the link to SUNs web site? There you'll find a thorough explanation what all the possible properties and their meaning are. I mean the properties in those boxes in the 'Enabling remote JMX' section, i.e.: set CATALINA_OPTS=-Dcom.sun.management.jmxremote \ -Dcom.sun.management.jmxremote.port=%my.jmx.port% \ -Dcom.sun.management.jmxremote.ssl=false \ -Dcom.sun.management.jmxremote.authenticate=false Regards Dirk -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR
I did follow the link to SUNs web site and did the exercise. I know how to use JMX, but I don't know how to get the mbeanserver that the tomcat JMX support registed. And I've been searching the material about mx4j at all times :(. From: Dirk Weigenand [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: Tomcat Users List tomcat-user@jakarta.apache.org Subject: Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR Date: Wed, 21 Sep 2005 16:57:20 +0200 (MEST) Hi, Before posting my question, I have studied http://jakarta.apache.org/tomcat/tomcat-5.5-doc/monitoring.html. It explains the way to activate HTTP adaptor. Well it explains how to activate jmx remote monitoring right at the start of the page. Did you follow the link to SUNs web site? There you'll find a thorough explanation what all the possible properties and their meaning are. I mean the properties in those boxes in the 'Enabling remote JMX' section, i.e.: set CATALINA_OPTS=-Dcom.sun.management.jmxremote \ -Dcom.sun.management.jmxremote.port=%my.jmx.port% \ -Dcom.sun.management.jmxremote.ssl=false \ -Dcom.sun.management.jmxremote.authenticate=false Regards Dirk -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen f�r GMX Partner: http://www.gmx.net/de/go/partner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ 免费下载 MSN Explorer: http://explorer.msn.com/lccn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR
Hi, --- Ursprüngliche Nachricht --- Von: jiang ying [EMAIL PROTECTED] An: tomcat-user@jakarta.apache.org Betreff: Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR Datum: Wed, 21 Sep 2005 23:38:36 +0800 I did follow the link to SUNs web site and did the exercise. I know how to use JMX, but I don't know how to get the mbeanserver that the tomcat JMX support registed. And I've been searching the material about mx4j at all times :(. Mmh, using SUNs reference implementation: MBeanServer mbeanServer = (MBeanServer)MBeanServerFactory.findMBeanServer( null ).get( 0 ); -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse für Mail, Message, More +++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR
well, after studied MC4j, I've already solved the problem with the code String urlForJMX = service:jmx:rmi:///jndi/rmi://localhost:9004/jmxrmi; MBeanServerConnection jmxServerConnection = JMXConnectorFactory.connect( new JMXServiceURL( urlForJMX ), null).getMBeanServerConnection(); A little different from yours, but it works. :) I've been wasting time finding the solution about mx4j and finally solved it by using mc4j. Thank you. :) From: Dirk Weigenand [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: Tomcat Users List tomcat-user@jakarta.apache.org Subject: Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR Date: Wed, 21 Sep 2005 17:58:33 +0200 (MEST) Hi, --- Urspr�ngliche Nachricht --- Von: jiang ying [EMAIL PROTECTED] An: tomcat-user@jakarta.apache.org Betreff: Re: ACCESSING TOMCAT JMX SUPPORT REMORTELY VIA THE RMI CONNECTOR Datum: Wed, 21 Sep 2005 23:38:36 +0800 I did follow the link to SUNs web site and did the exercise. I know how to use JMX, but I don't know how to get the mbeanserver that the tomcat JMX support registed. And I've been searching the material about mx4j at all times :(. Mmh, using SUNs reference implementation: MBeanServer mbeanServer = (MBeanServer)MBeanServerFactory.findMBeanServer( null ).get( 0 ); -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse f�r Mail, Message, More +++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Jk connector fails to connect... after some time working
Dear Tomcat list, I have a problem with our Tomcat server that is becoming really criticall for us. I need some help or at least a clue. There are quite a lot of people with a similar problem but I haven't found the solution. Let's go to the problem: After some time of working fine all the jsp pages served by the Tomcat stop to response anything. But Apache pages keep working fine and Tomcat alone serves all jsp without no problem at 8080 port. Restarting Tomcat solves the problem... for some time. The logs reflect some problems: /etc/httpd/logs/mod_jk.log: [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1468)]: sending request to tomcat failed in send loop. err=0 [Sun Sep 18 06:00:10 2005] [jk_connect.c (188)]: jk_open_socket, connect() failed errno = 111 [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (720)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong host/port (127.0.0.1:8009). Failed errno = 111 [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1024)]: Error connecting to the Tomcat process. [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1468)]: sending request to tomcat failed in send loop. err=1 [Sun Sep 18 06:00:10 2005] [jk_connect.c (188)]: jk_open_socket, connect() failed errno = 111 [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (720)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong host/port (127.0.0.1:8009). Failed errno = 111 [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1024)]: Error connecting to the Tomcat process. [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1468)]: sending request to tomcat failed in send loop. err=2 [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1477)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=ajp13 failed errno = 111 [Sun Sep 18 06:00:18 2005] [jk_ajp_common.c (783)]: ERROR: can't receive the response message from tomcat, network problems or tomcat is down (127.0.0.1:8009), err=-1 We have an apache 2.50 under Madriva Linux. The connector is 1.2.6 and Tomcat 4.1 I hope you may know what may be affecting the server. Thank you in advance. Borja - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jk connector fails to connect... after some time working
hi, i think its just apache trying to connect to tomcat using JK while the tomcat not confiigured to answer this request ? since you execute your jsp on (8080) i hope i understands your matter if not please try to be clearer about it if you need help with connnecting apache -mod_jk-tomcat i can provides you some working configs TC5.x regards Yassine directBOX Reply --- From: Borja Bravo Alférez ([EMAIL PROTECTED]) To: TomcatUsersList (tomcat-user@jakarta.apache.org) Date: 19.09.2005 11:26:57 Dear Tomcat list, I have a problem with our Tomcat server that is becoming really criticall for us. I need some help or at least a clue. There are quite a lot of people with a similar problem but I haven't found the solution. Let's go to the problem: After some time of working fine all the jsp pages served by the Tomcat stop to response anything. But Apache pages keep working fine and Tomcat alone serves all jsp without no problem at 8080 port. Restarting Tomcat solves the problem... for some time. The logs reflect some problems: /etc/httpd/logs/mod_jk.log: [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1468)]: sending request to tomcat failed in send loop. err=0 [Sun Sep 18 06:00:10 2005] [jk_connect.c (188)]: jk_open_socket, connect() failed errno = 111 [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (720)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong host/port (127.0.0.1:8009). Failed errno = 111 [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1024)]: Error connecting to the Tomcat process. [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1468)]: sending request to tomcat failed in send loop. err=1 [Sun Sep 18 06:00:10 2005] [jk_connect.c (188)]: jk_open_socket, connect() failed errno = 111 [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (720)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong host/port (127.0.0.1:8009). Failed errno = 111 [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1024)]: Error connecting to the Tomcat process. [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1468)]: sending request to tomcat failed in send loop. err=2 [Sun Sep 18 06:00:10 2005] [jk_ajp_common.c (1477)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=ajp13 failed errno = 111 [Sun Sep 18 06:00:18 2005] [jk_ajp_common.c (783)]: ERROR: can't receive the response message from tomcat, network problems or tomcat is down (127.0.0.1:8009), err=-1 We have an apache 2.50 under Madriva Linux. The connector is 1.2.6 and Tomcat 4.1 I hope you may know what may be affecting the server. Thank you in advance. Borja - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Verpassen Sie keine eBay-Auktion und bieten Sie bequem und schnell über das Telefon mit http://www.telefonbieten.de Ihre eMails auf dem Handy lesen - ohne Zeitverlust - 24h/Tag eMail, FAX, SMS, VoiceMail mit http://www.directbox.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jk connector fails to connect... after some time working
On Mon, 19 Sep 2005, Yassine ELassad wrote: hi, i think its just apache trying to connect to tomcat using JK while the tomcat not confiigured to answer this request ? since you execute your jsp on (8080) i hope i understands your matter if not please try to be clearer about it if you need help with connnecting apache -mod_jk-tomcat i can provides you some working configs TC5.x regards Yassine Thank you for your effort. I am sure there can be some configuration issues. But I do not understand why it can connect during hours and suddenly it can't. ( persistent connections? running out of something? Making wild hypothesis is not too hard ) Anyway, Any kind of server.xml examples of connectors will be really apreciated although I will prefer a 4.1 configuration. My jk connector config is: Connector className=org.apache.coyote.tomcat4.CoyoteConnector acceptCount=300 bufferSize=2048 connectionTimeout=1 debug=7 disableUploadTimeout=false enableLookups=true maxKeepAliveRequests=1000 maxProcessors=300 minProcessors=30 port=8009 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler proxyPort=0 redirectPort=8443 scheme=http secure=false tcpNoDelay=true useURIValidationHack=false Factory className=org.apache.catalina.net.DefaultServerSocketFactory/ /Connector ( I am making changes quite often looking a stable configuration ) Regards, Borja - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Jk connector fails to connect... after some time working
here it is my one and how i configured it on 5.0.28: what should be done: -- on your Webserver (Apache): there should be some Namensbasd Virtual Host Websites, which should runs some Java Servlets Apache have to foreward these request where they belon to (TC) Tomcat Configuration: - after installing jakarta-tomcat and apache2-jakarta-tomcat-connectors. you should look for your tomcat_base/conf/server.xml ../jk2.properties i eliminated every thing which is not needed and there is only the server and the service which are needed to connect to apache -- start -- Server port=8005 shutdown=SHUTDOWN debug=0 Service name=Tomcat-Apache !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat5.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- While starting off, leave debugging high for help in diagn. -- !-- When done, turn it back to 0 -- Engine name=Apache defaultHost=www.yourhost.foo debug=9 Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true/ !-- Access log processes all requests for this virtual host. -- !-- Leave pattern=combined for the most comprehensive logging -- Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=eddie_access_log. suffix=.txt pattern=combined resolveHosts=false/ Host name=www.yourhost2.foo debug=0 appBase=/srv/www/htdocs/manfred/www.yourhost2.foo unpackWARs=true autoDeploy=true Context path= docBase= debug=0/ Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=tomcat-yourhost2-foo_access_log. suffix=.txt pattern=combined resolveHosts=false/ /Host Host name=www.yourhost.foo debug=0 appBase=/srv/www/htdocs/manfred/ unpackWARs=true autoDeploy=true Context path= docBase= debug=0/ Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=tomcat-yourhost-foo_access_log. suffix=.txt pattern=combined resolveHosts=false/ /Host /Engine /Service /Server --- end -- jk2.properties: - uncoment these 2 lines -- start -- handler.list=channelSocket,request channelSocket.port=8009 --- ende -- TC config is now done configuration of Apache: I assume you already installed jk on apache and its working now look for your default /etc/apache2/workers2.properties: -- start -- # only at beginnin. In production uncomment it out [logger.apache2] level=ERROR [shm] file=/var/log/apache2/shm.file size=1048576 # Example socket channel, override port and host. [channel.socket:127.0.0.1:8009] port=8009 host=127.0.0.1 # define the worker [ajp13:127.0.0.1:8009] channel=channel.socket:127.0.0.1:8009 # Uri mapping in the vhost configs
Re: Re: Jk connector fails to connect... after some time working ( seems solved )
Hi, After changing the timeout to 10 seconds it _seems_ to work. It was at cero so it could have run out of connections. It has been 6 hours of uptime. Much better. thank you for everything, Borja On Mon, 19 Sep 2005, Yassine ELassad wrote: here it is my one and how i configured it on 5.0.28: what should be done: -- on your Webserver (Apache): there should be some Namensbasd Virtual Host Websites, which should runs some Java Servlets Apache have to foreward these request where they belon to (TC) Tomcat Configuration: - after installing jakarta-tomcat and apache2-jakarta-tomcat-connectors. you should look for your tomcat_base/conf/server.xml ../jk2.properties i eliminated every thing which is not needed and there is only the server and the service which are needed to connect to apache -- start -- Server port=8005 shutdown=SHUTDOWN debug=0 Service name=Tomcat-Apache !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat5.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ !-- While starting off, leave debugging high for help in diagn. -- !-- When done, turn it back to 0 -- Engine name=Apache defaultHost=www.yourhost.foo debug=9 Logger className=org.apache.catalina.logger.FileLogger prefix=apache_log. suffix=.txt timestamp=true/ !-- Access log processes all requests for this virtual host. -- !-- Leave pattern=combined for the most comprehensive logging -- Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=eddie_access_log. suffix=.txt pattern=combined resolveHosts=false/ Host name=www.yourhost2.foo debug=0 appBase=/srv/www/htdocs/manfred/www.yourhost2.foo unpackWARs=true autoDeploy=true Context path= docBase= debug=0/ Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=tomcat-yourhost2-foo_access_log. suffix=.txt pattern=combined resolveHosts=false/ /Host Host name=www.yourhost.foo debug=0 appBase=/srv/www/htdocs/manfred/ unpackWARs=true autoDeploy=true Context path= docBase= debug=0/ Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=tomcat-yourhost-foo_access_log. suffix=.txt pattern=combined resolveHosts=false/ /Host /Engine /Service /Server --- end -- jk2.properties: - uncoment these 2 lines -- start -- handler.list=channelSocket,request channelSocket.port=8009 --- ende -- TC config is now done configuration of Apache: I assume you already installed jk on apache and its working now look for your default /etc/apache2/workers2.properties: -- start -- # only at beginnin. In production uncomment it out [logger.apache2] level=ERROR [shm] file=/var/log/apache2/shm.file size=1048576 # Example
Re: AJP connector maxthreads problem
Thank you David and Wade for this information. I now have an idea what caused it. I have a fairly new programme that uses too many threads, and I can deal with it. However I would like to try the thread dump, but running kill -3 xxx or kill -QUIT xxx on the first Tomcat thread found after running ps ax does nothing. It doesn't kill the thread and nor does it print out the trace. I've experimented using the kill manual but I don't seem to be getting anywhere. I still have a 1.4 JVM unfortunately (as I saw that Jikes couldn't yet be used with 1.5). Am I doing something wrong - how else can I get a thread dump? I have Debian Linux 2.4.24 for what it's worth. Malcolm Warren Wade Chandler wrote: --- David Wall [EMAIL PROTECTED] wrote: 1) We have only a moderately busy site with about 500 new visitors entering from outside every day, so it would have thought it would be fairly difficult for them to use up all the 75 connections at the same time, but I do have some programmes that create their own threads, though in a fairly limited way. In your expert view are 75 jk2 connections sufficient for this kind of moderate use, or is it likely I've some kind of problem I've got to get to the bottom of? I've been through my recent new applications, and there really is nothing that could have created this problem recently. It sure sounds like something is not releasing the threads. In low volume sites, having 75 concurrent requests would be high. It sounds like they are not being properly released when done. 2) I've set connectionTimeout=2, which seems to be what everybody else was setting it to, can I reduce this without any problem? It seems quite long, 20 seconds, why hang on to connections for so long, or is there a lot of overhead in creating them? I believe this value is how long Tomcat will wait to receive the actual HTTP requests after it establishes the connection. So 20 seconds is more than adequate. Making it too low may cause people are slower dial up or the like to get problems. 3) If I want to, can I increase my max connections to 125 without any qualms? - This would appear to be the simplest solution here. That would certainly work, but if you are running out because threads are not being released, it just means you'll run out later than before. Good luck, David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Dump a stack trace of the JVM and see where it is locked up in the different threads. If you are able to run a 1.5 VM this would be much easier as you could use jps and jstack to dump all of this externally for your running tomcat process. Anyways, get a stack trace for all of your threads, and you can get a better idea of what is going on. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AJP connector maxthreads problem
P.S. I've found the stack trace in catalina.out. I thought I could pipe it to a file, but never mind. Anyway thankyou for your help, I think I can get to the bottom of it all now. Wade Chandler wrote: --- David Wall [EMAIL PROTECTED] wrote: 1) We have only a moderately busy site with about 500 new visitors entering from outside every day, so it would have thought it would be fairly difficult for them to use up all the 75 connections at the same time, but I do have some programmes that create their own threads, though in a fairly limited way. In your expert view are 75 jk2 connections sufficient for this kind of moderate use, or is it likely I've some kind of problem I've got to get to the bottom of? I've been through my recent new applications, and there really is nothing that could have created this problem recently. It sure sounds like something is not releasing the threads. In low volume sites, having 75 concurrent requests would be high. It sounds like they are not being properly released when done. 2) I've set connectionTimeout=2, which seems to be what everybody else was setting it to, can I reduce this without any problem? It seems quite long, 20 seconds, why hang on to connections for so long, or is there a lot of overhead in creating them? I believe this value is how long Tomcat will wait to receive the actual HTTP requests after it establishes the connection. So 20 seconds is more than adequate. Making it too low may cause people are slower dial up or the like to get problems. 3) If I want to, can I increase my max connections to 125 without any qualms? - This would appear to be the simplest solution here. That would certainly work, but if you are running out because threads are not being released, it just means you'll run out later than before. Good luck, David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Dump a stack trace of the JVM and see where it is locked up in the different threads. If you are able to run a 1.5 VM this would be much easier as you could use jps and jstack to dump all of this externally for your running tomcat process. Anyways, get a stack trace for all of your threads, and you can get a better idea of what is going on. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AJP connector maxthreads problem
I've got Tomcat 4.1.30 and Apache 1.3 on Linux and I've been using the jk2 connector for a year and a half without any problems. Now I've suddenly got Tomcat stopping with the following message: All threads (75) are currently busy, waiting. Increase maxThreads (75) or check the servlet status. Now I've done a lot of homework, googled and searched the jakarta site, but I can't seem to get answers to my specific questions, which if any of you are willing to help me, should be fairly simple to answer. 1) We have only a moderately busy site with about 500 new visitors entering from outside every day, so it would have thought it would be fairly difficult for them to use up all the 75 connections at the same time, but I do have some programmes that create their own threads, though in a fairly limited way. In your expert view are 75 jk2 connections sufficient for this kind of moderate use, or is it likely I've some kind of problem I've got to get to the bottom of? I've been through my recent new applications, and there really is nothing that could have created this problem recently. 2) I've set connectionTimeout=2, which seems to be what everybody else was setting it to, can I reduce this without any problem? It seems quite long, 20 seconds, why hang on to connections for so long, or is there a lot of overhead in creating them? 3) If I want to, can I increase my max connections to 125 without any qualms? - This would appear to be the simplest solution here. Thanks for any help on this. Regards, Malcolm Warren - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AJP connector maxthreads problem
1) We have only a moderately busy site with about 500 new visitors entering from outside every day, so it would have thought it would be fairly difficult for them to use up all the 75 connections at the same time, but I do have some programmes that create their own threads, though in a fairly limited way. In your expert view are 75 jk2 connections sufficient for this kind of moderate use, or is it likely I've some kind of problem I've got to get to the bottom of? I've been through my recent new applications, and there really is nothing that could have created this problem recently. It sure sounds like something is not releasing the threads. In low volume sites, having 75 concurrent requests would be high. It sounds like they are not being properly released when done. 2) I've set connectionTimeout=2, which seems to be what everybody else was setting it to, can I reduce this without any problem? It seems quite long, 20 seconds, why hang on to connections for so long, or is there a lot of overhead in creating them? I believe this value is how long Tomcat will wait to receive the actual HTTP requests after it establishes the connection. So 20 seconds is more than adequate. Making it too low may cause people are slower dial up or the like to get problems. 3) If I want to, can I increase my max connections to 125 without any qualms? - This would appear to be the simplest solution here. That would certainly work, but if you are running out because threads are not being released, it just means you'll run out later than before. Good luck, David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AJP connector maxthreads problem
--- David Wall [EMAIL PROTECTED] wrote: 1) We have only a moderately busy site with about 500 new visitors entering from outside every day, so it would have thought it would be fairly difficult for them to use up all the 75 connections at the same time, but I do have some programmes that create their own threads, though in a fairly limited way. In your expert view are 75 jk2 connections sufficient for this kind of moderate use, or is it likely I've some kind of problem I've got to get to the bottom of? I've been through my recent new applications, and there really is nothing that could have created this problem recently. It sure sounds like something is not releasing the threads. In low volume sites, having 75 concurrent requests would be high. It sounds like they are not being properly released when done. 2) I've set connectionTimeout=2, which seems to be what everybody else was setting it to, can I reduce this without any problem? It seems quite long, 20 seconds, why hang on to connections for so long, or is there a lot of overhead in creating them? I believe this value is how long Tomcat will wait to receive the actual HTTP requests after it establishes the connection. So 20 seconds is more than adequate. Making it too low may cause people are slower dial up or the like to get problems. 3) If I want to, can I increase my max connections to 125 without any qualms? - This would appear to be the simplest solution here. That would certainly work, but if you are running out because threads are not being released, it just means you'll run out later than before. Good luck, David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Dump a stack trace of the JVM and see where it is locked up in the different threads. If you are able to run a 1.5 VM this would be much easier as you could use jps and jstack to dump all of this externally for your running tomcat process. Anyways, get a stack trace for all of your threads, and you can get a better idea of what is going on. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connect IIS 6 to Tomcat 5 using Jakarta JK connector: steps, tips for J2EE newbies
This doc is targeted at developers using Macromedia Flex which is just a J2EE application. It might still be of use to newbies here though. It uses the Jakarta Tomcat JK installer. Please note the security caveat near the end. Corrections welcome. http://www.cflex.net/showfiledetails.cfm?ChannelID=1Object=FileobjectI D=296 Tracy
JK Connector with IIS
We're are successfully using the JK connector between IIS 6.0 and Tomcat 5.0.28 to forward on requests. We starting to run into some configuration issues that I haven't seen any documentation for. I guess I don't truly know what is possible so I thought I would ask. Is there a way to configure the connector so that www.somewebsite.com can only redirect to a specific tomcat web application and have www.someotherwebsite.com only point to a different tomcat web application all together. It appears that once a web site on IIS is setup with the redirector filter it will pass through to what ever tomcat application is there. So, for example www.somewebsite.com/tomcatapp1 would pass on, but www.somewebsite.com/tomcatapp2 would not. Next, is it possible to setup the connector so www.somewebsite.com would go straight into an application. As an example, I could use www.somewebsite.com and not have to type in www.somewebsite.com/tomcatappcontext. Finally, IIS is where the SSL certificates are located. What I would like to do for some applications is force http traffic to https. In IIS I can shut down http access, but in some instances I don't want to do that and would like to redirect it into it. If I were to use a security-constraint and set the redirect to the secure port on IIS would it redirect to IIS or would it choke? Thanks for any help, Joe Plautz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JK Connector with IIS
I am a rank newbie with this stuff, so please correct any nonsense!. First, can you not achieve your fist goal using the context specification in the uriworkermap.properties file? If tomcatapp2 is not in one of the specified contexts, you should not be able to access it. Second, To get a tomcat app to act like a default page in IIS, you can use default.htm for example, and in its properties specify Redirection to an URL, then specify the URL to the Tomcat app, using www.somewebsite.com/tomcatappcontext/myApp.jsp. Be sure default.htm is the first in the list in IIS. Tracy -Original Message- From: Joe Plautz [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 07, 2005 11:51 AM To: Tomcat Users List Subject: JK Connector with IIS We're are successfully using the JK connector between IIS 6.0 and Tomcat 5.0.28 to forward on requests. We starting to run into some configuration issues that I haven't seen any documentation for. I guess I don't truly know what is possible so I thought I would ask. Is there a way to configure the connector so that www.somewebsite.com can only redirect to a specific tomcat web application and have www.someotherwebsite.com only point to a different tomcat web application all together. It appears that once a web site on IIS is setup with the redirector filter it will pass through to what ever tomcat application is there. So, for example www.somewebsite.com/tomcatapp1 would pass on, but www.somewebsite.com/tomcatapp2 would not. Next, is it possible to setup the connector so www.somewebsite.com would go straight into an application. As an example, I could use www.somewebsite.com and not have to type in www.somewebsite.com/tomcatappcontext. Finally, IIS is where the SSL certificates are located. What I would like to do for some applications is force http traffic to https. In IIS I can shut down http access, but in some instances I don't want to do that and would like to redirect it into it. If I were to use a security-constraint and set the redirect to the secure port on IIS would it redirect to IIS or would it choke? Thanks for any help, Joe Plautz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
IIS connector problem
I'm using Tomcat 5.5.9 and IIS 6 on a Windows 2003 machine. Isapi_redirect.dll (version 1.2.14) seems to work if use a full url such as this: http://localhost/jsp-examples/index.html All the various jsp examples work. However, if I don't fully specify a document, such as http://localhost/jsp-examples, I get a 404 error. If I use http://localhost:8080/jsp-examples things work. I have [uri:/jsp-examples/*] in my workers2.properties, and I thought that should ensure that pages would be passed to Tomcat for handling. Unless Tomcat isn't finding (or using) my configuration file...? Other (probably related) symptoms: I'm not getting any information into the isapi_redirect.log file. The folder where it should be exists, and its pointer is in the registry, but nothing is getting there... No shm.file is being created in the work folder. Also, I'm not seeing any isapi_redirect.dll entries in the IIS logfiles (which should be there if IIS is passing data onwards?). If this wasn't a clean installation, I'd think something else was handling jsp requests. I've been trying to see if there's a detail I've missed, but sifting through the different howto's (for older versions) has been challenging. Thanks in advance, Mike P.S. I installed the connector using the exe installation (isapi_redirect-1.2.14.exe) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat5.5.9 - Apache Connector
Hi, I'm trying to configure the Apache-Tomcat Connector for Apache 2.0 and Tomcat 5.5.9 on my Redhat ES3.0. I downloaded the mod_jk (1.2.14) connector files : prefork and worker .so files. I' trying the Using TomCat Autoconfigure as given in the Apache website : http://jakarta.apache.org/tomcat/connectors-doc/howto/apache.html. The problem : As per the site: After making changes to Apache's httpd.conf anf Tomcat's server.xml and restarting Tomcat, the mod_jk.conf file must get generated. But this mod_jk.conf is not being generated. Where could the mistake be? Could anyone help me? Regards Deepak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ssl connector
In server.xml I configured an ssl connector like this:
Connector port=8443 address=${jboss.bind.address} maxThreads=100
strategy=ms maxHttpHeaderSize=8192 emptySessionPath=true
scheme=https secure=true clientAuth=true
keystoreFile=${jboss.server.home.dir}/keystore keystorePass=xx
password=yy
sslProtocol = TLS /
clientAuth=true requires a client certificate. If a user doesn't have a
certificate, I would like to redirect to a http-connection or show a costum
error page. how can I realize this redirect/error page in the connector?
Any thoughts?
Cheers,
Dani
The information contained herein is confidential and is intended solely for the
addressee. Access by any other party is unauthorised without the express
written permission of the sender. If you are not the intended recipient, please
contact the sender either via the company switchboard on +44 (0)20 7623 8000, or
via e-mail return. If you have received this e-mail in error or wish to read our
e-mail disclaimer statement and monitoring policy, please refer to
http://www.drkw.com/disc/email/ or contact the sender. 3166
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Long refresh delay with apache connector
Long refresh delay with apache connector Hi, When I make a out.flush() and response.flushBuffer() the browser gets refreshed but when I go through the apache connector, the browser refreshes only when the servlet is finished. The servlet might long for a long time, how can I provide some feedback? Zsolt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Long refresh delay with apache connector
Like this perhaps? http://www.unix.org.ua/orelly/java-ent/servlet/ch06_03.htm Best regards Robert -Original Message- From: Zsolt [mailto:[EMAIL PROTECTED] Sent: 22 August 2005 13:22 To: Tomcat Users List Subject: Long refresh delay with apache connector Long refresh delay with apache connector Hi, When I make a out.flush() and response.flushBuffer() the browser gets refreshed but when I go through the apache connector, the browser refreshes only when the servlet is finished. The servlet might long for a long time, how can I provide some feedback? Zsolt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The information contained in this message is intended only for the recipient, and may be a confidential attorney-client communication or may otherwise be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please be aware that any dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the message and deleting it from your computer. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mysql, Tomcat and Connector/mxj
All, Has anyone successfully run Connector MXJ successfully with Tomcat, Standalone, or with JBoss? Connector MXJ allows you to manage MySQL databases through JDBC or JMX MBeans. - andy - Start your day with Yahoo! - make it your home page
Error message in isapi.log of jk-connector IIS/Tomcat
Hi, on a customer system we have the following error message written into the log very often: [Thu Jul 28 14:27:52 2005] [error] write::jk_isapi_plugin.c (619): WriteClient failed with 2746 What does this message mean? What might be the problem causing this error? And what could I do to fix it? Thanx in advance, Ingo -- PIRONET NDH AG Ingo Rockel - Produktentwicklung Maarweg 149-161, 50825 Koeln Tel.: +49 (0)221-770-1788 / Fax: +49 (0)221-770-1005 mailto:[EMAIL PROTECTED] - http://www.pironet-ndh.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: What is the current stable version of jk connector?
Thanks for the info. I also noticed that the ChangeLog link is still pointing to v 1.2.13. And any idea as to whether the configuration pages are updated or not? Thanks, gary -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 27, 2005 07:00 To: Tomcat Users List Subject: Re: What is the current stable version of jk connector? Gary Moh wrote: According to http://www.apache.org/dist/jakarta/tomcat-connectors/jk/, the current stable version is 1.2.10. Thanks for spotting that. Updated to reflect the 1.2.14 stable. Now, four additional releases have been made. Does 1.2.10 remain the stable version? No. All other versions could be found in the archive.apache.org. Well it will probably take couple of days until all mirror sites pick up the current dist topology. Regards, Mladen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: What is the current stable version of jk connector?
Hi Gary. When I asked the same question a while ago the (unofficial) feedback I got was that 1.2.13 was the latest stable release however, after posting a bug report into the bug tracking system (http://issues.apache.org/bugzilla/show_bug.cgi?id=35755), the update I got was that 1.2.13 was never voted as stable and that I should use that. Also, looking at the documentation (http://jakarta.apache.org/tomcat/connectors-doc/index.html) again it seems to have been updated to say that 1.2.14 is the latest stable release. Hope this helps. Alex -Original Message- From: Gary Moh [mailto:[EMAIL PROTECTED] Sent: 27 July 2005 03:15 To: tomcat-user@jakarta.apache.org Subject: What is the current stable version of jk connector? According to http://www.apache.org/dist/jakarta/tomcat-connectors/jk/, the current stable version is 1.2.10. Now, four additional releases have been made. Does 1.2.10 remain the stable version? gary - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is the current stable version of jk connector?
Gary Moh wrote: According to http://www.apache.org/dist/jakarta/tomcat-connectors/jk/, the current stable version is 1.2.10. Thanks for spotting that. Updated to reflect the 1.2.14 stable. Now, four additional releases have been made. Does 1.2.10 remain the stable version? No. All other versions could be found in the archive.apache.org. Well it will probably take couple of days until all mirror sites pick up the current dist topology. Regards, Mladen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What is the current stable version of jk connector?
According to http://www.apache.org/dist/jakarta/tomcat-connectors/jk/, the current stable version is 1.2.10. Now, four additional releases have been made. Does 1.2.10 remain the stable version? gary
Which is the latest 'stable' JK connector?
Hi, Can someone please confirm which is the latest stable JK connector please? I've been looking at the JK documentation located at http://jakarta.apache.org/tomcat/connectors-doc/index.html but it is not clear which is the most recent 'stable' release. I'm currently using 1.2.10 for testing but I need to use 1.2.11 as there is a bug fix in that release that I require. The downloadable binaries at http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/win32/ are for 1.2.6 1.2.8 1.2.10 1.2.13 and 1.2.14. Are these all stable releases? Thanks, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Which is the latest 'stable' JK connector?
I believe it is v. 1.2.13. Bryan On 7/14/05, Alex Sansom [EMAIL PROTECTED] wrote: Hi, Can someone please confirm which is the latest stable JK connector please? I've been looking at the JK documentation located at http://jakarta.apache.org/tomcat/connectors-doc/index.html but it is not clear which is the most recent 'stable' release. I'm currently using 1.2.10 for testing but I need to use 1.2.11 as there is a bug fix in that release that I require. The downloadable binaries at http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/win32/ are for 1.2.6 1.2.8 1.2.10 1.2.13 and 1.2.14. Are these all stable releases? Thanks, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Which is the latest 'stable' JK connector?
Thanks for the response Bryan. Where did you get the information from? Do you have a link? No doubt it'll be handy for future reference... Regards, Alex -Original Message- From: Bryan Scarbrough [mailto:[EMAIL PROTECTED] Sent: 14 July 2005 14:09 To: Tomcat Users List Subject: Re: Which is the latest 'stable' JK connector? I believe it is v. 1.2.13. Bryan On 7/14/05, Alex Sansom [EMAIL PROTECTED] wrote: Hi, Can someone please confirm which is the latest stable JK connector please? I've been looking at the JK documentation located at http://jakarta.apache.org/tomcat/connectors-doc/index.html but it is not clear which is the most recent 'stable' release. I'm currently using 1.2.10 for testing but I need to use 1.2.11 as there is a bug fix in that release that I require. The downloadable binaries at http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/win32 / are for 1.2.6 1.2.8 1.2.10 1.2.13 and 1.2.14. Are these all stable releases? Thanks, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Which is the latest 'stable' JK connector?
If you look at the following link it only says that the 1.2.14 version is still awaiting approval to be specified as stable. http://jakarta.apache.org/tomcat/connectors-doc/news/20050101.html#20050713.1 Bryan On 7/14/05, Alex Sansom [EMAIL PROTECTED] wrote: Thanks for the response Bryan. Where did you get the information from? Do you have a link? No doubt it'll be handy for future reference... Regards, Alex -Original Message- From: Bryan Scarbrough [mailto:[EMAIL PROTECTED] Sent: 14 July 2005 14:09 To: Tomcat Users List Subject: Re: Which is the latest 'stable' JK connector? I believe it is v. 1.2.13. Bryan On 7/14/05, Alex Sansom [EMAIL PROTECTED] wrote: Hi, Can someone please confirm which is the latest stable JK connector please? I've been looking at the JK documentation located at http://jakarta.apache.org/tomcat/connectors-doc/index.html but it is not clear which is the most recent 'stable' release. I'm currently using 1.2.10 for testing but I need to use 1.2.11 as there is a bug fix in that release that I require. The downloadable binaries at http://www.apache.org/dist/jakarta/tomcat-connectors/jk/binaries/win32 / are for 1.2.6 1.2.8 1.2.10 1.2.13 and 1.2.14. Are these all stable releases? Thanks, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
error count for http connector and localhost/ default context seem to increment for no reason: mbean bug?
whenever i access any web application deployed on tomcat, i notice that error count for localhost/ default[/] increments (request count also increments, not sure either if request count is suppose to increment..). http connector error count also increments. i'm checking these counter values via the tomcat manager web application as well as through my own servlet which accesses tomcat mbeans. even without deploying any of my own web applications (ie just after fresh install of tomcat and w/o changing any default configuration), if i go to the tomcat manager web application and continuously refresh it, it'll increment error count for localhost/ default[/] and for http8080 each time i do the refresh. there doesn't seem to be any error, so not sure why these counters are incrementing.. i've checked the logs in $CATALINA_HOME/logs, but don't see anything suspicious. here are the specific counters from http://myserver:8080/manager/jmxproxy (indicated by ): Name: Catalina:type=GlobalRequestProcessor,name=http8080 modelerType: org.apache.coyote.RequestGroupInfo requestCount: 44 maxTime: 616 bytesSent: 1595769 bytesReceived: 0 processingTime: 2609 errorCount: 20 Name: Catalina:j2eeType=Servlet,name=default,WebModule=//localhost/,J2EEApplication=none,J2EEServer=none modelerType: org.apache.catalina.core.StandardWrapper engineName: Catalina eventProvider: false objectName: Catalina:j2eeType=Servlet,name=default,WebModule=//localhost/,J2EEApplication=none,J2EEServer=none stateManageable: false statisticsProvider: false processingTime: 17 maxTime: 16 minTime: 0 requestCount: 19 errorCount: 19 loadTime: 0 classLoadTime: 0 any ideas? thanks. -annie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error count for http connector and localhost/ default context seem to increment for no reason: mbean bug?
The errors are almost certainly 404s in response to the browser's request for favicon.ico every time you request a page. The Tomcat distro does not include a favicon.ico hence the 404 response. Mark Annie Wang wrote: whenever i access any web application deployed on tomcat, i notice that error count for localhost/ default[/] increments (request count also increments, not sure either if request count is suppose to increment..). http connector error count also increments. i'm checking these counter values via the tomcat manager web application as well as through my own servlet which accesses tomcat mbeans. even without deploying any of my own web applications (ie just after fresh install of tomcat and w/o changing any default configuration), if i go to the tomcat manager web application and continuously refresh it, it'll increment error count for localhost/ default[/] and for http8080 each time i do the refresh. there doesn't seem to be any error, so not sure why these counters are incrementing.. i've checked the logs in $CATALINA_HOME/logs, but don't see anything suspicious. here are the specific counters from http://myserver:8080/manager/jmxproxy (indicated by ): Name: Catalina:type=GlobalRequestProcessor,name=http8080 modelerType: org.apache.coyote.RequestGroupInfo requestCount: 44 maxTime: 616 bytesSent: 1595769 bytesReceived: 0 processingTime: 2609 errorCount: 20 Name: Catalina:j2eeType=Servlet,name=default,WebModule=//localhost/,J2EEApplication=none,J2EEServer=none modelerType: org.apache.catalina.core.StandardWrapper engineName: Catalina eventProvider: false objectName: Catalina:j2eeType=Servlet,name=default,WebModule=//localhost/,J2EEApplication=none,J2EEServer=none stateManageable: false statisticsProvider: false processingTime: 17 maxTime: 16 minTime: 0 requestCount: 19 errorCount: 19 loadTime: 0 classLoadTime: 0 any ideas? thanks. -annie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error count for http connector and localhost/ default context seem to increment for no reason: mbean bug?
thanks mark! it's working okay now w/the favicon.ico. -annie On 7/1/05, Mark Thomas [EMAIL PROTECTED] wrote: The errors are almost certainly 404s in response to the browser's request for favicon.ico every time you request a page. The Tomcat distro does not include a favicon.ico hence the 404 response. Mark Annie Wang wrote: whenever i access any web application deployed on tomcat, i notice that error count for localhost/ default[/] increments (request count also increments, not sure either if request count is suppose to increment..). http connector error count also increments. i'm checking these counter values via the tomcat manager web application as well as through my own servlet which accesses tomcat mbeans. even without deploying any of my own web applications (ie just after fresh install of tomcat and w/o changing any default configuration), if i go to the tomcat manager web application and continuously refresh it, it'll increment error count for localhost/ default[/] and for http8080 each time i do the refresh. there doesn't seem to be any error, so not sure why these counters are incrementing.. i've checked the logs in $CATALINA_HOME/logs, but don't see anything suspicious. here are the specific counters from http://myserver:8080/manager/jmxproxy (indicated by ): Name: Catalina:type=GlobalRequestProcessor,name=http8080 modelerType: org.apache.coyote.RequestGroupInfo requestCount: 44 maxTime: 616 bytesSent: 1595769 bytesReceived: 0 processingTime: 2609 errorCount: 20 Name: Catalina:j2eeType=Servlet,name=default,WebModule=//localhost/,J2EEApplication=none,J2EEServer=none modelerType: org.apache.catalina.core.StandardWrapper engineName: Catalina eventProvider: false objectName: Catalina:j2eeType=Servlet,name=default,WebModule=//localhost/,J2EEApplication=none,J2EEServer=none stateManageable: false statisticsProvider: false processingTime: 17 maxTime: 16 minTime: 0 requestCount: 19 errorCount: 19 loadTime: 0 classLoadTime: 0 any ideas? thanks. -annie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JK connector - behavior if cachesize is exceeded
Hi, Have set up JK (1.2.13) connector from IIS to tomcat. When I define a worker to have cachesize=1, and there happen to come two simultaneous requests, the second request is aborted with status 500 Internal Server Error (as seen in IIS log file) and no bytes are returned. The isapi redirector log contains a warning [warn] ajp_get_endpoint::jk_ajp_common.c (2126): Unable to get the free endpoint for worker from 1 slots While this works as desired up to the point when this warning is written to log, I would have expected that JK connector retries such a request a few times to see if it will find a free endpoint in the next few milliseconds. There is a worker property named retries, and I would have supposed that this setting will also be used in the situation described. Is this a bug, or do you think that the current behavior is what JK connector should do? In this case I think I should set cachesize to a very high value (say 100) since I don't want to have requests aborted when there happens to be a short peek in concurrent requests. If the requests were put into a queue and retried later, I could limit the resources (open sockets) on IIS and tomcat side to a reasonable value, and during this peek situation some requests would last a little longer, but this would be perfectly acceptable. Regards Manfred - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with apache 2.0.46 and jakarta connector 1.2.13
Hi, I'm having a very strange problem with the connector. It creates only one connection and after this it does not create any additional connections. In the mod_jk.log I only get : [Tue Jun 21 16:16:12 2005] [13609:34976] [debug] ajp_done::jk_ajp_common.c (2046): recycling connection cache slot=0 for worker ajp13 [Tue Jun 21 16:16:12 2005] [13609:34976] [debug] jk_handler::mod_jk.c (1959): Service finished with status=304 for worker=ajp13 [Tue Jun 21 16:16:12 2005] [13612:34976] [debug] map_uri_to_worker::jk_uri_worker_map.c (455): Attempting to map URI '/xxx/web/dlc_empty.jsp' from 1 maps [Tue Jun 21 16:16:12 2005] [13612:34976] [debug] map_uri_to_worker::jk_uri_worker_map.c (467): Attempting to map context URI '/xxx/web/*' [Tue Jun 21 16:16:12 2005] [13612:34976] [debug] map_uri_to_worker::jk_uri_worker_map.c (481): Found a wildchar match ajp13 - /xxx/web/* After this, nothing... So the worker is found but no additional connections are made. It seems that the reusing of the connections does not work. Has anyone had any similar problems? Regards, Jarkka Kivikanta - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0
I think the http protocol does not allow the parallel processing of requests using a single connection. At least the response of a following request cannot pass the predecessor on the same connection. (How could the responses be matched to the requests?) So parallel processing is not really useful on a single connection. If a client/browser wants to have parallel processing it uses more than one connection to a server. Karl-Heinz - Original Message - From: Feng Xie (fxie) [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Sunday, June 19, 2005 5:25 AM Subject: RE: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0 Bill: Thanks for your answer. In my case, the client just directly talks to Tomcat. So, the maxThread means maxConnections. Is it possible for Tomcat ( any version which supports HTTP/1.1 pipelining)'s multiple threads to work on *A same* connection at the same time. I mean, due to pipelining, there might be multiple HTTP requests in this connection waiting for process , therefore, multiple threads in Tomcat are working on processing those pipelined requests simutaneously -- each thread handling a single different request. -Feng -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Friday, June 17, 2005 10:47 PM To: tomcat-user@jakarta.apache.org Subject: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0 If you are fronting with Apache, then the mapping between connections and threads is more a function of your MPM. As a result, I'm just going to answer for the stand-alone Connector. In Tomcat 5.0, there is a one-to-one mapping between socket connections and threads. Pipelined HTTP/1.1 keep-alive connections will all use the same thread to process. In 5.5.10+ this will no longer necessarily be the case. It will be possible for Tomcat to handle many (and the value of 'many' is heavily dependent on what your app does :) more socket connections than the configured maxThreads. Feng Xie (fxie) [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] . I like to get some help on how to configure the maximum number of connections could be supported by Tomcat5.0. There is one config attribute called maxThreads, according to Tomcat doc, which isThe maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. . My question comes from the fact that there might be multiple HTTP requests pipelined in each HTTP/1.1 connections, so can we still treat the maxThread as the maxConnections. Thanks in advance, Feng - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0
Bill: Thanks for your answer. In my case, the client just directly talks to Tomcat. So, the maxThread means maxConnections. Is it possible for Tomcat ( any version which supports HTTP/1.1 pipelining)'s multiple threads to work on *A same* connection at the same time. I mean, due to pipelining, there might be multiple HTTP requests in this connection waiting for process , therefore, multiple threads in Tomcat are working on processing those pipelined requests simutaneously -- each thread handling a single different request. -Feng -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker Sent: Friday, June 17, 2005 10:47 PM To: tomcat-user@jakarta.apache.org Subject: Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0 If you are fronting with Apache, then the mapping between connections and threads is more a function of your MPM. As a result, I'm just going to answer for the stand-alone Connector. In Tomcat 5.0, there is a one-to-one mapping between socket connections and threads. Pipelined HTTP/1.1 keep-alive connections will all use the same thread to process. In 5.5.10+ this will no longer necessarily be the case. It will be possible for Tomcat to handle many (and the value of 'many' is heavily dependent on what your app does :) more socket connections than the configured maxThreads. Feng Xie (fxie) [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] . I like to get some help on how to configure the maximum number of connections could be supported by Tomcat5.0. There is one config attribute called maxThreads, according to Tomcat doc, which isThe maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. . My question comes from the fact that there might be multiple HTTP requests pipelined in each HTTP/1.1 connections, so can we still treat the maxThread as the maxConnections. Thanks in advance, Feng - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
configuration question : the number of connections could be supported by a connector in Tomcat 5.0
I like to get some help on how to configure the maximum number of connections could be supported by Tomcat5.0. There is one config attribute called maxThreads, according to Tomcat doc, which isThe maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. . My question comes from the fact that there might be multiple HTTP requests pipelined in each HTTP/1.1 connections, so can we still treat the maxThread as the maxConnections. Thanks in advance, Feng - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: configuration question : the number of connections could be supported by a connector in Tomcat 5.0
If you are fronting with Apache, then the mapping between connections and threads is more a function of your MPM. As a result, I'm just going to answer for the stand-alone Connector. In Tomcat 5.0, there is a one-to-one mapping between socket connections and threads. Pipelined HTTP/1.1 keep-alive connections will all use the same thread to process. In 5.5.10+ this will no longer necessarily be the case. It will be possible for Tomcat to handle many (and the value of 'many' is heavily dependent on what your app does :) more socket connections than the configured maxThreads. Feng Xie (fxie) [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I like to get some help on how to configure the maximum number of connections could be supported by Tomcat5.0. There is one config attribute called maxThreads, according to Tomcat doc, which isThe maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. . My question comes from the fact that there might be multiple HTTP requests pipelined in each HTTP/1.1 connections, so can we still treat the maxThread as the maxConnections. Thanks in advance, Feng - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connector for apache and tomcat
I fixed the problem already. thanks, Christine --- Christine Ho [EMAIL PROTECTED] wrote: Thanks. I have tried it and I still cant make it work. But it is better than before. I got HTTP status 404 - /jsp-eg/index.html. In error.log in apache, I got the following: [Wed Jun 15 15:33:04 2005] [emerg] No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! [Wed Jun 15 15:33:08 2005] [emerg] No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! In mod_jk.log in apache, I got the following: [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1024): received from ajp13 pos=0 len=96 max=8192 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (606): status = 404 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (613): Number of headers is = 2 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (669): Header[0] [Content-Type] = [text/html;charset=utf-8] [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (669): Header[1] [Content-Length] = [1019] [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1024): received from ajp13 pos=0 len=1023 max=8192 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ws_write::mod_jk.c (380): writing 1019 (1019) out of 1019 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1024): received from ajp13 pos=0 len=2 max=8192 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_done::jk_ajp_common.c (2046): recycling connection cache slot=0 for worker ajp13 [Wed Jun 15 16:42:34 2005] [3800:] [debug] jk_handler::mod_jk.c (1959): Service finished with status=404 for worker=ajp13 I am not sure what went wrong. In httpd.conf in apache, I added/modified the following lines: ServerRoot /export/chrisho/apache2 LoadModule jk_module libexec/mod_jk.so Directory /export/chrisho/jakarta-tomcat-5.5.9/webapps/jsp-examples/WEB-INF Options -Indexes FollowSymLinks Deny from all /Directory JkWorkersFile conf/workers.properties JkLogfile logs/mod_jk.log JkLogLevel debug Alias /jsp-eg /export/chrisho/jakarta-tomcat-5.5.9/webapps/jsp-examples Alias /servlets-eg /export/chrisho/jakarta-tomcat-5.5.9/webapps/servlets-examples JkMount /jsp-eg/*.jsp ajp13 JkMount /jsp-eg/*.html ajp13 JkMount /servlets-eg/*.html ajp13 The workers.properties in apache2 looks like the following: workers.tomcat_home=/export/chrisho/jakarta-tomcat-5.5.9 ps=/ worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 worker.ajp13.lbfactor=1 In server.xml in tomcat 5.5.9, I added/modified the following lines: Listener className=org.apache.jk.config.ApacheConfig configHome=/export/chrisho/jakarta-tomcat-5.5.9 modJk=/export/chrisho/apache2/libexec/mod_jk.so jkWorker=ajp13 forwardAll=False jkLog=/export/chrisho/apache2/logs/jk-tomcat.log jkDebug=debug noRoot=False workersConfig=/export/chrisho/apache2/conf/workers.properties / Connector port=8009 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler redirectPort=8443 protocol=AJP/1.3 / Then I restart the tomcat and apache respectively. I have no problem to go to the following link through tomcat: http://localhost:8080/jsp-examples/index.html But I have problem to go to the following link through apache: http://localhost/jsp-eg/index.html Can somebody please help me. thanks, Christine --- [EMAIL PROTECTED] wrote: Please refer to message 128209 for a complete howto. Request it by sending an email to : [EMAIL PROTECTED] __ Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connector for apache and tomcat
Please verify first that you did not added a secont connector on port 8009 in tomcat/conf/server.xml for they cannot listen both on the same port. Second, the instructions i've provided are for mod_jk.so version 1 minor 13. Please make sure you've got the right module library. It seems to me that your module is expecting something that I didn't configure and This particular configuration works fine for me. Luc Boudreau Universit du Qubec Canada -Message d'origine- De: Christine Ho [mailto:[EMAIL PROTECTED] Envoy: 15 juin 2005 20:15 : Tomcat Users List Objet: RE: Connector for apache and tomcat Thanks. I have tried it and I still cant make it work. But it is better than before. I got HTTP status 404 - /jsp-eg/index.html. In error.log in apache, I got the following: [Wed Jun 15 15:33:04 2005] [emerg] No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! [Wed Jun 15 15:33:08 2005] [emerg] No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! In mod_jk.log in apache, I got the following: [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1024): received from ajp13 pos=0 len=96 max=8192 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (606): status = 404 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (613): Number of headers is = 2 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (669): Header[0] [Content-Type] = [text/html;charset=utf-8] [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (669): Header[1] [Content-Length] = [1019] [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1024): received from ajp13 pos=0 len=1023 max=8192 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ws_write::mod_jk.c (380): writing 1019 (1019) out of 1019 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1024): received from ajp13 pos=0 len=2 max=8192 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_done::jk_ajp_common.c (2046): recycling connection cache slot=0 for worker ajp13 [Wed Jun 15 16:42:34 2005] [3800:] [debug] jk_handler::mod_jk.c (1959): Service finished with status=404 for worker=ajp13 I am not sure what went wrong. In httpd.conf in apache, I added/modified the following lines: ServerRoot /export/chrisho/apache2 LoadModule jk_module libexec/mod_jk.so Directory /export/chrisho/jakarta-tomcat-5.5.9/webapps/jsp-examples/WEB-INF Options -Indexes FollowSymLinks Deny from all /Directory JkWorkersFile conf/workers.properties JkLogfile logs/mod_jk.log JkLogLevel debug Alias /jsp-eg /export/chrisho/jakarta-tomcat-5.5.9/webapps/jsp-examples Alias /servlets-eg /export/chrisho/jakarta-tomcat-5.5.9/webapps/servlets-examples JkMount /jsp-eg/*.jsp ajp13 JkMount /jsp-eg/*.html ajp13 JkMount /servlets-eg/*.html ajp13 The workers.properties in apache2 looks like the following: workers.tomcat_home=/export/chrisho/jakarta-tomcat-5.5.9 ps=/ worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 worker.ajp13.lbfactor=1 In server.xml in tomcat 5.5.9, I added/modified the following lines: Listener className=org.apache.jk.config.ApacheConfig configHome=/export/chrisho/jakarta-tomcat-5.5.9 modJk=/export/chrisho/apache2/libexec/mod_jk.so jkWorker=ajp13 forwardAll=False jkLog=/export/chrisho/apache2/logs/jk-tomcat.log jkDebug=debug noRoot=False workersConfig=/export/chrisho/apache2/conf/workers.properties / Connector port=8009 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler redirectPort=8443 protocol=AJP/1.3 / Then I restart the tomcat and apache respectively. I have no problem to go to the following link through tomcat: http://localhost:8080/jsp-examples/index.html But I have problem to go to the following link through apache: http://localhost/jsp-eg/index.html Can somebody please help me. thanks, Christine --- [EMAIL PROTECTED] wrote: Please refer to message 128209 for a complete howto. Request it by sending an email to : [EMAIL PROTECTED] __ Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Connector for apache and tomcat
Hi, I am running the apache server 2.x and tomcat 5.5.x on RHEL4. I tried to setup the connector (JK1.2) between them and it didnt work. I know how to do the configuration on apache side. And I have documentation how to modify the Tomcat 4.1.x's server.xml file so that the tomcat can listen to the AJP13 requests. However, the jar files in tomcat 5.5.x is quite different from the ones in tomcat 4.1.x. I am not sure what needs to be modified in the tomcat 5.5.x's server.xml. Please give me some pointers how to do it. Besides the server.xml and workers.properties, what other things are required for tomcat 5.5.x to run on the connector? The integration between apache and tomcat is a must for my project. I cannot use just apache alone or tomcat alone. thanks, Christine __ Discover Yahoo! Stay in touch with email, IM, photo sharing and more. Check it out! http://discover.yahoo.com/stayintouch.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Connector for apache and tomcat
Please refer to message 128209 for a complete howto. Request it by sending an email to : [EMAIL PROTECTED]
RE: Connector for apache and tomcat
Thanks. I have tried it and I still cant make it work. But it is better than before. I got HTTP status 404 - /jsp-eg/index.html. In error.log in apache, I got the following: [Wed Jun 15 15:33:04 2005] [emerg] No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! [Wed Jun 15 15:33:08 2005] [emerg] No JkShmFile defined in httpd.conf. LoadBalancer will not function properly! In mod_jk.log in apache, I got the following: [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1024): received from ajp13 pos=0 len=96 max=8192 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (606): status = 404 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (613): Number of headers is = 2 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (669): Header[0] [Content-Type] = [text/html;charset=utf-8] [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_unmarshal_response::jk_ajp_common.c (669): Header[1] [Content-Length] = [1019] [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1024): received from ajp13 pos=0 len=1023 max=8192 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ws_write::mod_jk.c (380): writing 1019 (1019) out of 1019 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_connection_tcp_get_message::jk_ajp_common.c (1024): received from ajp13 pos=0 len=2 max=8192 [Wed Jun 15 16:42:34 2005] [3800:] [debug] ajp_done::jk_ajp_common.c (2046): recycling connection cache slot=0 for worker ajp13 [Wed Jun 15 16:42:34 2005] [3800:] [debug] jk_handler::mod_jk.c (1959): Service finished with status=404 for worker=ajp13 I am not sure what went wrong. In httpd.conf in apache, I added/modified the following lines: ServerRoot /export/chrisho/apache2 LoadModule jk_module libexec/mod_jk.so Directory /export/chrisho/jakarta-tomcat-5.5.9/webapps/jsp-examples/WEB-INF Options -Indexes FollowSymLinks Deny from all /Directory JkWorkersFile conf/workers.properties JkLogfile logs/mod_jk.log JkLogLevel debug Alias /jsp-eg /export/chrisho/jakarta-tomcat-5.5.9/webapps/jsp-examples Alias /servlets-eg /export/chrisho/jakarta-tomcat-5.5.9/webapps/servlets-examples JkMount /jsp-eg/*.jsp ajp13 JkMount /jsp-eg/*.html ajp13 JkMount /servlets-eg/*.html ajp13 The workers.properties in apache2 looks like the following: workers.tomcat_home=/export/chrisho/jakarta-tomcat-5.5.9 ps=/ worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 worker.ajp13.lbfactor=1 In server.xml in tomcat 5.5.9, I added/modified the following lines: Listener className=org.apache.jk.config.ApacheConfig configHome=/export/chrisho/jakarta-tomcat-5.5.9 modJk=/export/chrisho/apache2/libexec/mod_jk.so jkWorker=ajp13 forwardAll=False jkLog=/export/chrisho/apache2/logs/jk-tomcat.log jkDebug=debug noRoot=False workersConfig=/export/chrisho/apache2/conf/workers.properties / Connector port=8009 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler redirectPort=8443 protocol=AJP/1.3 / Then I restart the tomcat and apache respectively. I have no problem to go to the following link through tomcat: http://localhost:8080/jsp-examples/index.html But I have problem to go to the following link through apache: http://localhost/jsp-eg/index.html Can somebody please help me. thanks, Christine --- [EMAIL PROTECTED] wrote: Please refer to message 128209 for a complete howto. Request it by sending an email to : [EMAIL PROTECTED] __ Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with the connector
Hi all, I am having problems with the jakarta-connector version 1.2.13 and tomcat 5.5.9. The apache version is Apache/2.0.46 (White Box). I have the following configuration in httpd.conf: IfModule !mod_jk.c LoadModule jk_module /usr/lib/httpd/modules/mod_jk.so /IfModule JkWorkersFile /etc/httpd/conf/workers.properties JkLogFile logs/mod_jk.log JkLogLeveltrace JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkRequestLogFormat %w %V %T JkMount /jkmanager/* status # Send JSPs for context /examples to worker named worker1 JkMount /examples/*.jsp worker1 The workers.-properties file looks like this: ps=/ worker.list=jkstatus,worker1 workers.tomcat_home=/opt/tomcat/jakarta-tomcat-5.5.9 workers.java_home=/opt/jdk1.5.0_03 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=1 # Define a 'jkstatus' worker using status worker.jkstatus.type=status The problems is that in the mod_jk.log i will only get ... jk_handler::mod_jk.c (1715): Into handler jakarta-servlet worker=worker1 r-proxyreq=0 ... jk_handler::mod_jk.c (1883): Could not find a worker for worker name=worker1 It seems that the connector does not have the correct configuration? The JkWorkersFile /etc/httpd/conf/workers.properties is pointing to the correct configuration file. Does anyone have any suggestions? Regards, Jarkka Kivikanta - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with the connector
Hi all, I am having problems with the jakarta-connector version 1.2.13 and tomcat 5.5.9. The apache version is Apache/2.0.46 (White Box). I have the following configuration in httpd.conf: IfModule !mod_jk.c LoadModule jk_module /usr/lib/httpd/modules/mod_jk.so /IfModule JkWorkersFile /etc/httpd/conf/workers.properties JkLogFile logs/mod_jk.log JkLogLeveltrace JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkRequestLogFormat %w %V %T JkMount /jkmanager/* status # Send JSPs for context /examples to worker named worker1 JkMount /examples/*.jsp worker1 The workers.-properties file looks like this: ps=/ worker.list=jkstatus,worker1 workers.tomcat_home=/opt/tomcat/jakarta-tomcat-5.5.9 workers.java_home=/opt/jdk1.5.0_03 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=1 # Define a 'jkstatus' worker using status worker.jkstatus.type=status The problems is that in the mod_jk.log i will only get ... jk_handler::mod_jk.c (1715): Into handler jakarta-servlet worker=worker1 r-proxyreq=0 ... jk_handler::mod_jk.c (1883): Could not find a worker for worker name=worker1 It seems that the connector does not have the correct configuration? The JkWorkersFile /etc/httpd/conf/workers.properties is pointing to the correct configuration file. Does anyone have any suggestions? Regards, Jarkka Kivikanta - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with jakarta-connector
Hi all, I am having problems with the jakarta-connector version 1.2.13 and tomcat 5.5.9. The apache version is Apache/2.0.46 (White Box). I have the following configuration in httpd.conf: IfModule !mod_jk.c LoadModule jk_module /usr/lib/httpd/modules/mod_jk.so /IfModule JkWorkersFile /etc/httpd/conf/workers.properties JkLogFile logs/mod_jk.log JkLogLeveltrace JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkRequestLogFormat %w %V %T JkMount /jkmanager/* status # Send JSPs for context /examples to worker named worker1 JkMount /examples/*.jsp worker1 The workers.-properties file looks like this: ps=/ worker.list=jkstatus,worker1 workers.tomcat_home=/opt/tomcat/jakarta-tomcat-5.5.9 workers.java_home=/opt/jdk1.5.0_03 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=1 # Define a 'jkstatus' worker using status worker.jkstatus.type=status The problems is that in the mod_jk.log i will only get ... jk_handler::mod_jk.c (1715): Into handler jakarta-servlet worker=worker1 r-proxyreq=0 ... jk_handler::mod_jk.c (1883): Could not find a worker for worker name=worker1 It seems that the connector does not have the correct configuration? The JkWorkersFile /etc/httpd/conf/workers.properties is pointing to the correct configuration file. Does anyone have any suggestions? Regards, Jarkka Kivikanta - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with jakarta-connector
Hi all, I am having problems with the jakarta-connector version 1.2.13 and tomcat 5.5.9. The apache version is Apache/2.0.46 (White Box). I have the following configuration in httpd.conf: IfModule !mod_jk.c LoadModule jk_module /usr/lib/httpd/modules/mod_jk .so /IfModule JkWorkersFile /etc/httpd/conf/workers.properties JkLogFile logs/mod_jk.log JkLogLeveltrace JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkRequestLogFormat %w %V %T JkMount /jkmanager/* status # Send JSPs for context /examples to worker named worker1 JkMount /examples/*.jsp worker1 The workers.-properties file looks like this: ps=/ worker.list=jkstatus,worker1 workers.tomcat_home=/opt/tomcat/jakarta-tomcat-5.5.9 workers.java_home=/opt/jdk1.5.0_03 worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=1 # Define a 'jkstatus' worker using status worker.jkstatus.type=status The problems is that in the mod_jk.log i will only get ... jk_handler::mod_jk.c (1715): Into handler jakarta-servlet worker=worker1 r-proxyreq=0 ... jk_handler::mod_jk.c (1883): Could not find a worker for worker name=worker1 It seems that the connector does not have the correct configuration? The JkWorkersFile /etc/httpd/conf/workers.properties is pointing to the correct configuration file but the connector is still unable to find the correct worker. Does anyone have any suggestions? Regards, Jarkka Kivikanta - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache Tomcat JK1.2 Connector
Darrell Bechtel wrote: Both workers are setup to communicate to the localhost using port 8009?? Perhaps your /etc/hosts file has a entry that resolves the 'localhost' to that IP address. Anyhow use 127.0.0.1 instead localhost to be sure. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache Tomcat JK1.2 Connector
I have connected these 2 servers previously, but I am now running into problems getting apache 2.0.5 to communicate with tomcat 5.5.9 using the jk1.2 connector on the Fedora Core 3 test 4. From looking through the jk log file it appears that apache is trying to communicate to 66.103.44.3:8009. I have no idea where this ip is coming from since both apache and tomcat are installed locally and there is only 1 nic with an internal ip of 192.168.50.5. If anyone can shed light on where I should be looking to resolve this conflict it would be much appreciated. Thanks, Darrell Bechtel
RE: Apache Tomcat JK1.2 Connector
Look in the Apache2\conf\workers.properties file. -Original Message- From: Darrell Bechtel [mailto:[EMAIL PROTECTED] Sent: Sunday, June 12, 2005 5:41 PM To: tomcat-user@jakarta.apache.org Subject: Apache Tomcat JK1.2 Connector I have connected these 2 servers previously, but I am now running into problems getting apache 2.0.5 to communicate with tomcat 5.5.9 using the jk1.2 connector on the Fedora Core 3 test 4. From looking through the jk log file it appears that apache is trying to communicate to 66.103.44.3:8009. I have no idea where this ip is coming from since both apache and tomcat are installed locally and there is only 1 nic with an internal ip of 192.168.50.5. If anyone can shed light on where I should be looking to resolve this conflict it would be much appreciated. Thanks, Darrell Bechtel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache Tomcat JK1.2 Connector
Both workers are setup to communicate to the localhost using port 8009?? Darrell -Original Message- From: David Short [mailto:[EMAIL PROTECTED] Sent: Sunday, June 12, 2005 9:11 PM To: 'Tomcat Users List' Subject: RE: Apache Tomcat JK1.2 Connector Look in the Apache2\conf\workers.properties file. -Original Message- From: Darrell Bechtel [mailto:[EMAIL PROTECTED] Sent: Sunday, June 12, 2005 5:41 PM To: tomcat-user@jakarta.apache.org Subject: Apache Tomcat JK1.2 Connector I have connected these 2 servers previously, but I am now running into problems getting apache 2.0.5 to communicate with tomcat 5.5.9 using the jk1.2 connector on the Fedora Core 3 test 4. From looking through the jk log file it appears that apache is trying to communicate to 66.103.44.3:8009. I have no idea where this ip is coming from since both apache and tomcat are installed locally and there is only 1 nic with an internal ip of 192.168.50.5. If anyone can shed light on where I should be looking to resolve this conflict it would be much appreciated. Thanks, Darrell Bechtel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
default IP address connector binding?
My Linux server's eth0 supports ten IP addresses. What happens (in 5.5.9) if my HTTP Connector doesn't specify an address = 216.119.217.240 attribute? Does it use the first one? all of them? (it's working but I need to know exactly what it's doing) Paul Singleton -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.6.5 - Release Date: 7/Jun/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: default IP address connector binding?
All of them -Tim Paul Singleton wrote: My Linux server's eth0 supports ten IP addresses. What happens (in 5.5.9) if my HTTP Connector doesn't specify an address = 216.119.217.240 attribute? Does it use the first one? all of them? (it's working but I need to know exactly what it's doing) Paul Singleton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: default IP address connector binding?
Am Mittwoch, 8. Juni 2005 16:04 schrieb Paul Singleton: My Linux server's eth0 supports ten IP addresses. What happens (in 5.5.9) if my HTTP Connector doesn't specify an address = 216.119.217.240 attribute? Does it use the first one? all of them? (it's working but I need to know exactly what it's doing) If you don't specify an address, tomcat will bind to 0.0.0.0 (resp. to ::0 on IPv6) which effectively means it binds to all available addresses. Regards mks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Set Connector to secure but DON'T use TLS/keystore/etc.?
My suggested solution (2) below works ok as a temporary stopgap. So,
if you ever find yourself in this scenario -- Tomcat behind a hardware
ssl accelerator but you need to redirect for confidential matrials), a
stopgap solution is the code below.
My question is still open as to whether or not a Connector can be set
to be secure but without its wanting to do TLS, etc. I wonder if
there is a way through this problem with proxy settings. Also, in the
solution below, I think there are some issues with cached resources.
Anyhoo . . .
Scenario:
1. You have Tomcat behind a hardware SSL accelerator, which handles
TLS for you. And you want that performance boost.
2. You need to mark certain resources CONFIDENTIAL in your web.xml
with transport-guaranteeCONFIDENTIAL/transport-guarantee
3. However, CONFIDENTIAL means that when you get traffic to your
Tomcat on the non-secured Connector, there is a redirect to, say, 443
(i.e., back to the SSL accelerator).
4. When the SSL accelerator then sends the traffic to your Tomcat's
8443, there's a double-bind:
a. If you set the 8443 Connector to secure=true then Tomcat wants to
handle the SSL. But this is bad because it was already handled by the
hardware accelerator.
b. But if you set the 8443 Connect to secure=false then Tomcat wants
to send the redirect (again). Infinite loop.
Stopgap solution:
1. Remove the user-data-constraint
transport-guaranteeCONFIDENTIAL/transport-guarantee from your
web.xml
2. Change your 8443 Connector to secure=false
3. Handle the redirect yourself with a filter such as this one (this
is just the dofilter method):
(Note that the filter will have to look at the incoming paths, and
reproduce whatever your settings were in that required the
CONFIDENTIAL guarantee.)
(Also note that this is obviously a hack, with some hardcoding of a
port, assumption that the other port is regular http, etc., etc.)
public void doFilter(ServletRequest request, ServletResponse response,
FilterChain chain) throws IOException, ServletException {
// If incoming is not on the port that is for secure traffic, redirect
if (request.getLocalPort() != 8443) {
HttpServletRequest req = (HttpServletRequest) request;
HttpServletResponse res = (HttpServletResponse) response;
String url = NetUtils.getReconstructedURL(req);
// Change the scheme
String redirect = https + url.substring(4);
res.setStatus(HttpServletResponse.SC_FOUND);
res.setHeader(Location, redirect);
if (logger.isLoggable(Level.INFO)) {
logger.info(Redirecting: + url + to + redirect);
}
return;
} else {
chain.doFilter(request, response);
}
}
John
On 6/7/05, John G. Norman [EMAIL PROTECTED] wrote:
For Tomcat 5.0.28:
I have an SSL accelerator in front of a set of hardware load-balanced Tomcats.
SSL is handled by the accelerator.
HTTP requests come in on port 80 and are redirected via the load
balancer (it's actually an Inkra) to a Tomcat HTTP Connector listening
on port 8080.
I would like to mark some resources in the app with the security
constraint CONFIDENTIAL and have the request redirected to port 443.
So . . . A redirected request would now come in on 443, where the SSL
accelerator handles TLS. Then the request goes into the LB, and goes
to a Tomcat Connector on port 8443.
Therefore, in server.xml, I would like to set the secure attribute for
the Connector on port 8443 to true so that the request is no longer
redirected.
But if I set the secure attribute to true, it seems that I must
specify a keystore, and handle SSL on Tomcat. (If you set secure to
true but w/o a keystore, you get exceptions and the Connector
doesn't start.)
If I set the secure attribute to false, then the redirect happens
again (effectively an infinite loop).
So . . . any suggestions?
My ideas are:
(0) See if the load balancer can do the redirect. I.e., have certain
traffic (not all, I'm afraid) return a 304 and redirect to the 443
port? There *are* certain paths (for example, for privacy policy XML
files) that must not use https/443. Then the Tomcat's 8443 could be
insecure. This is a bad solution because now the authority for the
redirect isn't in the app; harder to change.
(1) Stop using the hardware acceleration, and put the SSL cert on each
of the Tomcats. This is probably big drag for performance reasons.
(2) Write a custom J2EE filter to do the 304/redirect.
(3) Any more flexibility on this in Tomcat 5.5?
John
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Set Connector to secure but DON'T use TLS/keystore/etc.?
For Tomcat 5.0.28: I have an SSL accelerator in front of a set of hardware load-balanced Tomcats. SSL is handled by the accelerator. HTTP requests come in on port 80 and are redirected via the load balancer (it's actually an Inkra) to a Tomcat HTTP Connector listening on port 8080. I would like to mark some resources in the app with the security constraint CONFIDENTIAL and have the request redirected to port 443. So . . . A redirected request would now come in on 443, where the SSL accelerator handles TLS. Then the request goes into the LB, and goes to a Tomcat Connector on port 8443. Therefore, in server.xml, I would like to set the secure attribute for the Connector on port 8443 to true so that the request is no longer redirected. But if I set the secure attribute to true, it seems that I must specify a keystore, and handle SSL on Tomcat. (If you set secure to true but w/o a keystore, you get exceptions and the Connector doesn't start.) If I set the secure attribute to false, then the redirect happens again (effectively an infinite loop). So . . . any suggestions? My ideas are: (0) See if the load balancer can do the redirect. I.e., have certain traffic (not all, I'm afraid) return a 304 and redirect to the 443 port? There *are* certain paths (for example, for privacy policy XML files) that must not use https/443. Then the Tomcat's 8443 could be insecure. This is a bad solution because now the authority for the redirect isn't in the app; harder to change. (1) Stop using the hardware acceleration, and put the SSL cert on each of the Tomcats. This is probably big drag for performance reasons. (2) Write a custom J2EE filter to do the 304/redirect. (3) Any more flexibility on this in Tomcat 5.5? John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
binding 5.5.9 HTTP connector to specific IP address
I run 5.5.9 standalone under Fedora Core 3, and have ten consecutive IP addresses on one NIC. When I configure a standard HTTP connector without any particular IP address, it seems to happily accept requests on all these addresses (is this by design?) When I configure it with the extra attribute address=195.108.201.212 (not the real address) then Tomcat seems to start up happily, and even spews reassuring INFO msgs like INFO: Initializing Coyote HTTP/1.1 on suggesting that it has done exactly what I hoped, but requests to that IP address fail with connection refused. What could be going wrong? Paul Singleton -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.6.2 - Release Date: 4/Jun/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: binding 5.5.9 HTTP connector to specific IP address
From: Paul Singleton [mailto:[EMAIL PROTECTED] Subject: binding 5.5.9 HTTP connector to specific IP address When I configure it with the extra attribute address=195.108.201.212 (not the real address) then Tomcat seems to start up happily snip but requests to that IP address fail with connection refused. Just tried it with TC 5.5.9 on our proprietary platform with JRE 1.4.2 and it seemed to work fine (except for a problem with the Admin app trying to display the connector address info - have to look into that). Do you have a firewall or iptables setting that might be blocking access? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat thread is dying unexpectedly (Tomcat5.0.28, apache2.0.54 and mod_jk 1.2.5 connector on Solaris 8)
Issue Resolved:
It was not the issue of mod_jk or tomcat either. It's the issue of Unix
shell from where I was starting tomcat. The thing which works for me is to
run tomcat in CSH Shell and in background.
Dear Pierre Aliye! Thanks a lot for your great support.
Regards,
Muhammad Owais Ansari
-Original Message-
From: M. Owais Ansari [mailto:[EMAIL PROTECTED]
Sent: Friday, June 03, 2005 9:46 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: tomcat-user@jakarta.apache.org
Subject: RE: Tomcat thread is dying unexpectedly (Tomcat5.0.28, apache2.0.54
and mod_jk 1.2.5 connector on Solaris 8)
Thanks for your response,
Yes the tomcat still dies with out apache might be because the configuration
for mod_jk are still there only the apache is shutdown.
below are the updated logs after changing in workers.properties, and
commenting out the following lines in server.xml
!--
Connector port=8082
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
enableLookups=false
acceptCount=100 debug=0 connectionTimeout=2
proxyPort=80 disableUploadTimeout=true /
--
Tomcathome/conf/workers.properties
--
# Define 1 real worker using ajp13
worker.list=exampWorker
# Set properties for worker1 (ajp13)
worker.exampWorker.type=ajp13
worker.exampWorker.host=127.0.0.1
worker.exampWorker.port=8009
worker.exampWorker.lbfactor=2.5
#worker.exampWorker.cachesize=10
#worker.exampWorker.cache_timeout=600
#worker.exampWorker.socket_keepalive=1
#worker.exampWorker.socket_timeout=300
Tomcathome/logs/localhost_log.2005-06-02.txt-
2005-06-02 17:46:05
StandardContext[/balancer]org.apache.webapp.balancer.BalancerFilter: init():
ruleChain: [org.apache.webapp.balancer.RuleChai
n: [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string: News
/ Redirect URL: http://www.cnn.com], [org.apache.webapp.balancer.ru
les.RequestParameterRule: Target param name: paramName / Target param value:
paramValue / Redirect URL: http://www.yahoo.com], [org.apache.webap
p.balancer.rules.AcceptEverythingRule: Redirect URL:
http://jakarta.apache.org]]
2005-06-02 17:46:22 StandardContext[/jsp-examples]ContextListener:
contextInitialized()
2005-06-02 17:46:22 StandardContext[/jsp-examples]SessionListener:
contextInitialized()
2005-06-02 17:46:23 StandardContext[/servlets-examples]ContextListener:
contextInitialized()
2005-06-02 17:46:23 StandardContext[/servlets-examples]SessionListener:
contextInitialized()
2005-06-02 18:09:40 StandardContext[/jsp-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES',
'[Ljava.lang.String;@5
75415')
2005-06-02 18:09:40 StandardContext[/jsp-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES',
'[Ljava.lang.String;@1
eb0')
2005-06-02 18:09:40 StandardContext[/jsp-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES',
'[Ljava.lang.String;@5
ee400')
2005-06-02 18:09:40 StandardContext[/jsp-examples]SessionListener:
contextDestroyed()
2005-06-02 18:09:40 StandardContext[/jsp-examples]ContextListener:
contextDestroyed()
2005-06-02 18:09:40 StandardContext[/servlets-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Stri
ng;@33319f')
2005-06-02 18:09:40 StandardContext[/servlets-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Stri
ng;@7ecd78')
2005-06-02 18:09:40 StandardContext[/servlets-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Stri
ng;@63849c')
2005-06-02 18:09:40 StandardContext[/servlets-examples]SessionListener:
contextDestroyed()
2005-06-02 18:09:40 StandardContext[/servlets-examples]ContextListener:
contextDestroyed()
--Tomcathome/logs/Catalina.out---
[INFO] Http11Protocol - Initializing Coyote HTTP/1.1 on http-8080
[INFO] Catalina - Initialization processed in 10455 ms
[INFO] StandardService - Starting service Catalina
[INFO] StandardEngine - Starting Servlet Engine: Apache Tomcat/5.0.28
[INFO] StandardHost - XML validation disabled
[INFO] StandardHost - Create Host deployer for direct deployment ( non-jmx )
[INFO] StandardHostDeployer - Processing Context configuration file URL
file:/export/home/tomcat5/conf/Catalina/localhost/balancer.xml
[INFO] StandardHostDeployer - Processing Context configuration file URL
file:/export/home/tomcat5/conf/Catalina/localhost/admin.xml
[INFO] PropertyMessageResources - Initializing,
config='org.apache.struts.util.LocalStrings', returnNull=true
[INFO] PropertyMessageResources - Initializing,
config='org.apache.struts.action.ActionResources', returnNull=true
[INFO] PropertyMessageResources - Initializing,
config='org.apache.webapp.admin.ApplicationResources', returnNull=true
[INFO] StandardHostDeployer - Processing Context configuration file URL
file:/export/home/tomcat5/conf/Catalina/localhost/manager.xml
[INFO
Tomcat thread is dying unexpectedly (Tomcat5.0.28, apache2.0.54 and mod_jk 1.2.5 connector on Solaris 8)
Hello there, I've tried to configure tomcat 5.0.28 with apache 2.0.54 through mod_jk connector (mod_jk.so used from file jakarta-tomcat-connectors-jk-1.2.5-solaris8-sparc-apache-2.0.47.tar.gz at jakarta.apache.org) on Solaris 5.8 (Solaris 8) platform but tomcat is dieing after some time with java.net.SocketException exception. Please help me to get out from this issue Following are the logs and configuration files. ---Tomcathome/logs/Catalina.out--- - [INFO] Http11Protocol - Initializing Coyote HTTP/1.1 on http-8080 [INFO] Http11Protocol - Initializing Coyote HTTP/1.1 on http-8082 [INFO] Catalina - Initialization processed in 10469 ms [INFO] StandardService - Starting service Catalina [INFO] StandardEngine - Starting Servlet Engine: Apache Tomcat/5.0.28 [INFO] StandardHost - XML validation disabled [INFO] StandardHost - Create Host deployer for direct deployment ( non-jmx ) [INFO] StandardHostDeployer - Processing Context configuration file URL file:/export/home/tomcat5/conf/Catalina/localhost/balancer.xml [INFO] StandardHostDeployer - Processing Context configuration file URL file:/export/home/tomcat5/conf/Catalina/localhost/admin.xml [INFO] PropertyMessageResources - Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true [INFO] PropertyMessageResources - Initializing, config='org.apache.struts.action.ActionResources', returnNull=true [INFO] PropertyMessageResources - Initializing, config='org.apache.webapp.admin.ApplicationResources', returnNull=true [INFO] StandardHostDeployer - Processing Context configuration file URL file:/export/home/tomcat5/conf/Catalina/localhost/manager.xml [INFO] StandardHostDeployer - Processing Context configuration file URL file:/export/home/tomcat5/conf/Catalina/localhost/wifi.xml [INFO] WebappClassLoader - validateJarFile(/export/home/webapps/WiFi/WEB-INF/lib/servlet-api.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class [INFO] StandardHostDeployer - Installing web application at context path /jsp-examples from URL file:/export/home/tomcat5/webapps/jsp-examples [INFO] StandardHostDeployer - Installing web application at context path from URL file:/export/home/tomcat5/webapps/ROOT [INFO] StandardHostDeployer - Installing web application at context path /servlets-examples from URL file:/export/home/tomcat5/webapps/servlets-examples [INFO] StandardHostDeployer - Installing web application at context path /tomcat-docs from URL file:/export/home/tomcat5/webapps/tomcat-docs [INFO] StandardHostDeployer - Installing web application at context path /webdav from URL file:/export/home/tomcat5/webapps/webdav [INFO] Http11Protocol - Starting Coyote HTTP/1.1 on http-8080 [INFO] ChannelSocket - JK2: ajp13 listening on /0.0.0.0:8009 [INFO] JkMain - Jk running ID=0 time=4/190 config=/export/home/tomcat5/conf/jk2.properties [INFO] Http11Protocol - Starting Coyote HTTP/1.1 on http-8082 [INFO] Catalina - Server startup in 28234 ms [INFO] Http11Protocol - Pausing Coyote HTTP/1.1 on http-8080 [WARN] ChannelSocket - Exception executing accept java.net.SocketException: Software caused connection abortjava.net.SocketException: Software caused connection abort at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463) at java.net.ServerSocket.implAccept(ServerSocket.java:238) at java.net.ServerSocket.accept(ServerSocket.java:217) at org.apache.jk.common.ChannelSocket.accept(ChannelSocket.java:295) at org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:638) at org.apache.jk.common.SocketAcceptor.runIt(ChannelSocket.java:847) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:683) at java.lang.Thread.run(Thread.java:479) [INFO] StandardService - Stopping service Catalina [INFO] StandardHostDeployer - Removing web application at context path /tomcat-docs [INFO] StandardHostDeployer - Removing web application at context path /admin [INFO] LoggerBase - unregistering logger Catalina:type=Logger,path=/admin,host=localhost [INFO] StandardHostDeployer - Removing web application at context path /jsp-examples [INFO] StandardHostDeployer - Removing web application at context path /billing [INFO] StandardHostDeployer - Removing web application at context path /webdav [INFO] StandardHostDeployer - Removing web application at context path /servlets-examples [INFO] StandardHostDeployer - Removing web application at context path /balancer [INFO] StandardHostDeployer - Removing web application at context path /manager [INFO] StandardHostDeployer - Removing web application at context path [INFO] LoggerBase - unregistering logger Catalina:type=Logger,host=localhost [INFO] LoggerBase - unregistering logger Catalina:type=Logger [INFO
tomcat 5.5.x J2EE Connector
I found this http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73629.html on the archive but this thread is very old and I am wondering if newer tomcat 5.5.x version implements JCA. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat 5.5.x J2EE Connector
tomcat is not a J2EE implementation so you should not expect JCA to be implemented in tomcat. -Original Message- From: faisal [mailto:[EMAIL PROTECTED] Sent: Thursday, June 02, 2005 1:35 PM To: tomcat-user@jakarta.apache.org Subject: tomcat 5.5.x J2EE Connector I found this http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73629.html on the archive but this thread is very old and I am wondering if newer tomcat 5.5.x version implements JCA. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat thread is dying unexpectedly (Tomcat5.0.28, apache2.0.54 and mod_jk 1.2.5 connector on Solaris 8)
Increase your log level to DEBUG everywhere you can, and then retry. Is the application dying when you access your application directly on tomcat (without using Apache) ? py -Original Message- From: Muhammad Owais Ansari [mailto:[EMAIL PROTECTED] Sent: jeudi 2 juin 2005 11:55 To: tomcat-user@jakarta.apache.org Subject: Tomcat thread is dying unexpectedly (Tomcat5.0.28, apache2.0.54 and mod_jk 1.2.5 connector on Solaris 8) Hello there, I've tried to configure tomcat 5.0.28 with apache 2.0.54 through mod_jk connector (mod_jk.so used from file jakarta-tomcat-connectors-jk-1.2.5-solaris8-sparc-apache-2.0.47.tar.gz at jakarta.apache.org) on Solaris 5.8 (Solaris 8) platform but tomcat is dieing after some time with java.net.SocketException exception. Please help me to get out from this issue Following are the logs and configuration files. ---Tomcathome/logs/Catalina.out--- - [INFO] Http11Protocol - Initializing Coyote HTTP/1.1 on http-8080 [INFO] Http11Protocol - Initializing Coyote HTTP/1.1 on http-8082 [INFO] Catalina - Initialization processed in 10469 ms [INFO] StandardService - Starting service Catalina [INFO] StandardEngine - Starting Servlet Engine: Apache Tomcat/5.0.28 [INFO] StandardHost - XML validation disabled [INFO] StandardHost - Create Host deployer for direct deployment ( non-jmx ) [INFO] StandardHostDeployer - Processing Context configuration file URL file:/export/home/tomcat5/conf/Catalina/localhost/balancer.xml [INFO] StandardHostDeployer - Processing Context configuration file URL file:/export/home/tomcat5/conf/Catalina/localhost/admin.xml [INFO] PropertyMessageResources - Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true [INFO] PropertyMessageResources - Initializing, config='org.apache.struts.action.ActionResources', returnNull=true [INFO] PropertyMessageResources - Initializing, config='org.apache.webapp.admin.ApplicationResources', returnNull=true [INFO] StandardHostDeployer - Processing Context configuration file URL file:/export/home/tomcat5/conf/Catalina/localhost/manager.xml [INFO] StandardHostDeployer - Processing Context configuration file URL file:/export/home/tomcat5/conf/Catalina/localhost/wifi.xml [INFO] WebappClassLoader - validateJarFile(/export/home/webapps/WiFi/WEB-INF/lib/servlet-api.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class [INFO] StandardHostDeployer - Installing web application at context path /jsp-examples from URL file:/export/home/tomcat5/webapps/jsp-examples [INFO] StandardHostDeployer - Installing web application at context path from URL file:/export/home/tomcat5/webapps/ROOT [INFO] StandardHostDeployer - Installing web application at context path /servlets-examples from URL file:/export/home/tomcat5/webapps/servlets-examples [INFO] StandardHostDeployer - Installing web application at context path /tomcat-docs from URL file:/export/home/tomcat5/webapps/tomcat-docs [INFO] StandardHostDeployer - Installing web application at context path /webdav from URL file:/export/home/tomcat5/webapps/webdav [INFO] Http11Protocol - Starting Coyote HTTP/1.1 on http-8080 [INFO] ChannelSocket - JK2: ajp13 listening on /0.0.0.0:8009 [INFO] JkMain - Jk running ID=0 time=4/190 config=/export/home/tomcat5/conf/jk2.properties [INFO] Http11Protocol - Starting Coyote HTTP/1.1 on http-8082 [INFO] Catalina - Server startup in 28234 ms [INFO] Http11Protocol - Pausing Coyote HTTP/1.1 on http-8080 [WARN] ChannelSocket - Exception executing accept java.net.SocketException: Software caused connection abortjava.net.SocketException: Software caused connection abort at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463) at java.net.ServerSocket.implAccept(ServerSocket.java:238) at java.net.ServerSocket.accept(ServerSocket.java:217) at org.apache.jk.common.ChannelSocket.accept(ChannelSocket.java:295) at org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java: 638) at org.apache.jk.common.SocketAcceptor.runIt(ChannelSocket.java:847) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .jav a:683) at java.lang.Thread.run(Thread.java:479) [INFO] StandardService - Stopping service Catalina [INFO] StandardHostDeployer - Removing web application at context path /tomcat-docs [INFO] StandardHostDeployer - Removing web application at context path /admin [INFO] LoggerBase - unregistering logger Catalina:type=Logger,path=/admin,host=localhost [INFO] StandardHostDeployer - Removing web application at context path /jsp-examples [INFO] StandardHostDeployer - Removing web application at context path /billing [INFO] StandardHostDeployer - Removing web application at context path /webdav [INFO
RE: Tomcat thread is dying unexpectedly (Tomcat5.0.28, apache2.0.54 and mod_jk 1.2.5 connector on Solaris 8)
Thanks for your response,
Yes the tomcat still dies with out apache might be because the configuration
for mod_jk are still there only the apache is shutdown.
below are the updated logs after changing in workers.properties, and commenting
out the following lines in server.xml
!--
Connector port=8082
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
enableLookups=false
acceptCount=100 debug=0 connectionTimeout=2
proxyPort=80 disableUploadTimeout=true /
--
Tomcathome/conf/workers.properties--
# Define 1 real worker using ajp13
worker.list=exampWorker
# Set properties for worker1 (ajp13)
worker.exampWorker.type=ajp13
worker.exampWorker.host=127.0.0.1
worker.exampWorker.port=8009
worker.exampWorker.lbfactor=2.5
#worker.exampWorker.cachesize=10
#worker.exampWorker.cache_timeout=600
#worker.exampWorker.socket_keepalive=1
#worker.exampWorker.socket_timeout=300
Tomcathome/logs/localhost_log.2005-06-02.txt-
2005-06-02 17:46:05
StandardContext[/balancer]org.apache.webapp.balancer.BalancerFilter: init():
ruleChain: [org.apache.webapp.balancer.RuleChai
n: [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string: News /
Redirect URL: http://www.cnn.com], [org.apache.webapp.balancer.ru
les.RequestParameterRule: Target param name: paramName / Target param value:
paramValue / Redirect URL: http://www.yahoo.com], [org.apache.webap
p.balancer.rules.AcceptEverythingRule: Redirect URL: http://jakarta.apache.org]]
2005-06-02 17:46:22 StandardContext[/jsp-examples]ContextListener:
contextInitialized()
2005-06-02 17:46:22 StandardContext[/jsp-examples]SessionListener:
contextInitialized()
2005-06-02 17:46:23 StandardContext[/servlets-examples]ContextListener:
contextInitialized()
2005-06-02 17:46:23 StandardContext[/servlets-examples]SessionListener:
contextInitialized()
2005-06-02 18:09:40 StandardContext[/jsp-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@5
75415')
2005-06-02 18:09:40 StandardContext[/jsp-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@1
eb0')
2005-06-02 18:09:40 StandardContext[/jsp-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@5
ee400')
2005-06-02 18:09:40 StandardContext[/jsp-examples]SessionListener:
contextDestroyed()
2005-06-02 18:09:40 StandardContext[/jsp-examples]ContextListener:
contextDestroyed()
2005-06-02 18:09:40 StandardContext[/servlets-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Stri
ng;@33319f')
2005-06-02 18:09:40 StandardContext[/servlets-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Stri
ng;@7ecd78')
2005-06-02 18:09:40 StandardContext[/servlets-examples]ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Stri
ng;@63849c')
2005-06-02 18:09:40 StandardContext[/servlets-examples]SessionListener:
contextDestroyed()
2005-06-02 18:09:40 StandardContext[/servlets-examples]ContextListener:
contextDestroyed()
--Tomcathome/logs/Catalina.out---
[INFO] Http11Protocol - Initializing Coyote HTTP/1.1 on http-8080
[INFO] Catalina - Initialization processed in 10455 ms
[INFO] StandardService - Starting service Catalina
[INFO] StandardEngine - Starting Servlet Engine: Apache Tomcat/5.0.28
[INFO] StandardHost - XML validation disabled
[INFO] StandardHost - Create Host deployer for direct deployment ( non-jmx )
[INFO] StandardHostDeployer - Processing Context configuration file URL
file:/export/home/tomcat5/conf/Catalina/localhost/balancer.xml
[INFO] StandardHostDeployer - Processing Context configuration file URL
file:/export/home/tomcat5/conf/Catalina/localhost/admin.xml
[INFO] PropertyMessageResources - Initializing,
config='org.apache.struts.util.LocalStrings', returnNull=true
[INFO] PropertyMessageResources - Initializing,
config='org.apache.struts.action.ActionResources', returnNull=true
[INFO] PropertyMessageResources - Initializing,
config='org.apache.webapp.admin.ApplicationResources', returnNull=true
[INFO] StandardHostDeployer - Processing Context configuration file URL
file:/export/home/tomcat5/conf/Catalina/localhost/manager.xml
[INFO] StandardHostDeployer - Processing Context configuration file URL
file:/export/home/tomcat5/conf/Catalina/localhost/wifi.xml
[INFO] WebappClassLoader -
validateJarFile(/export/home/webapps/WiFi/WEB-INF/lib/servlet-api.jar) - jar
not loaded. See Servlet Spec 2.3, sectio
n 9.7.2. Offending class: javax/servlet/Servlet.class
[INFO] StandardHostDeployer - Installing web application at context path
/jsp-examples from URL file:/export/home/tomcat5/webapps/jsp-examples
[INFO] StandardHostDeployer - Installing web application at context path from
URL file:/export/home/tomcat5/webapps
jk 1.2.14 connector connection problem
I've run with this configuration elsewhere without error. I'm not certain what the issue is. I have this same problem without using the loadbalancer worker. I can't even get to jkstatus. Any help is greatly appreciated. server.xml ?xml version='1.0' encoding='utf-8'? Server Listener className=org.apache.catalina.mbeans.ServerLifecycleListener/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener/ GlobalNamingResources Environment name=simpleValue type=java.lang.Integer value=30/ Resource auth=Container description=User database that can be updated and saved name=UserDatabase type=org.apache.catalina.UserDatabase/ ResourceParams name=UserDatabase parameter namefactory/name valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value /parameter parameter namepathname/name valueconf/tomcat-users.xml/value /parameter /ResourceParams /GlobalNamingResources Service name=Catalina Connector URIEncoding=UTF-8 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true port=8080 redirectPort=8443 /Connector Connector URIEncoding=UTF-8 port=8009 protocol=AJP/1.3 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler disableUploadTimeout=true maxProcessors=0 redirectPort=8443 debug=9 /Connector Engine defaultHost=localhost jvmRoute=djk name=Catalina Host appBase=webapps name=localhost Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ /Host Logger className=org.apache.catalina.logger.FileLogger prefix=catalina_log. suffix=.txt timestamp=true/ Realm className=org.apache.catalina.realm.UserDatabaseRealm/ /Engine /Service /Server workers.properties # +++ BEGIN CONFIGURATION ++ # # http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html # # The following configuration file describes a JK installation # which does round-robin, session-aware load balancing across all # defined workers. Having a single worker will balance the load on # that worker. This is the default, even if you don't spell it out, # but it is spelled out here for clarity. @TODO indicates a # configuration must be made here. @OPTIONAL indicates an optional # customization may be made. # # workers.properties - # # Copyright 1999-2004 The Apache Software Foundation # # Licensed under the Apache License, Version 2.0 (the License); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an AS IS BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. # # # This file provides jk derived plugins with the needed information to # connect to the different tomcat workers. Note that the distributed # version of this file requires modification before it is usable by a # plugin. # # As a general note, the characters $( and ) are used internally to define # macros. Do not use them in your own configuration!!! # # Whenever you see a set of lines such as: # x=value # y=$(x)\something # # the final value for y will be value\something # # Normaly all you will need to do is un-comment and modify the first three # properties, i.e. workers.tomcat_home, workers.java_home and ps. # Most of the configuration is derived from these. # # When you are done updating workers.tomcat_home, workers.java_home and ps # you should have 3 workers configured: # # - An ajp12 worker that connects to localhost:8007 # - An ajp13 worker that connects to localhost:8009 # - A jni inprocess worker. # - A load balancer worker # # However by default the plugins will only use the ajp12 worker. To have # the plugins use other workers you should modify the worker.list property. # # # You should configure your environment slash... ps=\ on NT and / on UNIX # and maybe something different elsewhere. # ps=\ # #-- ADVANCED MODE #- # # #-- DEFAULT worket list -- #- # # # The workers that your plugins should create and work with # The name of the worker can contain only the alphanumeric characters # [a-z][A-Z][0-9] and is case insensitive. # # Add 'inprocess' if you want JNI connector worker.list=loadbalancer,jkstatus # #-- DEFAULT ajp13 WORKER DEFINITION -- #- # # # Defining a worker named ajp13
Re: jk 1.2.14 connector connection problem
Derrick Koes wrote: I've run with this configuration elsewhere without error. I'm not certain what the issue is. I have this same problem without using the loadbalancer worker. I can't even get to jkstatus. Any help is greatly appreciated. The problem is with the installation. You probably do not have /jakarta virtual directory set up correctly. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jk 1.2.14 connector connection problem
After verifying with Mladen that the setup was correct, the problem is still exhibited. -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Thursday, May 26, 2005 2:39 PM To: Tomcat Users List Subject: Re: jk 1.2.14 connector connection problem Derrick Koes wrote: I've run with this configuration elsewhere without error. I'm not certain what the issue is. I have this same problem without using the loadbalancer worker. I can't even get to jkstatus. Any help is greatly appreciated. The problem is with the installation. You probably do not have /jakarta virtual directory set up correctly. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jk 1.2.14 connector connection problem
Try the simpliest configuration in workers.properties # Define 1 real worker using ajp13 worker.list=worker1,status # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.reclycle_timeout=300 worker.status.type=status -Original Message- From: Derrick Koes [mailto:[EMAIL PROTECTED] Sent: May 26, 2005 3:59 PM To: Tomcat Users List Subject: RE: jk 1.2.14 connector connection problem After verifying with Mladen that the setup was correct, the problem is still exhibited. -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Thursday, May 26, 2005 2:39 PM To: Tomcat Users List Subject: Re: jk 1.2.14 connector connection problem Derrick Koes wrote: I've run with this configuration elsewhere without error. I'm not certain what the issue is. I have this same problem without using the loadbalancer worker. I can't even get to jkstatus. Any help is greatly appreciated. The problem is with the installation. You probably do not have /jakarta virtual directory set up correctly. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:42962a91309751699410697!
RE: jk 1.2.14 connector connection problem
Nope, no dice. -Original Message- From: Phillip Qin [mailto:[EMAIL PROTECTED] Sent: Thursday, May 26, 2005 4:06 PM To: 'Tomcat Users List' Subject: RE: jk 1.2.14 connector connection problem Try the simpliest configuration in workers.properties # Define 1 real worker using ajp13 worker.list=worker1,status # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=8009 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.reclycle_timeout=300 worker.status.type=status -Original Message- From: Derrick Koes [mailto:[EMAIL PROTECTED] Sent: May 26, 2005 3:59 PM To: Tomcat Users List Subject: RE: jk 1.2.14 connector connection problem After verifying with Mladen that the setup was correct, the problem is still exhibited. -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Thursday, May 26, 2005 2:39 PM To: Tomcat Users List Subject: Re: jk 1.2.14 connector connection problem Derrick Koes wrote: I've run with this configuration elsewhere without error. I'm not certain what the issue is. I have this same problem without using the loadbalancer worker. I can't even get to jkstatus. Any help is greatly appreciated. The problem is with the installation. You probably do not have /jakarta virtual directory set up correctly. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !DSPAM:42962a91309751699410697! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Different Authentication Requirements Based On Connector, Port or Protocol?
Hi, We have a Tomcat server (without Apache HTTP server) serving on two ports, 8080 and 8443 (HTTP and HTTPS respectively) using two connectors as described in the various Tomcat SSL FAQs. What I want to do is require users coming in on port 8443 (from the internet) to pass basic user authentication before they can access anything while still allowing our internal users on port 8080 (which will not be accessible from the internet) access without authentication. Basically, I am trying to make a secure extranet the lazy way without annoying the existing intranet users. Can anybody suggest a reasonably easy way to do this? At first I was thinking that I could just put a url-pattern inside a security-constraint in web.xml but I realised that this does not operate on the full URL so I could not filter by port number or protocol here. Thanks, Daniel. -- Daniel Rigal MSc. Systems Administrator - Jai Kudo IT Support Team. This message has been scanned for viruses by MessageLabs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Different Authentication Requirements Based On Connector, Por t or Protocol?
You might think about using Apache HTTP server to proxy (mod_proxy) the external traffic back to your tomcat instance on ports 80 (80 -8080) 443 (443-8443). I've run into situations where ports other than the standard 80 443 are blocked by corporate firewalls. You might be able to use apache to do the authentication that way too. Just my 2 cents. --Dan -Original Message- From: Daniel Rigal [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 25, 2005 9:09 AM To: tomcat-user@jakarta.apache.org Subject: Different Authentication Requirements Based On Connector, Port or Protocol? Hi, We have a Tomcat server (without Apache HTTP server) serving on two ports, 8080 and 8443 (HTTP and HTTPS respectively) using two connectors as described in the various Tomcat SSL FAQs. What I want to do is require users coming in on port 8443 (from the internet) to pass basic user authentication before they can access anything while still allowing our internal users on port 8080 (which will not be accessible from the internet) access without authentication. Basically, I am trying to make a secure extranet the lazy way without annoying the existing intranet users. Can anybody suggest a reasonably easy way to do this? At first I was thinking that I could just put a url-pattern inside a security-constraint in web.xml but I realised that this does not operate on the full URL so I could not filter by port number or protocol here. Thanks, Daniel. -- Daniel Rigal MSc. Systems Administrator - Jai Kudo IT Support Team. This message has been scanned for viruses by MessageLabs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jakarta iis connector under heavy load
Hello! One question about jakarta connector on IIS (isapi filter): Our servlet under heavy load does not receive some pages, client get error The connection with the server was reset or The server returned an invalid or unrecognized response It was with ~ 100 connections per minute. I tried to tune as described in http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html (recovery_options=3,prepost_timeout=100,connect_timeout=100) but all fails with the same result With direct connection to Tomcat (without JK-connector) all works fine. Isapi filter debug log shows nothing unusual. Had anybody have successfull experience with heavyloaded IIS JK-connector? Anatoly - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jakarta iis connector under heavy load
Has you set the cachesize and cache_timeout at your tcp worker ? I have read that IIS default use only one TCP socket as default. Peter PS: 100 request per minute is not a heavy load and normal high end PC :-) Anatoly Kern schrieb: Hello! One question about jakarta connector on IIS (isapi filter): Our servlet under heavy load does not receive some pages, client get error The connection with the server was reset or The server returned an invalid or unrecognized response It was with ~ 100 connections per minute. I tried to tune as described in http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html (recovery_options=3,prepost_timeout=100,connect_timeout=100) but all fails with the same result With direct connection to Tomcat (without JK-connector) all works fine. Isapi filter debug log shows nothing unusual. Had anybody have successfull experience with heavyloaded IIS JK-connector? Anatoly - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jakarta iis connector under heavy load
Anatoly Kern wrote: Hello! http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html (recovery_options=3,prepost_timeout=100,connect_timeout=100) but all Hi, prepost_timeout and connect_timeout are defined in milliseconds, Like you said read the: http://jakarta.apache.org/tomcat/connectors-doc/config/workers.html and you will find that statement. So, under high load it's probable that your request will not be served inside 100 milliseconds, and that's why mod_jk will think your tomcat is dead. Since you probably meant to set that value to seconds, just multiply with 1000. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SSL Connector + truststore refresh without bouncing tomcat
Hello, I'm using ssl client authentication with Tomcat 5.0.28. I have configured it to use my truststoreFile and all works fine there. I have added a feature to my webapp (The freebXML Registry, http://ebxmlrr.sourceforge.net/) to allow the user to register his own certificate when creating an user account. The certificate gets added to truststoreFile and other account details are set. My problem is that the SSL Connector will only read the truststoreFile when it is initialized. What I would like to have something monitoring the keystore file for changes and reload it to to the connector when it happens. I could not find a way to do it yet by checking the source for JSSEConnector (method init() triggers keystore loading). Has anybody done something similar?? Another posibility would be to re-initialize the connector every hour, fo instance. There would be some delay after registration but user could be pacient and wait a bit. Is this easy to achieve/configure?? Thanks, Diego -- Diego Ballve Digital Artefacts Europe http://www.digital-artefacts.fi/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SSL Connector + truststore refresh without bouncing tomcat
Diego Ballve [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hello, I'm using ssl client authentication with Tomcat 5.0.28. I have configured it to use my truststoreFile and all works fine there. I have added a feature to my webapp (The freebXML Registry, http://ebxmlrr.sourceforge.net/) to allow the user to register his own certificate when creating an user account. The certificate gets added to truststoreFile and other account details are set. My problem is that the SSL Connector will only read the truststoreFile when it is initialized. What I would like to have something monitoring the keystore file for changes and reload it to to the connector when it happens. I could not find a way to do it yet by checking the source for JSSEConnector (method init() triggers keystore loading). Has anybody done something similar?? Strangely, there seems to be more requests to do this sort of thing. Take a look at http://issues.apache.org/bugzilla/show_bug.cgi?id=34643. It's possible to bounce the Connector using JMX (which probably isn't good enough, since it bounces already-connected sessions as well). Otherwise, no, Tomcat currently initializes the TrustStore on startup, and won't re-initialize it afterwards. As always, patches are always welcome :). Another posibility would be to re-initialize the connector every hour, fo instance. There would be some delay after registration but user could be pacient and wait a bit. Is this easy to achieve/configure?? Thanks, Diego -- Diego Ballve Digital Artefacts Europe http://www.digital-artefacts.fi/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JK Connector - Can't get it to work
Hi everyone, I have studied this problem for a week now, and I can't seem to figure it out. All I want to do is connect Tomcat 5.5.4 Server to Apache 2.0.52. I've read the documents about the jk connector over and over, and tried doing the setup with many tiny variations, but whatever I do I always get either a 404 or a 200. If I hit tomcat directly through localhost:8080 I can run all my servlets and jsps, but not when I try and hit it through apache. Here are the appropriate snips from all my files. Can anyone offer advice - I'm guessing the problem is in my server.xml since everything else is either a log, an auto-generated, or a one liner in the httpd.conf. Thanks in advance to anyone who can help. httpd.conf - I only have one Tomcat/Jk line in it right now - the include. Include C:/Program Files/Apache Software Foundation/Tomcat 5.5/conf/auto/mod_jk.conf mod_jk.conf (obviously this is 100% auto-generated) ## Auto generated on Thu May 05 21:33:00 CDT 2005## IfModule !mod_jk.c LoadModule jk_module C:/Program Files/Apache Group/Apache2/modules/mod_jk.so /IfModule JkWorkersFile C:/Program Files/Apache Software Foundation/Tomcat 5.5/conf/jk/workers.properties JkLogFile C:/Program Files/Apache Software Foundation/Tomcat 5.5/logs/mod_jk.log JkLogLevel emerg VirtualHost localhost ServerName localhost JkMount /roots ajp13 JkMount /roots/* ajp13 JkMount /wiki ajp13 JkMount /wiki/* ajp13 JkMount /tomcat-docs ajp13 JkMount /tomcat-docs/* ajp13 JkMount /manager ajp13 JkMount /manager/* ajp13 /VirtualHost server.xml Server port=8005 shutdown=SHUTDOWN Listener className=org.apache.jk.config.ApacheConfig modJk=C:/Program Files/Apache Group/Apache2/modules/mod_jk.so / GlobalNamingResources !-- Used by Manager webapp -- Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved factory=org.apache.catalina.users.MemoryUserDatabaseFactory pathname=conf/tomcat-users.xml / /GlobalNamingResources Service name=Catalina Connector port=8080 / !-- This is here for compatibility only, not required -- Connector port=8009 protocol=AJP/1.3 / Engine name=Catalina defaultHost=localhost Realm className=org.apache.catalina.realm.UserDatabaseRealm resourceName=UserDatabase / Host name=localhost appBase=webapps Listener className=org.apache.jk.config.ApacheConfig modJk=C:/Program Files/Apache Group/Apache2/modules/mod_jk.so append=true/ /Host /Engine /Service /Server mod_jk.log in the first line note that Apache seems to be asking jk about every request - that can't be right... in the last line this is what I usually get when I try and hit a jsp - I get different errors if I try tweaking my httpd.conf [Thu May 05 18:48:17 2005] [1924:2220] [debug] map_uri_to_worker::jk_uri_worker_map.c (455): Attempting to map URI '/index.php' from 1 maps ... snip [Thu May 05 21:23:18 2005] [error] ajp_service::jk_ajp_common.c (1733): Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=ajp13 failed - Yahoo! Mail Stay connected, organized, and protected. Take the tour
Re: JK Connector - Can't get it to work
Hey, Has your workers.properties a correct setup? worker.list=ajp13 worker.ajp13.type=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.cachesize=150 worker.ajp13.cache_timeout=600 What mod_jk Version you use? Better config at mod_jk =1.2.10 add this worker.list=router,jkstatus worker.router.type=lb worker.router.balance_workers=ajp13 worker.jkstatus.type=status and add JkMount /jkstatus jkstatus to your vhost at httpd.conf then you can see the mod_jk status wiht http://localhost/jkstatus Peter Pep Blast schrieb: Hi everyone, I have studied this problem for a week now, and I can't seem to figure it out. All I want to do is connect Tomcat 5.5.4 Server to Apache 2.0.52. I've read the documents about the jk connector over and over, and tried doing the setup with many tiny variations, but whatever I do I always get either a 404 or a 200. If I hit tomcat directly through localhost:8080 I can run all my servlets and jsps, but not when I try and hit it through apache. Here are the appropriate snips from all my files. Can anyone offer advice - I'm guessing the problem is in my server.xml since everything else is either a log, an auto-generated, or a one liner in the httpd.conf. Thanks in advance to anyone who can help. httpd.conf - I only have one Tomcat/Jk line in it right now - the include. Include C:/Program Files/Apache Software Foundation/Tomcat 5.5/conf/auto/mod_jk.conf mod_jk.conf (obviously this is 100% auto-generated) ## Auto generated on Thu May 05 21:33:00 CDT 2005## IfModule !mod_jk.c LoadModule jk_module C:/Program Files/Apache Group/Apache2/modules/mod_jk.so /IfModule JkWorkersFile C:/Program Files/Apache Software Foundation/Tomcat 5.5/conf/jk/workers.properties JkLogFile C:/Program Files/Apache Software Foundation/Tomcat 5.5/logs/mod_jk.log JkLogLevel emerg VirtualHost localhost ServerName localhost JkMount /roots ajp13 JkMount /roots/* ajp13 JkMount /wiki ajp13 JkMount /wiki/* ajp13 JkMount /tomcat-docs ajp13 JkMount /tomcat-docs/* ajp13 JkMount /manager ajp13 JkMount /manager/* ajp13 /VirtualHost server.xml Server port=8005 shutdown=SHUTDOWN Listener className=org.apache.jk.config.ApacheConfig modJk=C:/Program Files/Apache Group/Apache2/modules/mod_jk.so / GlobalNamingResources !-- Used by Manager webapp -- Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved factory=org.apache.catalina.users.MemoryUserDatabaseFactory pathname=conf/tomcat-users.xml / /GlobalNamingResources Service name=Catalina Connector port=8080 / !-- This is here for compatibility only, not required -- Connector port=8009 protocol=AJP/1.3 / Engine name=Catalina defaultHost=localhost Realm className=org.apache.catalina.realm.UserDatabaseRealm resourceName=UserDatabase / Host name=localhost appBase=webapps Listener className=org.apache.jk.config.ApacheConfig modJk=C:/Program Files/Apache Group/Apache2/modules/mod_jk.so append=true/ /Host /Engine /Service /Server mod_jk.log in the first line note that Apache seems to be asking jk about every request - that can't be right... in the last line this is what I usually get when I try and hit a jsp - I get different errors if I try tweaking my httpd.conf [Thu May 05 18:48:17 2005] [1924:2220] [debug] map_uri_to_worker::jk_uri_worker_map.c (455): Attempting to map URI '/index.php' from 1 maps ... snip [Thu May 05 21:23:18 2005] [error] ajp_service::jk_ajp_common.c (1733): Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=ajp13 failed - Yahoo! Mail Stay connected, organized, and protected. Take the tour - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building connector JK-1.2.11
Dan Baggott wrote: Hi, I'm attempting to build JK-1.2.11 on Solaris 2.8 (sparc) for use with Apache 1.3. There was a thread on the same subject but for the Apache 2 with the same problem. The reason why build fails is because the Solaris 8 make is some sort of BSD make that does not populate 'first prerequisite' ($ macro). The solution is to use the GNU make or gmake for building if this is not default make on the system. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SSL Connector with client auth in TC 5.5.9
We are switching to TC 5.5.9 in an embedded server. In version 5.0.29, whe configured SSL with client auth as follows: CoyoteConnector connector = new CoyoteConnector(); connector.setAddress( host ); connector.setPort( port ); connector.setSecure(true); connector.setCiphers( SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_3DES_EDE_CBC_SHA ); CoyoteServerSocketFactory factory = new CoyoteServerSocketFactory(); factory.setClientAuth( true ); factory.setKeystoreFile( keyStore ); factory.setKeystorePass( *** ); factory.setProtocol( TLS ); connector.setFactory( factory ); In 5.5.9 whe use org.apache.catalina.connector.Connector connector; connector = webServer.createConnector( host, port, true); but we cannot find out how to set the Socket Factory for client auth. Are we missing something with the new Connector class? Thanks in advance Domenico Aquilino - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Building connector JK-1.2.11
checking for style of include used by make... GNU checking dependency style of gcc... none checking for a sed that does not truncate output... /usr/xpg4/bin/sed checking for egrep... egrep checking for ld used by gcc... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for /usr/ccs/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/local/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... no checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... none checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 262144 checking command to parse /usr/local/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/ccs/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... solaris2.8 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking for shl_load... no checking for shl_load in -ldld... no checking for dlopen... no checking for dlopen in -ldl... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.8 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking for shl_load... (cached) no checking for shl_load in -ldld... (cached) no checking for dlopen... (cached) no checking for dlopen in -ldl... (cached) yes checking whether a program can dlopen itself... (cached) yes checking whether a statically linked program can dlopen itself... (cached) yes appending configuration tag F77 to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.8 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking for test... /usr/bin/test checking for rm... /usr/bin/rm checking for grep... /usr/bin/grep checking for echo... /usr/bin/echo checking for sed... /usr/xpg4/bin/sed checking for cp... /usr/bin/cp checking for mkdir... /usr/bin/mkdir checking for snprintf... yes checking for vsnprintf... yes checking for flock... no checking for setsockopt in -lsocket... yes checking whether to use SO_RCVTIMEO with setsockopt()... no checking whether to use SO_SNDTIMEO with setsockopt()... no need to check for Perl first, apxs depends on it... checking for perl... /usr/bin/perl building connector for apache-1.3 checking for target platform... unix no apache given ...Enabling EAPI Support... configure: creating ./config.status config.status: creating Makefile config.status: creating apache-1.3/Makefile config.status: creating apache-1.3/Makefile.apxs config.status: creating apache-2.0/Makefile config.status: creating apache-2.0
RE: apache + tomcat + JK connector configuration
http://www.one0.com/html/downloads.php Download the pdf ( nice ) / doc version Nice :o) Guru -Original Message- From: anshul shrivastava [mailto:[EMAIL PROTECTED] Sent: 26 April 2005 18:08 To: Tomcat Users List Subject: Re: apache + tomcat + JK connector configuration Importance: High Hi all, This is my first post to group. I've already asked this problem in popular forums, but can't resolve. Hope, someone of you'll help. Thank you, in advance, very much. I'm using Tomcat Apache Tomcat/5.0.16 on jdk 1.5.0 ( port 8080 ). I've installed Apache2 ( port 80 ) using MSI installer on Windows 200 Professional. I want to use mod_jserv and connect Tomcat, Apache and database MySQL. I read, it is better not to process .html requests by Tomcat, instead by Apache. Also, I want to run .jsp files from ~/wwwroot ( Apache is already working PHP files in ~/wwwroot ). Someone of you, said to forward, .jsp to Apache using .htaccess. Also, it can be done by Apache Module, how ? Please also tell me, where ( exact url ) can I download jk_connecter or mod_jserv ? ( I've already downloaded something! ). Please help. anshul shrivastava ( I'm very new to Java; swithcing to Java! from PHP ) What is the username/password for http://localhost:8080/admin/ What is catalina, by the way ? ( h'ven't seen it in previous versions ). - Original Message - From: Delphine Lê [EMAIL PROTECTED] To: 'Tomcat Users List' tomcat-user@jakarta.apache.org Sent: Monday, April 18, 2005 6:26 PM Subject: RE: apache + tomcat + JK connector configuration Bob, Thank you but Apache doesn't start if I add this line. The Apache config I have is: LoadModule jk_module modules/mod_jk.so JkWorkersFile conf/workers.properties JkLogFile logs/mod_jk.log JkLogLevel debug JkMount /examples worker1 It seems to works fine (see the logs in my very first message). And also, I can see that it automatically creates a mod_jk.conf file in $TOMCAT_HOME\conf\auto Regards -Original Message- From: Robert Harrison [mailto:[EMAIL PROTECTED] Sent: vendredi 15 avril 2005 19:52 To: Tomcat Users List Subject: Re: apache + tomcat + JK connector configuration Delphine, Have you added JkSet config.file ... to your apache config file? Bob On 4/14/05, Delphine Lê [EMAIL PROTECTED] wrote: I tried this, but it didn't help unfortunately Thank you Are you using load balance in your app? If not, you probably don't need this line: worker.worker1.lbfactor=50 Try to use this configuration in the server.xml Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=6969 minProcessors=5 maxProcessors=75 enableLookups=false acceptCount=10 debug=0/ Hope this helps... -Original Message- From: Delphine Lê [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 6:41 PM To: tomcat-user@jakarta.apache.org Subject: RE: apache + tomcat + JK connector configuration thank you, but it's got them: # Define 1 real worker using ajp13 worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=6969 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.reclycle_timeout=300 Post the workers.properties file. You probably need to include these lines in that file: worker.list=worker1 worker.worker1.port=6969 -Original Message- From: Delphine Lê [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 2:01 PM To: tomcat-user@jakarta.apache.org Subject: apache + tomcat + JK connector configuration Hello, Has anyone had any success in configuring Apache (2.0.53) with Tomcat (4.1.29) in Windows XP, using a recent JK connector ? We have a server running with the JK2 connector and I'm trying to replace it with the latest JK connector (JK-1.2.10), the reason being that JK2 is officially unsupported as of 15 Nov 2004 and we're experiencing a problem with truncated requests due to this connector. In Apache, I configured a worker called worker1 and I send everything from context /examples to this worker following http://jakarta.apache.org/tomcat/connectors-doc/howto/quick.html. The configuration looks fine, since I can see in the following lines in mod_jk.log: [Wed Apr 13 18:49:13 2005] [debug] uri_worker_map_add::jk_uri_worker_map.c (269): exact rule /examples=worker1 was added [Wed Apr 13 18:49:13 2005] [debug] build_worker_map::jk_worker.c (219): creating worker worker1 [Wed Apr 13 18:49:13 2005] [debug] wc_create_worker::jk_worker.c (125): about to create instance worker1 of ajp13 [Wed Apr 13 18:49:13 2005] [debug] wc_create_worker::jk_worker.c (138): about to validate and init worker1 [Wed Apr 13 18:49:13 2005] [debug] ajp_validate::jk_ajp_common.c (1781): worker worker1 contact is 'localhost:6969' However, if I send
Re: apache + tomcat + JK connector configuration
Hi all, This is my first post to group. I've already asked this problem in popular forums, but can't resolve. Hope, someone of you'll help. Thank you, in advance, very much. I'm using Tomcat Apache Tomcat/5.0.16 on jdk 1.5.0 ( port 8080 ). I've installed Apache2 ( port 80 ) using MSI installer on Windows 200 Professional. I want to use mod_jserv and connect Tomcat, Apache and database MySQL. I read, it is better not to process .html requests by Tomcat, instead by Apache. Also, I want to run .jsp files from ~/wwwroot ( Apache is already working PHP files in ~/wwwroot ). Someone of you, said to forward, .jsp to Apache using .htaccess. Also, it can be done by Apache Module, how ? Please also tell me, where ( exact url ) can I download jk_connecter or mod_jserv ? ( I've already downloaded something! ). Please help. anshul shrivastava ( I'm very new to Java; swithcing to Java! from PHP ) What is the username/password for http://localhost:8080/admin/ What is catalina, by the way ? ( h'ven't seen it in previous versions ). - Original Message - From: Delphine Lê [EMAIL PROTECTED] To: 'Tomcat Users List' tomcat-user@jakarta.apache.org Sent: Monday, April 18, 2005 6:26 PM Subject: RE: apache + tomcat + JK connector configuration Bob, Thank you but Apache doesn't start if I add this line. The Apache config I have is: LoadModule jk_module modules/mod_jk.so JkWorkersFile conf/workers.properties JkLogFile logs/mod_jk.log JkLogLevel debug JkMount /examples worker1 It seems to works fine (see the logs in my very first message). And also, I can see that it automatically creates a mod_jk.conf file in $TOMCAT_HOME\conf\auto Regards -Original Message- From: Robert Harrison [mailto:[EMAIL PROTECTED] Sent: vendredi 15 avril 2005 19:52 To: Tomcat Users List Subject: Re: apache + tomcat + JK connector configuration Delphine, Have you added JkSet config.file ... to your apache config file? Bob On 4/14/05, Delphine Lê [EMAIL PROTECTED] wrote: I tried this, but it didn't help unfortunately Thank you Are you using load balance in your app? If not, you probably don't need this line: worker.worker1.lbfactor=50 Try to use this configuration in the server.xml Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=6969 minProcessors=5 maxProcessors=75 enableLookups=false acceptCount=10 debug=0/ Hope this helps... -Original Message- From: Delphine Lê [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 6:41 PM To: tomcat-user@jakarta.apache.org Subject: RE: apache + tomcat + JK connector configuration thank you, but it's got them: # Define 1 real worker using ajp13 worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=localhost worker.worker1.port=6969 worker.worker1.lbfactor=50 worker.worker1.cachesize=10 worker.worker1.cache_timeout=600 worker.worker1.socket_keepalive=1 worker.worker1.reclycle_timeout=300 Post the workers.properties file. You probably need to include these lines in that file: worker.list=worker1 worker.worker1.port=6969 -Original Message- From: Delphine Lê [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 2:01 PM To: tomcat-user@jakarta.apache.org Subject: apache + tomcat + JK connector configuration Hello, Has anyone had any success in configuring Apache (2.0.53) with Tomcat (4.1.29) in Windows XP, using a recent JK connector ? We have a server running with the JK2 connector and I'm trying to replace it with the latest JK connector (JK-1.2.10), the reason being that JK2 is officially unsupported as of 15 Nov 2004 and we're experiencing a problem with truncated requests due to this connector. In Apache, I configured a worker called worker1 and I send everything from context /examples to this worker following http://jakarta.apache.org/tomcat/connectors-doc/howto/quick.html. The configuration looks fine, since I can see in the following lines in mod_jk.log: [Wed Apr 13 18:49:13 2005] [debug] uri_worker_map_add::jk_uri_worker_map.c (269): exact rule /examples=worker1 was added [Wed Apr 13 18:49:13 2005] [debug] build_worker_map::jk_worker.c (219): creating worker worker1 [Wed Apr 13 18:49:13 2005] [debug] wc_create_worker::jk_worker.c (125): about to create instance worker1 of ajp13 [Wed Apr 13 18:49:13 2005] [debug] wc_create_worker::jk_worker.c (138): about to validate and init worker1 [Wed Apr 13 18:49:13 2005] [debug] ajp_validate::jk_ajp_common.c (1781): worker worker1 contact is 'localhost:6969' However, if I send a request, it doesn't get through and I get an error message in the browser. The log shows: [Wed Apr 13 18:50:16 2005] [info] ajp_connect_to_endpoint::jk_ajp_common.c (877): Failed connecting to tomcat. Tomcat is probably not started or is listening on the wrong host/port
RE: apache + tomcat + JK connector configuration
From: anshul shrivastava [mailto:[EMAIL PROTECTED] Subject: Re: apache + tomcat + JK connector configuration I'm using Tomcat Apache Tomcat/5.0.16 Why such an old level? If you want to use the 5.0 branch, at least get the current version. Better yet, use 5.5. I read, it is better not to process .html requests by Tomcat, Although this was often true in the past, the performance of the current Tomcat levels is such that it can handle static content quite effectively. Avoiding use of Apache httpd also eliminates a significant amount of complexity. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: apache + tomcat + JK connector configuration
Avoiding use of Apache httpd also eliminates a significant amount of complexity. httpd.conf is an important file. I wanna use PHP/JSP/MySQL with Apache. ( surprised ) Please someone, send a useful reply ! - Original Message - From: Caldarale, Charles R [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Tuesday, April 26, 2005 11:11 PM Subject: RE: apache + tomcat + JK connector configuration From: anshul shrivastava [mailto:[EMAIL PROTECTED] Subject: Re: apache + tomcat + JK connector configuration I'm using Tomcat Apache Tomcat/5.0.16 Why such an old level? If you want to use the 5.0 branch, at least get the current version. Better yet, use 5.5. I read, it is better not to process .html requests by Tomcat, Although this was often true in the past, the performance of the current Tomcat levels is such that it can handle static content quite effectively. Avoiding use of Apache httpd also eliminates a significant amount of complexity. - Chuck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: apache + tomcat + JK connector configuration
Anshul, The mod_jk binaries I'm using I got at http://apache.intissite.com/jakarta/tomcat-connectors/jk/binaries/;, pick you flavor. This page was about the most help documentation http://jakarta.apache.org/tomcat/connectors-doc/howto/apache.html; for me. This won't solve the error for you, but I'm running into almost the exact same problem trying to get Apache 2.0.53, and Tomcat 4.1 under Solaris 8 working. I am using JK instead of JK2. If your are able to run the demos for Tomcat when you goto port 8080, then Tomcat is up and running. The apache module modifications I did are: At the end of the load modules section add: LoadModule jk_module modules/mod_jk.so You'll need to adjust the modules/ to be correct for your installation, I found it easy enough to simply copy the mod_jk.so file to the apache modules folder. There were also instructions to add AddModule jk_module to the httpd.conf file, but everytime I did, it barked on startup so I've left it out. The other mods to httpd.conf are to enable the connector, in a section of the file that is not part of a VirtualHost declaration. I modified the JkLogLevel and file so I could attempt to see what's happening with that, which I think you've done as well. JkWorkersFile /usr/local/apache2/conf/workers.properties JkLogFile /usr/local/apache2/logs/mod_jk_log #JkLogFile /var/log/httpd/mod_jk.log #JkLogLevel info JkLogLevel debug JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories JkRequestLogFormat %w %V %T In the VitualHost declarations, I've added: DocumentRoot /usr/local/apache2/htdocs ServerName myservername.domain.com JkMount /*.jsp ajp13 JkMount /servlet/* ajp13 JkMount /examples/servlet/* ajp13 JkMount /examples/*.jsp ajp13 JkMount /examples/jsp/*.jsp ajp13 jkMount /*.jsp ajp13 I think from your previous emails you're using worker1, so just change the 'ajp13' entries to 'worker1' And at that point when I try to run a simple 'testit.jsp' from the VirtualHost site, I can find in the /usr/local/apache2/logs/mod_jk_log file the following errors. I also posted a request last week about the same and got no response. snip --- [Sat Apr 23 20:06:02 2005] [jk_uri_worker_map.c (486)]: Into jk_uri_worker_map_t::map_uri_to_worker [Sat Apr 23 20:06:02 2005] [jk_uri_worker_map.c (500)]: Attempting to map URI '/testit.jsp' [Sat Apr 23 20:06:02 2005] [jk_uri_worker_map.c (580)]: jk_uri_worker_map_t::map_uri_to_worker, Found a suffix match ajp13 - *.jsp [Sat Apr 23 20:06:02 2005] [mod_jk.c (1709)]: Into handler r-proxyreq=0 r-handler=jakarta-servlet r-notes=2259208 worker=ajp13 [Sat Apr 23 20:06:02 2005] [jk_worker.c (132)]: Into wc_get_worker_for_name ajp13 [Sat Apr 23 20:06:02 2005] [jk_worker.c (136)]: wc_get_worker_for_name, done found a worker [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c (1546)]: Into jk_worker_t::get_endpoint [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c (1208)]: Into jk_endpoint_t::service [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c (295)]: Into ajp_marshal_into_msgb [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c (463)]: ajp_marshal_into_msgb - Done [Sat Apr 23 20:06:02 2005] [jk_connect.c (188)]: Into jk_open_socket [Sat Apr 23 20:06:02 2005] [jk_connect.c (195)]: jk_open_socket, try to connect socket = 16 [Sat Apr 23 20:06:02 2005] [jk_connect.c (204)]: jk_open_socket, after connect ret = -1 [Sat Apr 23 20:06:02 2005] [jk_connect.c (233)]: jk_open_socket, connect() failed errno = 128 [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c (676)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 128 [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c (955)]: Error connecting to the Tomcat process. [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c (1309)]: sending request to tomcat failed in send loop. err=0 [Sat Apr 23 20:06:02 2005] [jk_connect.c (188)]: Into jk_open_socket [Sat Apr 23 20:06:02 2005] [jk_connect.c (195)]: jk_open_socket, try to connect socket = 16 [Sat Apr 23 20:06:02 2005] [jk_connect.c (204)]: jk_open_socket, after connect ret = -1 [Sat Apr 23 20:06:02 2005] [jk_connect.c (233)]: jk_open_socket, connect() failed errno = 128 [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c (676)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 128 [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c (955)]: Error connecting to the Tomcat process. [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c (1309)]: sending request to tomcat failed in send loop. err=1 [Sat Apr 23 20:06:02 2005] [jk_connect.c (188)]: Into jk_open_socket [Sat Apr 23 20:06:02 2005] [jk_connect.c (195)]: jk_open_socket, try to connect socket = 16 [Sat Apr 23 20:06:02 2005] [jk_connect.c (204)]: jk_open_socket, after connect ret = -1 [Sat Apr 23 20:06:02 2005] [jk_connect.c (233)]: jk_open_socket, connect() failed errno = 128 [Sat Apr 23 20:06:02 2005] [jk_ajp_common.c
Pb with thread and http-connector
Hi, I'm running tomcat 4.1.31 on HP-UX 11i with the HotSpot JVM 1.4.2_02. I'm using a Coyote HTTP/1.1 Connector. I'm investigating the following memory issue : the heap size grows until the -Xmx value and then the I have a java.lan.OutOfMemory exception. Using HPjmeter to profile my appliation, I discovered that tomcat creates new http thread and destroys the older. The number of thread is stable (betwenn 5 and 10). I don't understand that behavior and I suspect that it's related with my memory issue. Someone has an idea on that behavior ? Is it a normal one ? How can I configure tomcat (or the coyote connector) to log why it creates and kills thread ? Thank you for your help Xavier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
