Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 828191

Summary: Autodiscovery for Drools application does not work
Product: [JBoss] JBoss Operations Network Reporter: Pavel Kralik <pkralik>
Component: Plugin -- BRMS 5Assignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED WORKSFORME QA Contact: Mike Foley <mfoley>
Severity: urgent Docs Contact:
Priority: urgent    
Version: JON 3.1.0CC: ldimaggi, loleary, mvecera, tcunning
Target Milestone: ---   
Target Release: JON 3.1.0   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-06 16:10:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
JON 3.1.0.CR1 logs none

Description Pavel Kralik 2012-06-04 12:39:36 UTC 
Created attachment 589135 [details]
JON 3.1.0.CR1 logs

When monitoring the Drools example (BRMS 5.2.0.GA, BRMS 5.3.0.ER6/8) application with JON 3.1.0.CR1, the application cannot be autodiscovered, just manually added for the platform.
Upgrade from JON 3.0.1.GA to JON 3.1.0.CR1 works.

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

BRMS-5.2.0.GA/5.3.0.ER6
JON 3.0.1.GA/3.1.0.CR1

How reproducible:

Always

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

2. 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

3. Try to autodiscover the application.

Actual results:

Autodiscovery fails.

Expected results:

The application is discovered.

Additional info:
N/A
Comment 2 Mike Foley 2012-06-04 13:38:11 UTC 
I have sent an email to have this triaged at the Monday 6/4/2012 Triage Meeting with ccrouch, asantos, loleary, myarborough, and ckannan.
Comment 3 Mike Foley 2012-06-04 14:02:22 UTC 
<ccrouch> mfoley: re: https://bugzilla.redhat.com/show_bug.cgi?id=828191 it sounds like a bug in the drools plugin


Len ... can you investigate/escalate with the plugin developers?
Comment 4 Mike Foley 2012-06-04 15:37:32 UTC 
BZ triage 6/4/2012.

asantos, loleary, ccrouch, mfoley .... 

we need a fix for this by 6/6.   if the fix is in by then ... then it will be included in jon 3.1.  otherwise non-blocking for jon 3.1 GA
Comment 7 Pavel Kralik 2012-06-05 08:42:37 UTC 
Steps to get Drools application running:

1) Checkout the drools application
2) Download the BRMS deployable zip file:

BRMS 5.3.0.ER8:
http://jawa05.englab.brq.redhat.com/candidate/BRMS-5.3.0-ER8/brms-p-5.3.0.BRMS-ER8-deployable.zip

BRMS 5.2.0.GA:
http://jawa05.englab.brq.redhat.com/released/BRMS-5.2.0.GA/brms-p-5.2.0.GA-deployable.zip

3) unzip brms-p-5.2.*-deployable.zip
4) unzip jboss-brms-engine.zip
5) Create link from binaries to drools-jon-example/drools
6) Run the application:
     ant compile; ant server
     ant client.phase1; ant client.phase2
7) Try to monitor with Jconsole and JON
Comment 8 tcunning 2012-06-06 16:10:33 UTC 
The sample app here seems to be the issue.     Pavel and I tried using the drools-jbpmintegration Broker application : 

https://github.com/droolsjbpm/droolsjbpm-integration

with the following sys properties added :
 
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=6002 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

and the app was discovered under JMX Servers.