I have been testing automatic database reconnection by pulling a network
cable out and putting it back in again.  I observed that when a client
thread reconnects it does not necessarily reconnect to its old thread on
the server.  (In my example I had two client threads.  They both
disconnected when pings were not received.  When I plugged the network
cable back in I noticed them reconnecting to each other's original
threads on the server.)

Is this behaviour by design?  If so I may need to be more careful with
my thread-global variables.


  Oliver

Oliver,

<< I have been testing automatic database reconnection by pulling a network
cable out and putting it back in again.  I observed that when a client
thread reconnects it does not necessarily reconnect to its old thread on the
server.  (In my example I had two client threads.  They both disconnected
when pings were not received.  When I plugged the network cable back in I
noticed them reconnecting to each other's original threads on the server.)

Is this behaviour by design?  If so I may need to be more careful with my
thread-global variables. >>

Yes, unfortunately we cannot control which thread ids are assigned to new
threads, so we simpy piggy-back the existing session on to the newly-created
thread (or re-used thread, in the case of the thread cache being used).

--
Tim Young
Elevate Software
www.elevatesoft.com