Cannot install BRMS 6.3 jar installer after changing default port of native management port of JBOSS/EAP 6

Solution Verified - Updated -

Issue

  • The default native management port of JBoss standalone.xml is 9999. BRMS 6.3 jar installer is not working properly if the management native port is being changed to some other value.

  • The BRMS installer fails when the install process is carried out and changes are reverted with default values.

  • Below steps were being followed to produce this issue.

  1. Installed EAP 6.4 by extracting the jboss-eap-6.4 zip file

  2. Patched the EAP to 6.4.8 by using jboss-cli.sh and the jboss-eap-6.4.8-patch.zip file (had used the override option)

  3. Edited the standalone.xml file and set the native management port to "19999" instead of "9999"

  4. The EAP instance starts fine after that using the standalone.sh script and we can connect to the management port 19999 by using the jboss-cli.sh

  5. Shut down the EAP instance to install BRMS 6.3 (jboss-brms-6.3.0.GA-installer.jar)

  6. Start the BRMS 6.3 installer (java -jar jboss-brms-6.3.0.GA-installer.jar)

  7. The warning message from the screenshot pops up ( port 9999 already in use)

  8. Installation fails if process is carried out further.

  9. The installer reverts the changed made by the installation.

Environment

  • Red Hat JBoss BRMS 6.3.0

  • Red Hat JBoss Enterprise Application Platform 6.4.8

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content