December 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1874) org.jbpm.jpdl.xml.JpdlXmlReader doesn't use org/jbpm/graph/action/action.types.xml to create Create(Cancel)TimerAction

by oleg babul (JIRA)

org.jbpm.jpdl.xml.JpdlXmlReader doesn't use org/jbpm/graph/action/action.types.xml to create Create(Cancel)TimerAction ----------------------------------------------------------------------------------------------------------------------- Key: JBPM-1874 URL: https://jira.jboss.org/jira/browse/JBPM-1874 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA Reporter: oleg babul It's impossible to customize CreateTimerAction, because org.jbpm.jpdl.xml.JpdlXmlReader uses new CreateTimerAction() in the org.jbpm.jpdl.xml.JpdlXmlReader.readNodeTimer(Element, Node) instead of creating action based on the org/jbpm/graph/action/action.types.xml (the same for CancelTimerAction) -- 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

17 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBPM-1110) Having issues when I execute a second instance of a workflow that contain sub-process's in a Oracle database

by Eric Paquette (JIRA)

Having issues when I execute a second instance of a workflow that contain sub-process's in a Oracle database ------------------------------------------------------------------------------------------------------------ Key: JBPM-1110 URL: http://jira.jboss.com/jira/browse/JBPM-1110 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.1 Environment: Oracle DB using Alfreso with Hibernate Reporter: Eric Paquette Assigned To: Tom Baeyens Priority: Critical I'm having issues when I execute a second instance of a workflow that contain sub-process's in a Oracle database: [20/12/07 14:25:33:757 EST] 00000029 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\logs\ffdc\server1_6500650_07.12.20_14.25.33_0.txt [20/12/07 14:25:33:978 EST] 00000029 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\logs\ffdc\server1_6500650_07.12.20_14.25.33_0.txt [20/12/07 14:25:34:018 EST] 00000029 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\logs\ffdc\server1_6500650_07.12.20_14.25.34_0.txt [20/12/07 14:25:34:859 EST] 00000029 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv01\logs\ffdc\server1_6500650_07.12.20_14.25.34_0.txt [20/12/07 14:25:35:249 EST] 00000029 SystemOut O 14:25:34,929 User:admin ERROR [ui.common.Utils] A system error happened during the operation: Transaction didn't commit: Could not execute JDBC batch update; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update javax.transaction.RollbackException: Transaction didn't commit: Could not execute JDBC batch update; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update at org.alfresco.util.transaction.SpringAwareUserTransaction.commit(SpringAwareUserTransaction.java:430) at org.alfresco.web.bean.workflow.ManageTaskDialog.transition(ManageTaskDialog.java:396) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.myfaces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:132) at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:61) at javax.faces.component.UICommand.broadcast(UICommand.java:109) at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:97) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:171) at org.apache.myfaces.lifecycle.InvokeApplicationExecutor.execute(InvokeApplicationExecutor.java:32) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:95) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:70) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:139) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:966) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:907) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145) at org.alfresco.web.app.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:81) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:701) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:646) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:475) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:92) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:93) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:394) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213) at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:194) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:741) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:863) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510) Caused by: org.springframework.dao.DataIntegrityViolationException: Could not execute JDBC batch update; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update at org.springframework.orm.hibernate3.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:622) at org.springframework.orm.hibernate3.HibernateTransactionManager.convertHibernateAccessException(HibernateTransactionManager.java:714) at org.springframework.orm.hibernate3.HibernateTransactionManager.doCommit(HibernateTransactionManager.java:583) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:662) at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:632) at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:314) at org.alfresco.util.transaction.SpringAwareUserTransaction.commit(SpringAwareUserTransaction.java:420) ... 40 more Caused by: org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:249) at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:92) at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:87) at org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(AbstractBatcher.java:218) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2174) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2610) at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:52) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:139) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at org.springframework.orm.hibernate3.HibernateTransactionManager.doCommit(HibernateTransactionManager.java:575) ... 44 more Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint (NHPOLS.SYS_C007328) violated at oracle.jdbc.dbaccess.DBError.throwBatchUpdateException(DBError.java:459) at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:4368) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteBatch(WSJdbcPreparedStatement.java:808) at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeBatch(WSJdbcStatement.java:612) at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:4 at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:242) ... 59 more -- 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

17 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBPM-1889) setVariable on token level works illogical

by Tom Eugelink (JIRA)

setVariable on token level works illogical ------------------------------------------ Key: JBPM-1889 URL: https://jira.jboss.org/jira/browse/JBPM-1889 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.3 Reporter: Tom Eugelink If you do a setVariable(<name>, <value>, <token>) on a token, but the variable does not exist, the token parameter is ignored and the setVariable is done on the root token. This is confusing. On the other hand createVariable(<name>, <value>, <token>) on a token works as one would expect setVariable to: a variable is created and updated with this call. The documentation only mentions setVariable, but the Javadoc does describe the setVariable behavior, so it is intentional. I still would suggest to make a more natural behavior: - createVariable truly only creates, if the variable exists it should thrown an exception. - setVariable, creates and/or updates the variable I'm fully aware that breaking the API's behavior is unwanted, which is why the following may come in handy. The only way AFAIK to set a variable starting at a token is by executing the code below: token.getProcessInstance().getContextInstance().setVariable("var","value", token); It would be more logical to be able to do it like this: token.setVariable("var","value"); So I would suggest adding a setVariable method to Token that behaves like the createVariable of ContextInstance. -- 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

17 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1129) On signalling a subprocess, the workflow does not stop at the start state of the subprocess even if a task is present in start state of subprocess

