Hello,

I'm using pound as a load balancer in a 2 tier application which uses a 
custom rpc protocol over HTTP as its communication layer.  A 
transaction in our system can occur over several requests through the 
communication layer and as such we need to maintain session on a per 
transaction basis.  Currently we are accomplishing this using a Cookie 
(e.g. txn=be0fda342-003xx03).  This works majority of the time, but 
occasionally transaction request gets routed to the wrong balanced 
server.  In addition, I've found that the sessions don't seem to get 
distributed evenly, eventually all requests start hitting one server (I 
have two servers setup in my test environment).

Has anyone else seen issues like these?  I'm using pound 1.4, but have 
tried pound 1.5 and still experience the same issues.

Alex

On Friday 07 November 2003 22:33, Alexander Southgate wrote:[...]

Hi Alex

We haven't observed this in our installation, but I could imagine it happening 
if one of your back-end servers is very slow to/overloaded: if Pound decides 
it is "dead" it will re-route requests to the other server and invalidate its 
sessions. Have a look in the logs if some messages to that effect are
shown.[...]