November 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-575) delete Timer fails in Scheduler

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-575?page=com.atlassian.jira.plugi... ] Alejandro Guizar resolved JBPM-575. ----------------------------------- Fix Version/s: (was: jBPM 3.3.1 GA) Resolution: Duplicate Issue The solution was not to delete timers (or execute-node-jobs) that are locked (that is, under execution) when a process instance ends. This solution includes the issue at hand, where execution of a timer reaches the end of the process instance. > delete Timer fails in Scheduler > ------------------------------- > > Key: JBPM-575 > URL: https://jira.jboss.org/jira/browse/JBPM-575 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.0 > Environment: jbpm 3.1, PostgreSQL / MS SQL Server / DB/2, jboss 4.0.4 RC1 > Reporter: maplat > Assignee: Alejandro Guizar > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > if a timer is scheduled, which execution leeds to the process end, the timer can not be deleted, > because at the end of the process instance all timers are canceld and after this the scheduler also tries > to delete the timer > I did a change on SchedulerSession.cancelTimersForProcessInstance > (the commented code ist the original one, I also added a new named query to hibernate.queries.hbm.xml) > The change does not directly delete the timers from database, it calls the deleteTimer methode, which causes the > timers beeing deleted to be added to the deletedTimers collection. If another delete is done from the scheduler > it is ignored, because in the delete timer methode the deletedTImers collection is checked. > public void cancelTimersForProcessInstance(ProcessInstance processInstance) { > try { > /*Query query = session.getNamedQuery("SchedulerSession.deleteTimersForProcessInstance"); > query.setEntity("processInstance", processInstance); > query.executeUpdate();*/ > Query query = session.getNamedQuery("SchedulerSession.findTimersForProcessInstance"); > query.setEntity("processInstance", processInstance); > Iterator iter = query.list().iterator(); > while(iter.hasNext()) { > deleteTimer((Timer) iter.next()); > } > } catch (Exception e) { > log.error(e); > jbpmSession.handleException(); > throw new JbpmException("couldn't delete timers for process instance '"+processInstance+"'", e); > } > } > -- new named query > <query name="SchedulerSession.findTimersForProcessInstance"> > <![CDATA[ > select t from org.jbpm.scheduler.exe.Timer t > where t.processInstance = :processInstance > ]]> > </query> > I'm not sure if the deleteTimersForProcessInstance query is used somewhere else, so I left it. > If this approch is right, someone of the developers maybe can fix it in the code, I do not have access to it -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1780) Make the GWT console an optional installation component

by Heiko Braun (JIRA)

Make the GWT console an optional installation component -------------------------------------------------------- Key: JBPM-1780 URL: https://jira.jboss.org/jira/browse/JBPM-1780 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jBPM 3.3.0 GA Reporter: Heiko Braun Assignee: Heiko Braun The GWT console will have a lifecycle on it's own and thus becomes an optional component to the installer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
1
0 / 0

[JBoss JIRA] Assigned: (JBPM-165) process instance versioning

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-165?page=com.atlassian.jira.plugi... ] Thomas Diesler reassigned JBPM-165: ----------------------------------- Assignee: Tom Baeyens > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: https://jira.jboss.org/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: jBPM 3.3.1 GA > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1833) Task assignment with simplified lifecycle

by Heiko Braun (JIRA)

Task assignment with simplified lifecycle ----------------------------------------- Key: JBPM-1833 URL: https://jira.jboss.org/jira/browse/JBPM-1833 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-1819) re-enable the standard configuration

by Tom Baeyens (JIRA)

re-enable the standard configuration ------------------------------------ Key: JBPM-1819 URL: https://jira.jboss.org/jira/browse/JBPM-1819 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 3.3.1 GA std configs should be the default. bindings to jms and ejb-timer service limit the number of deployment environments on which the shipped bytes will work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

3
3
0 / 0

