Hi, Just one last update. Nothing changed related to DNS or firewall rules. Tomcat does not work via localhost either.
Kind regards and thank you all for the feedback. Piet On Mon, Aug 17, 2009 at 5:39 PM, David Smith <d...@cornell.edu> wrote: > Hmmm ... maybe retour.mycompany.com isn't resolving to the IP you think > it is. Is there anything in your tomcat logs that might imply the > request is actually getting there? To me this smells a lot like a > network issue (DNS not resolving, firewall rules, etc., ...). Can you > verify tomcat works on the machine itself via a localhost request? I'd > also like to see what the server.xml file looks like. I don't think its > the issue, but it'd be nice to elliminate it entirely. > > --David > > java piet wrote: > > Sorry David, > > > > The addresses and names are fakes for reasons of confidentiality. > > The addresses and names in my code have worked before though. > > > > Kind regards, > > > > Piet > > > > On Mon, Aug 17, 2009 at 2:42 PM, David Smith <d...@cornell.edu> wrote: > > > > > >> Are you replacing DNS names and IPs with fakes for the purposes of email > >> or are these real values? 192.168.x.x is unroutable and suggests the > >> time out is because your firewall or cable router aren't passing through > >> the requests from clients. > >> > >> --David > >> > >> java piet wrote: > >> > >>> Thank you for the feedback. > >>> > >>> Sorry for the incomplete information. > >>> The Apache http server is functioning as a reverse proxy. > >>> Multiple applications have to be accessed through the internet. > >>> > >>> Now, I have Tomcat listening on 8081. > >>> > >>> Going to retour.mycompany.com:8080 or retour.mycompany.com:8081 > >>> gives a network timeout. (The server at retour.mycompany.com is taking > >>> > >> too > >> > >>> long to respond.) > >>> > >>> On the other hand, when I use the ip address like > >>> http://192.168.210.143:8080/ > >>> I get the resource (/) not found error > >>> while http://192.168.210.143:8081/ gives a network timeout. > >>> > >>> Tomcat without the Apache http server service gives the same network > >>> > >> timeout > >> > >>> when accessed through 8081. > >>> > >>> Hope this gives a clearer picture. > >>> > >>> Kind regards. > >>> > >>> Piet > >>> > >>> > >>> On Sun, Aug 16, 2009 at 9:02 PM, Caldarale, Charles R < > >>> chuck.caldar...@unisys.com> wrote: > >>> > >>> > >>> > >>>>> From: java piet [mailto:javap...@gmail.com] > >>>>> Subject: Re: apache2.2 tomcat5.5.27 Windows 2008 virtual hosts > >>>>> > >>>>> The reason for the Apache http server is because I thought I > >>>>> need it to handle the virtual hosting. > >>>>> > >>>>> > >>>> No, Tomcat can handle that quite well: > >>>> http://tomcat.apache.org/tomcat-5.5-doc/virtual-hosting-howto.html > >>>> > >>>> > >>>> > >>>>> As for the port 80, something else is already using it on the server. > >>>>> > >>>>> > >>>> You may be able to use a different IP address and have Tomcat use port > >>>> > >> 80 > >> > >>>> with that. > >>>> > >>>> > >>>> > >>>>> First I will try to have Tomcat listen on 8081 and see where > >>>>> that gets me. > >>>>> > >>>>> > >>>> Your first step should really be to eliminate httpd; it will make > things > >>>> much simpler. > >>>> > >>>> - 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: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
