Bug 1303985

Summary: AuditMode.NONE does not work properly in business-central
Product: [Retired] JBoss BPMS Platform 6 Reporter: Anton Giertli <agiertli>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:00:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Anton Giertli 2016-02-02 15:50:03 UTC 
Description of problem:

When AuditMode for given deployment is set to NONE (vie kie-deployment-descriptor.xml), the execution of a process from this deployment is not behaving properly.

Version-Release number of selected component (if applicable):

BPM Suite 6.2
How reproducible:
always

Steps to Reproduce:
1. Model random process
2. Configure AuditMode to NONE via business-central UI
3. Deploy and run this process

Actual results:
When starting the process, popup window with following message is displayed:
"Unexpected error encountered : null" 

Expected results:
Process execution goes flawlessly even with AuditMode == NONE

Additional info:

1st observation:

When logging was set on DEBUG level on package org.jboss.errai then following message can be observer in server.log
https://gist.github.com/agiertli/dff25e7fb09bb313e5eb

It seems like jbpm-console is trying to fetch process audit data - they are not there because of AuditMode == NONE --> NPE

2nd observation:
AuditTaskImpl and BamTaskSummary tables still includes audit data despite the AuditMode == NONE - this is unexpected.
*Log tables are empty - expected.

3rd observation:
The NPE was visible only on debug level - please don't swallow the exceptions like this. It's very hard to debug messages like : ""Unexpected error encountered : null" " - it would be better to provide stacktrace in this case.