Remedy - Server - ARS 9.x  - ERROR (8505): Message not in catalog...Server group ERROR (8509)Message number = 8509; GENERIC_NO_LOCAL_BROADCAST - javax.jms.JMSException: Could not connect to broker URL

Version 2
    Share:|

    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:

    BMC Remedy AR System Server 9.x



    PROBLEM:

     

    The arerror log displays the following error:

    ..........................
    ....  08:25:44.501 2016 Processing tag file: /etc/arsystem/dpscecars01/arsystem.tag
    ....  08:26:25.902 2016 updating statistics configuration: enabled=false aggregation interval (sec)=60
    ....  08:26:48.017 2016 Error while broadcasting messages to servergroup. Message[MemberNodeLifeCycleMessageData [serverUp=true, memberNode=MemberNode [host={AR Server}, port={AR TCP port}, cachePeerListenerPort=40001], super.toString()=ServerGroupMessageData [messageType=null, callType=null, super.toString()=AbstractMessageData [serverNameOfMessageOrigin={AR Server}, delayOutsideMsgDelivery=false]]]]ERROR (8505): Message not in catalog; Message number = 8505; Server group ERROR (8509): Message not in catalog; Message number = 8509; GENERIC_NO_LOCAL_BROADCAST - javax.jms.JMSException: Could not connect to broker URL: tcp://{AR Server node group}:{Messaging port}?wireFormat.maxInactivityDurationInitalDelay=120000. Reason: java.net.ConnectException: Conexión rehusada
    ....  08:26:49.383 2016 Action Request System Server Starting (default locale: es)
    ....  08:26:49.789 2016 AR System Assignment Engine 9.0.01 201508191530(c) Copyright 1991-2015 BMC Software, Inc.
    ....  08:26:52.707 2016 CMDB Server Starting
    ....  08:26:56.384 2016 CMDB Server Started.
    ....  08:26:56.432 2016 mié mar 30 08:26:56.432 2016 Server binding to TCP port {AR Server}/127.0.0.1 on assigned port {AR TCP port}
    ..........................


    There is no functional impact observed in the application.

      

     

     


    SOLUTION:

     

     Since the message states that a connection cannot be made while broadcasting messages to servergroup connecting to a node of the server group using the Messaging port:
    .....GENERIC_NO_LOCAL_BROADCAST - javax.jms.JMSException: Could not connect to broker URL: tcp://{AR Server node group}:{Messaging port}?......

      

    Example from an arerror log:
    .....Error while broadcasting messages to servergroup. Message[MemberNodeLifeCycleMessageData [serverUp=true, memberNode=MemberNode [host=remedy1, port=9000, cachePeerListenerPort=40001], super.toString()=ServerGroupMessageData [messageType=null, callType=null, super.toString()=AbstractMessageData [serverNameOfMessageOrigin=dpscecars01, delayOutsideMsgDelivery=false]]]]ERROR (8505): Message not in catalog; Message number = 8505; Server group ERROR (8509): Message not in catalog; Message number = 8509; GENERIC_NO_LOCAL_BROADCAST - javax.jms.JMSException: Could not connect to broker URL: tcp://remedy2:4145?wireFormat.maxInactivityDurationInitalDelay=120000. Reason: java.net.ConnectException: Conexión rehusada


    Basically states that the current AR Server node remedy1 which has configured an AR TCP Port 9000 cannot broadcast messages to the AR Server node remedy2 using the Broadcast Messaging port 4145

    Check the folowing:

    1- In the ar.cfg.ar.conf file locate the Default Messaging port parameter (example below):
    Default-messaging-port: 4145

    2- Do a telnet using the AR Server using the Default Messaging port.
    As pert the scenario above, from remedy2:
    # telnet ARServer node 1 Broadcast Messaging Port

    # telnet remedy1 4145
         Trying 12.122.122.10...
          telnet: connect to address
    12.122.122.10: Connection refused

    Checking also using the IP address:
    # telnet 12.122.122.10 4145
         Trying 12.122.122.10
          telnet: connect to address 11.111.111.15 : Connection refused


    The solution is check with the Network team to ensure the port used is open and available in the network in order to connect using it.
    Using telnet can be performed at any time to check the port and for any errors returned the network team will need to check further.
     

     


    Article Number:

    000115749


    Article Type:

    Solutions to a Product Problem



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