Created attachment 952179 [details] server log Description of problem: Metrics are not collected, configuration is not retrieved and operation fails with following exception: java.lang.Exception: Could not read query-cache children names: JBAS014749: Operation handler failed: String index out of range: 0, rolled-back=true Version-Release number of selected component (if applicable): Version : 3.3.0.ER04 Build Number : 99d2107:d7c537e How reproducible: It seems it happens after several days of running Steps to Reproduce: 1. install JON server and import RHQ Server resource 2. navigate to rhq.ear/rhq-core-domain-ejb3.jar#rhqpu resource 3. invoke some operation Actual results: Metrics are not collected, configuration is not retrieved and operation fails with following exception: java.lang.Exception: Could not read query-cache children names: JBAS014749: Operation handler failed: String index out of range: 0, rolled-back=true See attached log with full exception Expected results: No errors Additional info: Exception visible in server.log is the same as in bz1028468. The resource itself is UP. It's not visible on clean installation. After restart of the JON server, everything seems to be fine. No exceptions, resource configuration is loaded, metrics are being collected.
2:05:28 PM) tsegismont: asantos, 1158947 is limited to EAP6 plugin (2:06:53 PM) tsegismont: We've never seen it in server other than the RHQ server (2:07:03 PM) tsegismont: but I suspect it is an EAP bug (2:07:33 PM) tsegismont: It probably depends on the way the persistence unit is configured (2:08:00 PM) tsegismont: So only a portion of EAP users (like us) might be affected
It has been 5 days since the JON server restart and the issues is still not visible.
*** Bug 1279512 has been marked as a duplicate of this bug. ***
Verified in JON3.3.5 DR01 patch. Attached screen-shot(Operation.png)
Created attachment 1107276 [details] operation performed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-0118.html