[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-developers] FW: Tomcat is easily broken...
- Subject: [cobalt-developers] FW: Tomcat is easily broken...
- From: "Peter Ball" <peter.ball@xxxxxxxxxxxx>
- Date: Sat Sep 1 11:14:05 2001
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
We have recently installed the Java pkg from Cobalt on one of our raq4i's
and a Java guru who's been checking it out came back with the following.
As we are not very knowledgeable in this area can any of our learned
colleagues on this list or someone from Cobalt comment on what he has said?
Like is it a bug or a feature, have we done something wrong, can it be
prevented etc.?
-----Original Message-----
From: xxxxxxxxxxx
Subject: Tomcat is easily broken...
Hi Guys,
Well I seemed to have managed to screw up Tomcat fairly easily. If you place
the following line of code inside of a jsp page, tomcat will screw up and
not talk to you again:
<% System.exit(0); %>
PLEASE DON'T DO THIS!
I tried restarting just Tomcat but this wouldn't work. I tried restarting
Apache. This has fixed Apache but not Tomcat, which is still stuffed. Jasper
(the compiler) is functioning, but communication between Apache & Tomcat is
partially broken. I have requested a reboot.
I'm surprised that the default security policies didn't prevent this. My
quick scan through it looks as though it should be OK. Anyway, I'll look
into geting a fix to the file:
/usr/java/jakarta-tomcat/conf/tomcat.policy.master