DSIMPAIRED, I just wanted to make a comment on your resolution for this problem.
In that TID, one of the things that it mentions is that Tomcat needs to resolve LOCALHOST to work properly. Unfortunately, that's all it says and doesn't go into much more detail. You have to understand what this means and how to check for it's functionality.
But what this means is that you should be able to run 'PING LOCALHOST' from your server console, and it will ping your localhost address 127.0.0.1 successfully. If it can't do this simple test, Tomcat will fail.
I'm afraid that your tomcat dir is not what fixed the problem. When you said that you copied a HOSTS file from another server and it fixed it, I know exactly where it went bad.
I have seen in many cases, the LOCALHOST entry in the ETC\HOSTS file gets deleted or the IP ADDRESS (127.0.0.1) gets removed from the file. This causes TOMCAT to fail the LOCALHOST Lookup. I don't know when or why this entry gets deleted, but I've seen it on about 10 different servers since NetWare 6.5 was released. I've learned that one of the first things to do after installing it is to edit the hosts files and make sure the LOCALHOST entry is correct.
I'm betting that this is exactly what happened to your hosts file. WHen you put a one from another server, it had a good LOCALHOST line and therefore allowed Tomcat to load.
In the future, if you have problems getting tomcat to load, the first thing to check is that you have a valid HOSTS file. Really, in simplest form, you need two lines:
127.0.0.1 LOCALHOST LOOPBACK (or similar)
x.x.x.x SERVERNAME SERVERNAME.DOMAIN.COM
I feel bad that you spent 10 hours on this problem with Novell support. It's really a 5 minute fix. I hope you didn't pay too much for your Gold partners 'help'. I was going to elaborate when I initially replied but was heading out of town and didn't have time to say more than I did.
Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting