August 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1772) Fix JoinDbTest on postgresql

by Thomas Diesler (JIRA)

Fix JoinDbTest on postgresql ---------------------------- Key: JBPM-1772 URL: https://jira.jboss.org/jira/browse/JBPM-1772 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 3.3.1 GA expected:<[10X, 10Y, 10Z, 10a, 10b, 10c, 10d, 10e, 11X, 11Y, 11Z, 11a, 11b, 11c, 11d, 11e, 12X, 12Y, 12Z, 12a, 12b, 12c, 12d, 12e, 13X, 13Y, 13Z, 13a, 13b, 13c, 13d, 13e, 14X, 14Y, 14Z, 14a, 14b, 14c, 14d, 14e, 15X, 15Y, 15Z, 15a, 15b, 15c, 15d, 15e, 16X, 16Y, 16Z, 16a, 16b, 16c, 16d, 16e, 17X, 17Y, 17Z, 17a, 17b, 17c, 17d, 17e, 18X, 18Y, 18Z, 18a, 18b, 18c, 18d, 18e, 19X, 19Y, 19Z, 19a, 19b, 19c, 19d, 19e, 1X, 1Y, 1Z, 1a, 1b, 1c, 1d, 1e, 20X, 20Y, 20Z, 20a, 20b, 20c, 20d, 20e, 2X, 2Y, 2Z, 2a, 2b, 2c, 2d, 2e, 3X, 3Y, 3Z, 3a, 3b, 3c, 3d, 3e, 4X, 4Y, 4Z, 4a, 4b, 4c, 4d, 4e, 5X, 5Y, 5Z, 5a, 5b, 5c, 5d, 5e, 6X, 6Y, 6Z, 6a, 6b, 6c, 6d, 6e, 7X, 7Y, 7Z, 7a, 7b, 7c, 7d, 7e, 8X, 8Y, 8Z, 8a, 8b, 8c, 8d, 8e, 9X, 9Y, 9Z, 9a, 9b, 9c, 9d, 9e]> but was:<[100X, 100Y, 100Z, 100a, 100b, 100c, 100d, 100e, 108X, 108Y, 108Z, 108a, 108b, 108c, 108d, 108e, 116X, 116Y, 116Z, 116a, 116b, 116c, 116d, 116e, 124X, 124Y, 124Z, 124a, 124b, 124c, 124d, 124e, 132X, 132Y, 132Z, 132a, 132b, 132c, 132d, 132e, 140X, 140Y, 140Z, 140a, 140b, 140c, 140d, 140e, 148X, 148Y, 148Z, 148a, 148b, 148c, 148d, 148e, 156X, 156Y, 156Z, 156a, 156b, 156c, 156d, 156e, 164X, 164Y, 164Z, 164a, 164b, 164c, 164d, 164e, 172X, 172Y, 172Z, 172a, 172b, 172c, 172d, 172e, 180X, 180Y, 180Z, 180a, 180b, 180c, 180d, 180e, 188X, 188Y, 188Z, 188a, 188b, 188c, 188d, 188e, 36X, 36Y, 36Z, 36a, 36b, 36c, 36d, 36e, 44X, 44Y, 44Z, 44a, 44b, 44c, 44d, 44e, 52X, 52Y, 52Z, 52a, 52b, 52c, 52d, 52e, 60X, 60Y, 60Z, 60a, 60b, 60c, 60d, 60e, 68X, 68Y, 68Z, 68a, 68b, 68c, 68d, 68e, 76X, 76Y, 76Z, 76a, 76b, 76c, 76d, 76e, 84X, 84Y, 84Z, 84a, 84b, 84c, 84d, 84e, 92X, 92Y, 92Z, 92a, 92b, 92c, 92d, 92e]> -- 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, 2 months

4
13
0 / 0

[JBoss JIRA] Created: (JBPM-2509) database migration installation script

by Tom Baeyens (JIRA)

database migration installation script -------------------------------------- Key: JBPM-2509 URL: https://jira.jboss.org/jira/browse/JBPM-2509 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Alejandro Guizar Fix For: jBPM 4.2 Database migration should be offered as a target in the install build file. And it should work in the distro without requiring the source build. -- 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, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBPM-2453) Add suport for custom reports

by Joram Barrez (JIRA)

