Re: connection timeout reached JK IsapiRedirect.dll

[Reynir Hubner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
 
ah sorry, I mean IIS 6 (the newest one).
- -reynir


Reynir Hubner wrote:

> Hi, I'm using tomcat 4.1.x and Coyote JK connector, with IIS 5. I
> just updated to isapi_redirect-1.2.14.dll.
>
> I did that because I've been getting alot of those error 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 :
>
>  port="8009" minProcessors="5" maxProcessors="275"
> enableLookups="false" redirectPort="8443" acceptCount="100"
> debug="0" connectionTimeout="1" useURIValidationHack="false"
> tomcatAuthentication="true"
>
> protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
>
> thanx, [EMAIL PROTECTED]
>

- -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFDTOFG19KgIQihNwgRAtBdAJ9Tzd03Xisk0cmCIzmXN3ijGICvKwCaA/Hw
ZmGsSQ7Sv2iijXswfVLhHV4=
=dnj5
-END PGP SIGNATURE-


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

connection timeout reached JK IsapiRedirect.dll

[Reynir Hubner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
 
Hi,
I'm using tomcat 4.1.x and Coyote JK connector, with IIS 5. I just
updated to isapi_redirect-1.2.14.dll.

I did that because I've been getting alot of those error 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 :



thanx,
[EMAIL PROTECTED]

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFDTN9K19KgIQihNwgRAlEpAJ9sNvVp9B5cVaOROkswt2A0oyZu7ACfVDCA
PE2yIFPgurN3CX0jPv2duHo=
=pm9R
-END PGP SIGNATURE-


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [5.5.9] Excessive jk INFO log msgs "connection timeout reached" [255831:132361]

[RTE - Meridian Club]

Many thanks for your email. This is an automated response acknowledging receipt.

Please be advised that Badge mailing commences beginning of October 2005.

Should your message require a response we will respond shortly.

Regards
Meridian Club


> -Original Message-
> From: "Rick" <[EMAIL PROTECTED]>
> Received: 10/7/2005 6:35 PM
> To: "'Tomcat Users List'" 
> 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 in the code per my original
> post, noted below..  On all calls to log, isn't it required to do a check
> for that log level before making the call... i.e.  isDebugEnabled(),
> isInfoEnabled(), etc.   Maybe for some reason, log4j with filter without the
> check? (speculation), if this is the case.. The below mentioned change may
> fix the problem, I don't have the tomcat build environment setup or I would
> try it.. Anyone else do their own tomcat builds that could try 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] 
> Posted At: Friday, October 07, 2005 10:07 AM
> Posted To: Tomcat Dev
> Conversation: [5.5.9] Excessive jk INFO log msgs "connection timeout
> reached"
> 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, you'll have better success using a
> log4j or commons-logging properties configuration to set the threshold to
> ERROR. you may be able to do that in jk's config files too, i am sure 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.
> 
> 
> enableLookups="false" redirectPort="8443" debug="0"
>minProcessors="50" maxProcessors="500"
> connectionTimeout="2"
>protocol="AJP/1.3" />
> 
> I tried to modify the logger definition in the server.xml using
> verbosity="0"
> 
>   
>  prefix="catalina_log." suffix=".txt" verbosity="0"
>   timestamp="true"/>
> 
> 
> But its just the catalina_log and not the catalina.out which according to
> the start scripts of the tomcat daemon is a redirection of stdout of the
> daemon itself into the logfile.
> 
> Is there an option to make the tomcat daemon less noisy?
> 
> 
> 
> Thanks,
> Marcus
> 
> 
> 
> -- 
> 
> History tends to exaggerate.
>   -- Col. Green, "The Savage Curtain", stardate 5906.4
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

--
Meridian Club
Unit 5, Caxton Centre
Porters Wood
St Albans
Herts
UNITED KINGDOM
AL3 6XT

Tel: +44 1727 738855
Fax: +44 1700 578955
email: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"

[Rick]

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 in the code per my original
post, noted below..  On all calls to log, isn't it required to do a check
for that log level before making the call... i.e.  isDebugEnabled(),
isInfoEnabled(), etc.   Maybe for some reason, log4j with filter without the
check? (speculation), if this is the case.. The below mentioned change may
fix the problem, I don't have the tomcat build environment setup or I would
try it.. Anyone else do their own tomcat builds that could try 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] 
Posted At: Friday, October 07, 2005 10:07 AM
Posted To: Tomcat Dev
Conversation: [5.5.9] Excessive jk INFO log msgs "connection timeout
reached"
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, you'll have better success using a
log4j or commons-logging properties configuration to set the threshold to
ERROR. you may be able to do that in jk's config files too, i am sure 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.




I tried to modify the logger definition in the server.xml using
verbosity="0"

  
  


But its just the catalina_log and not the catalina.out which according to
the start scripts of the tomcat daemon is a redirection of stdout of the
daemon itself into the logfile.

Is there an option to make the tomcat daemon less noisy?



Thanks,
Marcus



-- 

History tends to exaggerate.
-- Col. Green, "The Savage Curtain", stardate 5906.4

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [5.5.9] Excessive jk INFO log msgs "connection timeout reached" [255825:132355]

[RTE - Meridian Club]

Many thanks for your email. This is an automated response acknowledging receipt.

Please be advised that Badge mailing commences beginning of October 2005.

Should your message require a response we will respond shortly.

Regards
Meridian Club


> -Original Message-
> From: "Marcus Franke" <[EMAIL PROTECTED]>
> Received: 10/7/2005 6:05 PM
> To: "Tomcat Users List" 
> 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, you'll have better success using a 
> > log4j or commons-logging properties configuration to set the threshold to 
> > ERROR. you may be able to do that in jk's config files too, i am sure 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.
> 
> 
> enableLookups="false" redirectPort="8443" debug="0"
>minProcessors="50" maxProcessors="500" 
> connectionTimeout="2"
>protocol="AJP/1.3" />
> 
> I tried to modify the logger definition in the server.xml using verbosity="0"
> 
>   
>  prefix="catalina_log." suffix=".txt" verbosity="0"
>   timestamp="true"/>
> 
> 
> But its just the catalina_log and not the catalina.out which according to
> the start scripts of the tomcat daemon is a redirection of stdout of the
> daemon itself into the logfile.
> 
> Is there an option to make the tomcat daemon less noisy?
> 
> 
> 
> Thanks,
> Marcus
> 
> 
> 
> -- 
> 
> History tends to exaggerate.
>   -- Col. Green, "The Savage Curtain", stardate 5906.4
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

--
Meridian Club
Unit 5, Caxton Centre
Porters Wood
St Albans
Herts
UNITED KINGDOM
AL3 6XT

Tel: +44 1727 738855
Fax: +44 1700 578955
email: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"

[Marcus Franke]

On Fri, Oct 07, 2005 at 05:24:27PM +0100, Allistair Crossley wrote:
> Hi,
> 
> looks like jk is using commons logging, you'll have better success using a 
> log4j or commons-logging properties configuration to set the threshold to 
> ERROR. you may be able to do that in jk's config files too, i am sure 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.




I tried to modify the logger definition in the server.xml using verbosity="0"

  
  


But its just the catalina_log and not the catalina.out which according to
the start scripts of the tomcat daemon is a redirection of stdout of the
daemon itself into the logfile.

Is there an option to make the tomcat daemon less noisy?



Thanks,
Marcus



-- 

History tends to exaggerate.
-- Col. Green, "The Savage Curtain", stardate 5906.4

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [5.5.9] Excessive jk INFO log msgs "connection timeout reached" [255820:132350]

[RTE - Meridian Club]

Many thanks for your email. This is an automated response acknowledging receipt.

Please be advised that Badge mailing commences beginning of October 2005.

Should your message require a response we will respond shortly.

Regards
Meridian Club


> -Original Message-
> From: "Marcus Franke" <[EMAIL PROTECTED]>
> Received: 10/7/2005 5:39 PM
> To: "Tomcat Users List" 
> 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, 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.
> > 
> 
> Hmm, I guess its not only an issue of the mod_jk, as I restarted the
> apache server and still had sessions in the jk connector with an age
> of over 19 hours.
> 
> Or am I missing something?
> 
> 
> Marcus
> 
> -- 
> 
> Live long and prosper.
>   -- Spock, "Amok Time", stardate 3372.7
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

