One troubleshooting suggestion would be to confirm that
Java itself is working. Use java -version, and run some
basic HelloWorld program.
If Java isn't working, Tomcat won't stand a chance.
- Original Message
From: "w...@serensoft.com"
To: users@tomcat.apache.org
Sent: Friday, May
I'm not sure if it still behaves this way. But historically IE has ignored the
declared content-type and instead used the file extension. The work-around was
to add a bogus argument to the URL:
http://server/get-the-goodies.jsp?filetype=.zip
This way it "looks" like a .zip file to IE.
Also, w
>> But would it not be easier to catch the OOM exception and then
>> return a "sorry, server overloaded" page to the browser ?
> It's difficult to do that when the OOME may occur in Tomcat code,
> outside of control of the webapp.
Wow I had assumed I could always catch this type of exception.
>> From: Todd Hivnor [spambox_98...@yahoo.com]
>> I would like to proactively avoid running out of heap
>> space. I would like people get a "Server Too Busy"
>> message, _before_ the heap is actually exhausted.
>
>> I would rather serve 40 users w
I have a Java application running under Tomcat 6.0.18
on Ubuntu. This is using Sun's 1.6.0_07 JVM. I know
how to set the max heap space by setting -Xmx256m
in CATALINA_OPTS. But with a lot of sessions, I still
have the possibility of running out of heap space. My
application uses a lot of memo
