Remedy - Server - Java Plug-in/ JMX listening on the wrong interface displays errors: "javax.jms.JMSException: Could not connect to broker URL.....Reason: java.net.ConnectException: Connection refused: connect"

Version 2
    Share This:

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


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System


    APPLIES TO:

    Remedy AR System Server on Windows OS.



    PROBLEM:

    Background:
    > 2 Network interfaces :
           >111.11.0.45
           >111.11.0.41

    > One NIC subnet (111.11.0.45) is for the application.

    > Other NIC Subnet (111.11.0.41) for Management purposes such as doing RDP etc ..

    > Errors : javax.jms.JMSException: Could not connect to broker URL: tcp://nnnnnn:61617?wireFormat.maxInactivityDurationInitalDelay=120000. Reason: java.net.ConnectException: Connection refused: connect

    > Performing netstat -ano |findstr 61617 it is found the traffic is happening in NIC subnet (111.11.0.41) as well, which is not suppose to go on interface 2 as per the below output:
    ...................

     TCP 111.11.0.45:61617 ARServer-name:49205 ESTABLISHED TCP 111.11.0.45:61617 ARServer-name:49206 ESTABLISHED TCP 111.11.0.45:61617 ARServer-name:49207 ESTABLISHED TCP 111.11.0.45:61617 ARServer-name:49208 ESTABLISHED TCP 111.11.0.45:61617 ARServer-name:49209 ESTABLISHED TCP 111.11.0.45:61617 ARServer-name:49210 ESTABLISHED TCP 111.11.0.45:61617 ARServer-name:49211 ESTABLISHED TCP 111.11.0.45:61617 ARServer-name:49212 ESTABLISHED TCP 111.11.0.45:61617 ARServer-name:49213 ESTABLISHED TCP 111.11.0.41:61617 ARServer-name:49214 ESTABLISHED TCP 111.11.0.41:61617 ARServer-name:49215 ESTABLISHED TCP 111.11.0.41:61617 ARServer-name:49216 ESTABLISHED...................
      
      

     


    CAUSE:

    N/A


    SOLUTION:

    1- Check the ar.cfg/ar.conf file for the actual AR Server name.
    Note, depending if being on a Server Group or not the Server Name will be located on a different parameter:
    Single Server env:
    Server-name: ARServerName

    Server Group env:
    Server-name: LoadBalancerName
    Server-Connect-Name: ARServerName

    2- Go into the Hosts file in the OS and make sure there is an entry for the ARServerName and current IP address.
    Example:
    111.11.1.1   ARServerName   ARServerName.abc.com

    If the env. is a Server Group env. then the Hosts file of each AR Server box will need to have the ARServerName for each AR Server belonging to the group and the correspondent IP address.
    Example:

    111.12.1.1   ARServerName1   ARServerName1.abc.com
    111.13.1.1   ARServerName2   ARServerName2.abc.com
    111.14.1.1   ARServerName3   ARServerName3.abc.com
    etc...


    The IP-Name parameter does not affect in any manner.

    3- So, make sure to do the following :
         - Take a backup before making any changes.
         - Flush DNS.
         - Restart AR server services on all servers.

     


    Article Number:

    000124411


    Article Type:

    Solutions to a Product Problem



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