Red Hat Bugzilla – Bug 850841
Drools application is not autodiscovered by JON
Last modified: 2013-09-11 06:59:42 EDT
Created attachment 606286 [details]
When monitoring the Drools example application (BRMS 5.2.0.GA, BRMS 5.3.0.GA) application with JON 3.1.1, the application is not autodiscovered, can be just manually added for the platform. Monitoring with Jconsole works.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install the JON 3.1.1.ER2 server and with the BRMS plugin
2. Run a drools-jon-example application
3. Try to autodiscover the Drools application.
The application is discovered.
Steps to get Drools application running:
1) Unpack drools_application.tar.gz
2) Download the BRMS deployable zip file:
3) unzip brms-p-5.*-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
Created attachment 606287 [details]
JON Server and Agent logs
If the Drools team are going to be able to get to the bottom of the issue, I expect they will need DEBUG level logs from the JON server and agent.
Created attachment 609643 [details]
JON 3.1.1.CR1 DEBUG logs for BRMS 5.2.0
did not fix the bug for BRMS 5.2.0/5.3.0.
Adding JON debug logs.
Created attachment 609644 [details]
JON 3.1.1.CR1 DEBUG logs for BRMS 5.3.0
Adding JON debug logs for BRMS 5.3.0
Is there a version of the BRMS plugin, prior to 5.2 or 5.3, that this standalone application worked with? It looks to me like the issue with discovery might be that the application and reproduce steps attached start up the drools application via ant and is confusing RHQ.
Setting needinfo on pavel for more information.
the BRMS 5.1/5.2 worked with JON 3.0.1 just fine. Problems started with JON 3.1.0 and BRMS 5.2/5.3. Please, see: https://bugzilla.redhat.com/show_bug.cgi?id=828191
Ok. That helps. The earlier e-mail thread that I was forwarded regarding this issue said that this was an issue between JON 3.1.0.GA and 3.1.1.RC which didn't make a lot of sense because I still saw the same issue with 3.1.0.GA and there were no changes in the related code between those releases.
>> It is regression from jon310. It is BRMS 5.2/5.3 problem, not SOA-P.
>> And we believe that this is a BRMS bug? That is - a BRMS-related JON
>> plugin bug, right? (Charles????)
A regression since 3.0.1 makes a bit more sense. Let me update you in a bit.
This is a regression. Looks to be a functional one caused by fixes for issues reported while accessing some secure JMX servers. Working on a fix now.
This bug was reported in JON 3.1.0:
Autodiscovery for Drools application does not work
and it was a part of the Root Cause Analysis BZ 828191 and 828464
discovered in JON 3.1.0.ER4 build. 828191 was closed as:
This has been fixed in master. The issue was that the code assumed that the main class for the JMX server would always be listed in the process listing which is not always the case as when the process description is truncated, for example. See https://bugzilla.redhat.com/show_bug.cgi?id=839087 for more details.
This will be fixed in the next JON release, likely 3.1.2 or later.
This is checked into the release/jon3.1.x branch with commits:
See BZ(https://bugzilla.redhat.com/show_bug.cgi?id=839087) for original commits and details description.
Moving this to MODIFIED awaiting a new ER build.
Moving to ON_QA as available for testing in ER3 or greater: https://brewweb.devel.redhat.com/buildinfo?buildID=246689
Verified. JON 3.1.2.ER4 and BRMS 5.2.0.GA/5.3.0.GA/5.3.1.CR1.