Re: [ZODB-Dev] "tid to old for invq" in zeo server logs?

2009-10-21 Thread Jim Fulton
On Tue, Oct 20, 2009 at 4:00 PM, Chris Withers wrote: > Jim Fulton wrote: >> >> It means that the server wasn't able to provide "quick" invalidations >> because a client was disconnected too long.  The message isn't very >> well worded, even aside from the misspelling. > > Has that been fixed in t

Re: [ZODB-Dev] "tid to old for invq" in zeo server logs?

2009-10-20 Thread Chris Withers
Jim Fulton wrote: > It means that the server wasn't able to provide "quick" invalidations > because a client was disconnected too long. The message isn't very > well worded, even aside from the misspelling. Has that been fixed in the latest zodb? If not, if I get a chance, I'm happy to patch...

Re: [ZODB-Dev] "tid to old for invq" in zeo server logs?

2009-10-20 Thread Jim Fulton
On Mon, Oct 19, 2009 at 6:38 AM, Chris Withers wrote: > Hi All, > > I saw a few entries like these in the event log of a storage server that > stopped responding for a couple of minutes: > > INFO ZEO.StorageServer (30332) tid to old for invq 252618838173181593 < > 252618856850589832 > -- > INF

[ZODB-Dev] "tid to old for invq" in zeo server logs?

2009-10-19 Thread Chris Withers
Hi All, I saw a few entries like these in the event log of a storage server that stopped responding for a couple of minutes: INFO ZEO.StorageServer (30332) tid to old for invq 252618838173181593 < 252618856850589832 -- INFO ZEO.StorageServer (30332) tid to old for invq 252618838177204172 <