Bug 783413 - jBPM Console logs an error when first accessing Process Overview: Could not find session data for id 1
Summary: jBPM Console logs an error when first accessing Process Overview: Could not f...
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM Console
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: BRMS 5.3.0.GA
Assignee: Kris Verlaenen
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-20 10:43 UTC by Jiri Locker
Modified: 2022-01-05 05:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
related server log section (5.84 KB, text/plain)
2012-01-20 10:44 UTC, Jiri Locker
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.