Description of problem: I have an EAP6 instance and a JDG standalone instance running. My agent inventoried my EAP6 instance and when it inventoried the JDG instance, the dashboard shows the JDG instance with the child resources of EAP6 (database pools, JMS, etc) - just that those resources are unavailable. Version-Release number of selected component (if applicable): JON plugin-pack tech preview 3.0.1 JON 3 JDG beta (with plugin) How reproducible: Verifiable in an environment with EAP6 and JDG running, the issue can be seen in the JON dashboard. Steps to Reproduce: 1) Install JON 3.0.1 tech preview for EAP 6 plugins 2) Install JDG plugin 3) Startup agent 4) Startup EAP6 5) Verify EAP6 is inventoried 6) Shutdown EAP6 instance 7) Startup JDG standalone 8) Verify JDG is inventoried 9) In JON browser, expand inventoried JDG instance, not its child resources Note that I have actually seen it where the status of the EAP6 instance will show up for the status of the JDG instance (available / down) and vice versa. Actual results: JDG shows child resources that it shouldn't Expected results: JDG should only show its relevant resources Additional info: Browser was chrome
Unlinking from RHQ tracker
Increasing priority to match upstream bug 812404 and setting target to JON 3.1.0
Joel-- I'm going to need more specifics. Which types of child Resources of the JDG server do you consider irrelevant? Do any of those types correspond to subsystems that JDG could simply not deploy? Thanks, Ian
Hi Ian, I honestly haven't looked at the plugin since JDG ER2, but back then it was showing everything from AS7. And this might have been because I had inventoried an AS7 instance first. Items that were irrelevant (not installed in ER2 default) that I recall offhand were JDBC pooling and JMS (Queue, Topic). But I haven't tried with any more recent builds. Hope this helps some. I have since torn down that environment. I can rebuild it if there is something you want me to verify / test. Best, Josl
The integration between EAP6 plugin and JDG plugin has been fixed for JON 3.1.1. Please reopen this issue if the problem is present. Relevant bugs that have been resolved recently: bug 820272, bug 826207, bug 825818, and bug 847865.