Re: Modjk and Tomcat 5.5.4 problem
Rick, Thanks for the info. I will try it out. It is interesting when I look at the config for all of the other Connectors, they all have a connectionTimeout value. -John On Oct 5, 2005, at 7:24 PM, Rick wrote: We had an issue where it seemed like it would crash using mod_jk, the trouble was the connections were not letting go. By default, I think the timeout is infinite, so after setting the property: connectionTimeout, in the server.xml's connector descriptor as follows, Connector port= protocol=AJP/1.3 connectionTimeout=6 .../ The old connections would get cleaned up and we stopped having problems, however, I'm not sure this was the correct way to do this, seems to work. Not sure if this is related to your problem. -Rick -Original Message- From: John Martyniak [mailto:[EMAIL PROTECTED] Posted At: Wednesday, October 05, 2005 3:53 PM Posted To: Tomcat Dev Conversation: Modjk and Tomcat 5.5.4 problem Subject: Modjk and Tomcat 5.5.4 problem Has anyone had any problems with ModJK crashing the server? I haven't been able to fully debug yet, primarily because it doesn't update any logs to state there is a problem, and I can't reliably replicate the problem. I am using Apache 2.0.47, modjk 1.2.5 and tomcat 5.5.4 I think that it has something to do with modjk because when I go directly to the appserver the problem doesn't seem to exist. Any help would be greatly appreciated. Thank you, -John - 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: Modjk and Tomcat 5.5.4 problem
Rick, I have made the changes and was able to replicate the problem pretty quickly. And again no message in the mod_jk or catalina.out files. It turns out that my workers file has all of those properties. I am including it below. # Define worker using ajp13 worker.list=worker1, worker2 # 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.socket_timeout=300 -John On Oct 6, 2005, at 12:01 PM, Rick wrote: Hey John, I have been looking into this on my end as well, since I'm not fully satisfied that it's the proper solution. As a question, what does your Apache workers.properties file look like. Do you have any of the properties such as recycle_timeout, socket_timeout, cachesize, or cache_timeout set? -Rick -Original Message- From: John Martyniak [mailto:[EMAIL PROTECTED] Posted At: Thursday, October 06, 2005 8:43 AM Posted To: Tomcat Dev Conversation: Modjk and Tomcat 5.5.4 problem Subject: Re: Modjk and Tomcat 5.5.4 problem Rick, Thanks for the info. I will try it out. It is interesting when I look at the config for all of the other Connectors, they all have a connectionTimeout value. -John On Oct 5, 2005, at 7:24 PM, Rick wrote: We had an issue where it seemed like it would crash using mod_jk, the trouble was the connections were not letting go. By default, I think the timeout is infinite, so after setting the property: connectionTimeout, in the server.xml's connector descriptor as follows, Connector port= protocol=AJP/1.3 connectionTimeout=6 .../ The old connections would get cleaned up and we stopped having problems, however, I'm not sure this was the correct way to do this, seems to work. Not sure if this is related to your problem. -Rick -Original Message- From: John Martyniak [mailto:[EMAIL PROTECTED] Posted At: Wednesday, October 05, 2005 3:53 PM Posted To: Tomcat Dev Conversation: Modjk and Tomcat 5.5.4 problem Subject: Modjk and Tomcat 5.5.4 problem Has anyone had any problems with ModJK crashing the server? I haven't been able to fully debug yet, primarily because it doesn't update any logs to state there is a problem, and I can't reliably replicate the problem. I am using Apache 2.0.47, modjk 1.2.5 and tomcat 5.5.4 I think that it has something to do with modjk because when I go directly to the appserver the problem doesn't seem to exist. Any help would be greatly appreciated. Thank you, -John - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Modjk and Tomcat 5.5.4 problem
Has anyone had any problems with ModJK crashing the server? I haven't been able to fully debug yet, primarily because it doesn't update any logs to state there is a problem, and I can't reliably replicate the problem. I am using Apache 2.0.47, modjk 1.2.5 and tomcat 5.5.4 I think that it has something to do with modjk because when I go directly to the appserver the problem doesn't seem to exist. Any help would be greatly appreciated. Thank you, -John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
A Problem with Apache, Mod_jk and Tomcat
I just put up a new app on Mac OSX server, Apache 2.0.47, mod_jk 1.2.4 and Tomcat 5.5.4. I currently have it configured to work in the following ways: http://apps:8080/appname --- straight out of the box. http://app/appname -- mod_jk and virtual hosts. When I run the application through the virtual host, after several logins and data grabs the application throws an internal 500 error, and Tomcat dies. It doesn't leave any error message in either apache log files, or the catalina log files. I have also enabled the log4J in DEBUG, and no help their. I can reproduce the error by logging in and out from several users. If I run the app directly on the app server using the 8080 address it works fine. The process that I normally use to crash the app doesn't seem to work. Also when I run this on my dev environment, I can't reproduce the problem, the only difference that I can tell is that the virtual host name isn't DNS'd. Any thoughts or ideas? I am really stumped on solving this one. Thanks in advance for any help. -john - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Setting maximum logging on Tomcat 5.5.4
Hi everyone, I have recently upgraded all of my apps to run on Tomcat 5.5.4, and Struts 1.2.4. I would like to find out how to set the maximum level of logging. In the the version that I was using before (4.1.27) it automatically created several kinds of log files. The new version only creates a catalina.out file. I am getting 500 error that I need to debug. Also I am currently using mod JK to connect the webserver and app server. Any and all help would be greatly appreciated. Thank you, -John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 4.1.x and mod_jk config
Hi everyone, I am trying to configure my Apache server to talk to my Tomcat server using mod_jk. It is kind of a major nightmare. The first step for me is to get it working at any level. Meaning that I can do http://localhost/examples/jsp/index.jsp and it brings the page up and runs the jsp. However this does not happen. I am looking for any help, or links that people that can send my way so that I can figure this out. The second step is to be able to run multiple Virtual hosts on the webserver with multiple webapps on the app server. Any help that can be provided would be greatly appreciated. Thank you, -John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using DNS name instead of port number
I would like to be able to use the following Virtual host apps.beforedawn.com to run my app. Instead of having to include the 8080. Their is also a Webserver running on the box. So that I could run http://apps.beforedawn.com/index.jsp So my question is can this be done inside of Tomcat, or will I need to use mod_jk. Thanks for any and all help. -John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using DNS name instead of port number
The server currently only has one IP address and several virtual hosts. Some that are served by the Web Server and some that are going to be served by Tomcat. For example on this box I would to do the following: Web Server: Serves http://www.beforedawn.com Tomcat Server: http://apps.beforedawn.com/index.jsp http://diagnostics.beforedawn.com/index.jsp Is this possible? -John On 1/13/05 3:38 PM, Hassan Schroeder [EMAIL PROTECTED] wrote: John Martyniak wrote: I would like to be able to use the following Virtual host apps.beforedawn.com to run my app. Instead of having to include the 8080. Their is also a Webserver running on the box. So that I could run http://apps.beforedawn.com/index.jsp So my question is can this be done inside of Tomcat, or will I need to use mod_jk. If the system in question has multiple IP addresses, yes. Configure your Tomcat connector to listen to the appropriate address(es) on port 80 and configure Apache to listen to the other address(es). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using DNS name instead of port number
Unfortunately this is for one of my external boxes (read have to pay ungodly sums of money to get another block of IP addresses). So if I set this up using mod_jk then I will have to do the following VirtualHost www.befordawn.com DocumentRoot /var/www/htmlbeforedawn ErrorLog logs/beforedawn_error_log DirectoryIndex index.php index.html index.htm index.shtml ServerAdmin root@ beforedawn.com # ServerName www. beforedawn.com ServerSignature email TransferLog logs/ beforedawn_access_log /VirtualHost VirtualHost apps.beforedawn.com DocumentRoot /var/www/appbeforedawn ErrorLog logs/appbeforedawn_error_log DirectoryIndex index.php index.html index.htm index.shtml ServerAdmin [EMAIL PROTECTED] # ServerName apps.beforedawn.com ServerSignature email TransferLog logs/appsbeforedawn_access_log JKMount /apps worker1 JKMount /apps/* worker1 /VirtualHost VirtualHost diagnostics.beforedawn.com DocumentRoot /var/www/diagbeforedawn ErrorLog logs/diagbeforedawn_error_log DirectoryIndex index.php index.html index.htm index.shtml ServerAdmin [EMAIL PROTECTED] # ServerName diagnostics.beforedawn.com ServerSignature email TransferLog logs/diagbeforedawn_access_log JKMount /diag worker1 JKMount /diag/* worker1 /VirtualHost Will this get me http://apps.beforedawn.com/index.jsp and http://diagnostics.beforedawn.com/index.jsp? Or would I have to put a rewrite in also? So that it would redirect any request to http://apps.beforedawn.com/apps/index.jsp Because I assume that the JKMount must correspond to the directory in the webapps directory. I am so confused on the way that mod_jk works! -john On 1/13/05 4:11 PM, Hassan Schroeder [EMAIL PROTECTED] wrote: John Martyniak wrote: The server currently only has one IP address and several virtual hosts. For example on this box I would to do the following: Web Server: Serves http://www.beforedawn.com Tomcat Server: http://apps.beforedawn.com/index.jsp http://diagnostics.beforedawn.com/index.jsp Is this possible? Yeah, but with only one IP you'll have to use mod_jk or mod_proxy. I'd say adding an IP address would be the easier setup :-) FWIW, this is how I run my dev box -- a couple of IP addresses for different versions of Tomcat and one for Apache (for the occasional PHP job). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using DNS name instead of port number
Thanks for the help. I will try and get the mod_jk working. I think that will give me the most flexibility for the future. -John On 1/13/05 5:53 PM, Hassan Schroeder [EMAIL PROTECTED] wrote: John Martyniak wrote: Unfortunately this is for one of my external boxes (read have to pay ungodly sums of money to get another block of IP addresses). Well, you only need one, eh? :-) So if I set this up using mod_jk then I will have to do the following It's been a long time since I used Apache in front of Tomcat, but that generally looked OK. Try it. You certainly won't need to use mod_rewrite, though. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Benefit of multiple workers?
I am preparing to set up my first production Tomcat using mod_jk. So what is the benefit of multiple workers? I can see that you can specify one worker per host, so the advantage would be that you could have one Webserver drive several app servers. I also read on this list, that you could use mod_jk2 to do load balancing. (is the same true for mod_jk 1.2.x?) Are these the only benefits? Or am I completely missing the point? -John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
