December 2007 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1095) jBPM project bug for SOA-P Platform bug SOA-196 (jBPM does not work with MySQL/Linux combo)

by Len DiMaggio (JIRA)

jBPM project bug for SOA-P Platform bug SOA-196 (jBPM does not work with MySQL/Linux combo) ------------------------------------------------------------------------------------------- Key: JBPM-1095 URL: http://jira.jboss.com/jira/browse/JBPM-1095 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Len DiMaggio Assigned To: Tom Baeyens jBPM project bug for SOA-P Platform bug SOA-196 (jBPM does not work with MySQL/Linux combo) http://jira.jboss.com/jira/browse/SOA-196 -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1084) NPE in VariableAccess with Oracle persistence

by Tom Baeyens (JIRA)

NPE in VariableAccess with Oracle persistence --------------------------------------------- Key: JBPM-1084 URL: http://jira.jboss.com/jira/browse/JBPM-1084 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Tom Baeyens Assigned To: Tom Baeyens Oracle treats empty strings as null values. So the Access component value object is removed after storage and retrieval fronm the db in case the Access value field is an empty string. As a solution, an empty string is replaced with a space in case an Access object is created with an empty string. -- 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, 7 months

2
2
0 / 0

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

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-1090) JBPM.3 SOA-P branch - merge recent database tests fixes from trunk

by Aleksandar Kostadinov (JIRA)

JBPM.3 SOA-P branch - merge recent database tests fixes from trunk ------------------------------------------------------------------ Key: JBPM-1090 URL: http://jira.jboss.com/jira/browse/JBPM-1090 Project: JBoss jBPM Issue Type: Task Reporter: Aleksandar Kostadinov Assigned To: Koen Aers Fix For: jBPM 3.2.2 SOA 1 Recently Fady Matar fixed jpdl database tests in trunk. These changes need to be merged into the SOA-P branch. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1094) some database tests fail when hsql configuration is removed

by Aleksandar Kostadinov (JIRA)

some database tests fail when hsql configuration is removed ----------------------------------------------------------- Key: JBPM-1094 URL: http://jira.jboss.com/jira/browse/JBPM-1094 Project: JBoss jBPM Issue Type: Bug Reporter: Aleksandar Kostadinov Assigned To: Fady Matar Tests org.jbpm.AllTests.testCustomVariableClassWithLongId org.jbpm.AllTests.testCustomVariableClassWithStringId org.jbpm.AllTests.testProcessDeployment fail with any database if hsqldb configuration from hibernate.cfg.xml is removed. Probably these are not picking up some configuration. See http://hudson.qa.jboss.com/hudson/view/jbpm/ for a reference. Assigning to Fady since he worked on database tests last time. Please reassign as appropriate. -- 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, 10 months

3
7
0 / 0

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

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-1105) jBPM download page missing lates GPD plugin

by Len DiMaggio (JIRA)

jBPM download page missing lates GPD plugin ------------------------------------------- Key: JBPM-1105 URL: http://jira.jboss.com/jira/browse/JBPM-1105 Project: JBoss jBPM Issue Type: Bug Components: Documentation Affects Versions: jBPM jPDL 3.2.2 Reporter: Len DiMaggio Assigned To: Tom Baeyens The problem is that this page lacks the latest jBPM GPD download: ------------------------------ http://www.jboss.com/products/jbpm/downloads JBoss jBPM Process Designer Plugin 3.0.13 9.15 MB 2007-01-25 ------------------------------ It's here: ------------------------------ http://labs.jboss.com/jbossjbpm/downloads/ jbpm-jpdl-designer-3.1.1 Stable 7.7 MB 2007-11-28 jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25 ------------------------------ So - how can we either remove the http://www.jboss.com/products/jbpm/downloads page or get it up-to-date? See: http://jira.jboss.com/jira/browse/JBPM-1088#action_12392651 -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Commented: (JBPM-807) Allow assignment of jBPM variables via EL evaluation

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-807?page=comments#action_12393329 ] Pete Muir commented on JBPM-807: -------------------------------- AFAICS only the second makes sense. Value expressions are bidirectional, but I can't see the point at which you would want to call the setter. However this could be useful. I will see if Gavin can remember what he wanted here. > Allow assignment of jBPM variables via EL evaluation > ---------------------------------------------------- > > Key: JBPM-807 > URL: http://jira.jboss.com/jira/browse/JBPM-807 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Gavin King > Assigned To: Tom Baeyens > Priority: Critical > Fix For: jBPM jPDL 3.2.3 > > > A really major issue in terms of Seam integration with jBPM is to be able to have the process "remember" state coming from Seam, w/o the Seam component needing to outject the value. > What I want is to be able to say: > <assign variable="orderId" value="#{order.id}"/> > when a transition occurs. -- 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

17 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1072) Concurrent JobExecutors can process the same job in parallel

by Alexey Kostylev (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1072?page=comments#action_12392824 ] Alexey Kostylev commented on JBPM-1072: --------------------------------------- As I investigate this issue I find that the problem with running several JobExecutor instances on the same machine is in query condition: where ( (job.lockOwner is null) or (job.lockOwner = :lockOwner) ) So 'lockOwner' is the same for all instances on the same machine, so every instance capture jobs that are executing on other instances at that time. So then I tried to run two instances of Job Executor on different machines. And there's second problem. The result of query 'JobSession.getFirstAcquirableJob' is always returned from the method acquireJobs() not depending on if optimistic locking is failed or not. Here is the log: ... 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG JobExecutorThread : querying for acquirable job... 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG JobExecutorThread : trying to obtain a lock for 'job[444795]' 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG JbpmContext : closing jbpmContext org.jbpm.JbpmContext@274874 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG Services : closing service 'persistence': org.jbpm.persistence.db.DbPersistenceService@116ce6e 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG DbPersistenceService : committing hibernate transaction org.hibernate.transaction.JDBCTransaction@105f759 12:09:42,687 [JbpmJobExector:192.168.125.34:1] INFO DbPersistenceService : optimistic locking failed 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG DbPersistenceService : rolling back hibernate transaction 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG DbPersistenceService : closing hibernate session 12:09:42,687 [JbpmJobExector:192.168.125.34:1] INFO Services : problem closing service 'persistence': optimistic locking failed 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG Services : closing service 'tx': org.jbpm.tx.TxService@4aa085 12:09:42,687 [JbpmJobExector:192.168.125.34:1] DEBUG JobExecutorThread : obtained locks on following jobs: [job[444795]] ... I looked in the code and saw there confirmation of this behaviour. Should I create the separate issue for second problem, what do you think? > Concurrent JobExecutors can process the same job in parallel > ------------------------------------------------------------ > > Key: JBPM-1072 > URL: http://jira.jboss.com/jira/browse/JBPM-1072 > 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: Koen Aers > Attachments: expl.tar.gz > > > Attached is a simple test case that > 1) Deploys process definition with two nodes > 2) Starts 20 executor threads > 2) Starts the process instance that will asynchronously execute action on the second node > 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 > Success 0 > Failure 0 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 1 > Action 2 > Action 2 > Action 2 1 > Action 2 1 > Action 2 > Action 2 1 > Explanation of the outcome > 9 job executors successfully executed the node action (same job) including database operation. All database operations were comitted (9 new records were created) -- 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

17 years

1
0
0 / 0

[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

17 years

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues December 2007