or try using ejb3 timers...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057291#4057291
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057291
___
jboss-user mailing list
ignore previous comment (wrong thread...)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057298#4057298
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057298
___
jboss-user
jbpm.cfg.xml
jbpm-context
| service name=persistence
factory=org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory
| field name=sessionFactoryJndiName
| string value=java:/WorkflowSessionFactory /
| /field
| field name=isCurrentSessionEnabledtrue //field
Ok, found the problem.
TimerService.add() does not have interval, so only one execution suppose to
run. Made a small patch, works fine now.
Still, the concurrent execption is really ugly. Will try tree cache to see if
any difference.
View the original post :