Please, see linked JIRA with elaborated issue description. + see attachment for scrrenshots depicting the issue.
https://bugzilla.redhat.com/show_bug.cgi?id=1054165 (JON (3.2.0) -- lib plug-in AVAILABILITY CHECK for cache manager failed -- app deployed on EAP 6.2) Availability check is not completely failing anymore. However, it is still not stable enough. We discovered that it is problematic during extensive deployments and we don't want to mix it together. Above-mentioned BZ was set as VERIFIED, because this is OK for small deployments and it was basically resolved. Now we face a new problem -- how to make it even more faster. Maybe we don't need it at all. It depends on customer use case but I think we should be able to properly monitor 2 application servers (with ispn-app deployed) on one machine (with one agent).
Created attachment 902993 [details] UP and DOWN repeatedly in domain mode doployment
Created attachment 902994 [details] Stabilized check in smaller deployment scenario
Removed from blockers. This issue directly depends on: https://bugzilla.redhat.com/show_bug.cgi?id=1105722, which already is a blocker for JDG 630.
William Burns <wburns> updated the status of jira ISPN-4366 to Resolved
This is no longer true for latest cumulative patch of JON 3.2 which contains back-ported changes from RHQ 4.11