July 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2395) fix mail listener: change task variable to task scope

by Tom Baeyens (JIRA)

fix mail listener: change task variable to task scope ----------------------------------------------------- Key: JBPM-2395 URL: https://jira.jboss.org/jira/browse/JBPM-2395 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0 -- 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

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2396) remove TaskServive.getVariable method

by Tom Baeyens (JIRA)

remove TaskServive.getVariable method ------------------------------------- Key: JBPM-2396 URL: https://jira.jboss.org/jira/browse/JBPM-2396 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0 If we want to introduce custom task-parameter-to-variable mappings later on, it's only possible if you have all the values at once. so setting the variables of a task should always be done with the method TaskService.setVariables(Map). that also gives users a central point to intercept task form submission. -- 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

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2390) Task completion not only deletes the task entry in the task table, but also the comments in the jbpm4_comment table.

by Shekhar Vemuri (JIRA)

Task completion not only deletes the task entry in the task table, but also the comments in the jbpm4_comment table. -------------------------------------------------------------------------------------------------------------------- Key: JBPM-2390 URL: https://jira.jboss.org/jira/browse/JBPM-2390 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0.CR1 Reporter: Shekhar Vemuri Completion of Task results in the deletion of the task from the JBPM4_TASK table, and also deletes the JBPM4_COMMENT table. There is no way to show the user the comments that they entered against a task,. which makes the comments feature, not as useful. -- 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

15 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1994) Provide process execution logging

by Heiko Braun (JIRA)

Provide process execution logging --------------------------------- Key: JBPM-1994 URL: https://jira.jboss.org/jira/browse/JBPM-1994 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.0.Beta2 Reporter: Heiko Braun Transactional storage of the history of a process execution (not software logging) Log pluggability is in place Basic pluggability infrastructure is in place HistoryRecords generated during process execution need to be created HistoryRecords need to merge themselves into the History DB schema Schema for storing history information needs to be build Filtering the history storage should be based on features We should not place the burden on the users to link log filtering to the features that remain available -- 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

15 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-2373) add task history

by Tom Baeyens (JIRA)

add task history ---------------- Key: JBPM-2373 URL: https://jira.jboss.org/jira/browse/JBPM-2373 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.x currently only task acitivity instances are stored in the history. in other words only tasks that are associated to an execution have history information. this issue means that also standalone tasks, dynamically created with the api, should have history as well. we (joram and me 30/06/2009) think that it's best to add a separate task history table for that purpose. -- 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

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2385) business calendar should be extracted from default configuration

by Tom Baeyens (JIRA)

business calendar should be extracted from default configuration ---------------------------------------------------------------- Key: JBPM-2385 URL: https://jira.jboss.org/jira/browse/JBPM-2385 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.1 otherwise users cannot easy customize the business calendar configuration -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-1292) Integrate simulation tests in automated testrun

by Thomas Diesler (JIRA)

Integrate simulation tests in automated testrun ----------------------------------------------- Key: JBPM-1292 URL: http://jira.jboss.com/jira/browse/JBPM-1292 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM jPDL 3.2.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

4
24
0 / 0

[JBoss JIRA] Created: (JBPM-2375) JobExecutorThread is terminated after an Error

by Martin Putz (JIRA)

JobExecutorThread is terminated after an Error ---------------------------------------------- Key: JBPM-2375 URL: https://jira.jboss.org/jira/browse/JBPM-2375 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.5.SP5, jBPM 3.2.6.SP1 Reporter: Martin Putz Assignee: Alejandro Guizar Fix For: jBPM 3.2.7 consider the following process: state1+timer -> state2+node-enter:action The ActionHandler class which is executed as a result of the timer moving the token forward runs into a serious problem, eg. a NoClassDefFoundError. As a result, the JobExecutorThread which has been executing this timer is killed: Exception in thread "JbpmJobExector:127.0.0.1:1", and eventually no JobExecutorThreads are left to execute timers. -- 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

15 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2321) Error while fetching latest version

by sri r (JIRA)

