May 2008 - jbpm-issues - Jboss List Archives

[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-1177) JBPM.3 in SOA-P 4.2 CP1 test suite failures with sybase

by Aleksandar Kostadinov (JIRA)

JBPM.3 in SOA-P 4.2 CP1 test suite failures with sybase ------------------------------------------------------- Key: JBPM-1177 URL: http://jira.jboss.com/jira/browse/JBPM-1177 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Reporter: Aleksandar Kostadinov Assigned To: Tom Baeyens I see the following tests fail with sybase12.5: * org.jbpm.AllTests.testManyBlocks * org.jbpm.AllTests.testVariableInstanceByteArray * org.jbpm.AllTests.testDeployProcessWithFile * org.jbpm.AllTests.testExecuteResourceUsingProcess * org.jbpm.AllTests.testProcessClassLoading See http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/jboss-soa-platform... for details. -- 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

4
14
0 / 0

[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-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-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-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, 4 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1121) Calculation of confidence interval / required sample size

by Bernd Ruecker (JIRA)

Calculation of confidence interval / required sample size --------------------------------------------------------- Key: JBPM-1121 URL: http://jira.jboss.com/jira/browse/JBPM-1121 Project: JBoss jBPM Issue Type: Feature Request Components: Simulation Reporter: Bernd Ruecker Assigned To: Tom Baeyens For simulation it would be nice to have an automatic calculation of the required sample saize for a simulation run with a give nconfidence level. For details on the theoretical background have a look in my master thesis page 36ff.: http://www.camunda.com/content/publikationen/bernd-ruecker-business-proce... Required formulas are prepared in the class org.jbpm.sim.report.StatUtil. -- 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, 4 months

3
4
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, 4 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, 4 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 May 2008