[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
[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
[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
[JBoss JIRA] Created: (JBPM-1085) Join of new process instance fails in Oracle
by Tom Baeyens (JIRA)
Join of new process instance fails in Oracle
--------------------------------------------
Key: JBPM-1085
URL: http://jira.jboss.com/jira/browse/JBPM-1085
Project: JBoss jBPM
Issue Type: Bug
Affects Versions: jBPM jPDL 3.2.2
Reporter: Tom Baeyens
Assigned To: Tom Baeyens
Fix For: jBPM jPDL 3.2.3, jBPM 3.2.2 SOA 1
If in one transaction you create a new process instance and reach a join, you'll get a invalid StaleObjectStateException. The cause is that in case of oracle, hibernate will not insert the record in the database before the forced version increment in the join will be executed. That results in 0 rows updated and hence a StaleStateObjectException.
The fix applied is that we added a flush before the forced version update in the join
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBPM-1089) JBPM.3 SOA-P branch to be testable against EAP/SOA-P distribution
by Aleksandar Kostadinov (JIRA)
JBPM.3 SOA-P branch to be testable against EAP/SOA-P distribution
-----------------------------------------------------------------
Key: JBPM-1089
URL: http://jira.jboss.com/jira/browse/JBPM-1089
Project: JBoss jBPM
Issue Type: Task
Reporter: Aleksandar Kostadinov
Assigned To: Koen Aers
We need to be able to test the SOA-P branch of jbpm against JBoss EAP 4.3 and JBoss SOA-P.
So that will require the availability of a build option to select location of EAP/SOA-P binary zip distribution and if that property has been set, the test.classpath of tested modules to be set to use libraries from the distribution instead using classes from the jbpm build directory.
As well there needs to be a property for the enterprise module test suite to skip deployment of jbpm on the JBoss server so we can test actual jars shipped and not these just compiled from sources.
--
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
16 years, 2 months
[JBoss JIRA] Created: (JBPM-1088) Trying to read any of the SOA-P IR7 bpm*orchestration processdefinition.xml files with the GPD fails - Eclipse Europa - Version: 3.3.1.1
by Len DiMaggio (JIRA)
Trying to read any of the SOA-P IR7 bpm*orchestration processdefinition.xml files with the GPD fails - Eclipse Europa - Version: 3.3.1.1
----------------------------------------------------------------------------------------------------------------------------------------
Key: JBPM-1088
URL: http://jira.jboss.com/jira/browse/JBPM-1088
Project: JBoss jBPM
Issue Type: Bug
Affects Versions: jBPM jPDL 3.2.2
Environment: Core and Designer plugin 3.0.13
jbpm-jpdl-suite-3.2.2 (for runtime)
Core and Designer plugin 3.0.13
Eclipse Europa - Version: 3.3.1.1
soa-4.2.0-IR7.0.zip
standalone-soa-4.2.0-IR7.0.zip
Reporter: Len DiMaggio
Assigned To: Tom Baeyens
Trying to read any of the SOA-P IR7 bpm*orchestration processdefinition.xml files with the GPD fails with this error - note that it is possible to read the processdefinition.xml file from the 3.2.2 "websale" example with this combination of Eclipse and jBPM plugin.
Note -> This is not a problem with RH Developer Studio beta 1
How reproducible:
100%
Steps to Reproduce:
1. With the components listed in the Envirnment section above
2. Create a new process project from the bpm1,2,3 orchestration quickstarts
3. Attempt to read the processdefinition.xml with the GPD
Actual results:
Error listed below:
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:546)
at java.util.ArrayList.get(ArrayList.java:321)
at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
at org.jbpm.ui.editor.DesignerContentProvider.addGraphicalInfo(Unknown Source)
at org.jbpm.ui.editor.DesignerGraphicalEditorPage.initInput(Unknown Source)
at org.jbpm.ui.editor.DesignerGraphicalEditorPage.init(Unknown Source)
at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:186)
at org.jbpm.ui.editor.DesignerEditor.addGraphPage(Unknown Source)
at org.jbpm.ui.editor.DesignerEditor.createPages(Unknown Source)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:299)
at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:179)
at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:268)
at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:400)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1604)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:217)
at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:207)
at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:774)
at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:673)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:634)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2737)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2651)
at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:2643)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2595)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2590)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2574)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2565)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:644)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:603)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:286)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:139)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:194)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:175)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:268)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:244)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:316)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.open(PackageExplorerPart.java:613)
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:857)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:46)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:199)
at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:818)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1183)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297)
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
16 years, 4 months
[JBoss JIRA] Assigned: (JBPM-1071) Possible problem in concurrent signalling from multiple threads
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-1071?page=all ]
Mark Little reassigned JBPM-1071:
---------------------------------
Assignee: Len DiMaggio (was: Koen Aers)
Assigning to Len for now because QE are going to try this on a Windows box.
> Possible problem in concurrent signalling from multiple threads
> ---------------------------------------------------------------
>
> Key: JBPM-1071
> URL: http://jira.jboss.com/jira/browse/JBPM-1071
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM jPDL 3.2.2
> Environment: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
> MySQL 5.0.22
> Reporter: Jiri Pechanec
> Assigned To: Len DiMaggio
> Priority: Critical
> Attachments: expl.tar.gz, LockingTest.java, log.txt
>
>
> Attached is a simple test case that
> 1) Deploys process definition with two nodes
> 2) Starts the process instance that will go to the wait state on first node
> 3) Starts 20 threads that tries concurrently signal the same process instance
> 4) The second node writes a record to the database
> The test case needs to be executed multiple times to see the incorrect behaviour.
> This is an example of run output
> Isol 8
> Action 1
> Action 2
> Action 2
> Action 2
> Action 2
> Action 2 1
> Action 2 1
> Action 2 1
> Action 2 1
> Signalist 5
> Signalist 6
> Signalist 8
> Signalist 12
> Signalist 7
> Signalist 13
> Signalist 14
> Signalist 15
> Signalist 9
> Signalist 16
> Signalist 17
> Signalist 18
> Signalist 4
> Success 7
> Failure 13
> Explanation of the outcome
> 4 threads successfully executed the node action including database operation. All database opeartion were comitted (4 new records were created)
> 3 threads successfully executed the signal operation but no real action was performed
> 13 threads attempted to execute the signal operation but ended with an 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
16 years, 4 months