JBossDeveloper

Hi,

I should mention that we use tasks without Mina server (or other), calling taskSession directly, inspirated by this discussion

http://community.jboss.org/message/595321

Not sure if this is really related to transaction problem.

My workitem handler which works with tasks looks like this:

public void executeWorkItem(WorkItem workItem, WorkItemManager manager) {
        // create new task, get info from WF
 
        // get task details from workitem
        Task newTask = new Task();
        String taskName = (String) workItem.getParameter("TaskName");
 
        .....
 
        taskSession.addTask(newTask, taskParameters);
 
    }

What do you think?

Thank you for you comments, I was also hoping that Mauricio starts again responding to this discussions.

I managed to find out where and when exactly it goes down with JDBC commit failed java.sql.SQLException: You cannot commit during a managed transaction!

When the org.drools.persistence.jpa.processinstance.JPAWorkItemManager is called and then it calls some function in org.jbpm.task.service.TaskServiceSession which has doOperationInTransaction (with commit()).

In JPAWorkItemManager it calls

PersistenceContext context = ((PersistenceContextManager) env.get( EnvironmentName.PERSISTENCE_CONTEXT_MANAGER )).getCommandScopedPersistenceContext();

which propably doesn't like when there is later tx.commit(); (tx is RESOURCE_LOCAL transition)

Any further insight?

Finally, I found solution for this.

In datasource for tasks it should be no-tx-datasource. See

https://forum.hibernate.org/viewtopic.php?f=1&t=998779

and http://community.jboss.org/wiki/ConfigDataSources

Thank you to all for your insights about transactions.