Jobs that already ran do not run again.
Here's the link to the jira...
https://jira.jboss.org/jira/browse/JBPM-2308
Thanks for your help,
Tom
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235858#4235858
Reply to the post :
http://www.jboss.org/index.html
Yes, I did look at the code and the select statement and observed the same
thing (that retries_ must be > 0 for a job to be considered acquirable). After
changing the statement that migrates data from jbpm_timer to jbpm_job such that
retries_ is set to 1 (instead of 0), my jobs ran (as required)
The release notes included in the jbpm-jpdl-3.2.3.zip file contain the very
same SQL migration steps as those posted on source forge. So, my questions
remain. And of upmost importance...
- why is the retries_ column explicitly set to zero for all of the the records
migrated from the jbpm_timer
I just unpacked the jbpm-jpdl-3.2.3.zip file and was surprised to discover that
the very same release notes distributed on sourceforge are included (in
release.notes.html). So, what am I missing? Why are the tables created by
hibernate (in a clean database) different than those created using the
Oh, I should have stated some of the discrepancies found between the table
created following the sourceforge migration notes and the table created by
Hibernate.
1. The duedate_ is created as a timestamp column in the "sourceforge" database
while it is a datetime column in the "hibernate" table.
After an extensive search of this forum, the jboss community, and the www, I've
only found what appears to be out of date migration notes on the sourceforge
website (due to the fact that the jbpm_job table created as part of the
migration is NOT the equivalent of the jbpm_job table created by hi
