Created attachment 1078579 [details] Process instances list error message 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]
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
Created attachment 1078713 [details] full stack trace The full stack trace shows the issue in the dash builder internal with an NPE.
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
Ok, verified with BPM Suite 6.2.0 ER4