Add suport for custom reports ----------------------------- Key: JBPM-2453 URL: https://jira.jboss.org/jira/browse/JBPM-2453 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0 Reporter: Joram Barrez Assignee: Heiko Braun Fix For: jBPM 4.1 Currently, the default reports can be customized completely if the file name is kept the same. The reporting mechanism should be extended that it is possible to add custom reports (ie with other names) for display in the gwt console. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-2487) Bug in GroupActivity.execute(ExecutionImpl execution)

by Michael Wohlfart (JIRA)

Bug in GroupActivity.execute(ExecutionImpl execution) ----------------------------------------------------- Key: JBPM-2487 URL: https://jira.jboss.org/jira/browse/JBPM-2487 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0 Reporter: Michael Wohlfart just browsing through the codebase and trying to understand the magic, I came across this in line 56 of GroupActivity.java: ExecutionImpl concurrentRoot = null; if (Execution.STATE_ACTIVE_ROOT.equals(execution.getState())) { concurrentRoot = execution; } else if (Execution.STATE_ACTIVE_ROOT.equals(execution.getState())) { concurrentRoot = execution.getParent(); } else { throw new JbpmException("illegal state"); } I assume getState() doesn't have any side effects, so I guess this is a bug -- 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, 2 months

4
13
0 / 0

[JBoss JIRA] Created: (JBPM-2388) extend coverage of jpdl process conversion tool

by Tom Baeyens (JIRA)

extend coverage of jpdl process conversion tool ----------------------------------------------- Key: JBPM-2388 URL: https://jira.jboss.org/jira/browse/JBPM-2388 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Jim Ma Fix For: jBPM 4.1 Further elaborate on the work started in 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2036) StaleObjectStateException when timer firing leads to process end and timer has 'repeat' attribute set

by Martin Putz (JIRA)

StaleObjectStateException when timer firing leads to process end and timer has 'repeat' attribute set ----------------------------------------------------------------------------------------------------- Key: JBPM-2036 URL: https://jira.jboss.org/jira/browse/JBPM-2036 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.3.1 GA, jBPM-3.2.5.SP1 Reporter: Martin Putz Assignee: Alejandro Guizar Fix For: jBPM 3.2.6 GA With the following timer definition on a state node <state name='state1'> <timer name='timer-to-end-with-repeat' duedate='1 second' repeat='5 seconds'> <action class='org.jbpm.scheduler.exe.TimerDbTest$Signal' /> </timer> <transition name='to_end' to='end'/> </state> and the action class execute() method being public void execute(ExecutionContext executionContext) throws Exception { executionContext.leaveNode(); } leads to: 2009-02-10 21:38:45,404 16508 ERROR [org.hibernate.event.def.AbstractFlushingEventListener] (JbpmJobExecutor:127.0.0.1:1:) Could not synchronize database state with session org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.job.Timer#86] at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1769) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2412) at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2312) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2612) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:96) 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:168) 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.jbpm.persistence.db.DbPersistenceService.commit(DbPersistenceService.java:226) at org.jbpm.persistence.db.DbPersistenceService.endTransaction(DbPersistenceService.java:131) at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:197) at org.jbpm.svc.Services.close(Services.java:243) at org.jbpm.JbpmContext.close(JbpmContext.java:133) at org.jbpm.job.executor.JobExecutorThread.executeJob(JobExecutorThread.java:194) at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:61) If 'repeat' is not set, the process finishes just fine. -- 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, 2 months

6
30
0 / 0

[JBoss JIRA] Created: (JBPM-2037) Release jBPM 3.2.7 GA

by Thomas Diesler (JIRA)

Release jBPM 3.2.7 GA --------------------- Key: JBPM-2037 URL: https://jira.jboss.org/jira/browse/JBPM-2037 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: jBPM 3.2.6 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

15 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-2290) Default config should use the db based implementations for messaging and scheduler service

by Martin Putz (JIRA)

