Bug 736706

Summary:	BRMS-MMR-09: For each RuleFlow its parameters are not presented.
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Pavel Kralik <pkralik>
Component:	JON	Assignee:	John Graham <jgraham>
Status:	NEW ---	QA Contact:	Martin Vecera <mvecera>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	BRMS 5.2.0-ER1	CC:	mvecera
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel Kralik 2011-09-08 13:09:45 UTC

Description of problem:

For each RuleFlow its parameters and if they have valid values are missing.

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

BRMS-5.2.0-ER3
brms-p-5.2.0.ER3-rhq-plugin.jar
JON 2.3.1.GA/2.4.0.GA/2.4.1.GA

How reproducible:

Always

Steps to Reproduce:

1. Run a drools-jon-example application

https://svn.devel.redhat.com/repos/jboss-qa/guvnor/branches/BRMS-5.2.x/drools-jon-example/
   with ant compile; ant server;ant client.phase1; ant
client.phase2

4. Try to inspect the Drools application with jconsole
(org.drools.kbases/my-own-knowledge-base/Sessions)

5. Try to auto discover the application in JON and inspect JMX Server/Drools
Service/KBase my-own-knowledge-base/KSessions Session-0.

Actual results:

Parameters are not presented in jconsole/JON.

Expected results:

Parameters are presented in jconsole/JON.

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=736704

Comment 1 Lukáš Petrovický 2011-09-08 13:12:04 UTC

This is a difference from the approved PRD. Either this issue must be fixed or
the PRD must be updated.

Comment 2 Edson Tirelli 2011-09-08 22:01:47 UTC

This is an operation:

getStatsForProcess( processId )

On a side note, last time I tried, JON had a bug that would raise a NPE when trying to execute any operation with parameters. I don't know if they fixed that or not.