Description of problem: I have BPMS 6.0.0.ER3 set with DB2. When any process instance proceed to a human task, the task server will throw an exception that it's not possible to create a task. I will attach the server.log but I think this part is most important. 08:57:23,676 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-localhost/127.0.0.1:8080-12) SQL Error: -1585, SQLState: 54048 08:57:23,676 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-localhost/127.0.0.1:8080-12) DB2 SQL Error: SQLCODE=-1585, SQLSTATE=54048, SQLERRMC=null, DRIVER=4.14.122 08:57:23,684 ERROR [org.jbpm.services.task.wih.LocalHTWorkItemHandler] (http-localhost/127.0.0.1:8080-12) Mon Sep 23 08:57:23 EDT 2013: Error when creating task on task server for work item id 1. Error reported by task server: Operation failed: java.lang.RuntimeException: Operation failed at org.jbpm.shared.services.impl.JbpmServicesPersistenceManagerImpl.persist(JbpmServicesPersistenceManagerImpl.java:208) [jbpm-shared-services-6.0.0-redhat-3.jar:6.0.0-redhat-3] On the client side I receive different exception but it's only a consequence: org.jbpm.workflow.instance.WorkflowRuntimeException: [org.jboss.qa.bpms.HumanTask:122 - :1] -- No active JTA transaction on joinTransaction call at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:161) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 801674 [details] Part of server log with the exceptions
Hi Ivo, can you attach your process? So we can try to reproduce it? Are you sure that the issue is only with DB2? or the same process is also failing with a different database?
Looking at DB2 docs I've found this: http://www-01.ibm.com/support/docview.wss?uid=swg21529563 Not sure how the DB2 instance is set up.. but it seems that it needs to be set up in that way. Can you try creating a single and isolated task in the task screens?
I talked with colleagues about it and we have a ticket to fix this. It's a configuration issue in DB then.