by Debnath Mukherjee (JIRA)

On signalling a subprocess, the workflow does not stop at the start state of the subprocess even if a task is present in start state of subprocess -------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBPM-1129 URL: http://jira.jboss.com/jira/browse/JBPM-1129 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2, jBPM 3.1.4 Environment: Windows XP, JBPM 3.1.4. Most likely also present in 3.2.2. Reporter: Debnath Mukherjee Assigned To: Tom Baeyens Test case and setup details are available in the JBPM forum post. If the first state of a subprocess contains a task, there is no opportunity to create the task, as, on signalling the process state, the workflow does not stop at the first state but goes to the first task (defined in a task-node) in the subprocess. -- 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

17 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1872) set up db matrix job for jbpm 4

by Tom Baeyens (JIRA)

set up db matrix job for jbpm 4 ------------------------------- Key: JBPM-1872 URL: https://jira.jboss.org/jira/browse/JBPM-1872 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0.0 Alpha1 At a minimal, MySql should be in there, but oracle, postgres and other tier 1 DBs from the soa platform would be nice. -- 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

17 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-1881) Release jBPM 4.0.0 Alpha1

by Thomas Diesler (JIRA)

Release jBPM 4.0.0 Alpha1 ------------------------- Key: JBPM-1881 URL: https://jira.jboss.org/jira/browse/JBPM-1881 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Core Engine Reporter: Thomas Diesler Fix For: jBPM 4.0.0 Alpha1 -- 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

17 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1824) Investigate core test failures against Sybase

by Thomas Diesler (JIRA)

Investigate core test failures against Sybase --------------------------------------------- Key: JBPM-1824 URL: https://jira.jboss.org/jira/browse/JBPM-1824 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Fix For: jBPM 3.3.1 GA <exclude>org/jbpm/db/DeleteProcessInstanceDbTest.java</exclude> <exclude>org/jbpm/graph/exe/SubProcessPlusConcurrencyDbTest.java</exclude> <exclude>org/jbpm/jbpm1072/JBPM1072Test.java</exclude> <exclude>org/jbpm/jbpm1755/JBPM1755Test.java</exclude> <exclude>org/jbpm/jbpm983/JBPM983Test.java</exclude> <exclude>org/jbpm/job/executor/JobExecutorDbTest.java</exclude> <exclude>org/jbpm/optimisticlocking/LockingTest.java</exclude> <exclude>org/jbpm/scheduler/exe/UnsafeSessionUsageTest.java</exclude> <exclude>org/jbpm/seam/JobExecutorCustomizationTest.java</exclude> -- 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

17 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-1921) getGroupTaskList(List actorids) behaviour changed

by Daniel Bremer-Tonn (JIRA)

getGroupTaskList(List actorids) behaviour changed ------------------------------------------------- Key: JBPM-1921 URL: https://jira.jboss.org/jira/browse/JBPM-1921 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: API Affects Versions: jBPM 3.3.0 GA Reporter: Daniel Bremer-Tonn We migrated from jpdl v3.2.3 to v3.3 and did see some new behaviour for "JBPMContext.getGroupTaskList(List actorIds)". Behaviour in V3.2.3: Assigning a task to two pooledActorIds and calling JBPMContext.getGroupTaskList(List actorIds) with these two pooledActorIds will get you a list with one TaskInstance. In v3.3 you will get now a list with two items, which are two references to the same Taskinstance. While digging into the code I've found a change in the corresponding hibernate-query ("TaskMgmtSession.findPooledTaskInstancesByActorIds" in hibernate.queries.hbm.xml). The 3.2.3 version uses the "distinct" keyword, while the 3.3 one does not. Since this is some change in behaviour of the method JBPMContext.getGroupTaskList(List actorIds) either it should be fixed, or if intended should be documented somewhere. Best regards, Daniel Bremer-Tonn -- 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

17 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1816) Sanitize tests that leak jBPM configurations (and connection pools)

by Alejandro Guizar (JIRA)

Sanitize tests that leak jBPM configurations (and connection pools) ------------------------------------------------------------------- Key: JBPM-1816 URL: https://jira.jboss.org/jira/browse/JBPM-1816 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.3.0 GA Tests that use a custom jBPM configuration leave it hanging around with a session factory and a pool of JDBC connections. The jBPM configuration must be explicitly closed so that those JDBC connections can be released. -- 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

17 years, 3 months

1
6
0 / 0

[JBoss JIRA] Created: (JBPM-1754) StaleObjectLog verbosity control code should be added to flushSession()

by Alejandro Guizar (JIRA)

StaleObjectLog verbosity control code should be added to flushSession() ----------------------------------------------------------------------- Key: JBPM-1754 URL: https://jira.jboss.org/jira/browse/JBPM-1754 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alejandro Guizar Fix For: jBPM 3.3.0 GA DbPersistenceService.flushSession line #272 Since a StaleObjectStateExcetion occures in flushSession() rather than commit(), StaleObjectLog verbosity control code should be added to flushSession() method as the same manner as commit(). See the following code snippet. An external transaction manager is being used and indeed DbPersistenceService.commit() does nothing. Exception flushSession() { if (mustSessionBeFlushed) { try { log.debug("flushing hibernate session " + session.toString()); session.flush(); // >>>>>>> begin } catch (StaleObjectStateException e) { log.info("optimistic locking failed"); StaleObjectLogConfigurer.staleObjectExceptionsLog.error("optimistic locking failed", e); return e; // <<<<<<< end } catch (Exception e) { log.error("hibernate flush failed", e); return e; } } return null; } -- 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

17 years, 3 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues December 2008