--
Meridian Club
Unit 5, Caxton Centre
Porters Wood
St Albans
Herts
UNITED KINGDOM
AL3 6XT

Tel: +44 1727 738855
Fax: +44 1700 578955
email: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"

[Marcus Franke]

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
> issue.  I'll give them a try.
> 

Hmm, I guess its not only an issue of the mod_jk, as I restarted the
apache server and still had sessions in the jk connector with an age
of over 19 hours.

Or am I missing something?


Marcus

-- 

Live long and prosper.
-- Spock, "Amok Time", stardate 3372.7

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [5.5.9] Excessive jk INFO log msgs "connection timeout reached" [255811:132338]

[RTE - Meridian Club]

Many thanks for your email. This is an automated response acknowledging receipt.

Please be advised that Badge mailing commences beginning of October 2005.

Should your message require a response we will respond shortly.

Regards
Meridian Club


> -Original Message-
> From: "Allistair Crossley" <[EMAIL PROTECTED]>
> Received: 10/7/2005 5:23 PM
> To: "Tomcat Users List" 
> 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 configuration to set the threshold to 
> ERROR. you may be able to do that in jk's config files too, i am sure there 
> is an error level setting. check out the jk docs.
> 
> Allistair.
> 
> > -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 the "connectionTimeout" set, jk seems 
> > to hold on to its
> > > connections indefinitely and after a while, the apache to 
> > tomcat connection
> > > hangs (pages quit serving).   Could you tell me which combo 
> > of versions you
> > > use for apache, jk, and tomcat.  I'm trying to figure out 
> > what is the
> > > "correct" configuration.  Or if you have a link to a guide, 
> >  I have yet to
> > > find a "best practices".
> > > 
> > 
> > Out of curiosity I activated the connectionTimeout in my ajp 
> > connector and
> > my catalina.out file gets spammed with hundreds 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: connection timeout reached
> > 07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket 
> > processConnection
> > INFO: connection timeout reached
> > 07.10.2005 17:47:20 org.apache.jk.common.ChannelSocket 
> > processConnection
> > INFO: connection timeout reached
> > 
> > I guess, it is because of definition of debug="9" in the same 
> > Connector.
> > 
> > What would be a reasonable debug level? Zero?
> > 
> > 
> > Marcus
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> 
>  
> ---
> QAS Ltd.
> Registered in England: No 2582055
> Registered in Australia: No 082 851 474
> ---
>   
> Disclaimer:  The information contained within this e-mail is confidential and 
> may be privileged. This email is intended solely for the named recipient 
> only; if you are not authorised you must not disclose, copy, distribute, or 
> retain this message or any part of it. If you have received this message in 
> error please contact the sender at once so that we may take the appropriate 
> action and avoid troubling you further.  Any views expressed in this message 
> are those of the individual sender.  QAS Limited has the right lawfully to 
> record, monitor and inspect messages between its employees and any third 
> party.  Your messages shall be subject to such lawful supervision as QAS 
> Limited deems to be necessary in order to protect its information, its 
> interests and its reputation.  
> 
> Whilst all efforts are made to safeguard Inbound and Outbound emails, QAS 
> Limited cannot guarantee that attachments are virus free or compatible with 
> your systems and does not accept any liability in respect of viruses or 
> computer problems experienced.
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

--
Meridian Club
Unit 5, Caxton Centre
Porters Wood
St Albans
Herts
UNITED KINGDOM
AL3 6XT

Tel: +44 1727 738855
Fax: +44 1700 578955
email: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"

[Allistair Crossley]

Hi,

looks like jk is using commons logging, you'll have better success using a 
log4j or commons-logging properties configuration to set the threshold to 
ERROR. you may be able to do that in jk's config files too, i am sure there is 
an error level setting. check out the jk docs.

Allistair.

> -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 the "connectionTimeout" set, jk seems 
> to hold on to its
> > connections indefinitely and after a while, the apache to 
> tomcat connection
> > hangs (pages quit serving).   Could you tell me which combo 
> of versions you
> > use for apache, jk, and tomcat.  I'm trying to figure out 
> what is the
> > "correct" configuration.  Or if you have a link to a guide, 
>  I have yet to
> > find a "best practices".
> > 
> 
> Out of curiosity I activated the connectionTimeout in my ajp 
> connector and
> my catalina.out file gets spammed with hundreds 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: connection timeout reached
> 07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket 
> processConnection
> INFO: connection timeout reached
> 07.10.2005 17:47:20 org.apache.jk.common.ChannelSocket 
> processConnection
> INFO: connection timeout reached
> 
> I guess, it is because of definition of debug="9" in the same 
> Connector.
> 
> What would be a reasonable debug level? Zero?
> 
> 
> Marcus
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


 
---
QAS Ltd.
Registered in England: No 2582055
Registered in Australia: No 082 851 474
---
  
Disclaimer:  The information contained within this e-mail is confidential and 
may be privileged. This email is intended solely for the named recipient only; 
if you are not authorised you must not disclose, copy, distribute, or retain 
this message or any part of it. If you have received this message in error 
please contact the sender at once so that we may take the appropriate action 
and avoid troubling you further.  Any views expressed in this message are those 
of the individual sender.  QAS Limited has the right lawfully to record, 
monitor and inspect messages between its employees and any third party.  Your 
messages shall be subject to such lawful supervision as QAS Limited deems to be 
necessary in order to protect its information, its interests and its 
reputation.  

Whilst all efforts are made to safeguard Inbound and Outbound emails, QAS 
Limited cannot guarantee that attachments are virus free or compatible with 
your systems and does not accept any liability in respect of viruses or 
computer problems experienced.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [5.5.9] Excessive jk INFO log msgs "connection timeout reached" [255808:132335]

[RTE - Meridian Club]

Many thanks for your email. This is an automated response acknowledging receipt.

Please be advised that Badge mailing commences beginning of October 2005.

Should your message require a response we will respond shortly.

Regards
Meridian Club


> -Original Message-
> From: "Marcus Franke" <[EMAIL PROTECTED]>
> Received: 10/7/2005 5:20 PM
> 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 the "connectionTimeout" set, jk seems to hold on to its
> > connections indefinitely and after a while, the apache to tomcat connection
> > hangs (pages quit serving).   Could you tell me which combo of versions you
> > use for apache, jk, and tomcat.  I'm trying to figure out what is the
> > "correct" configuration.  Or if you have a link to a guide,  I have yet to
> > find a "best practices".
> > 
> 
> Out of curiosity I activated the connectionTimeout in my ajp connector and
> my catalina.out file gets spammed with hundreds 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: connection timeout reached
> 07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket processConnection
> INFO: connection timeout reached
> 07.10.2005 17:47:20 org.apache.jk.common.ChannelSocket processConnection
> INFO: connection timeout reached
> 
> I guess, it is because of definition of debug="9" in the same Connector.
> 
> What would be a reasonable debug level? Zero?
> 
> 
> Marcus
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

--
Meridian Club
Unit 5, Caxton Centre
Porters Wood
St Albans
Herts
UNITED KINGDOM
AL3 6XT

Tel: +44 1727 738855
Fax: +44 1700 578955
email: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"

[Marcus Franke]

On Thu, Oct 06, 2005 at 06:53:36AM -0700, Rick wrote:
> Jean-Marc,
>   Actually, without the "connectionTimeout" set, jk seems to hold on to its
> connections indefinitely and after a while, the apache to tomcat connection
> hangs (pages quit serving).   Could you tell me which combo of versions you
> use for apache, jk, and tomcat.  I'm trying to figure out what is the
> "correct" configuration.  Or if you have a link to a guide,  I have yet to
> find a "best practices".
> 

Out of curiosity I activated the connectionTimeout in my ajp connector and
my catalina.out file gets spammed with hundreds 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: connection timeout reached
07.10.2005 17:47:18 org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
07.10.2005 17:47:20 org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached

I guess, it is because of definition of debug="9" in the same Connector.

