Hi All
 
Whenever I do any type of heavy (data) database query from my client through
the pound SSL server, it returns an error message. As of now, that's the
only thing stopping our company from putting the pound LB in production.
(NOTE* small database queries work fine through the LB pound.)
 
I get this error message on the client: "An internal server error occurred.
Please try again later."
 
On the POUND server log, I get this error message: "pound: (b7e21ba0) e500
response error read from 172.29.4.12:7777/GET /mkrrro/listMyLoadList.do
HTTP/1.1: Connection timed out (14.999 secs):"

In my pound config, I increased my timeout "CLIENT" to 120 seconds. I also
increased my "ALIVE" to 120 seconds. Still, not working. (If I remove the
pound SSL in front, the heavy (data) database queries work fine on the
servers.)
 
The Apache server on the backend web servers are set to 300 seconds. 
 
Again, this only happens when using pound. 
 
Any of you have ideas on how I can get pound to work with these heavy
database queries?
 
Thank you!
 
Anne

Hi Anne,

The correct parameter for BackEnd timeouts is the "TimeOut" parameter. Here is
a documentation snippet, you can find this by running "man pound" from your
shell.

        Alive value
              Specify how often Pound will check for resurected back-end hosts
(default: 30 seconds). In general,
              it is a good idea to set this as low as possible - it will find
resurected hosts  faster.  However,
              if you set it too low it will consume resources - so beware.

       Client value
              Specify  for  how  long Pound will wait for a client request
(default: 10 seconds). After this long
              has passed without the client sending any data Pound will close
the connection. Set  it  higher  if
              your  clients  time-out  on  a  slow  network or over-loaded
server, lower if you start getting DOS
              attacks or run into problems with IE clients.  This value can be
overridden for specific listeners.

       TimeOut value
              How  long  should  Pound  wait  for a response from the back-end
(in seconds). Default: 15 seconds.
              This value can be overridden for specific back-ends.

       ConnTO value
              How long should Pound wait for a connection to the back-end  (in 
seconds).  Default:  the  TimeOut
              value. This value can be overridden for specific back-ends.

- Chris

-----Original Message-----
From: Anne Moore [mailto:diabeticithink(at)yahoo.com]
Sent: Wednesday, April 07, 2010 8:05 PM
To: pound(at)apsis.ch
Subject: [Pound Mailing List] database queries not working

Hi All

Whenever I do any type of heavy (data) database query from my client through
the pound SSL server, it returns an error message. As of now, that's the
only thing stopping our company from putting the pound LB in production.
(NOTE* small database queries work fine through the LB pound.)

I get this error message on the client: "An internal server error occurred.
Please try again later."

On the POUND server log, I get this error message: "pound: (b7e21ba0) e500
response error read from 172.29.4.12:7777/GET /mkrrro/listMyLoadList.do
HTTP/1.1: Connection timed out (14.999 secs):"

In my pound config, I increased my timeout "CLIENT" to 120 seconds. I also
increased my "ALIVE" to 120 seconds. Still, not working. (If I remove the
pound SSL in front, the heavy (data) database queries work fine on the
servers.)

The Apache server on the backend web servers are set to 300 seconds.

Again, this only happens when using pound.

Any of you have ideas on how I can get pound to work with these heavy
database queries?

Thank you!

Anne



--
To unsubscribe send an email with subject unsubscribe to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.

[...]

Chris

I had no idea about that TimeOut value! You're awesome. You just saved us.

Thank you!

Anne

-----Original Message-----
From: Chris Morrow [mailto:cmorrow(at)verrus.com] 
Sent: Wednesday, April 07, 2010 11:58 PM
To: pound(at)apsis.ch
Subject: RE: [Pound Mailing List] database queries not working

Hi Anne,

The correct parameter for BackEnd timeouts is the "TimeOut" parameter. Here
is a documentation snippet, you can find this by running "man pound" from
your shell.

        Alive value
              Specify how often Pound will check for resurected back-end
hosts (default: 30 seconds). In general,
              it is a good idea to set this as low as possible - it will
find resurected hosts  faster.  However,
              if you set it too low it will consume resources - so beware.

       Client value
              Specify  for  how  long Pound will wait for a client request
(default: 10 seconds). After this long
              has passed without the client sending any data Pound will
close the connection. Set  it  higher  if
              your  clients  time-out  on  a  slow  network or over-loaded
server, lower if you start getting DOS
              attacks or run into problems with IE clients.  This value can
be overridden for specific listeners.

       TimeOut value
              How  long  should  Pound  wait  for a response from the
back-end (in seconds). Default: 15 seconds.
              This value can be overridden for specific back-ends.

       ConnTO value
              How long should Pound wait for a connection to the back-end
(in  seconds).  Default:  the  TimeOut
              value. This value can be overridden for specific back-ends.

- Chris

-----Original Message-----
From: Anne Moore [mailto:diabeticithink(at)yahoo.com]
Sent: Wednesday, April 07, 2010 8:05 PM
To: pound(at)apsis.ch
Subject: [Pound Mailing List] database queries not working

Hi All

Whenever I do any type of heavy (data) database query from my client through
the pound SSL server, it returns an error message. As of now, that's the
only thing stopping our company from putting the pound LB in production.
(NOTE* small database queries work fine through the LB pound.)

I get this error message on the client: "An internal server error occurred.
Please try again later."

On the POUND server log, I get this error message: "pound: (b7e21ba0) e500
response error read from 172.29.4.12:7777/GET /mkrrro/listMyLoadList.do
HTTP/1.1: Connection timed out (14.999 secs):"

In my pound config, I increased my timeout "CLIENT" to 120 seconds. I also
increased my "ALIVE" to 120 seconds. Still, not working. (If I remove the
pound SSL in front, the heavy (data) database queries work fine on the
servers.)

The Apache server on the backend web servers are set to 300 seconds.

Again, this only happens when using pound.

Any of you have ideas on how I can get pound to work with these heavy
database queries?

Thank you!

Anne



--
To unsubscribe send an email with subject unsubscribe to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.

[...]