org.apache.jk.common.ChannelSocket processConnection
- - INFO: connection timeout reached
Can anyone explaine these (still coming after the update). this is the
config for the connector :
Connector className=org.apache.coyote.tomcat4.CoyoteConnector
port=8009 minProcessors=5 maxProcessors=275
messages
into the log(stderr.log):
- 12.10.2005 09:50:53 org.apache.jk.common.ChannelSocket
processConnection - INFO: connection timeout reached
Can anyone explaine these (still coming after the update). this is
the config for the connector :
Connector className=org.apache.coyote.tomcat4
of these:
07.10.2005 17:47:15 org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
07.10.2005 17:47:17 org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket processConnection
INFO
[EMAIL PROTECTED]
Received: 10/7/2005 5:20 PM
To: Tomcat Users List tomcat-user@jakarta.apache.org
Subject: Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached
On Thu, Oct 06, 2005 at 06:53:36AM -0700, Rick wrote:
Jean-Marc,
Actually, without the connectionTimeout set, jk seems
.
-Original Message-
From: Marcus Franke [mailto:[EMAIL PROTECTED]
Sent: 07 October 2005 17:22
To: Tomcat Users List
Subject: Re: [5.5.9] Excessive jk INFO log msgs connection timeout
reached
On Thu, Oct 06, 2005 at 06:53:36AM -0700, Rick wrote:
Jean-Marc,
Actually, without
Crossley [EMAIL PROTECTED]
Received: 10/7/2005 5:23 PM
To: Tomcat Users List tomcat-user@jakarta.apache.org
Subject: RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached
Hi,
looks like jk is using commons logging, you'll have better success using a
log4j or commons-logging properties
On Thu, Oct 06, 2005 at 09:40:38AM -0700, Rick wrote:
Thanks Jean-Marc,
After checking over my workers.properties, orginally configured by someone
else, it appears to be missing some of the connection timeout handling
properties you have listed in yours. I'm guessing this is the root of my
[EMAIL PROTECTED]
Received: 10/7/2005 5:39 PM
To: Tomcat Users List tomcat-user@jakarta.apache.org
Subject: Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached
On Thu, Oct 06, 2005 at 09:40:38AM -0700, Rick wrote:
Thanks Jean-Marc,
After checking over my workers.properties
there
is an error level setting. check out the jk docs.
Hello Allistair,
Ok, did not understand a word :)
Seems to be too late.
I now changed the debug value in the Connector now step by step down to Zero.
But no changes, the catalina.out file still fills with those timeout Infos
[EMAIL PROTECTED]
Received: 10/7/2005 6:05 PM
To: Tomcat Users List tomcat-user@jakarta.apache.org
Subject: Re: [5.5.9] Excessive jk INFO log msgs connection timeout reached
On Fri, Oct 07, 2005 at 05:24:27PM +0100, Allistair Crossley wrote:
Hi,
looks like jk is using commons logging
it quick?
'org.apache.jk.common.ChannelSocket', the line reads...
log.info( connection timeout reached);
Should it not instead read...
if(log.isInfoEnabled()) log.info( connection timeout reached);
-Rick
-Original Message-
From: Marcus Franke [mailto:[EMAIL PROTECTED
PROTECTED]
Received: 10/7/2005 6:35 PM
To: 'Tomcat Users List' tomcat-user@jakarta.apache.org
Subject: RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached
Hi Marcus,
About that log entry that doesn't seem to be caught by the default
java.util.logging, I was wondering if it's a bug
I got rid of this message when I realized that my AJP connector's
configuration (in server.xml) had a connectionTimeout set.
Try setting it bigger or simply removing it, which will default
to 'no timeout'.
Cheers,
Jean-Marc
-Original Message-
From: Rick [mailto:[EMAIL PROTECTED
jk INFO log msgs connection timeout
reached
Subject: RE: [5.5.9] Excessive jk INFO log msgs connection timeout reached
I got rid of this message when I realized that my AJP connector's
configuration (in server.xml) had a connectionTimeout set.
Try setting it bigger or simply removing it, which
entries.
I don't know, I'm just guessing because my system is not in production
yet, but if I set my Tomcat connector to 'no timeout' and my Apache
worker to socket_timeout=30 secs, wouldn't the sockets be recycled on both
ends
anyway when not active for 30 secs?
My Apache workers.properties looks like
Thanks Jean-Marc,
After checking over my workers.properties, orginally configured by someone
else, it appears to be missing some of the connection timeout handling
properties you have listed in yours. I'm guessing this is the root of my
issue. I'll give them a try.
Thanks again,
Rick
Hello list,
I have a problem with a tomcat 5.0.28 installation connected to IIS 6.0
(Windows 2003 server) with isapi_redirect.dll
Everything is working well, except for the session timeout.
The timeout is set to 60 minutes in the context's web.xml file
(session-timeout60/session-timeout) which
Anyone know the proper way to handle these messages? I get piles of them in
catalina.out
Oct 5, 2005 3:00:23 PM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
Tried adding the following line to the default
catalina_home/common
On 15/09/05, Leon Rosenberg [EMAIL PROTECTED] wrote:
Hi,
I don't know if this fits, but could it be, that your problem is
related to the tomcat session synchronization bug?
http://issues.apache.org/bugzilla/show_bug.cgi?id=36541
That does look like a potential issue. However, I think I
On 14/09/05, James Shaw [EMAIL PROTECTED] wrote:
I have two issues relating to sessions:
1) Sessions seem to be expired too soon. This happens very
infrequently for me (perhaps 1 in 1000 requests). I'm adding some
HttpSessionListeners and HttpSessionAttributeListeners to attempt to
locate
I have two issues relating to sessions:
1) Sessions seem to be expired too soon. This happens very
infrequently for me (perhaps 1 in 1000 requests). I'm adding some
HttpSessionListeners and HttpSessionAttributeListeners to attempt to
locate this problem, but have little to go on at the moment.
Env:
Linux:
Apache 1.3.33
Tomcat 4.1.30
MySql 4.1.10
There is a page member_list.jsp which displays a grid of members.
After 20/75 members are displayed, html is displayed:
a class=CobaltDataLink
href=MemberMaint.jsp?fMemberID=83s_fStatusName=Activetype=notLoggedr
et_link=%2FtmJ%2Fme
This page
Hello,
within my web application i defined a session timeout of 30 minutes.
But some sessions strangly survive this timeout and keep being valid
until an explicit call to invalidate().
I already implemented a HttpSessionListener to keep track of session
creation, destruction, lastAccessedTime
of servlets and such)?
: Until we can solve the problem,
: can anyone suggest anything that can timeout these out-of-control threads?
: Session timeouts timeout on inactivity, correct? I don't know if that
: will work in this case...but I might try it anyway.
Let's take a step back: specifically, what
We've got a servlet problem that we're trying to track down. The problem
causes one of the threads to spin. Until we can solve the problem,
can anyone suggest anything that can timeout these out-of-control threads?
Session timeouts timeout on inactivity, correct? I don't know
How do you set the session timeout in tomcat so that the session only
timeouts when the browser is closed?
This e mail is from DLA Piper Rudnick Gray Cary UK LLP.
The contents of this email and any attachments are confidential to the intended
recipient. They may not be disclosed to or used
From: Harland, David [mailto:[EMAIL PROTECTED]
How do you set the session timeout in tomcat so that the session only
timeouts when the browser is closed?
You don't. There is no way in any Web architecture of reliably
detecting whether a browser has closed, or whether it has merely
On 6/7/05, Harland, David [EMAIL PROTECTED] wrote:
How do you set the session timeout in tomcat so that the session only
timeouts when the browser is closed?
Possible solution may be to refresh the page frequently and set a
short interval for session time out. You might use a frame
of
this listener. But the sessionDestroyed-method is never called and the
session is NEVER killed. I have also a
session-config
session-timeout2/session-timeout
/session-config
in my web.xml but this doesn't help ether.
What am I doing wrong? Why doesn't tomcat
Are you creating a basic authentication or form based authentication ?
-Original Message-
From: Hendrik Neumann [mailto:[EMAIL PROTECTED]
Sent: 18 May 2005 14:11
To: tomcat-user@jakarta.apache.org
Subject: Tomcat totally ignores my timeout-settings
Hi everybody,
I have the following
without tomcat or the web.xml-file or any offical auth-method.
I'm quite sure that the timeout-problems are independent from my login-method.
I have a personal testing-server which has just been used by myself in the
last 8 hours and till now the tomcat-manager tells me, that there are 35
okay, now I've created a new, small web-project with a very simple web.xml
just containing the HttpSessionListener, a 2-minute-session-timeout and very
small index.jsp and it works without any problems! but my original
jsf-web-app still doesn not release the sessions (I already have 40 sessions
Hi,
I have an app that uploads user files in a temporary folder. I want to
delete them when the session ends. I know I could solve this with a
cron-job, but I'm looking for a way to solve it with Tomcat.
Does anyone have an idea how to solve it?
Thx for your help in advance,
cheers,
Robert
Write a SessionListener... it has two methods, one that fires when a
session is created, one when it is destroyed. That should do the trick
for you. That's not a Tomcat-specific solution either, so it should be
rather portable should you ever need to move to another app server.
--
Frank W.
that sounds very useful, not something I've done before -- can I ask a
few questions -
1) how does one bind that into Tomcat -- declare a session listener in
(I presume) web.xml?
2) as I'm using Spring Framework, is this still relevant (or is there a
spring-specific way of binding in a
Let's see...
(1) You are correct, it's nothing more than an entry in web.xml.
Remember, this isn't a Tomcat-specific thing, it's a J2EE thing (servlet
spec specifically I think), so it's YOUR APP'S web.xml. The entry is
simply:
listener
I have a some java beans in the session scope which are instantiated by
one page by get their properties updated by several other pages.
When the session expires Tomcat (correctly) throws an error when it tries
to update the no longer existing bean. My question is thus: how do I
detect its
Hello,
I wonder if Tomcat will stop a servlet execution thread after a certain
timeout (adjustable?)?
Michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi every,
from web.xml:
session-config
session-timeout30/session-timeout
/session-config
Does the session-timeout refer to an idle session or an active session ?
Thk in advance
Cedric
-
To unsubscribe, e-mail: [EMAIL
If more than idle for 30 minutes.
-Tim
Cédric Buschini wrote:
Hi every,
from web.xml:
session-config
session-timeout30/session-timeout
/session-config
Does the session-timeout refer to an idle session or an active session
Think of the timeout as a 30 minute countdown timer. Every time there is any
session activity, like a page request, the timers starts over. If the timer
ever gets to 0, then the session times out.
Jay
Vertical Technology Group
http://www.vtgroup.com/
-Original Message-
From: Tim Funk
thank you !!
Jay Burgess wrote:
Think of the timeout as a 30 minute countdown timer. Every time there is any
session activity, like a page request, the timers starts over. If the timer
ever gets to 0, then the session times out.
Jay
Vertical Technology Group
http://www.vtgroup.com/
-Original
After looking at the code, it looks like the SSO session doesn't go away
until all other sessions for the user have expired. So, as far as I can
tell, the SSO session doesn't have it's own session timeout as far as I can
tell.
Jon
- Original Message -
From: Jonathan Eric Miller [EMAIL
After looking at the code, it looks like the SSO session doesn't go away
until all other sessions for the user have expired. So, as far as I can
tell, the SSO session doesn't have it's own session timeout as far as I can
tell.
Jon
- Original Message -
From: Jonathan Eric Miller [EMAIL
On 4/14/05, Jonathan Eric Miller [EMAIL PROTECTED] wrote:
After looking at the code, it looks like the SSO session doesn't go away
until all other sessions for the user have expired. So, as far as I can
tell, the SSO session doesn't have it's own session timeout as far as I can
tell.
Indeed
is is presumably for
the global session.
Jon
- Original Message -
From: Peter Rossbach [EMAIL PROTECTED]
To: Tomcat Users List tomcat-user@jakarta.apache.org
Sent: Tuesday, April 12, 2005 10:56 PM
Subject: Re: Way to specify SingleSignOn session timeout?
Look inside conf/web.xml
!-- created sessions
Hey,
I have been looking all over for a way to run code on a session time out.
Basically, before a session times out, I need to perform some functionality on
the data in that session. Ive read about Session Manager and Session
Listeners, but I have not been able to find any examples of how
Java Server Pages, 3rd Edition, O'Reilly - great book. I can send you an
example later tonight.
- Original Message -
From: Chris Bender [EMAIL PROTECTED]
Date: Wednesday, April 13, 2005 10:26 am
Subject: Running code on session timeout
Hey,
I have been looking all over for a way
Is there a way to set the timeout on request processing threads? I'd
like to be able to say that If a request takes more than 60 seconds,
then kill it.
Bernard Durfee
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
I'm using the SingleSignOn valve with Tomcat 5.5.9. Does anyone know what
the default session timeout is set to? Is there a way to specify this
timeout?
I'm finding that sometimes my session will timeout within an application,
but, it doesn't redisplay the login page. I want to try to set
Look inside conf/web.xml
!-- created sessions by modifying the value
below. --
session-config
session-timeout30/session-timeout
/session-config
Peter
Jonathan Eric Miller schrieb:
I'm using the SingleSignOn valve with Tomcat 5.5.9. Does anyone know
what
Hi,
I need in some exceptionnal condition to disable the session timeout for
one request.
Is there some convenient way to do so?
My idea is to do this but I'm unsure :
In the exceptionnal servlet (at the beginning):
session.setAttribute(OLD_TIMEOUT, new
Integer(session.getMaxInactiveInterval
you can set timeout from Tomcat Admin = Connections.
--- David Causse [EMAIL PROTECTED] wrote:
Hi,
I need in some exceptionnal condition to disable the
session timeout for
one request.
Is there some convenient way to do so?
My idea is to do this but I'm unsure :
In the exceptionnal
It is not my problem. I need to change it for only one servlet.
Thanks.
fed fin wrote:
you can set timeout from Tomcat Admin = Connections.
--- David Causse [EMAIL PROTECTED] wrote:
Hi,
I need in some exceptionnal condition to disable the
session timeout for
one request.
Is there some
Hello!
How to edit session timeout? Tomcat's default value is 30mins...
30 minutes of inactivity then a session will expire... In my apps,
i think 30minutes is too long.. i want 5 minutes of inactivity before
session expires...
is it in server.xml? i only see connectionTimeout which is 2
From: Aris Javier [EMAIL PROTECTED]
How to edit session timeout? Tomcat's default value is 30mins...
Look in web.xml instead of server.xml. You can change it for the entire
container, or on a per-webapp basis, depending on which web.xml you edit.
(Works for Tomcat 4.1, I haven't moved to 5 yet
session timeout
From: Aris Javier [EMAIL PROTECTED]
How to edit session timeout? Tomcat's default value is 30mins...
Look in web.xml instead of server.xml. You can change it for the entire
container, or on a per-webapp basis, depending on which web.xml you
edit.
(Works for Tomcat 4.1, I haven't moved
From: Aris Javier [mailto:[EMAIL PROTECTED]
Subject: RE: Edit session timeout
I looked at my web.xml, and no sessionTimeout found there...
can you give me an example on how to write it down in web.xml?
Not sure what you meant by my web.xml, since, as Wendy noted, there's a
global one
session-config
session-timeout120/session-timeout
/session-config
Look, at the web.xml file inside the conf directory, the global web.xml
file that is. You can usually find this right above the mime-type
mapping definitions.
Drew.
On Sun, 2005-01-30 at 20:28, Aris Javier wrote
Thanks Drew!
I found it.. =)
can I also use this setting per web app? by editing web.xml per web app?
-Original Message-
From: Drew Jorgenson [mailto:[EMAIL PROTECTED]
Sent: Monday, January 31, 2005 12:41 PM
To: Tomcat Users List
Subject: RE: Edit session timeout
session-config
Yes.
Doug
- Original Message -
From: Aris Javier [EMAIL PROTECTED]
To: Tomcat Users List tomcat-user@jakarta.apache.org
Sent: Sunday, January 30, 2005 11:53 PM
Subject: RE: Edit session timeout
Thanks Drew!
I found it.. =)
can I also use this setting per web app? by editing web.xml per
Thanks Everybody!
=)
-Original Message-
From: Parsons Technical Services [mailto:[EMAIL PROTECTED]
Sent: Monday, January 31, 2005 12:56 PM
To: Tomcat Users List
Subject: Re: Edit session timeout
Yes.
Doug
- Original Message -
From: Aris Javier [EMAIL PROTECTED]
To: Tomcat
It looks like the timeout is occurring when the first response is being
read, so this changes the problem.
I'm receiving a 401 Unauthorized response with the following headers:
Server: Apache-Coyote/1.1
WWW-Authenticate: [...]
Content-Type: text/html;charset=utf-8
Content-Length: 952
Date: Thu
So this is getting stranger.
Just to preclude any error on my part, I did a simple loop that output
every character received from the response. The HTTP response status
line and headers come down fine, including the CRLF that separates the
headers from the body. And then---timeout after 15
. And then---timeout after 15 seconds.
But the strange part is that if I connect using Firefox, I can view the
entire response---an HTML document including the 401 status code. This
document length is---you guessed it---952 bytes long, just like the
Content-Length header says.
Why can't I read the body from
the body. And then---timeout after 15 seconds.
But the strange part is that if I connect using Firefox, I can view
the entire response---an HTML document including the 401 status code.
This document length is---you guessed it---952 bytes long, just like
the Content-Length header says.
Why can't
that
separates the headers from the body. And then---timeout after 15
seconds.
But the strange part is that if I connect using Firefox, I can view
the entire response---an HTML document including the 401 status code.
This document length is---you guessed it---952 bytes long, just like
the Content-Length
what in the world could be happening.
But you're wrong. ;)
I had already thrown out the BufferedInputStream to eliminate that. I
switched to straight sockets. I set up a simple loop that simply read
bytes until receiving a timeout. The timeout occurred after the CRLF
divider, even though
dumbfounded
wondering what in the world could be happening.
But you're wrong. ;)
I had already thrown out the BufferedInputStream to eliminate that. I
switched to straight sockets. I set up a simple loop that simply read
bytes until receiving a timeout. The timeout occurred after the CRLF
divider
Hi everybody,
Is it possible to configure the session timeout using the
org.apache.catalina.session.StandardManager Session Manager or am I forced
to use the Persistent Manager just for doing so?
(Tomcat v4.1)
Regards,
F
How about trying? Put this inside your web-app in web.xml
session-config
session-timeout10/session-timeout
/session-config
The number within the session-timeout element must be expressed in minutes.
Works for me with the StandardManager, in tomcat 5
Trond
Freddy Villalba A. wrote:
Hi everybody
Hi,
I'm using TC 5.0.28 running 3 WARs with SingleSignOn feature.
I also have code that modify the user's timeout for authenticated users only.
(Anonymous have 5 minutes and authenticated users have 1 hour). It has been
worked for a year without problems!
Recently I'm getting short (5
I've just upgraded to 4.1.31 and I'm getting
org.apache.jk.common.ChannelSocket processConnection INFO:
connection Timeout received messages at the console every
second or so. Everything seems to be working OK so do I need
to do anything about these messages? If this is normal
PROTECTED]
Sent: November 5, 2004 10:18 AM
To: Tomcat Users List
Subject: Re: Connection Timeout
Hi Phillip,
The request is for example a 10K image.
Regards
Andrew
On 05.11.2004, at 16:11, Phillip Qin wrote:
My guess is the request was serviced by Tomcat, and took that much
time.
What did your
... eh?
You mention controller. Are you using TC as-is, or are you using a
framework such as struts or JSF by any chance?
If you suspect that the problem is triggered by a closing session, why not
try shortening the session timeout to a shorter length and see if it crashes
quicker? In fact, it's
PROTECTED]
Date: Monday, November 8, 2004 4:19 pm
Subject: RE: session-timeout means tomcat restart
Sorry for not replying sooner, I've been busy for a few days.
Can you say more about the crashing? Any evidence from the logs?
A bit
difficult to be any more specific without more to go
mention controller. Are you using TC as-is, or are you using a
framework such as struts or JSF by any chance?
If you suspect that the problem is triggered by a closing session, why not
try shortening the session timeout to a shorter length and see if it crashes
quicker? In fact, it's worth
sorry but no. what about the other points.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday 08 November 2004 22:37
To: Tomcat Users List
Subject: Re: RE: session-timeout means tomcat restart
We had a 'hung, and won't work without a reboot
/.
On Tue, 9 Nov 2004 00:51:09 -, Steve Kirk
[EMAIL PROTECTED] wrote:
sorry but no. what about the other points.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday 08 November 2004 22:37
To: Tomcat Users List
Subject: Re: RE: session-timeout
Resending...anyone know???
-Original Message-
From: Dan Carwin
Sent: Friday, November 05, 2004 11:01 AM
To: [EMAIL PROTECTED]
Subject: Tomcat 5 - coyote/jk2 connector defaults - maxthreads, timeout?
what is the default maxThreads in tomcat 5 jk2/coyote connector? What is
the default
a timeout for this, as a time 10
seconds makes very little sense with our application?
Thanks in advance,
Andrew
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-Original Message-
From: Eric Wulff [mailto:[EMAIL PROTECTED]
Sent: Friday 05 November 2004 07:01
To: Tomcat Users List
Subject: session-timeout means tomcat restart
Hi, I'm experiencing 2 interesting problems that may be related to my
session timeout.
1. It seems
My guess is the request was serviced by Tomcat, and took that much time.
What did your request column tell? A huge request, file upload?
-Original Message-
From: Andrew Miehs [mailto:[EMAIL PROTECTED]
Sent: November 5, 2004 4:24 AM
To: Tomcat Users List
Subject: Connection Timeout
Dear
[mailto:[EMAIL PROTECTED]
Sent: November 5, 2004 4:24 AM
To: Tomcat Users List
Subject: Connection Timeout
Dear List,
In /manager/status, I occasionally see connections where the status is
'S' and the time column is huge! 1 ms.
Does this mean that the request is still being processed by tomcat
Byte recv and byte sent?
-Original Message-
From: Andrew Miehs [mailto:[EMAIL PROTECTED]
Sent: November 5, 2004 10:18 AM
To: Tomcat Users List
Subject: Re: Connection Timeout
Hi Phillip,
The request is for example a 10K image.
Regards
Andrew
On 05.11.2004, at 16:11, Phillip Qin
To: Tomcat Users List
Subject: Re: Connection Timeout
Hi Phillip,
The request is for example a 10K image.
Regards
Andrew
On 05.11.2004, at 16:11, Phillip Qin wrote:
My guess is the request was serviced by Tomcat, and took that much
time.
What did your request column tell? A huge request, file upload
what is the default maxThreads in tomcat 5 jk2/coyote connector?
What is the default serverTimeout ?
#channelSocket.serverTimeout=???
#channelSocket.maxThreads=???
(fwiw I'm referring to the version included in tc 5.0.28)
Thanks,
Dan
eliminate the crashing
problem.
I also am now taking advantage of a connection pool. However, as you
figured, that does not solve the crash problem.
Finally, I removed the session-configsession-timeout element from
myapp web.xml to test if this is the initiator of the problem. Let
you know what I
problem.
I also am now taking advantage of a connection pool. However, as you
figured, that does not solve the crash problem.
Finally, I removed the session-configsession-timeout element from
myapp web.xml to test if this is the initiator of the problem. Let
you know what I find. Still
Hi
I've just upgraded to 4.1.31 and I'm getting org.apache.jk.common.ChannelSocket
processConnection INFO: connection Timeout received messages at the console every
second or so. Everything seems to be working OK so do I need to do anything about
these messages? If this is normal behaviour
Hi, I'm experiencing 2 interesting problems that may be related to my
session timeout.
1. It seems that when my session times out I need to restart tomcat,
often just the application via reload in the manager, in order to gain
access to my db again. Could this be because I've been accessing
of the time, but
sometimes forwarding the request takes about 75 seconds. I found out that
this is the default socket timeout of FreeBSD. The problem is that I
configured mod-jk2 the way, that it has its own timeout for connecting (see
attached workers2.properties). But this value is not recognized
=1
# Example socket channel, override port and host.
[channel.socket:192.168.1.124:8009]
tomcatId=camenzind
timeout=1
# Example socket channel, override port and host.
[channel.socket:192.168.1.123:8009]
tomcatId=haller
timeout=1
# define the worker 1
[ajp13:192.168.1.124:8009]
channel
Hi,
How are you checking the time remaining for a session?
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Peter Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, September 20, 2004 12:24 AM
To: Tomcat Users List
Subject: session-timeout is out by factor of 100?
Hi
Research Informatics
-Original Message-
From: Peter Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, September 20, 2004 12:24 AM
To: Tomcat Users List
Subject: session-timeout is out by factor of 100?
Hi,
Is anyone successfully using the web.xml session timeout configuration
are you checking the time remaining for a session?
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Peter Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, September 20, 2004 12:24 AM
To: Tomcat Users List
Subject: session-timeout is out by factor
Hi,
Is anyone successfully using the web.xml session timeout configuration
with Tomcat 5.0.25? Testing seems to indicate that this setting is out
by a factor of 100 however using session.setMaxInactiveInterval seems to
yield the desired result.
E.g. Printing the time remaining (in ms
to the other server works fine after 3-5 Seconds. But
if the whole host goes down (Network cable plugged out, Host switched off) the
failover takes ~60 Seconds, because themod_jk tries to connect about 6-10
times with the tomcat and runs into a timeout every time. After that the
failover works
/TestServlet
I receive:
..
Completed 14000 requests
apr_poll: The timeout specified has expired (70007)
Total of 15861 requests completed
The jvm is defenitly not out of memory, (top says 50m of -Xmx170m are
used) no garbage collection is performed during the test. After some
minites of waitung
:[EMAIL PROTECTED]
Sent: Thursday, September 09, 2004 12:05 PM
To: [EMAIL PROTECTED]
Subject: unexpected timeout during benchmark
Hi,
I want to measure the performance of a Servlet that I wrote. To have a
number to compare with i wrote a servlet which does only a single
println
in its doget method
1 - 100 of 512 matches
Mail list logo
