Bug 783413

Summary: jBPM Console logs an error when first accessing Process Overview: Could not find session data for id 1
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Jiri Locker <jlocker>
Component: jBPM ConsoleAssignee: Kris Verlaenen <kverlaen>
Status: VERIFIED --- QA Contact: Jiri Locker <jlocker>
Severity: medium Docs Contact:
Priority: medium    
Version: BRMS 5.3.0.GACC: lpetrovi, rzhang
Target Milestone: ---   
Target Release: BRMS 5.3.0.GA   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
related server log section none

Description Jiri Locker 2012-01-20 10:43:06 UTC 
Description of problem:
When the CommandDelegate creates a new session it first tries to load it to make sure it hasn't been created yet. In that case an exception is thrown, which signals the session does not exist and can be created, which is expected. However the exception is always logged at ERROR level. The log should not be polluted with error messages that don't signal a real problem.

Version-Release number of selected component (if applicable):
ER2 - jBPM 5.2.1-snapshot

How reproducible:
always

Steps to Reproduce:
1. after booting the server, open Process Overview
2. check server log
  
Actual results:
an error is always logged when accessing the Process Overview, although nothing unexpected actually happens

Expected results:
error should be logged only if an unexpected exception is encountered

Additional info:
see attached server log
Comment 1 Jiri Locker 2012-01-20 10:44:56 UTC 
Created attachment 556499 [details]
related server log section
Comment 2 Jiri Locker 2012-01-20 12:26:27 UTC 
Hmm.. I see it now, CommandDelegate logs only the exception message. The full exception is logged by org.drools.persistence.SingleSessionCommandService.
Comment 3 Marco Rietveld 2012-01-20 23:18:13 UTC 
This problem has been fixed with some of the commits I pushed today (Jan 21rst) to the 5.2.x branch. 

Please retest with the latest build from the 5.2.x branch.
Comment 4 Jiri Locker 2012-01-27 15:23:33 UTC 
Verified in ER3.