Error while fetching latest version ------------------------------------ Key: JBPM-2321 URL: https://jira.jboss.org/jira/browse/JBPM-2321 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.CR1 Reporter: sri r The query generated for the below statement results in two records causing below error. Basically i'm trying to check the latest version deployed so as to proceed with deploying a newer version of process definition xml. repositorySession .createProcessDefinitionQuery() .processDefinitionKey(key) .orderDesc(ProcessDefinitionQuery.PROPERTY_VERSION) .page(0, 1) .uniqueResult(); Caused by: org.jbpm.api.JbpmException: result not unique: 2 at org.jbpm.pvm.internal.query.AbstractQuery.untypedUniqueResult(AbstractQuery.java:81) at org.jbpm.pvm.internal.query.ProcessDefinitionQueryImpl.uniqueResult(ProcessDefinitionQueryImpl.java:151) Queries: Hibernate: select deployment1_.OBJNAME_ as col_0_0_, deployment1_.DEPLOYMENT_ as col_1_0_ from public.JBPM4_DEPLOYMENT deployment0_, public.JBPM4_DEPLOYPROP deployment1_, public.JBPM4_DEPLOYPROP deployment2_, public.JBPM4_DEPLOYPROP deployment3_ where deployment0_.STATE_<>'suspended' and deployment1_.KEY_='pdid' and deployment1_.DEPLOYMENT_=deployment0_.DBID_ and deployment2_.KEY_='pdkey' and deployment2_.OBJNAME_=deployment1_.OBJNAME_ and deployment2_.DEPLOYMENT_=deployment0_.DBID_ and deployment3_.KEY_='pdversion' and deployment3_.OBJNAME_=deployment1_.OBJNAME_ and deployment3_.DEPLOYMENT_=deployment0_.DBID_ and deployment1_.OBJNAME_=? Hibernate: select deployment0_.DBID_ as DBID1_10_0_, deployment0_.NAME_ as NAME2_10_0_, deployment0_.TIMESTAMP_ as TIMESTAMP3_10_0_, deployment0_.STATE_ as STATE4_10_0_ from public.JBPM4_DEPLOYMENT deployment0_ where deployment0_.DBID_=? Hibernate: select resources0_.DEPLOYMENT_ as DEPLOYMENT7_1_, resources0_.DBID_ as DBID1_1_, resources0_.NAME_ as NAME8_1_, resources0_.DBID_ as DBID1_3_0_, resources0_.DBVERSION_ as DBVERSION2_3_0_, resources0_.BLOB_VALUE_ as BLOB3_3_0_, resources0_.BINARY_VALUE_ as BINARY4_3_0_, resources0_.CLOB_VALUE_ as CLOB5_3_0_, resources0_.TEXT_VALUE_ as TEXT6_3_0_ from public.JBPM4_LOB resources0_ where resources0_.DEPLOYMENT_=? Hibernate: select objectprop0_.DEPLOYMENT_ as DEPLOYMENT2_1_, objectprop0_.DBID_ as DBID1_1_, objectprop0_.DBID_ as DBID1_11_0_, objectprop0_.DEPLOYMENT_ as DEPLOYMENT2_11_0_, objectprop0_.OBJNAME_ as OBJNAME3_11_0_, objectprop0_.KEY_ as KEY4_11_0_, objectprop0_.STRINGVAL_ as STRINGVAL5_11_0_, objectprop0_.LONGVAL_ as LONGVAL6_11_0_ from public.JBPM4_DEPLOYPROP objectprop0_ where objectprop0_.DEPLOYMENT_=? Hibernate: select deployment0_.DBID_ as DBID1_10_0_, deployment0_.NAME_ as NAME2_10_0_, deployment0_.TIMESTAMP_ as TIMESTAMP3_10_0_, deployment0_.STATE_ as STATE4_10_0_ from public.JBPM4_DEPLOYMENT deployment0_ where deployment0_.DBID_=? Hibernate: select resources0_.DEPLOYMENT_ as DEPLOYMENT7_1_, resources0_.DBID_ as DBID1_1_, resources0_.NAME_ as NAME8_1_, resources0_.DBID_ as DBID1_3_0_, resources0_.DBVERSION_ as DBVERSION2_3_0_, resources0_.BLOB_VALUE_ as BLOB3_3_0_, resources0_.BINARY_VALUE_ as BINARY4_3_0_, resources0_.CLOB_VALUE_ as CLOB5_3_0_, resources0_.TEXT_VALUE_ as TEXT6_3_0_ from public.JBPM4_LOB resources0_ where resources0_.DEPLOYMENT_=? Hibernate: select objectprop0_.DEPLOYMENT_ as DEPLOYMENT2_1_, objectprop0_.DBID_ as DBID1_1_, objectprop0_.DBID_ as DBID1_11_0_, objectprop0_.DEPLOYMENT_ as DEPLOYMENT2_11_0_, objectprop0_.OBJNAME_ as OBJNAME3_11_0_, objectprop0_.KEY_ as KEY4_11_0_, objectprop0_.STRINGVAL_ as STRINGVAL5_11_0_, objectprop0_.LONGVAL_ as LONGVAL6_11_0_ from public.JBPM4_DEPLOYPROP objectprop0_ where objectprop0_.DEPLOYMENT_=? -- 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

15 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2387) integrity constraint violation in process that runs end to end with no wait

by Alfie Kirkpatrick (JIRA)

integrity constraint violation in process that runs end to end with no wait --------------------------------------------------------------------------- Key: JBPM-2387 URL: https://jira.jboss.org/jira/browse/JBPM-2387 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0.CR1 Reporter: Alfie Kirkpatrick I am developing a process that, depending on various decisions, can potentially run from start to finish without any wait. In this scenario I get the following exception: org.hibernate.exception.ConstraintViolationException: could not delete: [org.jbpm.jpdl.internal.model.JpdlExecution#1] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:94) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2569) at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2725) at org.hibernate.action.EntityDeleteAction.execute(EntityDeleteAction.java:97) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:172) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027) at org.jbpm.pvm.internal.tx.HibernateSessionResource.prepare(HibernateSessionResource.java:54) at org.jbpm.pvm.internal.tx.StandardTransaction.commit(StandardTransaction.java:106) at org.jbpm.pvm.internal.tx.StandardTransaction.complete(StandardTransaction.java:65) at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:61) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:54) at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55) at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.startProcessInstanceByKey(ExecutionServiceImpl.java:65) at com.ioko.jbpm.JbpmTest.testEnd2End(JbpmTest.java:29) Caused by: java.sql.SQLException: Integrity constraint violation FK_EXEC_PARENT table: JBPM4_EXECUTION in statement [delete from JBPM4_EXECUTION where DBID_=? and DBVERSION_=?] at org.hsqldb.jdbc.Util.throwError(Unknown Source) at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source) at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2551) ... 38 more This is a serious problem for my process. Attached is a maven project that reproduces the problem. You should just be able to run mvn test to see the error. The problem seems to be with the fork/join. If I take that out it runs ok. I tried to workaround this issue by introducing a state with short timeout towards the start of the process but then I get a different error. I can reproduce this fairly easily if it would be of help in diagnosis. I make a lot of use of custom nodes. Could a workaround be to use state with handlers instead of custom nodes? ps. I tried to read the filing bug guidelines but the site is under maintenance. I feel this is a fairly clear cut issue and have provided test case so hope I haven't broken any rules! -- 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

15 years, 5 months

3
17
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2009