Issues

Issue #41 resolved

The transaction operation cannot be performed because there are pending requests working on this transaction.

Michael Manfre
repo owner created an issue

When using MARS support, uses_savepoints could result in the following DatabaseError. The database session store is not the primary transaction.

Traceback (most recent call last):

  File "D:\www\qa\env\lib\site-packages\django\core\handlers\base.py", line 187, in get_response
    response = middleware_method(request, response)

  File "D:\www\qa\env\lib\site-packages\django\contrib\sessions\middleware.py", line 38, in process_response
    request.session.save()

  File "D:\www\qa\env\lib\site-packages\django\contrib\sessions\backends\db.py", line 55, in save
    sid = transaction.savepoint(using=using)

  File "D:\www\qa\env\lib\site-packages\django\db\transaction.py", line 172, in savepoint
    return connection.savepoint()

  File "D:\www\qa\env\lib\site-packages\django\db\backends\__init__.py", line 264, in savepoint
    self._savepoint(sid)

  File "D:\www\qa\env\lib\site-packages\django\db\backends\__init__.py", line 79, in _savepoint
    self.cursor().execute(self.ops.savepoint_create_sql(sid))

  File "D:\www\qa\env\lib\site-packages\sqlserver_ado\dbapi.py", line 532, in execute
    self._execute_command()

  File "D:\www\qa\env\lib\site-packages\sqlserver_ado\dbapi.py", line 446, in _execute_command
    self._raiseCursorError(klass, _message)

  File "D:\www\qa\env\lib\site-packages\sqlserver_ado\dbapi.py", line 384, in _raiseCursorError
    eh(self.connection, self, errorclass, errorvalue)

  File "D:\www\qa\env\lib\site-packages\sqlserver_ado\dbapi.py", line 99, in standardErrorHandler
    raise errorclass(errorvalue)

DatabaseError: (-2147352567, 'Exception occurred.', (0, u'Microsoft SQL Server Native Client 10.0', u'The transaction operation cannot be performed because there are pending requests working on this transaction.', None, 0, -2147217900), None)
Command:
SAVE TRANSACTION [s3568_x1]
Parameters:
[]

Comments (4)

  1. Log in to comment