February 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1106) GetProcessInstancesCommand should use Query.setTimestamp instead of Query.setDate.

by Alexey Kostylev (JIRA)

GetProcessInstancesCommand should use Query.setTimestamp instead of Query.setDate. ---------------------------------------------------------------------------------- Key: JBPM-1106 URL: http://jira.jboss.com/jira/browse/JBPM-1106 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Alexey Kostylev Assigned To: Tom Baeyens In current impementation we cannot filter process instances using time. -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-1119) Timers using EjbSchedulerService are not persisted across JBoss restarts

by Aner Perez (JIRA)

Timers using EjbSchedulerService are not persisted across JBoss restarts ------------------------------------------------------------------------ Key: JBPM-1119 URL: http://jira.jboss.com/jira/browse/JBPM-1119 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.1 Environment: JBoss 4.0.5 Reporter: Aner Perez Assigned To: Tom Baeyens Timers created using the EjbSchedulerService do not fire if JBoss is restarted after the timer is set. The reason is that although the JBPM timer row still exists in the database, there is no corresponding EJB timer to kick off the JBPM timer action. EJB timers are supposed to persist across server restarts but there is a catch. JBPM uses an EJB with a "local" interface to dispatch the JBPM timers. JBoss (as of 4.0.2) has decided to make the jndi name of EJBs with local interfaces have a unique name by appending an '@' sign and a hashcode to the EJB name. This hash code is different every time the server is restarted. When the EJB timers are reloaded after a restart, the EJB that is supposed to receive the timer doesn't exist anymore because it now has a different name (different hashcode). This causes the timers to be deactivated and they do not fire at the appointed time. See http://wiki.jboss.org/wiki/Wiki.jsp?page=WhyDoesTheLocalNameContainARando... for an explanation of the EJB name issue for EJBs with a local interface. We need a local-jndi-name parameter added to the TimerServiceBean so we can always locate it under the same name and the timers will work as expected. adding the following to jboss.xml takes care of this issue: <session> <ejb-name>TimerServiceBean</ejb-name> <local-jndi-name>TimerServiceBean</local-jndi-name> </session> -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1130) complete Task fails with in transaction with Session closed Error.

by vijay koripella (JIRA)

