]
Alejandro Guizar commented on JBPM-1452:
----------------------------------------
Feedback: "The development team has reported that using the null entry for
jbpm.job.executor allows tasks to complete."
JbpmConfiguration assumes the object factory has a jbpm.job.executor
entry
--------------------------------------------------------------------------
Key: JBPM-1452
URL:
https://jira.jboss.org/jira/browse/JBPM-1452
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: JBossBPM-3.3.0
Environment: 3.3 snapshot
Spring
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: JBossBPM-3.3.0
The following exception is thrown while completing a task that ends a process. The
application runs with the 3.3 snapshot JAR.
org.jbpm.configuration.ConfigurationException: name 'jbpm.job.executor' is not
defined in the configuration. configured names: [resource.hibernate.queries.hbm.xml,
jbpm.msg.wait.timout, jbpm.task.instance.factory, resource.default.modules,
resource.varmapping, resource.business.calendar, resource.action.types, resource.parsers,
default.jbpm.context, resource.node.types, resource.converter, jbpm.variable.resolver,
jbpm.byte.block.size]
at org.jbpm.configuration.ObjectFactoryImpl.createObject(ObjectFactoryImpl.java:76)
at org.jbpm.JbpmConfiguration.getJobExecutor(JbpmConfiguration.java:603)
at
org.jbpm.scheduler.db.DbSchedulerService.<init>(DbSchedulerService.java:51)
at
org.jbpm.scheduler.db.DbSchedulerServiceFactory.openService(DbSchedulerServiceFactory.java:32)
at org.jbpm.svc.Services.getService(Services.java:156)
at org.jbpm.svc.Services.getCurrentService(Services.java:94)
at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328)
at org.jbpm.graph.exe.Token.notifyParentOfTokenEnd(Token.java:329)
at org.jbpm.graph.exe.Token.end(Token.java:301)
at org.jbpm.graph.exe.Token.end(Token.java:251)
at org.jbpm.graph.node.EndState.execute(EndState.java:59)
The 3.3 snapshot is looking for 'jbpm.job.executor' which is defined in the
default.jbpm.cfg.xml, but which the application does not have in its jbpm.cfg.xml. It
works with 3.2.2. The JobExecutor is set up manually in a Spring configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: