Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bug: sync db lock is not released when an db error occurs during sync #34

Open
peterhoepfl opened this issue Jun 2, 2023 · 1 comment
Open

Bug: sync db lock is not released when an db error occurs during sync #34

peterhoepfl opened this issue Jun 2, 2023 · 1 comment
Assignees
@peterhoepfl

Comments

@peterhoepfl
Copy link
Collaborator

When an error occurs during sync and the transaction is rolled back the dblock is not released although it should.
Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block

As consequence transaction in MirrorStratgey.run() must be split.
@peterhoepfl peterhoepfl self-assigned this Jun 2, 2023
@peterhoepfl
Copy link
Collaborator Author

Solution ist to set autocommit to true before calling the releasedblock method.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@peterhoepfl peterhoepfl

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

When branches are created from issues, their pull requests are automatically linked.

bugfix/34-sync-db-lock-is-not-released aservo/ldap-crowd-adapter
1 participant
@peterhoepfl