complete Task fails with in transaction with Session closed Error. ------------------------------------------------------------------ Key: JBPM-1130 URL: http://jira.jboss.com/jira/browse/JBPM-1130 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.1 Reporter: vijay koripella Assigned To: Tom Baeyens When ever we complete a task in the jbp process we get the below exception when ever we are using the transaction supports . If for the completeTask method we specify the TRANSACTION_NOT_SUPPORTED then this works. So in summary the jbpm complete Task fails when used with in transaction. This is the below exception we get. Please also refere to theese links , they are also the same issue. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105609#4105609 http://www.mail-archive.com/jboss-user@lists.jboss.org/msg106103.html Exception: Caused by: org.springframework.transaction.UnexpectedRollbackException: JTA transaction unexpectedly rolled back (maybe due to a timeout); nested exception is weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion: sync=org.jbpm.db.JobSession$DeleteJobsSynchronization@18db529 Session is closed! at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:845) 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.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:117) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy110.saveClaimAndCompleteClaimUserTask(Unknown Source) 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:585) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at com.marsh.itg.ddeepa.services.interception.ExportedServiceWrapperFactoryBean$2$1$1.run(ExportedServiceWrapperFactoryBean.java:83) at com.marsh.itg.ddeepa.services.interception.ExportedServiceWrapperFactoryBean$2$1.run(ExportedServiceWrapperFactoryBean.java:104) at com.marsh.itg.ddeepa.services.util.common.ThreadLocalVariable.runWith(ThreadLocalVariable.java:43) at com.marsh.itg.ddeepa.services.interception.ExportedServiceWrapperFactoryBean$2.invoke(ExportedServiceWrapperFactoryBean.java:75) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy110.saveClaimAndCompleteClaimUserTask(Unknown Source) 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:585) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at org.springframework.remoting.support.RemoteInvocationTraceInterceptor.invoke(RemoteInvocationTraceInterceptor.java:70) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy109.saveClaimAndCompleteClaimUserTask(Unknown Source) 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:585) at org.springframework.remoting.support.RemoteInvocation.invoke(RemoteInvocation.java:205) at org.springframework.remoting.support.DefaultRemoteInvocationExecutor.invoke(DefaultRemoteInvocationExecutor.java:38) at org.springframework.remoting.support.RemoteInvocationBasedExporter.invoke(RemoteInvocationBasedExporter.java:76) at org.springframework.remoting.support.RemoteInvocationBasedExporter.invokeAndCreateResult(RemoteInvocationBasedExporter.java:112) at org.springframework.remoting.httpinvoker.HttpInvokerServiceExporter.handleRequest(HttpInvokerServiceExporter.java:117) at org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter.handle(HttpRequestHandlerAdapter.java:49) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:857) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:792) at com.marsh.itg.ddeepa.services.platform.MarshDispatcherServlet.access$0(MarshDispatcherServlet.java:1) at com.marsh.itg.ddeepa.services.platform.MarshDispatcherServlet.doService(MarshDispatcherServlet.java:65) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:475) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:440) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3370) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2117) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2023) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200) at weblogic.work.ExecuteThread.run(ExecuteThread.java:172) at org.springframework.remoting.support.RemoteInvocationUtils.fillInClientStackTraceIfPossible(RemoteInvocationUtils.java:47) at org.springframework.remoting.support.RemoteInvocationResult.recreate(RemoteInvocationResult.java:105) at org.springframework.remoting.support.RemoteInvocationBasedAccessor.recreateRemoteInvocationResult(RemoteInvocationBasedAccessor.java:83) at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:159) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy159.saveClaimAndCompleteClaimUserTask(Unknown Source) 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:585) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at org.springframework.aop.framework.adapter.AfterReturningAdviceInterceptor.invoke(AfterReturningAdviceInterceptor.java:50) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:50) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy159.saveClaimAndCompleteClaimUserTask(Unknown Source) at com.marsh.itg.gws.presentation.order.view.component.OrderPaymentForm.finish(OrderPaymentForm.java:247) at com.marsh.itg.gws.presentation.order.view.component.OrderPaymentForm.access$2(OrderPaymentForm.java:180) at com.marsh.itg.gws.presentation.order.view.component.OrderPaymentForm$3.perform(OrderPaymentForm.java:141) at com.marsh.itg.ddeepa.presentation.framework.components.AbstractActionHandler.execute(AbstractActionHandler.java:31) at com.marsh.itg.ddeepa.presentation.framework.components.MButton.onSubmit(MButton.java:50) at wicket.markup.html.form.Form.delegateSubmit(Form.java:574) at wicket.markup.html.form.Form.onFormSubmitted(Form.java:313) ... 32 more Caused by: weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion: sync=org.jbpm.db.JobSession$DeleteJobsSynchronization@18db529 Session is closed! at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1818) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:333) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:281) at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:275) at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:842) ... 121 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

15 years, 3 months

6
16
0 / 0

[JBoss JIRA] Created: (JBPM-1098) businesscalendar is unaware of leapyears

by Ronald van Kuijk (JIRA)

businesscalendar is unaware of leapyears ---------------------------------------- Key: JBPM-1098 URL: http://jira.jboss.com/jira/browse/JBPM-1098 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: Windows 2000, jdk 1.5.2_12 Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Priority: Minor businesscalendar of 65 years is 65/4 = 16 days short ( based on 1971). -- 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, 3 months

3
12
0 / 0

[JBoss JIRA] Created: (JBPM-1135) JobSession.deleteJobsForProcessInstance doesn't work if jbpm isn't the transaction manager

by Jérôme Tellier (JIRA)

JobSession.deleteJobsForProcessInstance doesn't work if jbpm isn't the transaction manager ------------------------------------------------------------------------------------------ Key: JBPM-1135 URL: http://jira.jboss.com/jira/browse/JBPM-1135 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Jérôme Tellier Assigned To: Tom Baeyens My configuration of the persistence service is this : <service name="persistence"> <factory> <bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory"> <field name="isCurrentSessionEnabled"><false /></field> <field name="isTransactionEnabled"><false /></field> </bean> </factory> </service> When I call JobSession.deleteJobsForProcessInstance, the method beforeCompletion() in DeleteJobsSynchronization is never call in the commit, probably because jbpm isn't the transaction manager. -- 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, 3 months

