HTTP Status 503 - Servlet jsp is currently unavailable

Hello everyone,
I'm having something strange happen when I access my tomcat instance via assigned ip. If you go to http://24.95.93.109/bbs you will see the error that I'm getting. If I access the same link only replacing the ip with localhost it works fine. Has anyone seen this before. I have had this tomcat instance running for over a year now with no problems. My power went out this morning for a couple of hours but I double checked my ip to make sure it didn't get released. It's the same ip I was using before, so nothing should of changed. I have looked at my log files and I see no errors or exceptions. Could my ISP implemented something to prevent me from hosting? I've been doing it for 3 years now, so maybe they finally caught on. Any help would be greatly appreciated since I am out of options now. Yes I know I could probably just install Tomcat 5, but it would be a pretty big pain migrating all of my 'stuff' from Tomcat 4.1 to Tomcat 5. You can also ping this ip number successfully, but tomcat is not serving up pages. I looked up the 503 error and it said something about the server possible being temporarily overloaded, which I doubt is the case.
Thanks in advance for your help,
Ryan

Mysterious - The fact that you are getting this from Tomcat shows that at least Tomcat is running so I don't think your ISP is doing anything.
The "Unavailable" sounds like your servlet has thrown a "UnavailableException" - you might look at the JavaDocs for that exception.
You don't have to go to Tomcat 5 - in fact, I tried it and went to 4.1.30 due to odd behavior with a security policy.
Please let us know if you figure it out.
Bill

Thanks for your post Bill. The only other possible thing I can think that I did was creating webapps by hand. Basically I just wanted to host some static information so I created a folder under my webapps directory. I noticed that if I did not have at least the WEB-INF and web.xml in the webapps directory, Tomcat freaks out. So I disregarded the webapps that I created by hand. I did not modify the server.xml or web.xml that is found under the CATALINE_HOME/conf directory. Besides, I'm not sure if creating webapps by hand is an issue. I think the issue is how Tomcat is resolving my ip number since all of my webapps work fine when going thru http://localhost.
I'm confused

Ryan

Hmmm. Something is up. I can't even VNC into my computer. I think there are IP complications. Maybe I'll try reseting my cable router when I get home tonight. That's got to be it.

Tomcat needs to find WEB-INF and at least a minimum web.xml or it will not consider a directory under webapps to be a real web application. However, I would expect that to result in a 404 not found rather than an unavailable.
Bill

Hello Bill,
I resolved my issue. It must of been the way my router was holding my ip. I ended up powering everything down for the night and powering back up. Everything works fine. So what have some of your issues been with Tomcat 5? I have heard a few people complaining about it. Tomcat 5 is suppose to contain a lot more components other than just Tomcat. I think I'll stick with my Tomcat 4.2 install.
Thanks for your help,
Ryan