Bug 854310

Summary: first reload of EAP6 after installation throws exception on ui
Product: [Other] RHQ Project Reporter: Armine Hovsepyan <ahovsepy>
Component: Core UIAssignee: Nobody <nobody>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.5CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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
cridentialsError
none
reloadExc none

Description Armine Hovsepyan 2012-09-04 15:24:43 UTC
Created attachment 609729 [details]
cridentialsError

Description of problem:
First reload of eap6 after installation throws exception on ui while the reload operation goes on without problems.

Version-Release number of selected component (if applicable):
JON 3.1.1 CR1
EAP 6.0.0.GA

Steps to Reproduce:
1. Remove EAP from env.
2. Install new EAP
3. Start EAP (6) in standalone full-ha mode
4. Inventory EAP
5. Install RHQ user for EAP
6. Change the configuration of cluster connection/my cluster resource retry-interval-multiplier from 1 to 1.5 OR create a security domain resource and change it's cache type.
7. Reload EAP server

Actual result: reload fails for only first time with exception.


Expected result: no exception is visible in ui.

Additional information:
please get attached screen-shots - two different exceptions noticed.

Comment 1 Armine Hovsepyan 2012-09-04 15:26:01 UTC
Created attachment 609730 [details]
reloadExc

Comment 2 Charles Crouch 2012-09-04 16:47:46 UTC
Targeting at JON312

Comment 3 Armine Hovsepyan 2012-09-05 08:35:48 UTC
Additional information: bug is only visible in RHEL6 and not visible in Fedora 16.

Comment 4 Deon Ballard 2012-09-25 14:42:21 UTC
Sorry, I meant to change the state on the doc bug. Changing back to NEW.