Bug 1158947

Summary: Operations, configuration, monitoring are broken on rhq.ear/rhq-core-domain-ejb3.jar#rhqpu resource
Product: [JBoss] JBoss Operations Network Reporter: Filip Brychta <fbrychta>
Component: Core ServerAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED ERRATA QA Contact: Prachi <pyadav>
Severity: medium Docs Contact:
Priority: medium    
Version: JON 3.3.0CC: bkramer, hrupp, jshaughn, loleary, mmurray, myarboro, pyadav, tsegismo
Target Milestone: ER01Keywords: Triaged
Target Release: JON 3.3.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-03 15:02:03 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
server log
none
operation performed none

Description Filip Brychta 2014-10-30 14:52:19 UTC 
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.
Comment 1 Jay Shaughnessy 2014-10-31 18:16:50 UTC 
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
Comment 2 Filip Brychta 2014-11-05 07:27:08 UTC 
It has been 5 days since the JON server restart and the issues is still not visible.
Comment 7 Filip Brychta 2015-11-12 16:00:49 UTC 
*** Bug 1279512 has been marked as a duplicate of this bug. ***
Comment 9 Prachi 2015-12-18 17:15:39 UTC 
Verified in JON3.3.5 DR01 patch.

Attached screen-shot(Operation.png)
Comment 10 Prachi 2015-12-18 17:16:32 UTC 
Created attachment 1107276 [details]
operation performed
Comment 12 errata-xmlrpc 2016-02-03 15:02:03 UTC 
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