Replication+CBLLiveQuery too many Database Busy messages

[Frederic Yesid Peña Sánchez]

Hi.

We currently use a lot of CBLLiveQueries to keep several TableViews updated on multiple ViewControllers.

We are noticing frequent issues, when the app is open but idle (no user interaction), the replication starts and our logs show a lot of Database Busy messages.

Running 1.0beta2 for iOS

[Frederic Yesid Peña Sánchez]

It's possible to enqueue all CBLLiveQuery and replication on the same serial dispatch queue??

[Jens Alfke]

On Feb 27, 2014, at 9:45 AM, Frederic Yesid Peña Sánchez <freder...@gmail.com> wrote:

We are noticing frequent issues, when the app is open but idle (no user interaction), the replication starts and our logs show a lot of Database Busy messages.

Those messages mean you’re using CBL objects on multiple threads. Don’t do that! The API is not thread-safe and you’re likely to crash.

It's possible to enqueue all CBLLiveQuery and replication on the same serial dispatch queue??

Yes, but you have to first set the CBLManager’s dispatchQueue property to the queue you want to use it on, and then all access to the objects has to be from that queue.

There are instructions about concurrent access in the docs.

—Jens