[JBoss JIRA] Updated: (JBPM-575) delete Timer fails in Scheduler

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-575?page=com.atlassian.jira.plugi... ] Thomas Diesler updated JBPM-575: -------------------------------- Fix Version/s: jBPM 3.3.1 GA Assignee: Alejandro Guizar > delete Timer fails in Scheduler > ------------------------------- > > Key: JBPM-575 > URL: https://jira.jboss.org/jira/browse/JBPM-575 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.0 > Environment: jbpm 3.1, PostgreSQL / MS SQL Server / DB/2, jboss 4.0.4 RC1 > Reporter: maplat > Assignee: Alejandro Guizar > Fix For: jBPM 3.3.1 GA > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > if a timer is scheduled, which execution leeds to the process end, the timer can not be deleted, > because at the end of the process instance all timers are canceld and after this the scheduler also tries > to delete the timer > I did a change on SchedulerSession.cancelTimersForProcessInstance > (the commented code ist the original one, I also added a new named query to hibernate.queries.hbm.xml) > The change does not directly delete the timers from database, it calls the deleteTimer methode, which causes the > timers beeing deleted to be added to the deletedTimers collection. If another delete is done from the scheduler > it is ignored, because in the delete timer methode the deletedTImers collection is checked. > public void cancelTimersForProcessInstance(ProcessInstance processInstance) { > try { > /*Query query = session.getNamedQuery("SchedulerSession.deleteTimersForProcessInstance"); > query.setEntity("processInstance", processInstance); > query.executeUpdate();*/ > Query query = session.getNamedQuery("SchedulerSession.findTimersForProcessInstance"); > query.setEntity("processInstance", processInstance); > Iterator iter = query.list().iterator(); > while(iter.hasNext()) { > deleteTimer((Timer) iter.next()); > } > } catch (Exception e) { > log.error(e); > jbpmSession.handleException(); > throw new JbpmException("couldn't delete timers for process instance '"+processInstance+"'", e); > } > } > -- new named query > <query name="SchedulerSession.findTimersForProcessInstance"> > <![CDATA[ > select t from org.jbpm.scheduler.exe.Timer t > where t.processInstance = :processInstance > ]]> > </query> > I'm not sure if the deleteTimersForProcessInstance query is used somewhere else, so I left it. > If this approch is right, someone of the developers maybe can fix it in the code, I do not have access to it -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1767) jBPM jPDL User Guide: Documentation flaw regarding timers

by JÃÂÃÂ¼rgen Lampe (JIRA)

jBPM jPDL User Guide: Documentation flaw regarding timers --------------------------------------------------------- Key: JBPM-1767 URL: https://jira.jboss.org/jira/browse/JBPM-1767 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.3 Reporter: JÃÂÃÂ¼rgen Lampe Priority: Trivial jBPM jPDL User Guide 3.2.3 Table 21.20 Description of attribute cancel-event says: "this attribute is only to be used in timers of tasks. it specifies the event on which the timer should be cancelled. by default, this is the task-end event, but it can be set to e.g. task-assign or task-start. The cancel-event types can be combined by specifying them in a comma separated list in the attribute. " It works fine in state-node timers too, where it seems to be the easiest way to build a wait state of fixed duration. (see http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179889#4179889) Also missing a statement indicating: "You cannot (and should not) cancel the timer within itself. " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBPM-1785) Release jBPM 3.3.0 GA

by Thomas Diesler (JIRA)

Release jBPM 3.3.0 GA --------------------- Key: JBPM-1785 URL: https://jira.jboss.org/jira/browse/JBPM-1785 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: jBPM 3.3.0 GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-1719) Pass testsuite against sybase

by Thomas Diesler (JIRA)

Pass testsuite against sybase ----------------------------- Key: JBPM-1719 URL: https://jira.jboss.org/jira/browse/JBPM-1719 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 3.3.0 <excludes> <exclude>org/jbpm/persistence/db/PersistenceServiceDbTest.java</exclude> <exclude>org/jbpm/persistence/db/PersistenceServiceFactoryDbTest.java</exclude> </excludes> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBPM-1820) Replace proprietary sybase driver with OS alternative

by Thomas Diesler (JIRA)

Replace proprietary sybase driver with OS alternative ----------------------------------------------------- Key: JBPM-1820 URL: https://jira.jboss.org/jira/browse/JBPM-1820 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Fix For: jBPM 3.3.1 GA SYBASE_JDBC_DRIVER=/opt/sybase/ase1502dev/shared/lib/jconn3.jar if [ -f $SYBASE_JDBC_DRIVER ]; then echo "cp $SYBASE_JDBC_DRIVER $JBOSS_HOME/server/$JBOSS_SERVER/deploy/jbpm/jbpm-service.sar" cp $SYBASE_JDBC_DRIVER $JBOSS_HOME/server/$JBOSS_SERVER/deploy/jbpm/jbpm-service.sar fi -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues November 2008