Bug 886537 - Operations with parameters does not work for Drools application
Summary: Operations with parameters does not work for Drools application
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: JON
Version: BRMS 5.2.0.GA,unspecified,BRMS 5.3.0.GA,BRMS 5.3.1
Hardware: i386
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: John Graham
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 806027
TreeView+ depends on / blocked
 
Reported: 2012-12-12 14:00 UTC by Pavel Kralik
Modified: 2023-05-01 08:28 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
drools-jon-example application (18.64 KB, application/gtar)
2012-12-12 14:00 UTC, Pavel Kralik
no flags Details

Description Pavel Kralik 2012-12-12 14:00:26 UTC
Created attachment 662378 [details]
drools-jon-example application

Description of problem:

When monitoring the Drools example application, the Operations with parameters for the Drools app session rise an IllegalStateException. The same application monitored by JConsole executes Operations with parameter without problem.

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

BRMS-5.2.0.GA/BRMS-5.3.0.GA/BRMS-5.3.1.CR1
JON 3.1.0.GA/3.1.2.ER3

How reproducible:

Always

Steps to Reproduce:
1. Install the JON 3.1.1 server and with BRMS plugin

2. Run a drools-jon-example application (attached zip)

with ant compile; ant server
     ant client.phase1; ant client.phase2

3. Discover the JMXServer and go to JMXServer > Drools Services ... > KSession {sessionId} to the Operations tab and execute eg Get statistics for rule with "hello world" parameter.

Actual results:

java.lang.IllegalStateException: Name [ruleName] specified for parameter of operation [getStatsForRule] on MBean [org.drools.kbases:type=my-own-knowledge-base,group=Sessions,sessionId=Session-1] is invalid. The MBean operation does not take a parameter by that name.
	at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:576)
	at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:524)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:552)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)


Expected results:

The Operations with parameter should return:
activationsCreated=1 activationsCancelled=0 activationsFired=1 firingTime=0ms

Additional info:
N/A

JON BZ: https://bugzilla.redhat.com/show_bug.cgi?id=806027


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