Scheduler problems jbpm.war(3.1.3) to jboss as 4.0.5GA

[jesperb]

I have spent the last couple of days trying to get the scheduler to work on JBoss 4.0.5 GA but when a task with a timer is executed the 'scheduler' is not found.
I have downloaded the 3.1.3 jbpm starter kit and modded it to work (as in previous posts).
I have copied the jbpm.sar and the jbpm.war to the dir. I removed dom4j and jaxen jars from the war (hence it is already included in the jboss dist) and added the following in the web.xml to load the scheduler thread.

<!-- jBPM SchedulerServlet -->
 <servlet>
 <servlet-name>SchedulerServlet</servlet-name>
 <servlet-class>org.jbpm.scheduler.impl.SchedulerServlet</servlet-class>
 <load-on-startup>1</load-on-startup>
 </servlet>
 <servlet-mapping>
 <servlet-name>SchedulerServlet</servlet-name>
 <url-pattern>/scheduler</url-pattern>
 </servlet-mapping>

I have verified that the scheduler is running:

...
DEBUG [Scheduler] starting the scheduler
...
DEBUG [CommandExecutorThread] waiting for more messages
DEBUG [JbpmContextInfo] creating jbpm context with service factories '[message, scheduler, authentication, persistence, logging]'
DEBUG [JbpmContext] creating JbpmContext
DEBUG [DbPersistenceServiceFactory] creating persistence service
DEBUG [DbPersistenceService] creating hibernate session
DEBUG [DbPersistenceService] beginning hibernate transaction
DEBUG [SchedulerThread] checking for timers
DEBUG [JbpmContext] closing JbpmContext
DEBUG [Services] closing service 'persistence': org.jbpm.persistence.db.DbPersistenceService@1d427b1
DEBUG [DbPersistenceService] committing hibernate transaction
DEBUG [DbPersistenceService] closing hibernate session

This is the code that creates and executes the process:

 ProcessDefinition processDefinition = ProcessDefinition.parseXmlString(
 "<process-definition>" +
 " <start-state>" +
 " <transition to='executeAction' />" +
 " </start-state>" +
 " <node name='executeAction'>" +
 " <transition to='timedAction' />" +
 " <action class='se.pertexo.test.workflow.TestAction' />" +
 " </node>" +
 " <node name='timedAction'>" +
 " <timer name='timer1' duedate='15 seconds'/>" +
 " <transition to='end' />" +
 " <action class='se.pertexo.test.workflow.TestAction' />" +
 " </node>" +
 " <end-state name='end' />" +
 "</process-definition>"
 );

 ProcessInstance processInstance =
 new ProcessInstance( processDefinition );

 Token token = processInstance.getRootToken();
 logger.info( " Starting workflow" );

 token.signal();

The TestAction code:

public class TestAction implements ActionHandler
{
 private static Logger logger = Logger.getLogger( TestAction.class );

 public void execute(ExecutionContext executionContext) throws Exception
 {
 logger.info( "Test action: execute");
 executionContext.getToken().signal();
 }
}

The first nodes action is executed and signals the transition to the timer task, this is the log and exception I get:

11:35:33,058 INFO [TestBean] -----> Testing jBPM <-----
11:35:33,151 INFO [TestBean] Starting workflow
11:35:33,167 INFO [TestAction] Test action: execute
11:35:33,167 ERROR [GraphElement] action threw exception: service 'scheduler' unavailable
org.jbpm.svc.JbpmServiceException: service 'scheduler' unavailable
 at org.jbpm.svc.Services.getCurrentService(Services.java:86)
 at org.jbpm.svc.Services.getCurrentService(Services.java:76)
 at org.jbpm.scheduler.def.CreateTimerAction.execute(CreateTimerAction.java:66)
 at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:235)
 at org.jbpm.graph.def.GraphElement.executeActions(GraphElement.java:212)
 at org.jbpm.graph.def.GraphElement.fireAndPropagateEvent(GraphElement.java:182)
 at org.jbpm.graph.def.GraphElement.fireEvent(GraphElement.java:166)
 at org.jbpm.graph.def.Node.enter(Node.java:301)
 at org.jbpm.graph.def.Transition.take(Transition.java:119)
 at org.jbpm.graph.def.Node.leave(Node.java:383)
 at org.jbpm.graph.exe.Token.signal(Token.java:178)
 at org.jbpm.graph.exe.Token.signal(Token.java:123)
 at se.sqs.production.workflow.TestAction.execute(TestAction.java:22)

My question is:
Where does the scheduler get registered with the JbpmContext?

Is there anything else that I have missed?

Regards

Jesper

[kukeltje]

In the config file used by jbpm. The default one is in org.jbpm and is called default.jbpm.cfg.xml but this can be overridden

[jesperb]

Ok, If I have understood you right, JBPM needs a configuration file.

I copied the default.jbpm.cfg.xml and put it in the root of my classpath and renamed it to jbpm.cfg.xml, but I still get the error.

Is there any configuration that I am missing?

Any help or hints is appreciated!

/ Jesper

[kukeltje]

the default file is the one used UNLESS you specify one, so no need to copy it. If this was not the case, I have no idea (at the moment)

[jesperb]

Thanks for trying to help me out here.

I see that my first post can be misunderstod, so let me clarify how I did.

Hence we have an existing application running on the JBoss 4.0.5 server, I have copied the jbpm.sar dir and the modded jbpm.war from the starter kit to our jboss configuration.
That configuration is a standard medium configuration. I am not using the DefaultDS, I am using our datasource which is a MySQL database. I have changed the hibernate.cfg.xml in the sar so that the database is automatically created and the datasource is using the MySQL database.

Is there any other jBPM configuration from the starter kit that i must copy to our configuration of JBoss?

Regards

/ Jesper B

[mihochan]

I am having exactly the same problems. Have you found a solution yet?

[mihochan]

I've solved my problem.

It is necessary to specify which class to use for the Scheduler service in the jbpm.cfg.xml file.

 <jbpm-context>
 ...
 <service name="scheduler" factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory" />
 </jbpm-context>

Hope this helps

[jesperb]

Yes, I had that configuration in my configuration file, that was the thing..

Anyhow, it works for me now and I have no qlue what it was that was wrong.

I am running Quartz in the application I am developing and I updraged that from verstion 1.5.2 to 1.6.0. When I restarted the server and tried to add a timer to a node, it just worked.

Well, now it works and I am leaving it with that.

/Jesper