No, that isn't what I said. What I said is that you can't have Apache on port 8080 and Tomcat on port 8080. When you specify "VirtualHost some_ip:8080" to Apache, you are telling Apache to "listen" on that port. If you tell Apache to listen on that port, you can't tell Tomcat to listen on that port. System Administration 101.
You can certainly have a meta-refresh in an HTML page that redirects to a URL on a non-standard (non 80) port. However, you have to make sure that ONLY ONE software service is listening on that port! You just have to think things through, or if you have done this, work on explaining it to us (or anyone trying to help you) better. It's really just that simple. If your app is all servlet/Tomcat, then don't even deal with Apache. Tell Tomcat to listen on port 80 and be done with it. I'm not tooting my own horn, but I've gotten emails from all over the world telling me my HOWTOs on using Apache + mod_jk + Tomcat are quite good. I don't know if you are using Redhat or not, but if you are, check them out: http://www.johnturner.com/howto There are other HOWTOs for Windows and other environments that are also done quite well. I'm not saying you have to use Apache and mod_jk, I am just pointing out that if you WANT to use them, there are plenty of concise documents available to help you use them. I'll repeat myself...don't just wing it and jump into something...think it through. If your site is down, getting it up is paramount, and the fastest way to do that is to do it the simplest way and deal with adding bells and whistles later. Also, I wanted to add that putting Apache into the mix will DO NOTHING to resolve a servlet error you're getting from Tomcat and your Turbine app. If anything, putting Apache and mod_jk into the mix will make it HARDER to diagnose the servlet error you are getting. Put Tomcat on port 80 and be done with it. John > -----Original Message----- > From: David Wynter [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 03, 2002 2:14 PM > To: Tomcat Users List > Subject: RE: problems with paths using mod_jk 1.2 > > > I think best approach is to install Apache 2.0.42 as I had before the > corrupt filesystem where it all worked using the redirect with the > configuration I had without the Turbine error. I don't find > the Apache HowTo > on mod_jk very good, the standard mod_jk.conf you get when > you install has > Alias and Directory used in contexts that are not explained > in the HowTos. > Also these are not explained in isolation anyway. Possibly > this is only a > small part of my problem, but rather than try to understand > mod_jk I will be > better to build what know worked. I thought that I could > change the URL so > that it inserted the 8080 port part for that first URL hit using a > VirtualHost or Alias , which I gather from John response I cannot do. > > Thanks > > David > > -----Original Message----- > From: Michael Schulz [mailto:[EMAIL PROTECTED]] > Sent: 03 October 2002 18:54 > To: Tomcat Users List > Subject: RE: problems with paths using mod_jk 1.2 > > > Dave, > > I have to agree with John. I spent a great deal of time > helping on that > debacle as well...it is really sad to hear that you lost > everything as a > result of a corrupt file system...(:<) > > You have to know what you want to achieve before I would be > willing to lend > more assistance. How will you get there if you don't know > where you are > going? > > Apache...Tomcat...port 80...port 8080...meta-redirects...body onload > handlers...this is way more complex than it needs to be. > > I think John's idea of running tomcat as root and changing the http > connector listen port from 8080 to 80 is the simplest idea. > Why you would > use apache just to redirect from port 80 to 8080 is beyond me. Your > situation is exactly what Craig McClanahan was referring to > recently when he > made a valid case for using tomcat in a standalone environment. > > -Mike Schulz > > > -----Original Message----- > From: Turner, John [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 03, 2002 12:43 PM > To: 'Tomcat Users List' > Subject: RE: problems with paths using mod_jk 1.2 > > > > Whoa, I think you've got some things mixed up. > > If you want to use mod_jk, then requests NEVER go to 8080. > That's the whole > point of a connector. It connects Apache to Tomcat so that > requests are > served on port 80, not port 8080. > > I hesitate to get involved, because we went around and around > in circles the > last time you had a problem, so I will try and sum things up > as clearly as I > can: > > - if you are getting some error message from a Turbine > servlet, then fix > that error...don't go grabbing at straws > > - if you want your app served on port 8080, don't use Apache > at all...use > Tomcat in stand-alone mode > > - if you want your app served on port 80, and don't mind > running Tomcat as > root (some people do mind this) then change server.xml to > listen on port 80 > and be done with it > > - if you want your app served on port 80 with Apache, then > setup Apache with > mod_jk. There are NUMEROUS docs on this available, most of > them fairly > good, including the docs from the Tomcat site. > > - if you use Apache + mod_jk + Tomcat you DON'T need a > refresh in index.html > to redirect to 8080...that just makes Apache and mod_jk completely > irrelevant > > - you didn't post your server.xml in any case, but my guess > is that whatever > you are trying to do (I'm not exactly sure why you are > following the path > you are following) isn't working because your hostnames look pretty > goofy...you're telling Apache to listen on port 8080 > (VirtualHost IP:8080) > but then you want to run Tomcat on port 8080, but then you > want to serve > content on port 80 with a redirect to 8080 etc. etc. etc. > etc. Too crazy to > even begin sorting it out, to be honest. > > My advice: Either 1) get Apache working on port 80 serving a > single static > page, then post back here and explain EXACTLY where you want > to go from > there so that people can help, or 2) stop trying to use > Apache, use Tomcat > in stand-alone mode and post back here and explain EXACTLY > what the error > message that you get from your Turbine servlet is. > > I don't mean to sound critical, but you've really got things > munged up. I > know you are desperate, I know your site is down, but you > aren't making it > any better. Slow down, keep it simple, and take things one > step at a time. > Follow any of the Apache + mod_jk + Tomcat HOWTOs > available...none of them > say anything about setting things up the way you've got them > set up. Don't > wing it, you'll only spin your wheels as a result. > > John > > > > -----Original Message----- > > From: David Wynter [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, October 03, 2002 12:17 PM > > To: [EMAIL PROTECTED] > > Subject: problems with paths using mod_jk 1.2 > > > > > > Hi, > > > > I had been redirecting from Apache 2.0.42 index page to > Tomcat 4.1.12 > > successfully. Then I had a corrupt filesystem and have had to > > do a complete > > installation. This time I am using Apache 1.3.23 with Tomcat > > 4.1.12 and for > > some reason my Turbine based servlet did not like th > > eredicrect and had an > > 'Infinite Redited exception'. So I am forced to get mod_jk working. > > > > What I am trying to achieve is have people who hit my > > 'www.roamware.com' URL > > be directed to 'www.roamware.com:8080/rwsite/servlet/template' > > > > I downloaded the binaries for mod_jk 1.2 and installed them > > successfully. > > > > I have my config files below. I followed an example given by > > a fellow Turbine > > user, but I get a connection refused error. > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
