[10.0]Could not acquire advisory lock about queue HOT 3 CLOSED

The interesting line is
odoo.addons.connector_odoo.components.backend_adapter: <traceback object at 0x7fc6bdb0a488>
The next line indicates that the job has been postponed, because of the error. The error being probably this Could not acquire advisory lock.

The WARNING line indicates that the job has been set on a channel root.odoo, but this channel has not been configured at the startup of the queue job runner. It will just execute it in in the root channel.

The last 3 lines are normal operations of the jobrunner.

Back to the advisory lock:

First you may want to show the full traceback in your logs, because <traceback object at 0x7fc6bdb0a488> is not very informative :)

The exporter tries to acquires the advisory lock here:
https://github.com/OCA/connector-odoo2odoo/pull/7/files#diff-490b3ec0560bd042a97411edb4d1e534R204

If it can't acquires it, it's probably because it has already been acquired by another transaction (but you may find another reason I guess). The purpose of this lock is to prevent 2 jobs to import the same record at the same time. The lock is set on a hash composed from attributes that define the uniqueness of a job (https://github.com/OCA/connector-odoo2odoo/pull/7/files#diff-490b3ec0560bd042a97411edb4d1e534R180). Are you sure the values you use here are unique?

Also, check if you don't have a staled transaction in postgres which would have kept the lock.

I don't see any issue in the queue, it's either in your setup, either in your implementation.

I find it weird that the exception is logged by odoo.addons.connector_odoo.components.backend_adapter, you should try to display the traceback.

from queue.

Thanks @guewen , I'll gonna give feedback on this

from queue.

Thanks @guewen you're right, a constraint was missing and I had duplicates in bindings !

from queue.