search

camunda-community-hub / zeebe-simple-tasklist

Zeebe worker to manage manual/user tasks
Apache License 2.0
74 stars 18 forks source link

Simple tasklist using custom postgreSql not working #102

Open Belajariah opened 2 years ago

Belajariah commented 2 years ago

I'm trying to run a simple tasklist using custom postgreql in docker compose with the following configuration:

Screenshot from 2022-09-15 18-01-53

but i get issue when i add user task to process. It looks like an error like this:

Screenshot from 2022-09-15 18-08-09

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.

saig0 commented 1 year ago

@Belajariah thank you for reporting. :+1: I can confirm the issue. :heavy_check_mark:

The issue sounds familiar. It is probably the same as https://github.com/camunda-community-hub/zeebe-simple-monitor/issues/79. We may be able to apply the same fix as in https://github.com/camunda-community-hub/zeebe-simple-monitor/pull/159: add @Transactional in the view controller.

mariansoban commented 1 year ago

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: Caused by: org.postgresql.util.PSQLException: Large Objects may not be used in auto-commit mode. full exception Is there any plan to fix this issue?

saig0 commented 1 year ago

Is there any plan to fix this issue?

It should be easy to fix. But it's currently not my priority.

Happy to receive a contribution. :wink:

shaiksuhel1999 commented 1 month ago

Hi @saig0 ,

Caused by: org.postgresql.util.PSQLException: Large Objects may not be used in auto-commit mode. at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:285) [postgresql-42.7.3.jar:42.7.3]

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: I was able to find out a solution for this. I have changed the DB column to Bytea type in PostgreSQL and change the JBPM 4.4 implementation to use byte[] over java.sql.Blob (in org.jbpm.pvm.internal.lob.Lob class).

Version details

postgresql db version -16 postgresql driver version - 42.7.3

Any Suggestions how can I fix this , Thank you!!!