5
17
0 / 0

[JBoss JIRA] Created: (JBPM-1092) EjbSchedulerService does not delete executed timer from DB

by Britt Miner (JIRA)

EjbSchedulerService does not delete executed timer from DB ---------------------------------------------------------- Key: JBPM-1092 URL: http://jira.jboss.com/jira/browse/JBPM-1092 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Britt Miner Assigned To: Tom Baeyens When using the EjbSchedulerService, I've been having a problem with non-repeating timers not being removed from the database after they are executed. Of course, they won't be executed again because there is no longer an EJB timer to call them; however, if the EjbSchedulerService is ever replaced on the same installation with a DbSchedulerService, then all of these timers would likely be re-executed. I was unable to find any code in the implementation that should have deleted a non-repeating timer from the database after execution, so I modified org.jbpm.scheduler.ejbtimer.ExecuteTimerCommand to take advantage of the boolean already being returned from Timer.execute(): //original line //timer.execute(jbpmContext); // BRITT-- if we're done with this timer, let's get rid of it... boolean deleteJob = timer.execute(jbpmContext); if(deleteJob) { jbpmContext.getJobSession().deleteJob(timer); } // --BRITT Note: While I doubt that it has any effect on this issue, I'll note that to get the EjbSchedulerService working in the first place, I implemented the EJB reference changes proposed here http://jira.jboss.com/jira/browse/JBPM-836. -Britt -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-1123) Simulation doesn't work correctly without Start-State

by Bernd Ruecker (JIRA)

Simulation doesn't work correctly without Start-State ----------------------------------------------------- Key: JBPM-1123 URL: http://jira.jboss.com/jira/browse/JBPM-1123 Project: JBoss jBPM Issue Type: Bug Components: Simulation Reporter: Bernd Ruecker Assigned To: Tom Baeyens Simulation cannot handle processes without start-state at the moment. This is because an event is added to the start-state needed to work correctly. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-1125) XML-Schema for experiment-configuration XML is missing

by Bernd Ruecker (JIRA)

XML-Schema for experiment-configuration XML is missing ------------------------------------------------------ Key: JBPM-1125 URL: http://jira.jboss.com/jira/browse/JBPM-1125 Project: JBoss jBPM Issue Type: Task Components: Simulation Reporter: Bernd Ruecker Assigned To: Tom Baeyens Priority: Optional There is not XML-Schema for the simulation configuration available yet. This should be solved as soon as the configuration becomes stable. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1122) Suport multiple simulation runs and apply statistical evaluation of them

by Bernd Ruecker (JIRA)

Suport multiple simulation runs and apply statistical evaluation of them ------------------------------------------------------------------------ Key: JBPM-1122 URL: http://jira.jboss.com/jira/browse/JBPM-1122 Project: JBoss jBPM Issue Type: Feature Request Components: Simulation Reporter: Bernd Ruecker Assigned To: Tom Baeyens Priority: Optional Currently every scenario is only executed once during an experiment. If you want to draw valid conclusions you need more than one simulation run (as a rule of thumb 30 is a good number). If running the same scenario multiple times (with different seeds for the random number generator) the results of the single runs is no more interesting, the means of the figures are important. The tool should support configuring multiple runs in the configuration and provide an additional result with the means. These means allow to draw conclusions about probabilities for a special result (for example "cycle time < 2 hours") with a easy normal distribution (because of the central limit theorem). have a look in my master thesis for details (http://www.camunda.com/content/publikationen/bernd-ruecker-business-proce...), there I also implemented it manually for the prototype (source code on page 112). Very cool would be an automatic detection of the required number of runs if JBPM-1121 is implemented (http://jira.jboss.org/jira/browse/JBPM-1121). -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1124) Simulation doesn't support sub-process, super-state and timer

by Bernd Ruecker (JIRA)

Simulation doesn't support sub-process, super-state and timer ------------------------------------------------------------- Key: JBPM-1124 URL: http://jira.jboss.com/jira/browse/JBPM-1124 Project: JBoss jBPM Issue Type: Feature Request Components: Simulation Reporter: Bernd Ruecker Assigned To: Tom Baeyens Priority: Minor As the summary says, these concepts are not yet supported. -- 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, 3 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues February 2008