taire de ce document, nous vous signalons qu'il est strictement interdit
de le diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: "Aditya Prasad" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Monday, March 12, 2007 8:15 PM
Subject: Re: T
for conflicting ports - see if another app is using the same port as
Tomcat. On my machine Oracle 10g HTML interface was using port 8080, so I
changed
Tomcat port to 9090.
-Check CATALINA_HOME path
-Rashmi
- Original Message ----
From: Aditya Prasad <[EMAIL PROTECTED]>
To: users@tom
I've set my JULI logging to FINE to figure out why I always get "The
requested resource (/) is not available." Unfortunately, the log
seems to indicate that the ROOT context was started up all right:
Mar 12, 2007 2:32:56 PM org.apache.catalina.startup.HostConfig deployDirectory
FINE: Deploying w
Hi All,
The recent "Tomcat shuts down thread" discussion reminds me of a
problem I had to work around but whose cause I never figured out:
It used to be that if I started any (non-daemon) threads from a
request thread, they wouldn't go away when shutdown.sh was invoked.
The JVM would stay up, as
I take it back. I didn't turn off Nagling (TCP_NODELAY) on the
client, so the whole request was sent in one packet. Everything works
now. Sorry!
On 12/27/06, Aditya Prasad <[EMAIL PROTECTED]> wrote:
Hi all,
I'm having a hard time setting the SO_TIMEOUT value for the socket o
Hi all,
I'm having a hard time setting the SO_TIMEOUT value for the socket on
my server (5.5). I want to prevent DOS attacks where a user sends one
byte at a time, separated by a second or so. I can set the overall
timeout, but I want finer-level control. I'm doing this:
But it doesn't seem
