[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
17 years, 3 months
[JBoss JIRA] Resolved: (JBPM-1029) calling getGroupTaskList results in 4N queries being made to the database
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1029?page=com.atlassian.jira.plug... ]
Thomas Diesler resolved JBPM-1029.
----------------------------------
Fix Version/s: (was: jBPM 3.3.2 GA )
Resolution: Out of Date
Resolve bugs older than a year as "Out of Date"
> calling getGroupTaskList results in 4N queries being made to the database
> -------------------------------------------------------------------------
>
> Key: JBPM-1029
> URL: https://jira.jboss.org/jira/browse/JBPM-1029
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 3.2.1
> Reporter: David Sheth
>
> In the seam 2.0.0.Beta 1 dvdstore example, which uses jbpm-jpdl 3.2.1, one of the admin pages lists all the tasks assigned to the group of the admin, allowing the admin to assign one of the tasks to him or herself. In this page, a task represents an order placed in the store.
> Each time a new order is placed in the store, the number of tasks on that admin page goes up by one, as would be expected. However, the number of queries used render the page of tasks goes up by 4 each time a new order is placed.
> This seems bad. I asked about this in the seam forum, and got this back from Gavin:
> --begin quote
> AFAIK, this is a jBPM question, not a Seam question, unless you have evidence otherwise.
> --end quote
> The specific bit of code in the seam bpm libs that is being called is :
> return ManagedJbpmContext.instance()
> .getGroupTaskList( new ArrayList( Actor.instance().getGroupActorIds() ) );
> which is basically just calling getGroupTaskList on an org.jbpm.JbpmContext instance.
> Reference to the post in the seam forum:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=114668
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months
[JBoss JIRA] Resolved: (JBPM-1075) org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1075?page=com.atlassian.jira.plug... ]
Thomas Diesler resolved JBPM-1075.
----------------------------------
Fix Version/s: (was: jBPM 3.3.2 GA )
Resolution: Out of Date
Resolve bugs older than a year as "Out of Date"
> org.hibernate.hql.ast.QuerySyntaxException in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(List actorIds)
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBPM-1075
> URL: https://jira.jboss.org/jira/browse/JBPM-1075
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 3.1.4, jBPM 3.2.0, jBPM 3.2.1, jBPM 3.2.2
> Environment: java version "1.5.0_04"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
> Reporter: Jo Geraerts
> Attachments: patch
>
>
> I encountered this bug when I was developping an application with jboss seam. At some point there was a Actor with no group ids. The processInstanceList component will invoke the getGroupTaskList(List actorIds) with a List with 0 entries.
> So we end up in org.jbpm.db.TaskMgmtSession.findPooledTaskInstances(actorIds) with the same List ( with 0 entries)
> I get this Exception:
> 10:43:42,265 ERROR [TaskMgmtSession] org.hibernate.hql.ast.QuerySyntaxException: unexpected end of s
> ubtree [
> select distinct ti
> from org.jbpm.taskmgmt.exe.PooledActor pooledActor
> join pooledActor.taskInstances ti
> where pooledActor.actorId in ( )
> and ti.actorId is null
> and ti.isSuspended != true
> and ti.isOpen = true
> ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months
[JBoss JIRA] Resolved: (JBPM-1070) The jBPM test configuration has problem with database setup
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-1070?page=com.atlassian.jira.plug... ]
Thomas Diesler resolved JBPM-1070.
----------------------------------
Fix Version/s: (was: jBPM 3.3.2 GA )
Resolution: Out of Date
Resolve bugs older than a year as "Out of Date"
> The jBPM test configuration has problem with database setup
> -----------------------------------------------------------
>
> Key: JBPM-1070
> URL: https://jira.jboss.org/jira/browse/JBPM-1070
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 3.2.2
> Reporter: Jiri Pechanec
>
> The jBPM test process expects hiberante.properties file to be placed in defined configuration directory. jBPM config file JBPM.3/jpdl/jar/src/test/config/jbpm.cfg.xml orders to use hibernate.properties file (<string name="resource.hibernate.properties" value="hibernate.properties" />).
> But the JBPM.3/jpdl/jar/src/test/java/org/jbpm/db/AbstractDbTestCase.java uses config file less JBPM.3/jpdl/jar/src/test/java/org/jbpm/jbpm.test.cfg.xml and the line mentioned above is missing. Thus the configuration is read from standard hibernate.cfg.xml.
> Solution
> Either add the missing line to jbpm.test.cfg.xml or change AbstractDbTestCase.java to use central config file in config directory. The second one is preferred.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 3 months