cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathaniel Alfred" <>
Subject RE: connection pool fail over
Date Wed, 29 Jun 2005 15:16:15 GMT
You are probably better off to write your own meta connection pool manager as a layer between
Cocoon and the actual connection pools.  

Network problems usually mean that you connection will get stuck waiting for a long timeout
instead of returning an error immediately.  In that case, you soon run out of request handling
thread.  To avoid that, your meta pool manager can race the underlying pools in detached threads
against each other and hand the first working connection to the application.

HTH, Alfred.  

-----Original Message-----
From: Rui Alberto []
Sent: Mittwoch, 29. Juni 2005 16:56
Subject: connection pool fail over

I have three replicated databases and a connection pool to each database
The network to database instances is a little unstable, so I want to
check at least one connection in the pool before passing pool identifier
to SQLTransformer. If connection is broken, I wanna try next other pool.
Does anyone know if there's a simple way to handle this situation?
Should I write a selector, or an input module maybe or an action?! 
Writing a selector or action implies an exhaustive sitemap! :|

Any idea?

Thanks for any help,

This message is for the named person's use only. It may contain confidential, proprietary
or legally privileged information. No confidentiality or privilege is waived or lost by any
mistransmission. If you receive this message in error, please notify the sender urgently and
then immediately delete the message and any copies of it from your system. Please also immediately
destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the intended recipient.
The sender's company reserves the right to monitor all e-mail communications through their
networks. Any views expressed in this message are those of the individual sender, except where
the message states otherwise and the sender is authorised to state them to be the views of
the sender's company.

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

View raw message