Description of problem:
Trying to list active, completed, aborted process instances results error modal dialog

Version-Release number of selected component (if applicable):
BPMS 6.2.0.ER5

How reproducible:
Always

Additional info:
15:27:23,273 ERROR [org.dashbuilder.dataset.backend.exception.ExceptionManager] (http-localhost/127.0.0.1:8080-11) Can't lookup on specified data set: jbpmProcessInstances: org.dashbuilder.dataset.exception.DataSetLookupException: Can't lookup on specified data set: jbpmProcessInstances
at org.dashbuilder.dataset.backend.BackendDataSetManager.lookupDataSet(BackendDataSetManager.java:134) [dashbuilder-dataset-core-0.3.4.Final-redhat-2.jar:0.3.4.Final-redhat-2]
at org.dashbuilder.dataset.backend.BackendDataSetManager$Proxy$$$_WeldClientProxy.lookupDataSet(BackendDataSetManager$Proxy$$$_WeldClientProxy.java) [dashbuilder-dataset-core-0.3.4.Final-redhat-2.jar:0.3.4.Final-redhat-2]

+++ This bug was initially created as a clone of Bug #1267528 +++

Description of problem:
Trying to list active process instances results in many error modal dialogs

Version-Release number of selected component (if applicable):
BPMS 6.2.0.ER3

How reproducible:
Always

Steps to Reproduce:
1. Start process definition eg. simple timer
2. Go to process instances and click the Active tab
3. See many error dialogs (3-10): Can't lookup on specified data set: jbpmProcessInstances: org.dashbuilder.dataset.exception.DataSetLookupException: Can't lookup on specified data set: jbpmProcessInstances

Actual results:
Error messages

Expected results:
Listing the active instances

Additional info:
ERROR [org.dashbuilder.dataset.backend.exception.ExceptionManager] (http-localhost/127.0.0.1:8080-17) Can't lookup on specified data set: jbpmProcessInstances: org.dashbuilder.dataset.exception.DataSetLookupException: Can't lookup on specified data set: jbpmProcessInstances
at org.dashbuilder.dataset.backend.BackendDataSetManager.lookupDataSet(BackendDataSetManager.java:134) [dashbuilder-dataset-core-0.3.2.Final-redhat-1.jar:0.3.2.Final-redhat-1]
at org.dashbuilder.dataset.backend.BackendDataSetManager$Proxy$$$_WeldClientProxy.lookupDataSet(BackendDataSetManager$Proxy$$$_WeldClientProxy.java) [dashbuilder-dataset-core-0.3.2.Final-redhat-1.jar:0.3.2.Final-redhat-1]
at org.dashbuilder.dataset.backend.DataSetLookupServicesImpl.lookupDataSet(DataSetLookupServicesImpl.java:72) [dashbuilder-services-0.3.2.Final-redhat-1.jar:0.3.2.Final-redhat-1]
at org.dashbuilder.dataset.backend.DataSetLookupServicesImpl$Proxy$$$_WeldClientProxy.lookupDataSet(DataSetLookupServicesImpl$Proxy$$$_WeldClientProxy.java) [dashbuilder-services-0.3.2.Final-redhat-1.jar:0.3.2.Final-redhat-1]

— Additional comment from JBoss Product and Program Management on 2015-09-30 06:20:09 EDT —

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

— Additional comment from Pavel Kralik on 2015-09-30 10:54:55 EDT —

The same errors are generated if hitting several buttons in Process Instances perspective too:

• "Restore default filters"
• "New process instance" - going through "Start process instance" dialogs and hitting "Submit" button

— Additional comment from Mauricio Salatino on 2015-09-30 11:51 EDT —

The full stack trace shows the issue in the dash builder internal with an NPE.

— Additional comment from David Gutierrez on 2015-10-01 05:07:28 EDT —

This issue was fixed for jBPM 6.3 community final. It was not included in BxMS 6.2 ER3 though.

(master) https://github.com/dashbuilder/dashbuilder/commit/efb44a18185b401ac04cfb2a1db1cc6c7f684379

(0.3.x) https://github.com/dashbuilder/dashbuilder/commit/d6ae85cfd6e16b3a5f09b58ce31c7c8b47114265

— Additional comment from Jan Hrcek on 2015-10-14 11:26:39 EDT —

Ok, verified with BPM Suite 6.2.0 ER4