ConflictErrors cause "Shouldn't load state for?"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope 2 |
Invalid
|
Medium
|
Unassigned |
Bug Description
Again, I'm the only one who sees these *schniff*
(and of the weirdies I've been reporting, these are the most frequent, still don't seem to cause much harm, but are a little disturbing)
------
2005-10-12T09:15:39 INFO(0) ZODB conflict error at
/VirtualHostBas
2005-10-
------
2005-10-12T09:15:43 INFO(0) ZODB conflict error at
/VirtualHostBas
(18 conflicts since startup at 2005-10-
------
2005-10-12T09:15:43 ERROR(200) ZODB Shouldn't load state for 0x9aaa86
when the connection is closed
------
2005-10-12T09:15:48 ERROR(200) ZODB Shouldn't load state for 0x9aaa86
when the connection is closed
------
2005-10-12T09:15:48 ERROR(200) ZODB Shouldn't load state for 0x660bab
when the connection is closed
------
Changed in zope2: | |
status: | Incomplete → Triaged |
I don't see anything in the report that suggests this is a Zope level problem and not application code.