Well, I can understand Tim's comment about droppings. This configuration has made a mockery of my weekend. >:-(
Looking on the bright side - it'll soon be Monday ;)
First an interesting data point.
Assume for now that I'm not naming my zeo-clients - this would be begging for disaster - but all
On Sun, 2004-07-25 at 12:43, Russ Ferriday wrote:
Assume for now that I'm not naming my zeo-clients - this would
bebegging for disaster - but all is not lost. For some arcane reason
Ihave not yet tracked down, after running my 2 clients under load,
Iget these...
-rw-r--r-- 1 plone staff
On Sun, 2004-07-25 at 14:06, Chris McDonough wrote:
Grrr... ok, here's the deal. zeo-client-name apparently no longer has
any effect on.. the ZEO client name. ;-) I have no idea when this
happened; I'm sure interested parties can spelunk the CVS logs to find
out.
FWIW, I have entered this
Brad Clements wrote at 2004-7-23 16:12 -0400:
On 23 Jul 2004 at 20:08, Dieter Maurer wrote:
The bad sequence can look as follows:
* Zope starts a request (and thereby a transaction)
* The request sends a modifying request to a relational database
* The connection is lost; the former
sathya wrote at 2004-7-23 18:00 -0500:
I dont see a data loss problem either (unless there are hardware failures)
If a connection is dropped due to inactivity it should not affect any
transactions going to occur in the future as a reconnect is issued
before submitted new transactions.
However,
Russ Ferriday wrote at 2004-7-25 17:43 +0100:
Well, I can understand Tim's comment about droppings. This
configuration has made a mockery of my weekend. :-(
Looking on the bright side - it'll soon be Monday ;)
First an interesting data point.
Assume for now that I'm not naming my zeo-clients -
On Sun, 2004-07-25 at 18:15, Dieter Maurer wrote:
The bug Chris mentioned and fixed by my patch (the CHANGES.txt
report for which Chris thought uninformative)...
The patch is appreciated though!
- C
___
Zope-Dev maillist - [EMAIL PROTECTED]
