December 2007 - jbpm-issues - Jboss List Archives

[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-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-1087) Creating a new process project raises FileNotFoundException

by Len DiMaggio (JIRA)

Creating a new process project raises FileNotFoundException ----------------------------------------------------------- Key: JBPM-1087 URL: http://jira.jboss.com/jira/browse/JBPM-1087 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Environment: jbpm-jpdl-suite-3.2.2 (for runtime) Core and Designer plugin 3.0.13 Eclipse Europa - Version: 3.3.1.1 RHEL5 Sun Java 1.5.0_13 Reporter: Len DiMaggio Assigned To: Tom Baeyens Priority: Minor Creating a new process project raises this exception - there doesn't appear to have a functional impact. ./eclipse jbpm-jpdl-3.2.2 java.io.FileNotFoundException: /opt/jbpm_Nov/jbpm-jpdl-3.2.2/config/META-INF (Is a directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at org.jbpm.ui.wizard.NewProcessProjectWizard.copyJbpmResource(Unknown Source) at org.jbpm.ui.wizard.NewProcessProjectWizard.copyJbpmResources(Unknown Source) at org.jbpm.ui.wizard.NewProcessProjectWizard.createInitialContent(Unknown Source) at org.jbpm.ui.wizard.NewProcessProjectWizard.createJavaProject(Unknown Source) at org.jbpm.ui.wizard.NewProcessProjectWizard.performFinish(Unknown Source) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:116) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) -- 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-1107) MessageProducer.send(Destination, Message) throws UnsupportedOperationException.

by Alexey Kostylev (JIRA)

MessageProducer.send(Destination, Message) throws UnsupportedOperationException. -------------------------------------------------------------------------------- Key: JBPM-1107 URL: http://jira.jboss.com/jira/browse/JBPM-1107 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: Glassfish V2 Reporter: Alexey Kostylev Assigned To: Tom Baeyens When deploying on Glassfish V2 server JmsMessageServiceImpl throws an Exception. Due to the JMS API docs (http://java.sun.com/j2ee/1.4/docs/api/javax/jms/MessageProducer.html#send... this is expected behaviour: ... UnsupportedOperationException - if a client uses this method with a MessageProducer that specified a destination at creation time ... If change getMessageProducer().send(destination, message); to getMessageProducer().send(message); then all is working. -- 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-1104) StartProcessInstanceCommand and SignalCommand do not save process instance in JbpmContext.

by Alexey Kostylev (JIRA)

StartProcessInstanceCommand and SignalCommand do not save process instance in JbpmContext. ------------------------------------------------------------------------------------------ Key: JBPM-1104 URL: http://jira.jboss.com/jira/browse/JBPM-1104 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Alexey Kostylev Assigned To: Tom Baeyens When using CommandService interface to start process instance logs are not saved in the database. -- 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-1102) Despite source comment, JobExecutorServlet does not stop threads on destroy

by Pierre Demeestere (JIRA)

Despite source comment, JobExecutorServlet does not stop threads on destroy --------------------------------------------------------------------------- Key: JBPM-1102 URL: http://jira.jboss.com/jira/browse/JBPM-1102 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: Windows NT and Linux RH 4 Reporter: Pierre Demeestere Assigned To: Tom Baeyens Priority: Minor when stopping application server, an NullPointerException is spoted at line 84 for JobExecutorThread. That maybe because threads are not stopped properly when the JobExecutorServlet is undeployed. Indeed, despite source comments in JobExecutorServlet, nothing is done in this servlet to stop the threads when the servlet is undeployed. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBPM-1096) NewProcessInstanceCommand.execute() return ProcessInstance object, not id as mentioned in docs.

by Alexey Kostylev (JIRA)

NewProcessInstanceCommand.execute() return ProcessInstance object, not id as mentioned in docs. ----------------------------------------------------------------------------------------------- Key: JBPM-1096 URL: http://jira.jboss.com/jira/browse/JBPM-1096 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Alexey Kostylev Assigned To: Tom Baeyens As I looked into the source I saw that this method return the whole object: Object result = null; if (createStartTask) { result = processInstance.getTaskMgmtInstance().createStartTaskInstance(); } else { result = processInstance; } But doc says that: /** * return the id of the newly created process instance. * @throws Exception */ public Object execute(JbpmContext jbpmContext) throws Exception { ... } -- 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
4
0 / 0

[JBoss JIRA] Created: (JBPM-1103) Make repeat accept EL in addition to the already existing businesscalendar

by Ronald van Kuijk (JIRA)

Make repeat accept EL in addition to the already existing businesscalendar -------------------------------------------------------------------------- Key: JBPM-1103 URL: http://jira.jboss.com/jira/browse/JBPM-1103 Project: JBoss jBPM Issue Type: Feature Request Affects Versions: jBPM jPDL 3.2.2 Reporter: Ronald van Kuijk Assigned To: Ronald van Kuijk Priority: Optional Fix For: jBPM 3.3 Just like with the dueate itself.... Note: make sure to refacor this code into a new class in the calendar package -- 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-1093) Allow more than one action to be executed when entering a page node

by Matthew Lieder (JIRA)

Allow more than one action to be executed when entering a page node ------------------------------------------------------------------- Key: JBPM-1093 URL: http://jira.jboss.com/jira/browse/JBPM-1093 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Matthew Lieder Assigned To: Tom Baeyens Only the first <action> is executed when multiple actions are children of <page> and <start-page> elements in a jPDL pageflow. It would be greatly appreciated if the logic could be changed so that all <action> elements are executed (like they are when children of <transition> elements). Example: <page name="page1" view-id="/page1.xhtml"> <action expression="#{someMethodThatIsExecuted} /> <action expression="#{someMethodThatIsNotExecuted} /> <transition name="save" to="terminate"> <action expression="#{someMethodThatIsExecuted} /> <action expression="#{someMethodThatIsExecuted} /> </transition> </page> -- 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
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues December 2007