Process is not restored after restart?

[4ntoine]

The problem is that the process in wait state ("state" element) can not be found after application server restart, where application with jbpm is deployed:

Searching of process looks like this:
------------------

String processInstanceRefId = getProcessInstanceRefId(context, messageKind); // (GUID)
String executionId = MessageFormat.format("{0}.{1}", messageKind.getProcessDefinitionKey(), processInstanceRefId);

log.debug(MessageFormat.format("Searching processInstance with executionId={0} in {1} state",
executionId, messageKind.getState()));
ProcessInstance processInstance = processEngine.getExecutionService().findProcessInstanceById(executionId);

if (processInstance == null) {
log.error(MessageFormat.format("processInstance with executionId={0} in {1} not found",
executionId, messageKind.getState()));
return;
}

------------------

Are process instances waiting in "state" restored after application server restart?

jbpm db data is stored in hsqldb file (not in memory):
jdbc:hsqldb:file:WorkflowDB

[kukeltje]

Yes... but is it IN your database

[4ntoine]

"kukeltje" wrote:
Yes... but is it IN your database

Is it a bug or feature? Please, give a link to doc, if it is documented.

[4ntoine]

"kukeltje" wrote:
Yes... but is it IN your database

Is it possible to have process just in the same state as before restarting?

[kukeltje]

yes, that is normal jbpm behaviour.

[4ntoine]

"kukeltje" wrote:
yes, that is normal jbpm behaviour.

can you link to doc describing that situation, please. probably, i made smth wrong like params or configs

[kukeltje]

all docs about jBPM assume this behaviour, so it is very hard for us to point to something specific other than the normal docs.

[4ntoine]

"kukeltje" wrote:
all docs about jBPM assume this behaviour, so it is very hard for us to point to something specific other than the normal docs.

i can't find smth about this in doc (jbpm4) at all - neigher in "state" section nor running/finding process instances.. where is this behaviour described pls?

[kukeltje]

paragraph 1.5, PERSISTENT mode, paragraph 2.3 hsqldb and that is only in the first few paragraphs. So you see it is the DEFAULT to work this way. Therefore my question if anything was in the db. Maybe your hibernate config has create-drop in it