ZODB bug? (Surrogate instance '_p_oid')
Hello everybody. Can somebody explain what this error means? I think this sounds like a bug in ZODB somewhere... :( Zope: 2.6.1 OS: Linux SuSE 8.0 Pro ============================================== Traceback (innermost last): * Module ZPublisher.Publish, line 102, in publish * Module Zope.App.startup, line 200, in commit * Module ZODB.Transaction, line 261, in commit * Module ZODB.Transaction, line 392, in _commit_error AttributeError: Surrogate instance has no attribute '_p_oid' ============================================== -- Regards, Bogdan If nothing else helps, read the documentation.
Bo M. Maryniuck wrote:
Hello everybody.
Can somebody explain what this error means? I think this sounds like a bug in ZODB somewhere... :(
Dunno what a 'Surrogate' is, but that doesn't sound like part of ZODB and it is likely where your error lies. What Zope version/Products/etc are you using? Chris
On Monday 31 March 2003 11:28, Chris Withers wrote:
Dunno what a 'Surrogate' is, but that doesn't sound like part of ZODB and it is likely where your error lies.
What Zope version/Products/etc are you using?
This appears I don't know why. The only thing I know it is from ZODB (probably). After error appears, Zope does not responds anymore untill I restart it. As I mentioned, I use Zope 2.6.1. Products? Absolutely nothing special. Standard. -- Regards, Bogdan Any sufficiently advanced Operating System is indistinguishable from Linux. -- Jim Dennis
hmm... surrogate is used by the rdb txn integration.. what version of zope and what version of which da are you using? -haz Bo M. Maryniuck wrote:
Hello everybody.
Can somebody explain what this error means? I think this sounds like a bug in ZODB somewhere... :(
Zope: 2.6.1 OS: Linux SuSE 8.0 Pro
============================================== Traceback (innermost last):
* Module ZPublisher.Publish, line 102, in publish * Module Zope.App.startup, line 200, in commit * Module ZODB.Transaction, line 261, in commit * Module ZODB.Transaction, line 392, in _commit_error
AttributeError: Surrogate instance has no attribute '_p_oid' ==============================================
On Monday 31 March 2003 14:14, hazmat wrote:
what version of zope and what version of which da are you using? Sorry? I already mentioned it TWICE. :-) Zope 2.6.1. So I use
Z O P E TWO DOT SIX DOT ONE
Can somebody explain what this error means? I think this sounds like a bug in ZODB somewhere... :(
Zope: 2.6.1 ^^^^^^^^^^^
:-) -- Regards, Bogdan My mail reader can beat up your mail reader.
Bo M. Maryniuck wrote:
On Monday 31 March 2003 14:14, hazmat wrote:
what version of zope and what version of which da are you using?
Sorry? I already mentioned it TWICE. :-) Zope 2.6.1. So I use
Z O P E TWO DOT SIX DOT ONE
ok. so let me ask the second part of the question above again, what version (of i assume the oracle DA) are you using?
Can somebody explain what this error means? I think this sounds like a bug in ZODB somewhere... :(
Zope: 2.6.1
^^^^^^^^^^^
:-)
Bo M. Maryniuck wrote at 2003-3-31 10:34 +0200:
Can somebody explain what this error means? I think this sounds like a bug in ZODB somewhere... :(
Zope: 2.6.1 OS: Linux SuSE 8.0 Pro
============================================== Traceback (innermost last):
* Module ZPublisher.Publish, line 102, in publish * Module Zope.App.startup, line 200, in commit * Module ZODB.Transaction, line 261, in commit * Module ZODB.Transaction, line 392, in _commit_error
AttributeError: Surrogate instance has no attribute '_p_oid'
When an object needs to have special treatment at transaction commit/abort, it registers either itself or a surrogate object with the transaction. The transaction expects the object registered to have a "_p_jar" attribute. It calls this object's "tpc_begin/finish/vote/commit/abort" method when the transaction commits/aborts. When "_p_jar" is a ZODB connection (the most usual case), the connection expects the object to have a "_p_oid" attribute. Apparently, one of your objects registers a surrogate with a ZODB connection as "_p_jar" but without a "_p_oid". This is definitely a bug. You must find this object and fix its class. Dieter
On Monday 31 March 2003 22:43, Dieter Maurer wrote:
When "_p_jar" is a ZODB connection (the most usual case), the connection expects the object to have a "_p_oid" attribute.
Apparently, one of your objects registers a surrogate with a ZODB connection as "_p_jar" but without a "_p_oid". This is definitely a bug. You must find this object and fix its class.
I think this is ZOracleDA bug in Zope 2.6.x since there is no such stuff in 2.5.x. Thank you. -- Regards, Bogdan For Sale: Parachute. Only used once, never opened, small stain.
Bo M. Maryniuck wrote:
I think this is ZOracleDA bug in Zope 2.6.x since there is no such stuff in 2.5.x. Thank you.
For the record, ZOracleDA is not a standard part of Zoep and it would have made lfie easier had you mentioned you were using it, and what version you were using... cheers, Chris
On Monday 31 March 2003 9:43 pm, Dieter Maurer wrote:
Apparently, one of your objects registers a surrogate with a ZODB connection as "_p_jar" but without a "_p_oid".
ZODB was wrong to assume the presence of the _p_oid attribute. This has since been fixed. -- Toby Dickenson http://www.geminidataloggers.com/people/tdickenson
On Tuesday 01 April 2003 10:07, Toby Dickenson wrote:
ZODB was wrong to assume the presence of the _p_oid attribute. This has since been fixed.
Now it sounds much better for me. But I can't find a patch for Zope 2.6.1 Release? -- Regards, Bogdan Added mysterious, undocumented --scanflags and --fuzzy options. -- nmap 3.0 announcement
participants (5)
-
Bo M. Maryniuck -
Chris Withers -
Dieter Maurer -
hazmat -
Toby Dickenson