Bug 982191

Summary: "Checking if server is up" operation is blocking server boot with jdk1.6 on windows
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Petr Kremensky <pkremens>
Component: InstallerAssignee: Thomas Hauser <thauser>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: myarboro, smumford, thauser, tkirby
Target Milestone: ER3   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Doc Text Cause: Consequence: Workaround (if any): Result:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 16:21:36 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
Checking if server is up
none
Checking if server is up with feedback none

Description Petr Kremensky 2013-07-08 11:09:57 UTC
Created attachment 770434 [details]
Checking if server is up

Description of problem:
There is a problem with Server Launch feature with jdk1.6 on windows. I am unable to finish installation once I choose to launch server during installation. It seem like "Checking if server is up" will block the server booting. Installer will show "server failed to start" after a while with jdk1.7, but with jdk1.6 installer will stuck with "Checking if server is up" message and all I can do is to Quit installation, kill processes, delete install folder and star again. 

Version-Release number of selected component (if applicable):
EAP 6.1.1 ER2

Steps to Reproduce:
1. java -jar jboss-eap-6.1.1.ER2-installer.jar [-console]
2. On server Launch screen choose to start Domain Mode
3. Carry on with installation until Starting server screen

Actual results:
Installation will stuck with "Checking if server is up" message

Expected results:
Either server will start successfully or "server failed to start" message is shown and I am able to finish installation

Additional info:
Same with --console installation. You may not be able to reproduce this, if server will fully boot before "Checking if server is up" message (that is why I use domain to reproduce).

Picture description:
You can see, that I am stuck with "Checking if server is up" for almost 7 minutes (I must either kill process or quit installation, because installer will never go on) and there is no server-two process (1448 - HC process, 5404 - server-one process). Sever one is not fully booted (see server.log)

Comment 1 Jyoti Tripathi 2013-07-16 19:04:25 UTC
Created attachment 774449 [details]
Checking if server is up with feedback

(see attached image) This should either fix the behaviour or let us know exactly where it is freezing.

Comment 2 Petr Kremensky 2013-07-22 07:28:32 UTC
Hi Jyoti,
I am stuck in 

Checking... (1/3)

Again, no problem with jdk1.7 only with 1.6.

Comment 3 Scott Mumford 2013-08-29 03:51:24 UTC
Marking for exclusion from the 6.1.1 Release Notes document as an entry for this bug could not be completed or verified in time.

Comment 5 mark yarborough 2013-09-05 22:54:20 UTC
Missed 6.1.1, proposing for 6.2.0, cleaning up erroneous nacks from ackviewer crash earlier today.

Comment 6 Petr Kremensky 2013-09-23 10:51:34 UTC
With 6.2.0.ER1 I am stuck with:
Checking if server is ready...(1/21).

Comment 7 Thomas Hauser 2013-09-30 14:59:17 UTC
Hmm, this shouldn't be occuring. Can you paste more information? Does the Checking if server is ready task ever time out / advance? (2/21, 3/21) etc?

Comment 11 Petr Kremensky 2013-10-18 13:28:19 UTC
This was fixed by BZ1015573.

Verified on EAP 6.2.0.ER6 installer.