JBossDeveloper

There is an additional task to complete afterwards which I have not completed so the process should not be ended. I am doing an

assertTrue(processInstance.isActive("task2"));

I am going to turn up the loglevel. The process was deployed with just one timer, does not change anything. The duplicate timers are due to the GPD bug already reported in JIRA.

I must be doing something wrong since I don't see more in the log.

handlers= java.util.logging.ConsoleHandler
redirect.commons.logging = enabled

java.util.logging.ConsoleHandler.level = FINEST
java.util.logging.ConsoleHandler.formatter = org.jbpm.internal.log.LogFormatter

org.jbpm.level=FINEST
org.jbpm.pvm.internal.tx.level=FINEST
org.jbpm.pvm.internal.wire.level=FINEST
org.jbpm.pvm.internal.util.level=FINEST

org.hibernate.level=FINEST
org.hibernate.cfg.SettingsFactory.level=FINEST
org.hibernate.cfg.HbmBinder.level=FINEST
# org.hibernate.SQL.level=FINEST
# org.hibernate.type.level=FINEST
# org.hibernate.tool.hbm2ddl.SchemaExport.level=FINEST
org.hibernate.transaction.level=FINEST

I don't manage to turn up the loglevel. Any hints?

Okay, thanks for all the hints. It was really due to a classpath problem.

Here's what I found:

Logging and using Tom's hint with the DBManager showed that there was a query for an execution which did not exist anymore. Before the executing of the job (transition with timer to task "escalation") there are 2 entries in the Execution Table. One is "escalation.1" and the second is "escalation.1-timeout". After the transition to "escalation" escalation.1-timeout gets deleted, execution.1 is active again and when you try to complete the task "timeout" which is still in the tasklist you get the Exception because the associated execution cannot be found.

(I did not post logs since there cannot be seen really a lot and they get very large with a higher loglevel set.

I'd really like having some feedback on this since for me questions arise:

- Is this behaviour just not desired from my point of view but conform to the processs excecution model in jBPM?

- Is this a bug since there is a task in somebody's task list which cannot be completed nor deleted? It cannot be deleted since tasks which belong to an execution cannot be deleted and it cannot be completed since the execution it belongs to does not exist anymore.

Or am I completely wrong?

Thanks in advance!

Here we go:

https://jira.jboss.org/jira/browse/JBPM-2559

I did not write a lot since there is a link to the forum post and I supplied a process definition and the unit test.

No problem, I did not succeed either in finding it on JIRA. Forgot to mention I tried searching JIRA. Thanks for your effort. I really hope this will be fixed in 4.2.

I commented on this again since I consider this really important because at the moment it makes you change your process model for escalations which is probably not wanted. If this was possible in 3.x this would also lead to problems when migrating from 3.x to 4.x, right?

Regarding the behaviour in 3.x Joram stated in the comments answering your question:

The most logical is not necessarily what was in 3 ;-)

But you are right: in 3, the task is kept open, but it can't be completed anymore. The only option is than to delete the task. Imo, this makes sense.

It seems strange to me that are just a few people interested in this topic although the situation described seems to me very common. Are there still so few people working with 4.x or has nobody run across the problem? If you have it would be great to count on your vote in JIRA.