Default config should use the db based implementations for messaging and scheduler service ------------------------------------------------------------------------------------------ Key: JBPM-2290 URL: https://jira.jboss.org/jira/browse/JBPM-2290 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 3.2.5.SP5 Reporter: Martin Putz Fix For: SOA 4.3 CP02 The default configuration in the jbpm-jpdl-3.2.5SP5 package defines the usage of the JmsMessageServiceFactory for the 'message' service and EntitySchedulerServiceFactory for the 'scheduler' service in /deploy/server/default/deploy/jbpm/jbpm-service.sar/jbpm.cfg.xml. The default configuration should use the db based implementations for these services instead, as it used to be in previous versions. -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2129) Failed to ManagedJbpmContext.joinTransaction in My Quartz Dispatcher Event on rare occasions

by Akihito Nohara (JIRA)

Failed to ManagedJbpmContext.joinTransaction in My Quartz Dispatcher Event on rare occasions -------------------------------------------------------------------------------------------- Key: JBPM-2129 URL: https://jira.jboss.org/jira/browse/JBPM-2129 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.2 Environment: * seam 2.0.2.SP1 * jBPM 3.2.3 * and added <transaction:ejb-transaction /> in conponents.xml Reporter: Akihito Nohara usually, its processed nomally. any ideas??? {{{ 2009-04-01 14:20:00,033 ERROR [org.quartz.core.JobRunShell] (DefaultQuartzScheduler_Worker-3) Job DEFAULT.701fab4a:11fbb06f0cb:-7fc2 threw an unhandled Exception: javax.ejb.EJBTransactionRolledbackException: JbpmContext may only be used inside a transaction at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:240) at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:210) at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:84) at $Proxy649.send(Unknown Source) at sun.reflect.GeneratedMethodAccessor16177.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54) at org.javassist.tmp.java.lang.Object_$$_javassist_37.send(Object_$$_javassist_37.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2092) at org.jboss.seam.core.Events.raiseEvent(Events.java:84) at org.jboss.seam.async.AsynchronousEvent.call(AsynchronousEvent.java:27) at org.jboss.seam.async.Asynchronous.executeInContexts(Asynchronous.java:76) at org.jboss.seam.async.Asynchronous.execute(Asynchronous.java:45) at org.jboss.seam.async.QuartzDispatcher$QuartzJob.execute(QuartzDispatcher.java:240) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: java.lang.IllegalStateException: JbpmContext may only be used inside a transaction at org.jboss.seam.bpm.ManagedJbpmContext.joinTransaction(ManagedJbpmContext.java:83) at org.jboss.seam.bpm.ManagedJbpmContext.getJbpmContext(ManagedJbpmContext.java:73) at sun.reflect.GeneratedMethodAccessor40220.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2092) at org.jboss.seam.Component.unwrap(Component.java:2118) at org.jboss.seam.Component.getInstance(Component.java:1890) at org.jboss.seam.Component.getInstance(Component.java:1855) at org.jboss.seam.Component.getInstance(Component.java:1832) at org.jboss.seam.Component.getInstance(Component.java:1827) at org.jboss.seam.bpm.ManagedJbpmContext.instance(ManagedJbpmContext.java:165) at com.doramura.system.SendFtpObserver.send(SendFtpObserver.java:43) at sun.reflect.GeneratedMethodAccessor16178.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.seam.intercept.EJBInvocationContext.proceed(EJBInvocationContext.java:44) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.bpm.BusinessProcessInterceptor.aroundInvoke(BusinessProcessInterceptor.java:49) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.persistence.EntityManagerProxyInterceptor.aroundInvoke(EntityManagerProxyInterceptor.java:26) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.persistence.HibernateSessionProxyInterceptor.aroundInvoke(HibernateSessionProxyInterceptor.java:27) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:50) at sun.reflect.GeneratedMethodAccessor110.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) }}} {{{ @Stateless @TransactionManagement(TransactionManagementType.CONTAINER) @org.jboss.seam.annotations.Name("SendFtpObserver") public class SendFtpObserver implements ISendFtpObserver { @Logger private Log log; @Observer("SendFtpStart") @TransactionAttribute(TransactionAttributeType.REQUIRED) public void send() { : : : } } }}} -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2501) revisit jboss jbpm service archive architecture

by Tom Baeyens (JIRA)

revisit jboss jbpm service archive architecture ----------------------------------------------- Key: JBPM-2501 URL: https://jira.jboss.org/jira/browse/JBPM-2501 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.2 revisit the jbpm service archive and the way that the process engine is published into JNDI the process/businessarchive deployer should be removed -- 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, 2 months

1
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues August 2009