On Thu, Aug 13, 2009 at 5:45 PM, Ross J. Reedstromreeds...@rice.edu wrote:
On Wed, Aug 12, 2009 at 08:57:39PM -0300, Rudá Porto Filgueiras wrote:
On Wed, Aug 12, 2009 at 8:20 PM, Shane Hathawaysh...@hathawaymix.org wrote:
A concurrent pack might provide another explanation. Have you ever
On Wed, August 12, 2009 22:23, Rudá Porto Filgueiras wrote:
I begin to use RelStorage in a production site with Plone 2.5.
Everything was running without failures since 01 august 2009.
But today after a failure in tpc_abort, all instances conneceted to
MySQL can't acquire commit lock.
On Wed, Aug 12, 2009 at 5:35 PM, Jürgen
Herrmannjuergen.herrm...@xlhost.de wrote:
On Wed, August 12, 2009 22:23, Rudá Porto Filgueiras wrote:
I begin to use RelStorage in a production site with Plone 2.5.
Everything was running without failures since 01 august 2009.
But today after a failure
Rudá Porto Filgueiras wrote:
(...)
Module relstorage.adapters.mysql, line 506, in start_commit
Module relstorage.adapters.mysql, line 672, in _hold_commit_lock
StorageError: Unable to acquire commit lock
I solve the problem restarting all instances, and the site became
operational
On Wed, Aug 12, 2009 at 8:20 PM, Shane Hathawaysh...@hathawaymix.org wrote:
Rudá Porto Filgueiras wrote:
(...)
Module relstorage.adapters.mysql, line 506, in start_commit
Module relstorage.adapters.mysql, line 672, in _hold_commit_lock
StorageError: Unable to acquire commit lock
I solve
Rudá Porto Filgueiras wrote:
Yes, it was closed in the midle of transaction, but if you are sure
there is nothing to do with RelStorage and there is no possible or
workaround to the RelStoratge MySQL adapter to lead with MySQL bugs or
resistent do to network failures and recover from this
