This is not with the Debian apt-get that I'm having trouble figuring out
where it's finding its webapp contexts.
It's with the downloaded-from-Apache one that I've got running (on port
7070, no HTTPS) on a CentOS 5 box, and that I haven't figured out how to
run as a service (but that's not the immediate problem).
It seems that the Tomcat server was apparently running fine for several
days (albeit unmonitored and without any firewall opening allowing it to
be reached from outside, up until yesterday afternoon), up until a few
hours ago. Then it started going down.
Yesterday afternoon, I put our webapp context on it, and changed the
port forwarding in the firewall, so that the outside access (and
therefore, the Site24x7 monitor on this particular server) pointed to
it, rather than to what it replaced.
And then I got a message from Site24x7 telling me that it had gone down.
After a brief inspection, I shut it down and restarted it.
Less than an hour later, the same story. And a third time.
The fourth time, I had my hands too full to go in and manually restart
it, and to my surprise, without my having restarted it, I got a message
from Site24x7 telling me it was back up.
And it bounced up and down a few times since then. I eventually shut it
down.
There's nothing in catalina.out between our webapp announcing that it
was running (9:14 AM), and the messages from my shutting it down (11:46 AM).
So far as I've been able to determine, when it's reported as down, it's
not accepting requests even from within the LAN.
Anybody ever seen anything like this before?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
