Tomcat broken link

[jd wong]

Hi everyone,

I'm trying to run a pre-packaged jsp website. After running the build script and clicking on the newly deployed web application link in the manager application. I'm presented with a "broken link" error by my browser. This isn't the tomcat 404 error.

I'm very new to tomcat and was wondering what the problem could be and how to troubleshoot this.

Relevant tomcat log entries:

Aug 29, 2011 10:15:08 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive flybasemine.war

This is the only log entry when I deployed and tried to access the webapp

Any help would be greatly appreciated!

[Guy deLyonesse]

If it isn't the Tomcat error then it sounds like maybe Tomcat isn't even receiving the request. Check your server.xml file to see what ports Tomcat is listening on and make sure your request is on one of them.

[jd wong]

I think I have the right port:

Server.xml:

    <Connector port="8080" protocol="HTTP/1.1" 
               connectionTimeout="20000" 
               redirectPort="8443" />

I can access the manager app using <hostname>:8080 just fine too, maybe Tomcat isn't receiving the request in a different way.

Thanks!

[William Brogden]

I'm presented with a "broken link" error by my browser. This isn't the tomcat 404 error.

Be aware that if you have the misfortune to be using MSIE, it may be generating "friendly" error messages which conceal the error code.

Internet options -> advanced -> scroll down to the Show friendly HTTP error message check box and leave it unchecked.

Bill

[Bear Bibeault]

Or use a real browser.

[jd wong]

I turned off "Use a web service to help resolve navigation errors" in Chrome, but that doesn't work either, I get a blank page. If I mistype the URL ("begin.doz") I get the tomcat 404 page, is there a file where I can examine the targets of "begin.do"?

[Bear Bibeault]

If you are using Chrome there are extensive debugging tools built into it. Use those to find out what's going on.

[jd wong]

It doesn't work with Safari either, and accessing the URL with curl gives me an empty document. This looks like a Tomcat "routing" error

[Tim Holloway]

Actually, if your URLs are ending with ".do", chances are very good that the webapp is Struts-based and not simple JSPs.

However, you never did actually show what the URL that you're clicking on looks like. If the URL isn't targeting what you think it is, all other suggestions are pretty much moot.

[jd wong]

I'm not sure where to find that, I can't find struts.xml anywhere. Struts-config.xml has this though:

    <action path="/begin" type="org.intermine.web.struts.BeginAction">
      <forward name="begin" path="begin.page"/>
      <forward name="blockingError" path="/blockingError.jsp"/>
    </action>

The error that was causing the blank page was a problem with the java I fixed. Now I get a 503 error though. When I intentionally mistype the URL after the "localhost:8080/webapp/" I get the same error.

Anyone have an idea on what is causing this?

[William Brogden]

When I intentionally mistype the URL after the "localhost:8080/webapp/" I get the same error.

Exactly where is this error message displayed? Did Tomcat do a redirect to an error page - in which case the URL would change.


Bill

[jd wong]

Hi,

No, it was a plain old browser 503 page.

The error was in the underlying java program again. It's solved now, but thank you for your input everybody! Everything has been much appreciated!