Hi everyone,
I'm encountering problems with transactions when using ZODB. On very rare
occasions the primary connection seems to have dumped the transaction
manager before running the request callbacks. As far as I understand the
code, transaction_manager on the primary connection is set to None once
it's finished.
Since I haven't seen this problem before and I've been running ZODB
instances with roughly the same code for 5 years I'm guessing something
else is new.
Does anyone have any advice on what could be going on?
Some relevant(?) versions:
pyramid_zodbconn 0.7
pyramid_tm 1.0.2
ZODB 4.4.4
transaction 1.7.0
Pyramid 1.7.3
The only pattern I've really found seems to be:
- It always happens on aborts
- It seems to be during some server load
- It only seems to happen during requests that only read data
If anyone have some insight in this I'd really appreciate it.
All the best,
Robin
ps
Basically logged exceptions will look something like this:
<...>
File "./eggs/pyramid-1.7.3-py2.7.egg/pyramid/request.py", line 147, in
_process_finished_callbacks
callback(self)
File
"./eggs/pyramid_zodbconn-0.7-py2.7.egg/pyramid_zodbconn/__init__.py", line
56, in finished
primary_conn.transaction_manager.abort()
AttributeError: 'NoneType' object has no attribute 'abort'
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pylons-devel+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/pylons-devel.
For more options, visit https://groups.google.com/d/optout.