What would be a reasonable debug level? Zero?


Marcus


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"

[Rick]

 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

-Original Message-
From: Jean-Marc Marchand [mailto:[EMAIL PROTECTED] 
Posted At: Thursday, October 06, 2005 9:15 AM
Posted To: Tomcat Dev
Conversation: [5.5.9] Excessive jk INFO log msgs "connection timeout
reached"
Subject: RE: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"


I`m using Tomcat 5.0.30 / Apache 2.0.54 / JK 1.2.14.1

I looked a bit in the source of the Tomcat JK connector, and the
'connectionTimeout' parameter of the  is relayed to 'soTimeout'
of the listening JK sockets "ChannelSocket.java".
...which takes us to the java.net.Socket api and SO_TIMEOUT parameter.

Seems to me that mod_jk in Apache keeps the connection opened, therefore
never closing it and reusing it for future calls.
If so, and if I set a connectionTimeout on the Tomcat JK connector, it would
always close the connection with a TimeoutException. That would explain the
log 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:

worker.tomcat1.port=8009
worker.tomcat1.host=localhost
worker.tomcat1.type=ajp13
worker.tomcat1.cachesize=150
worker.tomcat1.cache_timeout=600
worker.tomcat1.recycle_timeout=300
worker.tomcat1.socket_timeout=30
worker.tomcat1.socket_keepalive=1

and I haven't had the log entry in Tomcat since I set the cache and timeouts
in Apache.

Hope it helps...
Jean-Marc

> -Original Message-
> From: Rick [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 06, 2005 09:54
> To: 'Tomcat Users List'; [EMAIL PROTECTED]
> Subject: RE: [5.5.9] Excessive jk INFO log msgs "connection timeout 
> reached"
>
>
> Jean-Marc,
>   Actually, without the "connectionTimeout" set, jk seems to hold on 
> to its connections indefinitely and after a while, the apache to 
> tomcat connection
> hangs (pages quit serving).   Could you tell me which combo
> of versions you
> use for apache, jk, and tomcat.  I'm trying to figure out what is the 
> "correct" configuration.  Or if you have a link to a guide, I have yet 
> to find a "best practices".
>
> Thanks,
> Rick
>
> -----Original Message-
> From: Jean-Marc Marchand [mailto:[EMAIL PROTECTED]
> Posted At: Thursday, October 06, 2005 6:36 AM Posted To: Tomcat Dev
> Conversation: [5.5.9] Excessive 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 will default to 'no 
> timeout'.
>
> Cheers,
> Jean-Marc
>
>
>
> > -Original Message-
> > From: Rick [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, October 05, 2005 18:19
> > To: 'Tomcat Users List'
> > Subject: [5.5.9] Excessive jk INFO log msgs "connection timeout 
> > reached"
> >
> >
> > 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 
> > /common/classes/logging.properties
> > org.apache.jk.common.ChannelSocket.level=WARN
> >
> > Has no effect.  The only thing I have been able to find is people 
> > using Log4j instead of the default java.util.logging that
> came setup
> > with Tomcat 5.5.  Was wondering, is that the only way?  If so, why 
> > does it work w/ Log4j and not the default java.util.logging?
> >
> > Looking at the source for
> > '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");
> >
> >
> > Anyway, thanks for any help to this.
> >
> > -Rick Gavin
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"

[Jean-Marc Marchand]

I`m using Tomcat 5.0.30 / Apache 2.0.54 / JK 1.2.14.1

I looked a bit in the source of the Tomcat JK connector,
and the 'connectionTimeout' parameter of the  is
relayed to 'soTimeout' of the listening JK sockets "ChannelSocket.java".
...which takes us to the java.net.Socket api and SO_TIMEOUT parameter.

Seems to me that mod_jk in Apache keeps the connection opened,
therefore never closing it and reusing it for future calls.
If so, and if I set a connectionTimeout on the Tomcat JK connector, it would
always close the connection with a TimeoutException. That would
explain the log 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:

worker.tomcat1.port=8009
worker.tomcat1.host=localhost
worker.tomcat1.type=ajp13
worker.tomcat1.cachesize=150
worker.tomcat1.cache_timeout=600
worker.tomcat1.recycle_timeout=300
worker.tomcat1.socket_timeout=30
worker.tomcat1.socket_keepalive=1

and I haven't had the log entry in Tomcat since I set the
cache and timeouts in Apache.

Hope it helps...
Jean-Marc

> -Original Message-
> From: Rick [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 06, 2005 09:54
> To: 'Tomcat Users List'; [EMAIL PROTECTED]
> Subject: RE: [5.5.9] Excessive jk INFO log msgs "connection timeout
> reached"
>
>
> Jean-Marc,
>   Actually, without the "connectionTimeout" set, jk seems to
> hold on to its
> connections indefinitely and after a while, the apache to
> tomcat connection
> hangs (pages quit serving).   Could you tell me which combo
> of versions you
> use for apache, jk, and tomcat.  I'm trying to figure out what is the
> "correct" configuration.  Or if you have a link to a guide,
> I have yet to
> find a "best practices".
>
> Thanks,
> Rick
>
> -Original Message-
> From: Jean-Marc Marchand [mailto:[EMAIL PROTECTED]
> Posted At: Thursday, October 06, 2005 6:36 AM
> Posted To: Tomcat Dev
> Conversation: [5.5.9] Excessive 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 will default to 'no
> timeout'.
>
> Cheers,
> Jean-Marc
>
>
>
> > -Original Message-
> > From: Rick [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, October 05, 2005 18:19
> > To: 'Tomcat Users List'
> > Subject: [5.5.9] Excessive jk INFO log msgs "connection timeout
> > reached"
> >
> >
> > 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
> > /common/classes/logging.properties
> > org.apache.jk.common.ChannelSocket.level=WARN
> >
> > Has no effect.  The only thing I have been able to find is people
> > using Log4j instead of the default java.util.logging that
> came setup
> > with Tomcat 5.5.  Was wondering, is that the only way?  If so, why
> > does it work w/ Log4j and not the default java.util.logging?
> >
> > Looking at the source for
> > '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");
> >
> >
> > Anyway, thanks for any help to this.
> >
> > -Rick Gavin
> >
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"

[Rick]

Jean-Marc,
  Actually, without the "connectionTimeout" set, jk seems to hold on to its
connections indefinitely and after a while, the apache to tomcat connection
hangs (pages quit serving).   Could you tell me which combo of versions you
use for apache, jk, and tomcat.  I'm trying to figure out what is the
"correct" configuration.  Or if you have a link to a guide,  I have yet to
find a "best practices".

Thanks,
Rick

-Original Message-
From: Jean-Marc Marchand [mailto:[EMAIL PROTECTED] 
Posted At: Thursday, October 06, 2005 6:36 AM
Posted To: Tomcat Dev
Conversation: [5.5.9] Excessive 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 will default to 'no
timeout'.

Cheers,
Jean-Marc



> -Original Message-
> From: Rick [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 05, 2005 18:19
> To: 'Tomcat Users List'
> Subject: [5.5.9] Excessive jk INFO log msgs "connection timeout 
> reached"
> 
> 
> 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 
> /common/classes/logging.properties
> org.apache.jk.common.ChannelSocket.level=WARN
> 
> Has no effect.  The only thing I have been able to find is people 
> using Log4j instead of the default java.util.logging that came setup 
> with Tomcat 5.5.  Was wondering, is that the only way?  If so, why 
> does it work w/ Log4j and not the default java.util.logging?
> 
> Looking at the source for
> '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");
> 
> 
> Anyway, thanks for any help to this.
> 
> -Rick Gavin
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [5.5.9] Excessive jk INFO log msgs "connection timeout reached"

[Jean-Marc Marchand]

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]
> Sent: Wednesday, October 05, 2005 18:19
> To: 'Tomcat Users List'
> Subject: [5.5.9] Excessive jk INFO log msgs "connection 
> timeout reached"
> 
> 
> 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
> /common/classes/logging.properties
> org.apache.jk.common.ChannelSocket.level=WARN
> 
> Has no effect.  The only thing I have been able to find is 
> people using
> Log4j instead of the default java.util.logging that came 
> setup with Tomcat
> 5.5.  Was wondering, is that the only way?  If so, why does 
> it work w/ Log4j
> and not the default java.util.logging?
> 
> Looking at the source for 
> '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");
> 
> 
> Anyway, thanks for any help to this.
> 
> -Rick Gavin
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[5.5.9] Excessive jk INFO log msgs "connection timeout reached"

[Rick]

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
/common/classes/logging.properties
org.apache.jk.common.ChannelSocket.level=WARN

Has no effect.  The only thing I have been able to find is people using
Log4j instead of the default java.util.logging that came setup with Tomcat
5.5.  Was wondering, is that the only way?  If so, why does it work w/ Log4j
and not the default java.util.logging?

Looking at the source for '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");


Anyway, thanks for any help to this.

-Rick Gavin


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Connection Timeout

[Andrew Miehs]

Does anyone know any way that I can tell tomcat to kill the 'thread' if 
it isn't back in a ready state within 30 seconds? (waiting for new 
requests)

Thanks
Andrew
On 05.11.2004, at 16:20, Phillip Qin wrote:

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 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?
-Original Message-
From: Andrew Miehs [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? or
is this a request waiting to be picked up - ie: chunked?
If so, is there any way I can set 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]

RE: INFO: connection Timeout reached

[Varley, Roger]

> 
> 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, is there anyway I can stop Tomcat from logging 
> these messages as it makes it impossible to see any other 
> messages since they scroll off the console too quickly?
> 

I realise that this is probably an FAQ but I would be grateful if someone could 
point me in the right direction on this as I don't seem to be getting anywhere. 
Googling has revealed a suggestion that I should be setting the "verbosity" 
parameter on the Logger in my server.xml to suppress INFO messages, but the 
documentation at 
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/logger.html suggests 
that the default out-of-the-box setting should be to display error messages 
only.

Regards
Roger


__
This e-mail and the documents attached are confidential and intended 
solely for the addressee; it may also be privileged. If you receive this 
e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group 
liability cannot be triggered for the message content. Although the 
sender endeavours to maintain a computer virus-free network, the sender 
does not warrant that this transmission is virus-free and will not be 
liable for any damages resulting from any virus transmitted.
__

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Connection Timeout

[Andrew Miehs]

Hi Phillip,
S506331 ms17 KB0 KBx.x.2.24www.x.comGET 
/x//img/x/Image.gif HTTP/1.1

Regards
Andrew
On 05.11.2004, at 16:20, Phillip Qin wrote:

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 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?
-Original Message-
From: Andrew Miehs [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? or
is this a request waiting to be picked up - ie: chunked?
If so, is there any way I can set 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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!DSPAM:418b99c3205412059510077!

RE: Connection Timeout

[Phillip Qin]

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 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?
>
> -Original Message-
> From: Andrew Miehs [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? or 
> is this a request waiting to be picked up - ie: chunked?
>
> If so, is there any way I can set 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]
>
>
> 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


!DSPAM:418b99c3205412059510077!

Re: Connection Timeout

[Andrew Miehs]

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?

-Original Message-
From: Andrew Miehs [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? or
is this a request waiting to be picked up - ie: chunked?
If so, is there any way I can set 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]
!DSPAM:418b46a1164289526310470!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Connection Timeout

[Phillip Qin]

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 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? or 
is this a request waiting to be picked up - ie: chunked?

If so, is there any way I can set 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]


!DSPAM:418b46a1164289526310470!

Connection Timeout

[Andrew Miehs]

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? or 
is this a request waiting to be picked up - ie: chunked?

If so, is there any way I can set 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]

INFO: connection Timeout reached

[Varley, Roger]

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, is there anyway I can stop Tomcat from 
logging these messages as it makes it impossible to see any other messages since they 
scroll off the console too quickly?

Regards
Roger



__
This e-mail and the documents attached are confidential and intended 
solely for the addressee; it may also be privileged. If you receive this 
e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group 
liability cannot be triggered for the message content. Although the 
sender endeavours to maintain a computer virus-free network, the sender 
does not warrant that this transmission is virus-free and will not be 
liable for any damages resulting from any virus transmitted.
__

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Repost::Connection Timeout

[Sameer Danthurthy]

Hello,
  Iam working on high perf servlet that needs to return the response 
within few seconds and hence I want to emulate an non existant connection
rather than a delayed response i.e. the webserver break the tcp connection
rather than hold the client for delayed response from the servlet. I played
around
with the connection timeout parameter in server.xml as well as the timeout
directive in httpd.conf for apache without much success. Iam running the apps
on redhat 8 on intel platform. How should I approach such a thing?
Apache 2.0.47
tomcat 5.x
JK 2

Thanks
sameer


This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please notify
the sender immediately by e-mail if you have received this e-mail by
mistake and delete this e-mail from your system. E-mail transmission
cannot be guaranteed to be secure or error-free as information could
be intercepted, corrupted,lost, destroyed, arrive late or incomplete
or contain viruses. The sender therefore does not accept liability
for any errors or omissions in the contents of this message, which
arise as a result of e-mail transmission.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Connection timeout when using OutputStream

[Paul Mitchell]

I forgot to mention - I am running Tomcat 4.1.27 on Win2K.

Thanks.
--- Paul Mitchell <[EMAIL PROTECTED]> wrote:
> Hello,
>   I am running into problems with downloading unusually big files within my
> application using the ServletOutputStream.
> From what I read on the documentation I set the Coyote Connector attribute
> connectionTimeout="-1" and still the problem persists.
> Any ideas/advice anyone ?
> 
> Thanks,
> Paul.
> 
> 
>   
>   
> __
> Do you Yahoo!?
> Friends.  Fun.  Try the all-new Yahoo! Messenger.
> http://messenger.yahoo.com/ 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 





__
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Connection timeout when using OutputStream

[Paul Mitchell]

Hello,
  I am running into problems with downloading unusually big files within my
application using the ServletOutputStream.
>From what I read on the documentation I set the Coyote Connector attribute
connectionTimeout="-1" and still the problem persists.
Any ideas/advice anyone ?

Thanks,
Paul.




__
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached

[Bill Barker]

The 'RESET' message is most likely somebody hitting the 'stop' button in the
browser.  The 'connection timeout' is Tomcat hanging up the line when it
didn't get another request from Apache within 20sec of the last one (which
is what you told it to do :).

"Kommineni, Sateesh (GE Consumer & Industrial)" <[EMAIL PROTECTED]>
wrote in message
news:[EMAIL PROTECTED]
Hi All,

I am trying to deploy a Web Application in my Tomcat and got the
following Error in the Log Files..

Apr 20, 2004 11:05:04 AM org.apache.jk.server.JkCoyoteHandler action
INFO: RESET
Apr 20, 2004 11:05:04 AM org.apache.jk.server.JkCoyoteHandler action
INFO: RESET
Apr 20, 2004 11:05:14 AM org.apache.jk.common.ChannelSocket
processConnection
INFO: connection timeout reached

What does this mean ??

I have the following entries in my server.xml.

  




Factory className="org.apache.catalina.net.DefaultServerSocketFactory"/>


   what is the significance of ajp13 scheme ??

  Pls let me know.. Thanks a lot..

-Sateesh




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached

[Thomas Tang]

Hello,

I get the same messages in my log, but the application appears to work 
without a hitch. I was never able to figure out what the cause of this is, 
or if I should even be concerned with it?

One of my programmers tells me this is related when a client abruptly 
terminates a session. Im not totally convinced of it, but i don't have a 
better explanation or theory.





"Kommineni, Sateesh \(GE Consumer & Industrial\)" 
<[EMAIL PROTECTED]> 
04/20/2004 11:34 AM
Please respond to
"Tomcat Users List" <[EMAIL PROTECTED]>


To
<[EMAIL PROTECTED]>
cc

Subject
org.apache.jk.common.ChannelSocket processConnection INFO: connection 
timeout reached






Hi All,

I am trying to deploy a Web Application in my Tomcat and got the 
following Error in the Log Files..

 Apr 20, 2004 11:05:04 AM 
org.apache.jk.server.JkCoyoteHandler action
 INFO: RESET 
 Apr 20, 2004 11:05:04 AM 
org.apache.jk.server.JkCoyoteHandler action
 INFO: RESET 
 Apr 20, 2004 11:05:14 AM 
org.apache.jk.common.ChannelSocket processConnection
 INFO: connection timeout reached

What does this mean ??

I have the following entries in my server.xml.

  
 



Factory className="org.apache.catalina.net.DefaultServerSocketFactory"/>


   what is the significance of ajp13 scheme ??

  Pls let me know.. Thanks a lot..

-Sateesh


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached

[Kommineni, Sateesh \(GE Consumer & Industrial\)]

Hi All,

I am trying to deploy a Web Application in my Tomcat and got the following Error 
in the Log Files..

Apr 20, 2004 11:05:04 AM org.apache.jk.server.JkCoyoteHandler action
INFO: RESET 
Apr 20, 2004 11:05:04 AM org.apache.jk.server.JkCoyoteHandler action
INFO: RESET 
Apr 20, 2004 11:05:14 AM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached

What does this mean ??

I have the following entries in my server.xml.

  




Factory className="org.apache.catalina.net.DefaultServerSocketFactory"/>


   what is the significance of ajp13 scheme ??

  Pls let me know.. Thanks a lot..

-Sateesh


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [INFO] ChannelSocket - -connection timeout reached

[Bill Barker]

My experience has been that I need to have a connectionTimeout on RH.
However, you can get rid of the message either by setting
'connectionTimeout="-1"' in the server.xml file or setting
'channelSocket.soTimeout=-1' in jk2.properties.

"Asif Chowdhary" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Hi

I am running the RH linux with apache and mod_jk2. On the window machine I
have tomcat.
When I run the examples I see this message in the windows console where
tomcat is running.

[INFO] ChannelSocket - -connection timeout reached

Do I need to increase the time in server.xml or jk2.properties

Thanks




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[INFO] ChannelSocket - -connection timeout reached

[Asif Chowdhary]

Hi

I am running the RH linux with apache and mod_jk2. On the window machine I have tomcat.
When I run the examples I see this message in the windows console where tomcat is 
running.

[INFO] ChannelSocket - -connection timeout reached

Do I need to increase the time in server.xml or jk2.properties

Thanks




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

connection timeout reached

[L.Karam]

 
What is the reason of this INFO to happen?
 
05/12/2003 06:46:01 org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached
 
It appears with sufficient frequency. What I must make to stop it?
 
Tks
 
Leandro Karam







  IncrediMail - Email has finally evolved - Click Here

Re: Connection timeout Problem

[Christopher Schultz]

Gary,
My tomcat 4.1.27 connects to mysql thu. jdbc driver.
If I keep some connections overnite, i found they all got lost in the next
morning, and hence my tomcat need to restart.
does anybody has some hint?
You replied to a thread which already contained the fix:

Add autoreconnect=true to your JDBC URL that you use to connect.

I've seen people ignore archive posts. I've seen people ignore posts 
from the previous day. But I've never seen anyone ignore the post to 
which they're replying.

Finally, please note that this has nothing to do with Tomcat. It's 
either a MySQL issue, a MySQL driver issue, or a connection pool issue. 
Please try to keep the questions at least tangentially related to Tomcat.

-chris

Thanks

- Original Message -
From: Veselin Kovacevic <[EMAIL PROTECTED]>
To: Tomcat Users List <[EMAIL PROTECTED]>
Sent: Wednesday, November 12, 2003 4:17 PM
Subject: RE: Problem with ConnectionPool on Linux
You think DBCP 1.1?
I try to install Tomcat 4.1.29 but I get some error with connection
pool.
Is there some changes in server.xml settings?
-Original Message-
From: Kwok Peng Tuck [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 9:13 AM
To: Tomcat Users List
Subject: Re: Problem with ConnectionPool on Linux
The new version of DBCP should be able to cope with this as well. I
tested it with MaxDB and it works ok.
Veselin Kovacevic wrote:


Now, everything working fine. :)

Thanks Jon.



-Original Message-
From: Jon Wingfield [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 4:50 PM
To: Tomcat Users List
Subject: Re: Problem with ConnectionPool on Linux
MySql times out idle connections. If your pool implementation doesn't
take care of weeding out dead connections you need to add
autoReconnect=true to your connection string.
HTH,

Jon

Veselin Kovacevic wrote:




Hi,

I have o problem with Tomcat 4.1.24 on SuseLinux7.3. Our application
has Controller servlet (below) where using connection objects from
connection pool. When tomcat started, application working fine and
everything OK that day. But next day when we try to start application
we get error message in isUser method (PortalUserDB class). It's first




place where we use connection object in application. Method isUser is
very simple method for authenticate user (below). We get this
exception: SQL Exception:java.sql.SQLException: No operations allowed
after connection closed
Connection object is not null in this case, and this message for me is





not correct. Next, if I restart tomcat, everything working ok... (for
next day).
On windows (we using windows for development platform) we have not
this problem.
What is problem?
Is configuration server.xml or similar configuration files on Linux
different rather on windows?
Note:
On both platform we using Tomcat 4.1.24 and j2sdk1.4.1_03.
public class Controller extends HttpServlet {

private DataSource ds;

public void init(ServletConfig config) throws ServletException {
super.init(config);
try {
InitialContext initCtx = new InitialContext();
Context envCtx =
(Context)initCtx.lookup("java:comp/env");
ds =
(DataSource)envCtx.lookup("jdbc/MySQLPool");
} catch (Exception e){
throw new UnavailableException(e.getMessage());
}
}
public void doGet(HttpServletRequest request,


HttpServletResponse



response)
 throws IOException,
ServletException {
request.setCharacterEncoding("iso-8859-2");



if (ds != null) {
Connection conn = ds.getConnection();
if (conn != null) {
boolean isUserExists =
PortalUserDB.isUser(conn, userName, userPass);


conn.close();
}


}
}
public static boolean isUser(Connection conn, String userName, String
userPass)
throws SQLException, IOException {
String query = "SELECT user_name FROM admin_user " +
  "WHERE user_name = ? " +
  "AND user_pass = ?";
boolean isUserExists = false;

try {
PreparedStatement pstmt = conn.prepareStatement(query);
pstmt.setString(1, userName);
pstmt.setString(2, userPass);
ResultSet rs = pstmt.executeQuery();

isUserExists = rs.next();

rs.close();
rs = null;
pstmt.close();
pstmt = null;
} catch (SQLException sqle) {
PortalLog.addLogLine("Class: PortalUserDB, Method:
isUser. SQL Exception:" + sqle, userName);
}
return isUserExists;
}
Thanks,
Veso
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional 

Re: Connection timeout Problem

[Vincent Aumont]

MySQL drops the connection after a certain period of inactivity. Just 
add autoReconnect=true to you jdbc url:
E.g. jdbc:mysql://localhost:3306/mydb?autoReconnect=true

-Vincent.
Gary Lee wrote:
My tomcat 4.1.27 connects to mysql thu. jdbc driver.
If I keep some connections overnite, i found they all got lost in the next
morning, and hence my tomcat need to restart.
does anybody has some hint?

Thanks

- Original Message -
From: Veselin Kovacevic <[EMAIL PROTECTED]>
To: Tomcat Users List <[EMAIL PROTECTED]>
Sent: Wednesday, November 12, 2003 4:17 PM
Subject: RE: Problem with ConnectionPool on Linux
You think DBCP 1.1?
I try to install Tomcat 4.1.29 but I get some error with connection
pool.
Is there some changes in server.xml settings?
-Original Message-
From: Kwok Peng Tuck [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 9:13 AM
To: Tomcat Users List
Subject: Re: Problem with ConnectionPool on Linux
The new version of DBCP should be able to cope with this as well. I
tested it with MaxDB and it works ok.
Veselin Kovacevic wrote:

 

Now, everything working fine. :)

Thanks Jon.



-Original Message-
From: Jon Wingfield [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 4:50 PM
To: Tomcat Users List
Subject: Re: Problem with ConnectionPool on Linux
MySql times out idle connections. If your pool implementation doesn't
take care of weeding out dead connections you need to add
autoReconnect=true to your connection string.
HTH,

Jon

Veselin Kovacevic wrote:



   

Hi,

I have o problem with Tomcat 4.1.24 on SuseLinux7.3. Our application
has Controller servlet (below) where using connection objects from
connection pool. When tomcat started, application working fine and
everything OK that day. But next day when we try to start application
we get error message in isUser method (PortalUserDB class). It's first
 

   

place where we use connection object in application. Method isUser is
very simple method for authenticate user (below). We get this
exception: SQL Exception:java.sql.SQLException: No operations allowed
after connection closed
Connection object is not null in this case, and this message for me is

 

   

not correct. Next, if I restart tomcat, everything working ok... (for
next day).
On windows (we using windows for development platform) we have not
this problem.
What is problem?
Is configuration server.xml or similar configuration files on Linux
different rather on windows?
Note:
On both platform we using Tomcat 4.1.24 and j2sdk1.4.1_03.
public class Controller extends HttpServlet {

private DataSource ds;

public void init(ServletConfig config) throws ServletException {
super.init(config);
try {
InitialContext initCtx = new InitialContext();
Context envCtx =
(Context)initCtx.lookup("java:comp/env");
ds =
(DataSource)envCtx.lookup("jdbc/MySQLPool");
} catch (Exception e){
throw new UnavailableException(e.getMessage());
}
}
public void doGet(HttpServletRequest request,

 

HttpServletResponse

   

response)
 throws IOException,
ServletException {
request.setCharacterEncoding("iso-8859-2");



if (ds != null) {
Connection conn = ds.getConnection();
if (conn != null) {
boolean isUserExists =
PortalUserDB.isUser(conn, userName, userPass);


conn.close();
}


}
}
public static boolean isUser(Connection conn, String userName, String
userPass)
throws SQLException, IOException {
String query = "SELECT user_name FROM admin_user " +
  "WHERE user_name = ? " +
  "AND user_pass = ?";
boolean isUserExists = false;

try {
PreparedStatement pstmt = conn.prepareStatement(query);
pstmt.setString(1, userName);
pstmt.setString(2, userPass);
ResultSet rs = pstmt.executeQuery();

isUserExists = rs.next();

rs.close();
rs = null;
pstmt.close();
pstmt = null;
} catch (SQLException sqle) {
PortalLog.addLogLine("Class: PortalUserDB, Method:
isUser. SQL Exception:" + sqle, userName);
}
return isUserExists;
}
Thanks,
Veso
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




   



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe,

Connection timeout Problem

[Gary Lee]

My tomcat 4.1.27 connects to mysql thu. jdbc driver.
If I keep some connections overnite, i found they all got lost in the next
morning, and hence my tomcat need to restart.

does anybody has some hint?

Thanks


- Original Message -
From: Veselin Kovacevic <[EMAIL PROTECTED]>
To: Tomcat Users List <[EMAIL PROTECTED]>
Sent: Wednesday, November 12, 2003 4:17 PM
Subject: RE: Problem with ConnectionPool on Linux


You think DBCP 1.1?
I try to install Tomcat 4.1.29 but I get some error with connection
pool.
Is there some changes in server.xml settings?

-Original Message-
From: Kwok Peng Tuck [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 9:13 AM
To: Tomcat Users List
Subject: Re: Problem with ConnectionPool on Linux


The new version of DBCP should be able to cope with this as well. I
tested it with MaxDB and it works ok.

Veselin Kovacevic wrote:

>Now, everything working fine. :)
>
>Thanks Jon.
>
>
>
>
>-Original Message-
>From: Jon Wingfield [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, November 11, 2003 4:50 PM
>To: Tomcat Users List
>Subject: Re: Problem with ConnectionPool on Linux
>
>
>MySql times out idle connections. If your pool implementation doesn't
>take care of weeding out dead connections you need to add
>autoReconnect=true to your connection string.
>
>HTH,
>
>Jon
>
>Veselin Kovacevic wrote:
>
>
>
>>Hi,
>>
>>I have o problem with Tomcat 4.1.24 on SuseLinux7.3. Our application
>>has Controller servlet (below) where using connection objects from
>>connection pool. When tomcat started, application working fine and
>>everything OK that day. But next day when we try to start application
>>we get error message in isUser method (PortalUserDB class). It's first
>>
>>
>
>
>
>>place where we use connection object in application. Method isUser is
>>very simple method for authenticate user (below). We get this
>>exception: SQL Exception:java.sql.SQLException: No operations allowed
>>after connection closed
>>
>>Connection object is not null in this case, and this message for me is
>>
>>
>
>
>
>>not correct. Next, if I restart tomcat, everything working ok... (for
>>next day).
>>
>>On windows (we using windows for development platform) we have not
>>this problem.
>>
>>What is problem?
>>Is configuration server.xml or similar configuration files on Linux
>>different rather on windows?
>>
>>Note:
>>On both platform we using Tomcat 4.1.24 and j2sdk1.4.1_03.
>>
>>
>>public class Controller extends HttpServlet {
>>
>> private DataSource ds;
>>
>> public void init(ServletConfig config) throws ServletException {
>> super.init(config);
>> try {
>> InitialContext initCtx = new InitialContext();
>> Context envCtx =
>>(Context)initCtx.lookup("java:comp/env");
>> ds =
>>(DataSource)envCtx.lookup("jdbc/MySQLPool");
>> } catch (Exception e){
>> throw new UnavailableException(e.getMessage());
>> }
>> }
>>
>> public void doGet(HttpServletRequest request,
>>
>>
>HttpServletResponse
>
>
>>response)
>>   throws IOException,
>>ServletException {
>>
>> request.setCharacterEncoding("iso-8859-2");
>>
>> 
>> 
>>
>> if (ds != null) {
>> Connection conn = ds.getConnection();
>> if (conn != null) {
>> boolean isUserExists =
>>PortalUserDB.isUser(conn, userName, userPass);
>> 
>> 
>> conn.close();
>> }
>> 
>> 
>>
>> }
>>}
>>
>>public static boolean isUser(Connection conn, String userName, String
>>userPass)
>> throws SQLException, IOException {
>>
>> String query = "SELECT user_name FROM admin_user " +
>>"WHERE user_name = ? " +
>>"AND user_pass = ?";
>>
>> boolean isUserExists = false;
>>
>> try {
>> PreparedStatement pstmt = conn.prepareStatement(query);
>> pstmt.setString(1, userName);
>> pstmt.setString(2, userPass);
>>
>> ResultSet rs = pstmt.executeQuery();
>>
>> isUserExists = rs.next();
>>
>> rs.close();
>> rs = null;
>> pstmt.close();
>> pstmt = null;
>>
>> } catch (SQLException sqle) {
>> PortalLog.addLogLine("Class: PortalUserDB, Method:
>>isUser. SQL Exception:" + sqle, userName);
>> }
>>
>> return isUserExists;
>>}
>>
>>Thanks,
>>Veso
>>
>>-
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]

org/apache/jk/common/ChannelSocket.processConnection INFO: connection timeout rached.

[Victor Gonzalez]

Hi guys,
  Well, I will go to here point (alone, culeros!) but, I don't know
which parameter respect the timeout is necessary modify, if anyone is
very gentle to tell me, I will be very thankful, and I promise a cool
bear.

Regards,

I have...

W2k
Tomcat 4.1.18
IIS 5.0
SQL Server
Tomcat - SQL Server with jtds0.5.1
Tomcat - IIS with isapi_redirect.dll


Victor Gonzalez
***
PD. The info message is only the message subject.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

connection timeout problem -- apache1.3/mod_ssl/mod_jk2/tomcat 4.1.18

[SSchaubach]

my session is expiring with the following message:

==> stderr.log <==
Feb 4, 2003 12:01:38 PM org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached

Is there a way to extend the session timout on jk2 ??

here is my worker2.properties (fyi, we are not load balancing through jk2)


#
#   workers2.properties

[logger]
level=DEBUG

[config:]
file=/etc/httpd/conf/workers2.properties
debug=0
debugEnv=0

[uriMap:]
info=Maps the requests. Options: debug
debug=0

# Alternate file logger
[logger.file:0]
level=DEBUG
file=/var/log/httpd/jk2.log

[shm:]
info=Scoreboard. Required for reconfiguration and status with multiprocess
servers
file=/var/run/jk2.shm
size=100
debug=0
disabled=0

[workerEnv:]
info=Global server options
timing=1
debug=0

[channel.socket:10.3.17.131:8009]
info=Ajp13 forwarding over socket
debug=0
tomcatId=10.3.17.131:8009

[status:]
info=Status worker, displays runtime informations

[uri:/jkstatus/*]
info=Display status information and checks the config file for changes.
group=status:

#mappings
##
[uri:/*.jsp]
worker=ajp13:10.3.17.131:8009
[uri:/*.do]
worker=ajp13:10.3.17.131:8009
[uri:/*.info]
worker=ajp13:10.3.17.131:8009
[uri:/*.policy]
worker=ajp13:10.3.17.131:8009
[uri:/sqweb3/]
worker=ajp13:10.3.17.131:8009

jk "connection timeout reached"

[Nick Wesselman]

I'm seeing a lot of messages like this in my catalina.out with TC 
4.1.18.

Jan 16, 2003 3:20:40 PM org.apache.jk.common.ChannelSocket 
processConnection
INFO: connection timeout reached
Jan 16, 2003 3:20:40 PM org.apache.jk.common.ChannelSocket 
processConnection
INFO: connection timeout reached
Jan 16, 2003 3:20:40 PM org.apache.jk.common.ChannelSocket 
processConnection
INFO: server has been restarted or reset this connection

First off, do I need to worry about these? Second, if not, how can I 
disable them? I have debug="0" for everything in my server.xml.

Nick Wesselman
Digital Visions, Inc.


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: ConnectionPool with Oracle - connection timeout

[Raible, Matt]

This works though! ;-)

I got this syntax off this list for configuring an Oracle JDBCRealm.

-Original Message-
From: Filip Hanik [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 9:42 AM
To: Tomcat Users List
Subject: RE: ConnectionPool with Oracle - connection timeout


jdbc:oracle:thin:username/password@host:1521:sid

is an invalid URL. password doesn't belong in the url
at least I don't think so :)
Filip



~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
www.filip.net 

>-Original Message-
>From: Raible, Matt [mailto:[EMAIL PROTECTED]]
>Sent: Friday, January 17, 2003 8:31 AM
>To: 'Tomcat Users List'
>Subject: ConnectionPool with Oracle - connection timeout
>
>
>I am using Tomcat's JDBCRealm as well as a DBCP Connection pool.  I am
>connecting to Oracle 9, and everything works fine - for about 24 hours.
>I've experienced this with MySQL and adding autoReconnect=true to the
>connectionURL fixed the problem.  However, adding this to Oracle's
>connectionURL causes a "Cannot load JDBC driver class 'null'".
>
>My connectionURL is:
>
>jdbc:oracle:thin:username/password@host:1521:sid
>
>Thanks,
>
>Matt
>
>
>--
>To unsubscribe, e-mail:   
><mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: 
><mailto:[EMAIL PROTECTED]>
>
>

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: ConnectionPool with Oracle - connection timeout

[Filip Hanik]

jdbc:oracle:thin:username/password@host:1521:sid

is an invalid URL. password doesn't belong in the url
at least I don't think so :)
Filip



~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
www.filip.net 

>-Original Message-
>From: Raible, Matt [mailto:[EMAIL PROTECTED]]
>Sent: Friday, January 17, 2003 8:31 AM
>To: 'Tomcat Users List'
>Subject: ConnectionPool with Oracle - connection timeout
>
>
>I am using Tomcat's JDBCRealm as well as a DBCP Connection pool.  I am
>connecting to Oracle 9, and everything works fine - for about 24 hours.
>I've experienced this with MySQL and adding autoReconnect=true to the
>connectionURL fixed the problem.  However, adding this to Oracle's
>connectionURL causes a "Cannot load JDBC driver class 'null'".
>
>My connectionURL is:
>
>jdbc:oracle:thin:username/password@host:1521:sid
>
>Thanks,
>
>Matt
>
>
>--
>To unsubscribe, e-mail:   
><mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: 
><mailto:[EMAIL PROTECTED]>
>
>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

ConnectionPool with Oracle - connection timeout

[Raible, Matt]

I am using Tomcat's JDBCRealm as well as a DBCP Connection pool.  I am
connecting to Oracle 9, and everything works fine - for about 24 hours.
I've experienced this with MySQL and adding autoReconnect=true to the
connectionURL fixed the problem.  However, adding this to Oracle's
connectionURL causes a "Cannot load JDBC driver class 'null'".

My connectionURL is:

jdbc:oracle:thin:username/password@host:1521:sid

Thanks,

Matt


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

"connection timeout reached"

[Nick Wesselman]

I'm seeing a lot of messages like this in my catalina.out with TC 
4.1.18.

Jan 16, 2003 3:20:40 PM org.apache.jk.common.ChannelSocket 
processConnection
INFO: connection timeout reached
Jan 16, 2003 3:20:40 PM org.apache.jk.common.ChannelSocket 
processConnection
INFO: connection timeout reached
Jan 16, 2003 3:20:40 PM org.apache.jk.common.ChannelSocket 
processConnection
INFO: server has been restarted or reset this connection

First off, do I need to worry about these? Second, if not, how can I 
disable them? I have debug="0" for everything in my server.xml.

Nick Wesselman
Digital Visions, Inc.


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Request/Connection Timeout

[Ralph Einfeldt]

Multipart responses are nice, if you can make shure that 
all clients have a browser that support this. (Like in an 
intra- or extranet).

Have also a look at:
http://www.pushlets.com

Especially:
http://www.pushlets.com/pushlet/examples/basics/index.html

> -Original Message-
> From: Tim Funk [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 11, 2002 4:37 PM
> To: Tomcat Users List
> Subject: Re: Request/Connection Timeout
> 
> Or you can use a multipart response  where the first part(s) are 
> messages saying work is being done.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Request/Connection Timeout

[GUNTURU, SRINIVAS [AG-Contractor/1000]]

Thanks to everyone for their responses.

I probably should have mentioned a little bit about our application
architecture.  The client is a Java Applet and all requests to server are
made using Java HttpConnection.  We have not had this problem when we ran on
JRun.  At times, we had a request run for 4+ hours and still came back with
results.  Only switching to Tomcat put the 5 minute restriction on us.  The
application is used by scientists and depending on number of datapoints they
select, the analysis could run well over an hour at times. As you can see,
there is no web page involved to keep refreshing.  True, we could redesign
our application if we have time and money.

However, I am looking for some configuration change that would help me solve
this problem quickly.

-Original Message-
From: Sexton, George [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 9:55 AM
To: Tomcat Users List
Subject: RE: Request/Connection Timeout


As others have said, you need to re-design your app. Personally, I would
initiate the computation in a background thread and mail the results to the
user as a PDF document. Further, I would use  a queue design so that only
one computation is running at a time. What will your app do if the user hits
back, and keeps re-submitting? What will your app do if Monday morning, 40
managers come in and request a big report?

George Sexton
MH Software, Inc.
Home of Connect Daily Web Calendar Software
http://www.mhsoftware.com/connectdaily.htm
Voice: 303 438 9585


-Original Message-
From: GUNTURU, SRINIVAS [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]]
Sent: 11 December, 2002 8:28 AM
To: '[EMAIL PROTECTED]'
Subject: Request/Connection Timeout


Hi,

We are using Tomcat 4.0.4 on Apache.  Right now when we have a request that
takes longer than 300 seconds(5 minutes), connections are timing out and we
are getting various errors.  How do we go about increasing this timeout so
that the request does not timeout.  Unfortunately, The analysis that runs on
the server is very computational intensive and we have done a lot of tuning
and most of the times it does run under 5 minutes however depending on
server load and database load we do run over 5 minutes frequently and error
out.  Ideally, we would like to not have this restriction.  I have searched
in the archives and Tomcat documentation and have not found anything.

Thanks for your help.

Srinivas

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Request/Connection Timeout

[Boris Folgmann]

Hari Venkatesan wrote:
> You can set session time outs in Web.xml file
> 
> Hari

This is for the automatic cleanup of beans in the session context.
This has nothing to do with HTTP timeouts.

-- 
Dipl.-Inf. Boris Folgmann   mailto:[EMAIL PROTECTED]
Folgmann IT-Consulting  http://www.folgmann.de


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Request/Connection Timeout

[Sexton, George]

As others have said, you need to re-design your app. Personally, I would
initiate the computation in a background thread and mail the results to the
user as a PDF document. Further, I would use  a queue design so that only
one computation is running at a time. What will your app do if the user hits
back, and keeps re-submitting? What will your app do if Monday morning, 40
managers come in and request a big report?

George Sexton
MH Software, Inc.
Home of Connect Daily Web Calendar Software
http://www.mhsoftware.com/connectdaily.htm
Voice: 303 438 9585


-Original Message-
From: GUNTURU, SRINIVAS [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]]
Sent: 11 December, 2002 8:28 AM
To: '[EMAIL PROTECTED]'
Subject: Request/Connection Timeout


Hi,

We are using Tomcat 4.0.4 on Apache.  Right now when we have a request that
takes longer than 300 seconds(5 minutes), connections are timing out and we
are getting various errors.  How do we go about increasing this timeout so
that the request does not timeout.  Unfortunately, The analysis that runs on
the server is very computational intensive and we have done a lot of tuning
and most of the times it does run under 5 minutes however depending on
server load and database load we do run over 5 minutes frequently and error
out.  Ideally, we would like to not have this restriction.  I have searched
in the archives and Tomcat documentation and have not found anything.

Thanks for your help.

Srinivas

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Request/Connection Timeout

[Tim Funk]

Personally - I would ...

- first create servlet which starts the computational work in a new thread.
- the servlet then redirects to another page which can monitor the 
progress of the computational work (and does a meta refresh every few 
seconds)
- when the computational work is done - redirect to your real results

Or you can use a multipart response  where the first part(s) are 
messages saying work is being done. Get a demo of Keynote web monitoring 
services for a similar concept.

Good luck, tasks like this are always a pain in the rear.

-Tim

GUNTURU, SRINIVAS [AG-Contractor/1000] wrote:
Hi,

We are using Tomcat 4.0.4 on Apache.  Right now when we have a request that
takes longer than 300 seconds(5 minutes), connections are timing out and we
are getting various errors.  How do we go about increasing this timeout so
that the request does not timeout.  Unfortunately, The analysis that runs on
the server is very computational intensive and we have done a lot of tuning
and most of the times it does run under 5 minutes however depending on
server load and database load we do run over 5 minutes frequently and error
out.  Ideally, we would like to not have this restriction.  I have searched
in the archives and Tomcat documentation and have not found anything.

Thanks for your help.

Srinivas

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 






--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Request/Connection Timeout

[Hari Venkatesan]

In Server.xml file you have connection time out for each of the
connector class. Also if you have configured connection pools in
server.xml you can increase  the maxwait parameter value.

Hari

-Original Message-
From: GUNTURU, SRINIVAS [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, December 11, 2002 10:36 AM
To: 'Tomcat Users List'
Subject: RE: Request/Connection Timeout

Thanks for the quick response Hari.  But, It's not the session that is
timing out.  It is the request that is timing out though the server is
still
working on the request.  Hope this helps.

-Original Message-
From: Hari Venkatesan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 9:34 AM
To: Tomcat Users List
Subject: RE: Request/Connection Timeout


You can set session time outs in Web.xml file

Hari

-Original Message-
From: GUNTURU, SRINIVAS [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, December 11, 2002 10:28 AM
To: '[EMAIL PROTECTED]'
Subject: Request/Connection Timeout

Hi,

We are using Tomcat 4.0.4 on Apache.  Right now when we have a request
that
takes longer than 300 seconds(5 minutes), connections are timing out and
we
are getting various errors.  How do we go about increasing this timeout
so
that the request does not timeout.  Unfortunately, The analysis that
runs on
the server is very computational intensive and we have done a lot of
tuning
and most of the times it does run under 5 minutes however depending on
server load and database load we do run over 5 minutes frequently and
error
out.  Ideally, we would like to not have this restriction.  I have
searched
in the archives and Tomcat documentation and have not found anything.

Thanks for your help.

Srinivas

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Request/Connection Timeout

[Ralph Einfeldt]

I would recommend that you redesign your app.

There are request timeouts on several levels (Browsers, 
proxies, caches, ...), so changing such value just in 
tomcat may not help you.

Just one solution:

  Encapsulate the processing in bean.

  Start the processing in a seperate thread.
  Set the refresh meta tag in html to refresh the page
  every n seconds.

  For each refresh-request use the bean to find out the 
  current state of the processing.

  Report the state to the user.

  If the bean is ready show the result.


> -Original Message-
> From: GUNTURU, SRINIVAS [AG-Contractor/1000]
> [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 11, 2002 4:28 PM
> To: '[EMAIL PROTECTED]'
> Subject: Request/Connection Timeout
> 
> How do we go about increasing this timeout so
> that the request does not timeout.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Request/Connection Timeout

[GUNTURU, SRINIVAS [AG-Contractor/1000]]

Thanks for the quick response Hari.  But, It's not the session that is
timing out.  It is the request that is timing out though the server is still
working on the request.  Hope this helps.

-Original Message-
From: Hari Venkatesan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 9:34 AM
To: Tomcat Users List
Subject: RE: Request/Connection Timeout


You can set session time outs in Web.xml file

Hari

-Original Message-
From: GUNTURU, SRINIVAS [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, December 11, 2002 10:28 AM
To: '[EMAIL PROTECTED]'
Subject: Request/Connection Timeout

Hi,

We are using Tomcat 4.0.4 on Apache.  Right now when we have a request
that
takes longer than 300 seconds(5 minutes), connections are timing out and
we
are getting various errors.  How do we go about increasing this timeout
so
that the request does not timeout.  Unfortunately, The analysis that
runs on
the server is very computational intensive and we have done a lot of
tuning
and most of the times it does run under 5 minutes however depending on
server load and database load we do run over 5 minutes frequently and
error
out.  Ideally, we would like to not have this restriction.  I have
searched
in the archives and Tomcat documentation and have not found anything.

Thanks for your help.

Srinivas

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Request/Connection Timeout

[Hari Venkatesan]

You can set session time outs in Web.xml file

Hari

-Original Message-
From: GUNTURU, SRINIVAS [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, December 11, 2002 10:28 AM
To: '[EMAIL PROTECTED]'
Subject: Request/Connection Timeout

Hi,

We are using Tomcat 4.0.4 on Apache.  Right now when we have a request
that
takes longer than 300 seconds(5 minutes), connections are timing out and
we
are getting various errors.  How do we go about increasing this timeout
so
that the request does not timeout.  Unfortunately, The analysis that
runs on
the server is very computational intensive and we have done a lot of
tuning
and most of the times it does run under 5 minutes however depending on
server load and database load we do run over 5 minutes frequently and
error
out.  Ideally, we would like to not have this restriction.  I have
searched
in the archives and Tomcat documentation and have not found anything.

Thanks for your help.

Srinivas

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Request/Connection Timeout

[GUNTURU, SRINIVAS [AG-Contractor/1000]]

Hi,

We are using Tomcat 4.0.4 on Apache.  Right now when we have a request that
takes longer than 300 seconds(5 minutes), connections are timing out and we
are getting various errors.  How do we go about increasing this timeout so
that the request does not timeout.  Unfortunately, The analysis that runs on
the server is very computational intensive and we have done a lot of tuning
and most of the times it does run under 5 minutes however depending on
server load and database load we do run over 5 minutes frequently and error
out.  Ideally, we would like to not have this restriction.  I have searched
in the archives and Tomcat documentation and have not found anything.

Thanks for your help.

Srinivas

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

URL connection timeout

[Drinkwater, GJ (Glen)]

Hi

Is there any way to specify a timeout for a URL connection with tomcat. Is
there something in the server.xml file???

Glen


--
To unsubscribe, e-mail:   
For additional commands, e-mail: