I've been using Sybase with Coccon for sometime. Resently we added a DB2 connection to
the pools defined in cocoon.conf and although it worked for awhile, there seems to be a
problem, perhaps with the way the DB2 driver behaves.
Under some unknown, at least not exactly, conditions, when the DB2 database is brought
down, connections held in cocoon's pool become exhausted. Users then get no response
while coccoon waits for a connection to become available.
The way cocoon.xconf works, there appears to be no way to define a timeout. Is
there?
Is there a way to force connections closed after a period of inactivity?
Is there a way to re-initialize a pool after it gets into this state, short or reloading
the cocoon context?
The Sybase connections seem to recover fine when anything happens to the Sybase
servers.
I did find these posts which appear related:
http://www.planetcocoon.com/node/4831
However, there appears to be no way to make the needed settings in cocoon.xconf.
Does anyone know if DB2 can be configured in some way to avoid this perhaps?
Thanks
--
The ODS Companies
Jeff Sexton
Information Services
(503) 228-6554 x1026
http://www.odscompanies.com
This message is intended for the sole use of the individual and entity
to whom it is addressed, and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If you are
not the intended addressee, nor authorized to receive for the intended
addressee, you are hereby notified that you may not use, copy, disclose
or distribute to anyone the message or any information contained in the
message. If you have received this message in error, please immediately
advise the sender by reply email and delete the message.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
