Tomcat serving the wrong app
I suspect this is a Tomcat configuration issue. I use Tomcat 4 as the servlet container for my Apache2 web server. Apache's DocumentRoot is $CATALINA_HOME/webapps. The application I want to serve over my LAN and the www is organized as follows: Let's call my domain www.my-domain.com for now. $CATALINA_HOME/webapps/nirvana -- main app $CATALINA_HOME/webapps/secure -- SSL virtual host When users try to visit the site via www.my-domain.com they are redirected to a Domain Search page because the name can not be resolved. However, over the LAN we get served the Tomcat Welcome page from $CATALINA_HOME/webapps/ROOT. In either of these two cases the user can only successfully navigate to the site by appending the app dir to the end of the URI like this: www.my-domain.com/nirvana. Ideally, I want www.my-domain.com to serve $CATALINA_HOME/webapps/nirvana The second option is to have www.my-domain.com redirected to www.my-domain.com/nirvana. Can anyone please advise? Thank CMDGet more from the Web. FREE MSN Explorer download : http://explorer.msn.com
Re: SSL and form-based login
From: [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: SSL and form-based login Date: Wed, 24 Nov 2004 01:11:11 -0600 On Tue, Nov 23, 2004 at 01:20:16PM -0800, footh wrote: However, if the original page is http and the login form is submitted with https then it works fine. That seems like an explicit constraint that tomcat enforces, but I can't find where in the authentication code it does that. Of course, encrypting other requests and not the login page is a pretty stupid thing to do. :) You kind of lost me here...sorry if I'm being dense. So you are saying the only way to have a link within an SSL page go to non-SSL is either to hardcode the entire URL in the link or have all the links flow through a page that forces a redirect to the requested URL with non-SSL? uh.. what you just said is true, but it wasn't the point I was making above. I was talking about the behavior of tomcat with respect to how and when it saves the original url when it needs to display the login form. For a new session, the first request the browser makes to a protected causes that url to be stored in the session, but that value isn't always available to subsequent requests if the protocol is different. Now that I think about it, most (if not all) of my non-SSL links are in include files. So, it is easy enough to just place the full link in there. What bugs me is I've seen other sites with relative links on SSL pages that go to the non-SSL version (even when you hover over the link and your browser claims it is going to https). Using full links will be a pain too for maintaining production and development environments. Ugh... as Carl Howells mentioned in a different message, this could be done with a filter. Or you could write a javascript function that runs when the body onload happens that goes and and rewrites the urls of all the links on the page. (or if you want to be evil, leaves the urls alone but sets onclick handlers that redirect the browser directly.) eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] You say some sites have links within their SSL pages that navigate to Non-SSL destinations. This can be accomplished by using the rewrite capabilities of some web servers. In my case I have used Apache's mod_rewrite to enforce those rules in the past. Let's say I have a page called registration.jsp under $CATALINA_HOME/webapps/myhost that I want to be SSL encrypted. One problem is that the user can bypass encryption by passing the URL http://www.myhost.com/registration.jsp. I need some way to force the user to use https for the registration.jsp page and others like it. Likewise, I want pages that don't require SSL to be rewritten as http://something/something.jsp. I can create Apache rewriting rules for either case. For a period of time I used Apache's mod_rewrite. The module compares the URL it receives to a list of wildcards that the admin defines in the rules section of the server's config file. In my case, any URL containing the word register, would be rewritten as https://something/register.jsp. So even if you had a relative page link like 'href=register.jsp', mod_rewrite would convert it to the https equiv before the webserver processed it. In a sense this URL rewritting had the same effect as redirection. Also look into the MVC design archictecture for your applications. That is the Model, View, Controller architecture. Many sites designate one or more JSPs as a controller only page. This controller doesn't display any output. It's only function is to receive requests from the other JSPs on your site and forward them on to their proper destinations utilizing jsp:forward tags. In this way all of the discision making can be centralized into one controller. This simplifies the functions of the other JSPs by removing decision making logic from them. So page links, submits, imagemaps, inputs, selects and the like are simply passing requests to the controller JSP. Consider the following links: href=control.jsp?operation=login href=control.jsp?operation=register The control.jsp file will receive the request and examine the parameter called operation. Embedded JSP scriptlettes will decide (usually via if..then..else logic) what to do next. Since operations like logging in and registering need to be secured, the JSP can use the HTTPResponse object to do a redirect to https://something/login.jsp or https://something/register.jsp. Just because your site uses a controller doesn't mean that the user has to obey the controller though. The user can still use URL manipulation to view any page on your site, thereby bypassing the controller. Thats why I recommend using mod_rewrite in conjunction with MVC. If an attempt is made to bypass your
Re: ssl certs
While Tomcat can be used as a web server, it is more commonly used as a servlet container behind a more robust web server like Apache. I use the Apache + Tomcat combination for my site development. My SSL is configured on Apace. Consequently, I never installed SSL on Tomcat. However, the server.xml setup doesn't look too complicated. It certainly should not be an obsticle to a reputable company that wants to do business on the web. In a climate of rampant internet fraud, I think the lack of such a facility on a so-called reputable site would send up red flags to most of your customers. You will certainly lose business because of this. - Original Message - From: Didier McGillis Sent: Tuesday, August 24, 2004 11:14 AM To: [EMAIL PROTECTED] Subject: ssl certs I have come to discover that there is a small problem with a web site I have recently gone to work for. Now let me disclaimer this thing. They dont take credit card but they do handle names and addresses and account login So while its not horrible to me it is still unexceptable. The site is all Java, tomcat is the app and web server, I have never dealt with Tomcat as a web server so is it easy to setup tomcat to handle ssl certs and https requests. Any thing I have to watch out for? thanks _ Take advantage of powerful junk e-mail filters built on patented Microsoft® SmartScreen Technology. http://join.msn.com/?pgmarket=en-capage=byoa/premxAPID=1994DI=1034SU=http://hotmail.com/encaHL=Market_MSNIS_Taglines Start enjoying all the benefits of MSN® Premium right now and get the first two months FREE*. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] more from the Web. FREE MSN Explorer download : http://explorer.msn.com
Re: virtual hosting
Do you have the URL (www.mycompany.com) defined by a DNS server? You need a DNS to
translate the URL to an IP address. If you are already on the net then two DNS
servers will be required. The primary DNS should be provided by your ISP and you can
manage your own secondary if you like for your internal network (local intranet).
Virtual Hosting is normally used when you are attempting to server multiple web sites
from a single web server. If this is not what you are trying to do then don't concern
yourself with virtual hosting.
In either case a DNS setup is required.
Osensei
[EMAIL PROTECTED]
- Original Message -
From: Charles Jordan
To: [EMAIL PROTECTED]
Sent: Tuesday, May 04, 2004 3:31 PM
Subject: virtual hosting
I have tomcat 4.1 and apache 2 working together using jk2, but I want to
be able to type in www.mycompany.com in the browser and have it run the
jsp in ${tomcat home}/webapps/mycompany
Do I need to enable virtual host in http.conf and server.xml?
Do I need to add anything to workers2.properties?
Any help would be appreciated.
Am I missing something
Charles (Allen) Jordan [EMAIL PROTECTED]
System Administrator(407)771-8919
Convergys
285 International Parkway,
Lake Mary, FL 32746-5007
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
What's happening to my beans?
My installation is Apache2+Tomcat4+mod_ssl. I am running a http main server along with a https virtual host on an aliased ip address. To track users I created a session bean which holds user info ( e-mail, login status ). Naturally this bean holds vital information as it allows links to the users transactions such as shopping cart transactions. The bean is accessible by both servers (same machine and application directory tree). The SSL enabled virtual host now serves my Login, Registration and Shopping Cart JSP's while the main server serves the non-secure pages. Before I implemented SSL the strategy of using a bean to track users was sound, but now it seems that the bean is not persistant between the main server and virtual host. My guess is that main server and the virtual host have their own version of the bean. Therefore, the bean in my virtual host is out of scope once I navigate back to page controlled by the main server. The result is that the main server is left unaware if the user has logged in or whether or not the user has a shopping cart containing items. Is there a better strategy for communicating information like this between the main server and the virtual host. I am reluctant to try using cookies. I've tried the java.sun.com JSP forum with no success. Maybe you guys can help even if this post is a little off subject for this forum.
Re: What's happening to my beans?
Thanks Yoav, I've figured as much. From my old C programming days I am well aware of scoping rules. Yet I am still at a loss of how to solve this particular problem. I'm not certain how to using a database would solve the problem and I'm not familiar with singleton. What is it and how can I use it. Thanks Charles - Original Message - From: Shapira, Yoavmailto:[EMAIL PROTECTED] To: Tomcat Users Listmailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 12:41 PM Subject: RE: What's happening to my beans? Hi, I think you can't have the same session for both SSL and non-SSL activity. You get different sessions, each with its own bean, hence the behavior you describe. Can you use a database? A share singleton? Yoav Shapira Millennium Research Informatics -Original Message- From: Charles Daniel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 1:37 PM To: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] Subject: What's happening to my beans? My installation is Apache2+Tomcat4+mod_ssl. I am running a http main server along with a https virtual host on an aliased ip address. To track users I created a session bean which holds user info ( e-mail, login status ). Naturally this bean holds vital information as it allows links to the users transactions such as shopping cart transactions. The bean is accessible by both servers (same machine and application directory tree). The SSL enabled virtual host now serves my Login, Registration and Shopping Cart JSP's while the main server serves the non- secure pages. Before I implemented SSL the strategy of using a bean to track users was sound, but now it seems that the bean is not persistant between the main server and virtual host. My guess is that main server and the virtual host have their own version of the bean. Therefore, the bean in my virtual host is out of scope once I navigate back to page controlled by the main server. The result is that the main server is left unaware if the user has logged in or whether or not the user has a shopping cart containing items. Is there a better strategy for communicating information like this between the main server and the virtual host. I am reluctant to try using cookies. I've tried the java.sun.com JSP forum with no success. Maybe you guys can help even if this post is a little off subject for this forum. This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]
Re: What's happening to my beans?
Thanks, I'll try google first to see what it's all about. Thanks Again, Charles - Original Message - From: Shapira, Yoavmailto:[EMAIL PROTECTED] To: Tomcat Users Listmailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 12:56 PM Subject: RE: What's happening to my beans? Hi, You can google for the exact definition of the singleton design pattern. In this case, you would write a singleton to hold all the beans, one per user, instead of putting them in the session object. Because there will be only one instance of this singleton in the JVM, it will be shared by the non-SSL and SSL hosts. Your JSP pages and servlets would get the user bean from this singleton instead of from the session. If you need specific code we'll be glad to help. Yoav Shapira Millennium Research Informatics -Original Message- From: Charles Daniel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 1:53 PM To: Tomcat Users List Subject: Re: What's happening to my beans? Thanks Yoav, I've figured as much. From my old C programming days I am well aware of scoping rules. Yet I am still at a loss of how to solve this particular problem. I'm not certain how to using a database would solve the problem and I'm not familiar with singleton. What is it and how can I use it. Thanks Charles - Original Message - From: Shapira, Yoavmailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED] To: Tomcat Users Listmailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 12:41 PM Subject: RE: What's happening to my beans? Hi, I think you can't have the same session for both SSL and non-SSL activity. You get different sessions, each with its own bean, hence the behavior you describe. Can you use a database? A share singleton? Yoav Shapira Millennium Research Informatics -Original Message- From: Charles Daniel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 1:37 PM To: [EMAIL PROTECTED]mailto:tomcatmailto:[EMAIL PROTECTED]mailto:tomcat- [EMAIL PROTECTED] Subject: What's happening to my beans? My installation is Apache2+Tomcat4+mod_ssl. I am running a http main server along with a https virtual host on an aliased ip address. To track users I created a session bean which holds user info ( e-mail, login status ). Naturally this bean holds vital information as it allows links to the users transactions such as shopping cart transactions. The bean is accessible by both servers (same machine and application directory tree). The SSL enabled virtual host now serves my Login, Registration and Shopping Cart JSP's while the main server serves the non- secure pages. Before I implemented SSL the strategy of using a bean to track users was sound, but now it seems that the bean is not persistant between the main server and virtual host. My guess is that main server and the virtual host have their own version of the bean. Therefore, the bean in my virtual host is out of scope once I navigate back to page controlled by the main server. The result is that the main server is left unaware if the user has logged in or whether or not the user has a shopping cart containing items. Is there a better strategy for communicating information like this between the main server and the virtual host. I am reluctant to try using cookies. I've tried the java.sun.com JSP forum with no success. Maybe you guys can help even if this post is a little off subject for this forum. This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: tomcat-user- [EMAIL PROTECTED]mailto:tomcat-usermailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: tomcat-user- [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify
Re: Re: done did not found a worker
Hi Dwayne, If I remember from my own experience then mod_jk binaries are only available for Solaris. Others have tried to use these and got the error that read something like ... encoding not little-endian. To avoid this, get the jk module from source or CSV that is appropriate for your operating system. You'll need to compile whatever version you need. Osensei - Original Message - From: Dwayne Ghantmailto:[EMAIL PROTECTED] To: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 9:17 AM Subject: Fwd: Re: done did not found a worker I have tried to go to http://jakarta.apache.org/site/binindex.cgihttp://jakarta.apache.org/site/binindex.cgi and download mod_jk 1.2 , it's not available. Does anybody know how I can get mod_jk1.2 ? David O'Brien wrote: If you are using mod_jk and NOT mod_jk2 then this file's content makes no difference in your configuration. You need to tell apache to use the workers.properties NOT the workers2.properties in your httpd.conf file -Dave At 11:58 AM 2/10/2004, you wrote: But Dave you didn't address this stuff below? I think this is where I'm having the most problems. ##= ##Other needed configuratoin(s) ##= ##define the shared memory file [shm] file=/usr/local/tomcat-4.1.24/work/jk2.shm file=1048576 ## Define the communication channel [channel.socket:localhost:8009] #tomcatId=localhost:8009 port=8009 host=127.0.0.1 #define the worker [balance_all_workers:localhost:8009] channel=channel.socket:localhost:8009 #Uri mapping [uri:saturn.temple.edu/examples/*] #worker=ajp13:localhost:8009 worker=balance_all_workers:localhost:8009 [uri:saturn.temple.edu/developers/*] #worker=ajp13:localhost:8009 worker=balance_all_workers:localhost:8009 [uri:saturn.temple.edu/product/*] #worker=ajp13:localhost:8010 worker=balance_all_workers:localhost:8010 [uri:saturn.temple.edu/uPortal/*] #worker=ajp13:localhost:8010 worker=balance_all_workers:localhost:8010 #[status:] #info=Status worker, displays runtime information channel=channel.socket:localhost:8009 #[uri:/status/*] #worker=status:localhost:8009 #group=status: David Rees wrote: Dwayne Ghant wrote, On 2/9/2004 7:02 PM: Dave, I have been having semular issues would it be impossible for to post the four files listed below: 1. http.conf 2. ssl.conf 3. server.xml 4. workers2.properties Here's a sample for setting up Apache. This will work on either Apache 2.0.X or Apache 1.3.X, and mod_jk 1.2.5. Any version of Tomcat will work, use the example connector config included with every default server.xml as it varies a little between Tomcat versions. httpd.conf # This only shows the portions relevant to mod_jk, you should stick the # lines somewhere in your config file. This config also works for # Apache 1.3.X as well as Apache 2.0.X. --- LoadModule jk_module modules/mod_jk.so JkWorkersFile path-to-apache-conf/tomcat_workers.properties JkLogFile path-to-apache-logs/mod_jk.log JkLogLevel error VirtualHost *:80 ServerName www.example.comhttp://www.example.com/ JkMount /*.jsp tomcat JkMount /servlet/* tomcat /VirtualHost --- path-to-apache-conf/tomcat_workers.properties --- worker.list=tomcat worker.tomcat.port=8007 worker.tomcat.host=localhost worker.tomcat.type=ajp13 --- That's it! -Dave aka the mod_jk expert NOT a mod_jk2 expert! - To unsubscribe, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] David G. O'Brien Web Services Coordinator / Systems Administrator NACCRRA The Nation's Network of Child Care Resource Referral 1319 F Street NW, Suite 500 Washington, DC 20004 (202) 393-5501 ext. 113 (202) 393-1109 fax - To unsubscribe, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] -- Dwayne A. Ghant Application Developer Temple University 215.204. [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]
Re: done did not found a worker
Nicholas: Give up trying to use Apache2 with mod_jk. After spending days on the message boards trying to solve this one, I was ultimately told by the so-called experts that I had a network configuration problem and that some process was likely to be either already using or blocking port 8009. Poppy-Cock! Boulder Dash! I decided to attempt installing JK2 on the same server just to see if it would work. Guess what? JK2 and Apache2 worked on my first attempt. So much for getting advice from the EXPERTS! JK2 is not recommended if you are in a production environment however. JK2 is too young and untested for production environments and exploitable bugs and stability problems may arise. If you are building a production system -or- you just insist on using mod_jk then revert back to Apache 1.x. w/ mod_jk. Otherwise you may never get your server working. That's just the opinion of one who has suffered long enough with the Apache2 mod_jk SNAFFU. IMHO that combo just doesn't work together inspite of what Apache says. And if anybody thinks I'm wrong then they had ample time to help me when I was posting help requests concerning this issue all over the www. As it stands few would touch it with a ten foot pole. And the few who did were wrong. Osensei [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] - Original Message - From: Nicholas Bernsteinmailto:[EMAIL PROTECTED] To: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] Sent: Monday, February 09, 2004 1:33 PM Subject: done did not found a worker
Re: done did not found a worker
David: Then let me congratulate you on your positive experience with this ughm ... software. You must have been very good in your past life. Honestly, I'm sure that there are some who have installed this uhm .. software successfully, but I tried everything I could think of and no cigar. Maybe there are certain versions of Linux that make mod_jk hiccup when combined with Apace2. Mine is SuSE Linux 8.0. I previously had mod_jk and Apache 1.x working on the same server. When I upgraded to Apache2 I started from scratch. All new binaries and tar files from both the Apache and Jakarta web sites. I used the auto config feature, so it wasn't like I configured something wrong in the .conf files. Tomcat generated it own config in the auto directory. When that failed manually edited all of my httpd.conf file with the same results. Oh and by the way let me refer you to Nicholas, who seems to be having the same problem as I did. Maybe an expert like yourself can help him. I'm no longer interested. Osensei - OUT - Original Message - From: David Reesmailto:[EMAIL PROTECTED] To: Tomcat Users Listmailto:[EMAIL PROTECTED] Sent: Monday, February 09, 2004 7:37 PM Subject: Re: done did not found a worker On Mon, February 9, 2004 at 4:41 pm, Charles Daniel wrote: Give up trying to use Apache2 with mod_jk. After spending days on the message boards trying to solve this one, I was ultimately told by the so-called experts that I had a network configuration problem and that some process was likely to be either already using or blocking port 8009. Hmm, I've had no problems at all using mod_jk with Apache2 on both various Linux and SGI Irix machines. I must be a so-called expert. ;-) -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]
Re: done did not found a worker
Dear Nicholas, I'll look at it when I get a chance, but be warned - I used the auto config feature when mine failed. To make a long story short, Tomcat automatically generates the config in it's own conf directory ($CATALINA_HOME/conf/auto) whenever I ran startup.sh. If Tomcats own auto config blows up then what chance does you human edited conf stand in the diabolical world of Apache2. When that failed I reinstalled everything and used an edited httpd.conf as you are doing now. I got the same results both ways. Osensei [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] - Original Message - From: Nicholas Bernsteinmailto:[EMAIL PROTECTED] To: Tomcat Users Listmailto:[EMAIL PROTECTED] Sent: Monday, February 09, 2004 8:26 PM Subject: Re: done did not found a worker
Apache+Tomcat error -101 cannot connect to tomcat
I get an error -101 when Apache attempts to get a *.jsp from Tomcat. Please Help! [EMAIL PROTECTED] SUSE Linux 8.0, Apache 2.048, Tomcat 4.1.29, mod_jk. Installation Instructions @ http://www.johnturner.com/howto/apache2-tomcat4127-jk-rh9-howto.html The http.conf is reverted to the original distribution version with appended by the include of the Tomcat autoconfig.conf file Include /usr/local/tomcat/conf/auto/mod_jk.config The server.xml file is edited as follows: Server port=8005 shutdown=SHUTDOWN debug=0 # !-- My Listener -- Listener className=org.apache.ajp.tomcat4.config.ApacheConfig modJk=/usr/local/apache2/modules/mod_jk.so / !-- End My Listener -- Coyote Connector, but AJP 13 fails as well so I've tried them both !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ Host container here. Host name=localhost debug=0 appBase=webapps unpackWARs=true autoDeploy=true # !-- My Listener (inside of host container) -- Listener className=org.apache.ajp.tomcat4.config.ApacheConfig append = true forwardAll=false modJk=/usr/local/apache2/modules/mod_jk.so / !-- End My Listener -- The workers.properties: worker.list=ajp13 worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 Error Log: [Thu Jan 29 14:44:33 2004] [jk_ajp_common.c (955)]: Error connecting to the Tomcat process. [Thu Jan 29 14:44:33 2004] [jk_ajp_common.c (1309)]: sending request to tomcat failed in send loop. err=1 [Thu Jan 29 14:44:33 2004] [jk_connect.c (188)]: Into jk_open_socket [Thu Jan 29 14:44:33 2004] [jk_connect.c (195)]: jk_open_socket, try to connect socket = 10 [Thu Jan 29 14:44:33 2004] [jk_connect.c (204)]: jk_open_socket, after connect ret = -1 [Thu Jan 29 14:44:33 2004] [jk_connect.c (233)]: jk_open_socket, connect() failed errno = 101 [Thu Jan 29 14:44:33 2004] [jk_ajp_common.c (676)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 101
