Bug 796189

Summary:	ERROR jbpm.console.directory property not found
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Zuzana Krejčová <zkrejcov>
Component:	jBPM Console	Assignee:	Kris Verlaenen <kverlaen>
Status:	VERIFIED ---	QA Contact:	Lukáš Petrovický <lpetrovi>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	BRMS 5.3.0.GA	CC:	atangrin, lpetrovi
Target Milestone:	ER7
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:

Description Zuzana Krejčová 2012-02-22 12:58:48 UTC

Description of problem:
Clicking Process Overview results in 
ERROR [StatefulKnowledgeSessionUtil] jbpm.console.directory property not found 
being logged into the server log.

It happens every time, but seemingly doesn't have effect on jbpm-console functionality.


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


Additional info:
As far as I know, the jbpm.console.directory property was used in the demo installation to tell the console where to look for processes, images... We test with processes from Guvnor's defaultPackage, so we don't use the property. The error should not be logged, or at least not as an error.

Comment 1 Kris Verlaenen 2012-02-28 23:39:41 UTC

Agreed, this should simply be logged, but not as an error.

Comment 3 Ryan Zhang 2012-04-23 07:36:49 UTC

Update status to ON_QA. Please verify them against ER6.

Comment 5 Zuzana Krejčová 2012-05-02 13:55:29 UTC

Sorry for the confusion, found it again. This time, I get:
ERROR [GraphViewerPluginImpl] jbpm.console.directory property not found

Still error, this time only from GraphViewerPluginImpl.
Could you please look at it again?

Comment 6 Maciej Swiderski 2012-05-02 14:55:40 UTC

already fixed as part of BZ-813412 but seems like it was not picked up by the ER6 build.

Comment 7 Ryan Zhang 2012-05-14 08:16:29 UTC

The fixed for this issue should be included in ER7. Please do verification on it.