Bug 900913 (JBPAPP6-1157)

http://git.app.eng.bos.redhat.com/?p=jbossas-installer.git;a=commit;h=3b917aebdef3ca9fbcd24110a04fd11017066a9d

Script works for standalone and domain when running management interface on standard port 9999.

But it doesn't reflect case when custom port for management interface is defined in installer. On the other side different port for management interface can be defined for standalone and domain.

So question is:
* Can be shutdown script extended to reflect custom port for management interface ?
* Is it enough to add information about port limitation for shutdown in documentation?

Hello Rostislav,

Our decision is this: the shortcut will need to use the custom port for the management interface from the installer. If the port is changed after the installer has configured everything...the shortcut will not function until the jboss-cli.xml file is configured to default to the new management interface port (the script makes use of jboss-cli.sh functionality). Once it is configured correctly, however, the shortcut will function once more. 

Thanks for discovering this issue :) 

Tom

http://git.app.eng.bos.redhat.com/?p=jbossas-installer.git;a=commit;h=d7befd1e0c3e0ff5fb30793d2be5e83e9f699590

This modifies jboss-cli.xml to use the custom port for management-native defined during installation. As Tom mentioned above, if the user modifies standalone.xml manually after installation, jboss-cli.xml would need to be modified as well for the shutdown shortcut to work.

Changing fix version back to ER3 as the rebuild of installer for ER3 will include this fix.

This does not work as of EAP 6.0.1.ER3 hence moved fixed version.

I checked installer and here is what I found:

* I didn't change any port during installation
* Standalone starts with native management port bind to 8999, shutdown script works
* Domain starts with native management port bind to 9999, shutdown script works

* I changed native management port to 8999 in installer
* Standalone starts with native management port bind to 8999, shutdown script works
* Domain starts with native management port bind to 9999, shutdown  script DOESN'T work, 
** It expects management port on 8999 -- Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:8999. The connection timed out

Installer doesn't support to define custom native management port for domain.

Maybe when customer changes native management port for standaole it could be propagated to domain configuration too - EAP-6.0.1/jboss-eap-6.0/domain/configuration/host.xml 
Or just add new step to wizard to define native / http / https management ports for domain.

Hi Thomas/jyoti,

          I noticed that the installer GUI only provides option to provide custom port value for management-interface and management-console for standlaone only and there is no such option for domain.So currently if I modify management interface and console values for standalone the domain configuration still continues to use the default 9999 and 9990.
So after installation if I start server in standalone mode then invoke the shutdown shortcut it works.Next if I start the server in domain mode and invoke the shutdown script it of course uses the custom values entered from installer for standlaone and fails to shut down the server for domain.

Attaching screenshot and changing the component back to Installers....Tom it will be great if you create a new jira for console-end changes.

So, what should be fixed in the CLI? The XML? I don't want this property in the default config.
You can pass the host and port as arguments to the CLI script.

Attachment: Added: Shutdownshortcut_yields_blankscreen.png

How would one know that the server was started in a different port so as to know an argument is necessary?

There is a disconnection between the act of changing the port on the standalone or domain configurations and the CLI.
A value for the same thing is set independently in two different XML files.

I see that the problem is that you may have several configuration files and even start more than you server from the same install tree using different ports.

Can you think of a better alternative than having to specify the port for the cli?

http://git.app.eng.bos.redhat.com/?p=jbossas-installer.git;a=commit;h=110d14340bd9647b0feeb471b50753d70f813da5

We have decided to remove the shutdown script and instead have separate shortcuts to for domain and standalone. This can also support the possibility for running instances of domain and standalone at the same time, on different ports.

Release Notes Docs Status: Added: Not Required

Release Notes Docs Status: Removed: Not Required 
Docs QE Status: Removed: NEW 

Link: Added: This issue is a dependency of JBPAPP6-1058

The shutdown scripts have been separated for domain and standalone mode and works for both as in 6.0.1.ER4 build