Re: JSP setup problems on XP Pro

From: Henry (greenclay_at_optonline.net)
Date: 10/12/03 

Date: Sun, 12 Oct 2003 02:48:41 GMT

I found the problem. I made one mistake, and the system just plain didn't
like something else. In the jakarta-tomcat-4.1.27\bin\catalina.bat I had
set the JAVA_HOME variable, which is not necessary. I think this was, for
me, a holdover from earlier versions of Tomcat, such as 3.2 and 3.3.

I hadn't mentioned earlier that no instance of Tomcat actually ran- which
was why I couldn't even point to the default Tomcat page at
http://localhost:8080/.

The last part of the puzzle was the port number. As soon as I changed it to
7080 instead of 8080, the default page loaded in a blink of an eye.
Changing back to 8080 again brings up the password/login dialog.

I'm also running Oracle 9i, which installs JServ (optionally). I was just
beginning to suspect something funny due to JServ.

Maybe it was IIS after all. I'm not sure if I would have considered the
port number so soon. I even have some documentation that recommends
changing the default port as a normal course of operation; see
http://www.moreservlets.com/Using-Tomcat-4.html for the reference.

In any case, I've got things running. Thanks for your help!

Henry

"PerfectDayToChaseTornados" <pdtct@emailaddress.invalid> wrote in message
news:5APhb.690$9O3.409@news-binary.blueyonder.co.uk...
>
> "Henry" <greenclay@optonline.net> wrote in message
> news:ECHhb.49236$Ri4.19222287@news4.srv.hcvlny.cv.net...
> | Nope- it looks as if the dfault IIS Web site is on port 80. I've found
> that
> | IE and XP want me to enter the default JSP address
> | as https://localhost:8080/ but even then, although I no longer get the
> | password screen, I get an error page that says the page cannot be found.
> |
> | This is making me a bit nuts. I had no idea that it would be so much
more
> | difficult to set it up under XP Pro than Win2K.
> |
> |
> | Henry
> |
>
> Henry, I have Tomcat running on XP pro with no problems at all. My guess
> would still be that the problem lies with running IIS as well. Have you
> tried turning IIS off & running it then?
> --
> -P
> "Sometimes I feel so goddam trapped by everything that I know"
>
>

Relevant Pages

  • Re: SPN problems?
    ... Why use port 8080? ... Just run the ISAPI filter and have tomcat service ... specific extensions all managed through IIS. ...
    (microsoft.public.windows.server.active_directory)
  • JspISAPI - Run Jsp Through IIS with SSL and NTLM
    ... IIS to tomcat webserver running on same machine. ... Disadvantages of running Tomcat/JRun on 8080 port: ... Setting up SSL on Tomcat is very difficult, ... You can block ports other then 80 on your web server, ...
    (microsoft.public.inetserver.iis.security)
  • Re: How to configure jakarta-tomcat-connectors-jk2-win32-IIS?
    ... Now I have on a same server IIS and Tomcat, both listening on port 80 (or to be specific, IIS forwards requests of special folders to Tomcat and Tomcat replys throw IIS to the client. ... So this solution makes it possible not to alter our firewall configuration and to use servlets and jps! ...
    (comp.lang.java.programmer)
  • Re: How to configure jakarta-tomcat-connectors-jk2-win32-IIS?
    ... Mika Myllyvirta wrote: ... I have installed Tomcat 5.5.12. ... > servlets and applets communicate fine throw port 8080. ... IIS, you have to change the port from 80 to something else. ...
    (comp.lang.java.programmer)
  • Re: Cantt download "exe" file because of IIS version
    ... with IIS and can completely alter IIS behavior in arbitrary manners, ... cut out the EXE download and just standardize the installation using your ... As far as I can tell, we are only running Tomcat as an ISAPI application. ...
    (microsoft.public.inetserver.iis)