I'm running SQLite 3.6.22 on Linux, with shared cache enabled and multiple
sqlite3 connections open from multiple threads (a dedicated connection in
each thread - no connection sharing between threads).
In one thread I'm executing a set of SQL statements, bracketed by BEGIN and
COMMIT. That set executes thousands of times without error. Then, out of
the blue, SQLite fails the COMMIT with the following message:
"cannot commit - no transaction is active"
Every indication is that no errors were encountered while executing the
statements in the set.
I recently moved up from 3.6.17 to pickup the FTS3 enhancements, and I can't
recall every having seen this message until I started running with 3.6.22.
In one case of the error, I am doing an insert into a FTS3 table. In
another case of the error, I'm doing a Select from the same FTS3 table.
What could cause a transaction to come to an arbitrary end before
encountering the COMMIT?
--
View this message in context:
http://old.nabble.com/Occasional-%22cannot-commit---no-transaction-is-active%22-tp27871274p27871274.html
Sent from the SQLite mailing list archive at Nabble.com.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
