Bug 1080443

Summary: JBAS012144 exception during application of CP1
Product: [JBoss] JBoss Operations Network Reporter: Filip Brychta <fbrychta>
Component: Installer, UpgradeAssignee: Simeon Pinder <spinder>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2.1CC: spinder
Target Milestone: DR03   
Target Release: JON 3.2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-08 17:44:01 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:
Bug Depends On:    
Bug Blocks: 1048595    
Attachments:
Description Flags
output of apply-updates.sh
none
server log none

Description Filip Brychta 2014-03-25 12:53:30 UTC
Created attachment 878453 [details]
output of apply-updates.sh

Description of problem:
Following exception it thrown during application of CP1 on JON3.2.0.GA:

RHQ Server                     (pid 7358   ) IS starting
The controller is not available at localhost:6999: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:6999. The connection timed out: JBAS012144: Could not connect to remote://localhost:6999. The connection timed out


Version-Release number of selected component (if applicable):
Version :	
3.2.0.GA
Build Number :	
33013e3:152b372
(aka JON 3.2 CP1)

How reproducible:
3/3

Steps to Reproduce:
1. JON3.2.0.GA is installed and running
2. stop all JON services (./rhqctl stop)
3. apply CP1 (./apply-updates.sh /home/hudson/jon-server-3.2.0.GA)

Actual results:
RHQ Server                     (pid 7358   ) IS starting
The controller is not available at localhost:6999: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:6999. The connection timed out: JBAS012144: Could not connect to remote://localhost:6999. The connection timed out

server.log contains following exception:
Failure in initialisation: java.lang.IllegalStateException: Container is down

Expected results:
No errors

Additional info:
Port 6999 was not used before applying step 3 (verified by netstat)
If you start JON (./rhqctl start) after step 4, everything seems to be Ok.
Complete logs attached.

Comment 1 Filip Brychta 2014-03-25 12:54:57 UTC
Created attachment 878455 [details]
server log

Comment 2 Simeon Pinder 2014-03-25 18:54:31 UTC
Already mentioned by GSS. Need to provide more time before executing configuration update.

Comment 3 Simeon Pinder 2014-04-01 17:05:33 UTC
Added 10s sleep logic to wait longer before attempting to apply eap configuration updates. Matching logic has been applied to batch scripts as well. See related commits for BZ 1080492 for more details.  Fixed with commit: 99778b7899491 to jon.git. Moving to MODIFIED.

Comment 4 Simeon Pinder 2014-04-01 20:43:59 UTC
Moving to ON_QA as available for test in newest cumulative patch build from here:
http://jon01.mw.lab.eng.bos.redhat.com:8042/dist/release/jon/3.2.1.GA/4-01-2014/
I moved the earlier build to 3-18-2014.

Comment 5 Filip Brychta 2014-04-02 08:23:24 UTC
Verified on:
Version :	
3.2.0.GA update-1
Build Number :	
13f0eea:c372b58

Comment 6 Mike Foley 2014-05-08 17:44:01 UTC
JON 3.2.1 released week of 5/5/2014