Re: [Zope3-Users] Strange ZODB error
On Aug 10, 2007, at 2:30 AM, Christian Theune wrote: Am Donnerstag, den 09.08.2007, 09:52 -0400 schrieb Gary Poster: You probably need to find out what the object is for anyone to have a chance of helping. I usually just put a pdb in the ZODB that is triggered if there's an error here, and then start poking around. Using the postmortem debug publisher might work too, but it has caused enough problems for me in the past that I dropped it, myself. One way to do this is to use the http postmortem debugger server, especially helpful if you try to debug problems in code that is triggered many times in an app, but you only want to see the pdb when an error happens. That's what I meant by postmortem debugger publisher. I was being fuzzy: your terminology is correct. However, my observation stands. I know Jim likes it, among others, but I have found it to not work the way I want enough to be a nuisance. I seem to recall that this may be related to the ZODB connection being closed, but I could be remembering incorrectly. Gary ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Strange ZODB error
Am Donnerstag, den 09.08.2007, 09:52 -0400 schrieb Gary Poster: You probably need to find out what the object is for anyone to have a chance of helping. I usually just put a pdb in the ZODB that is triggered if there's an error here, and then start poking around. Using the postmortem debug publisher might work too, but it has caused enough problems for me in the past that I dropped it, myself. One way to do this is to use the http postmortem debugger server, especially helpful if you try to debug problems in code that is triggered many times in an app, but you only want to see the pdb when an error happens. Christian ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Strange ZODB error
You probably need to find out what the object is for anyone to have a chance of helping. I usually just put a pdb in the ZODB that is triggered if there's an error here, and then start poking around. Using the postmortem debug publisher might work too, but it has caused enough problems for me in the past that I dropped it, myself. Gary On Aug 9, 2007, at 9:44 AM, Hermann Himmelbauer wrote: Hi, After updating some z3c packages and changing some of my code, I receive a very strange traceback from Zope3: -- Traceback (most recent call last): File /local/home/dusty/Zope-3.4.0b1/lib/python/zope/publisher/ publish.py, line 138, in publish publication.afterCall(request, obj) File /local/home/dusty/Zope-3.4.0b1/lib/python/zope/app/ publication/browser.py, line 78, in afterCall super(BrowserPublication, self).afterCall(request, ob) File /local/home/dusty/Zope-3.4.0b1/lib/python/zope/app/ publication/zopepublication.py, line 175, in afterCall txn.commit() File /local/home/dusty/Zope-3.4.0b1/lib/python/transaction/ _transaction.py, line 325, in commit self._commitResources() File /local/home/dusty/Zope-3.4.0b1/lib/python/transaction/ _transaction.py, line 424, in _commitResources rm.commit(self) File /local/home/dusty/Zope-3.4.0b1/lib/python/ZODB/ Connection.py, line 524, in commit self._commit(transaction) File /local/home/dusty/Zope-3.4.0b1/lib/python/ZODB/ Connection.py, line 569, in _commit self._store_objects(ObjectWriter(obj), transaction) File /local/home/dusty/Zope-3.4.0b1/lib/python/ZODB/ Connection.py, line 596, in _store_objects p = writer.serialize(obj) # This calls __getstate__ of obj File /local/home/dusty/Zope-3.4.0b1/lib/python/ZODB/ serialize.py, line 407, in serialize return self._dump(meta, obj.__getstate__()) File /local/home/dusty/Zope-3.4.0b1/lib/python/ZODB/ serialize.py, line 416, in _dump self._p.dump(state) File copy_reg.py, line 69, in _reduce_ex raise TypeError, can't pickle %s objects % base.__name__ TypeError: can't pickle file objects -- I ran all tests of additional z3c/zc packages, all went well, so it seems there's something wrong in my code, however I don't see where. I don't use any file objects, so I'm clueless... Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Strange ZODB error - Solved: Zalchemy bug
Am Donnerstag, 9. August 2007 15:44 schrieb Hermann Himmelbauer: Hi, After updating some z3c packages and changing some of my code, I receive a very strange traceback from Zope3: Ah, after fiddling around I found out that the svn update of the zalchemy package resulted in this error. If somewhere in my code zalchemy is used, the TypeError emerges. It seems that recently there was a change to the zalchemy package (svn log): r78682 | zagy | 2007-08-08 10:53:01 +0200 (Mi, 08 Aug 2007) | 1 line using the threadlocal strategy of sqlalchemy instead of creating one engine per thread. This allows connection pooling for instance. I reverted zalchemy to an older version an all is well again. Once again it proves that updating only makes sense if an update is really necessary... ;-) Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
