Bug 1329231 - JBoss EAP 6 silent installer doesn't work if port 9999 is in use
Summary: JBoss EAP 6 silent installer doesn't work if port 9999 is in use
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Installer
Version: 6.4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Enrique Gonzalez Martinez
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-21 13:13 UTC by Abhijit humbe
Modified: 2019-12-16 05:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-03 07:13:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-1291 0 Major Closed Installer should make use of CLI embedded EAP instances for runtime configuration tasks 2016-10-17 13:21:04 UTC

Description Abhijit humbe 2016-04-21 13:13:57 UTC
Description of problem:

I have generated the response xml file for installing jboss eap 6 (auto.xml),which also created the auto.xml.variable file.  I have another JBoss instance running on system, so I have modified management ports in auto.xml.variables

~~~
domain.management-http = 19990
domain.management-native = 19999
~~~
When we try to install JBoss instance using following command it fails with exception:

$ java -jar /path/to/jboss-as-server-installer-6.4.0.jar /path/to/auto.xml

~~~
The port 9999 is already in use, and may be required to be open for this installation. Do you wish to continue?
~~~

Version-Release number of selected component (if applicable):
JBoss EAP 6.x

How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:
After modifying auto.xml file, we should be able install JBoss server instance.

Expected results:
Not able to install JBoss server after modification in auto.xml


Additional info:
The installer seems to have a class that validates port, uses hardcoded port:
NoPortClashValidator.class:
~~~~
if (!available(9999))
    {
      this.warning = "NoPortClashValidator.warning";
      setMessage(idata.langpack.getString(this.warning));
      return DataValidator.Status.WARNING;
  }
~~~~

Comment 6 JBoss JIRA Server 2016-06-14 11:36:29 UTC
Jiri Pallich <jpallich> updated the status of jira JBEAP-1291 to Closed


Note You need to log in before you can comment on or make changes to this bug.