-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
Simple tasklist using custom postgreSql not working #102
Comments
@Belajariah thank you for reporting. 👍 I can confirm the issue. ✔️ The issue sounds familiar. It is probably the same as camunda-community-hub/zeebe-simple-monitor#79. We may be able to apply the same fix as in camunda-community-hub/zeebe-simple-monitor#159: add |
I'm getting the same issue as soon as there is at least one User Task created - then the simple tasklist fails (e.g. http://localhost:8081/views/all-tasks/) with error: |
It should be easy to fix. But it's currently not my priority. Happy to receive a contribution. 😉 |
Hi @saig0 , Caused by: org.postgresql.util.PSQLException: Large Objects may not be used in auto-commit mode. I'm also facing the same Issue when dealing with large objects, let me explain the scenario... I'm working with jbpm-5.5 and jbpm has it's own tables which uses those tables to store some sort of information about workflow.. when jbpm trying to insert the records into postgresql data base, It's giving me an same error.. I don't have control over those jbpm tables, it's handle on it's own tried below solution which I got from stackoverflow but no luck Solution: Version details postgresql db version -16 Any Suggestions how can I fix this , Thank you!!! |
I'm trying to run a simple tasklist using custom postgreql in docker compose with the following configuration:
but i get issue when i add user task to process. It looks like an error like this:
I've checked the db, the data has been inputted and nothing strange. I think there is a problem with the version db but for versions postgres:13.3-alpine and postgres:12.2 I get the same issue.
Everyone is there any suggestions for this case. Thankyou.
The text was updated successfully, but these errors were encountered: