BMC Release Process Management - Stop command is not stopping the services

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Release Process Management


    COMPONENT:

    Release Process Management


    APPLIES TO:

    All versions of BRPM



    QUESTION:

    BMC Release Process Management - Stop command is not stopping the services

    When you go to <BRPM_INSTALL_HOME>/bin folder and initiate a stop.sh or stop.bat command or any method to stop BRPM services then the services are not brought down.


    ANSWER:

    There could be many reasons why the stop command wont work:

       
    • Permissions on the files
    •  
    • Ownership of the installation/files/folders
    •  
    • Misconfiguration or customizations on standalone/standalone-ha.xml files
      
    This article covers the misconfiguration/customizations. 
    BRPM runs on JBoss Application Server. The stop and start commands are dependent many files:  
       
    • stop.sh or stop.bat - Make sure the paths are pointing to the right locations. Path: <BRPM_INSTALL_HOME>/bin
    •  
    • standalone.xml (or standalone-ha.xml for cluster setup) Path: <BRPM_INSTALL_HOME>/server/jboss/standalone/configuration
    •  
    • jboss-cli.xml Path: <BRPM_INSTALL_HOME>/server/jboss/bin
    Snippet from the jboss-cli.xml (beginning of the file) 
        <!-- The default controller to connect to when 'connect' command is executed w/o arguments -->
        <default-controller>
            <host>localhost</host>
            <port>9999</port>
        </default-controller>


    Snippet from the standalone.xml or standalone-ha.xml (around last 20 lines) 
        <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
            <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
            <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
            <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>


    The default-controller port from jboss-cli.xml should match with the jboss.management,native.port value in standalone.xml (or standalone-ha.xml). 
    Please note that the jboss.management,native.port value in standalone.xml (or standalone-ha.xml) is also dependent on the   jboss.socket.binding.port-offset.
    You need to add the offset value to the jboss.management.native.port to get the real value. 

    For example if offset is 1000 and the   jboss.management.native.port:9999  then in the jboss-cli.xml you have to set the default controller port value as 10999. 
      

     


    Article Number:

    000193671


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles