Smarts Alcatel 5620 SAM Adapter 3.2: Adapter disconnects from Alcatel SAM server with AlcatelConnectionLost to server notification
search cancel

Smarts Alcatel 5620 SAM Adapter 3.2: Adapter disconnects from Alcatel SAM server with AlcatelConnectionLost to server notification

book

Article ID: 303753

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:




Smarts Alcatel 5620 SAM Adapter 3.2 disconnects from Alcatel Service Aware Manager (SAM) server with AlcatelConnectionLost to server notification
Java Messaging Service (JMS) connectivity issue observed between the Smarts Alcatel 5620 SAM Adapter 3.2 and Alcatel SAM server

Error messages similar to the following are seen in the Smarts Alcatel 5620 SAM Adapter 3.2 logs:

  [May 18, 2012 9:01:56 AM GMT+03:00 +052ms] t@1258785088

ASAM_MESSAGE-*-INFO-.[Connector] Attempting (re)connection to JMS.  [May 18, 2012 9:01:56 AM GMT+03:00 +188ms] t@1258785088 ASAM_MESSAGE-*-INFO-.[Connector] Completed createTopicSession with DUPS_OK_ACKNOWLEDGE  [May 18, 2012 9:01:56 AM GMT+03:00 +424ms] t@1258785088 ASAM_MESSAGE-*-SEVERE-.[Connector] Error in makeXmlDirectRequest(): java.io.FileNotFoundException: http://172.x.x.x:8080/xmlapi/invoke  [May 18, 2012 9:01:56 AM GMT+03:00 +424ms] t@1258785088 ASAM_MESSAGE-*-SEVERE-.[Connector] Cannot send version query to 5620Sam: java.io.FileNotFoundException: http://172.x.x.x:8080/xmlapi/invoke [May 18, 2012 9:01:56 AM GMT+03:00 +425ms] t@1258785088 ASAM_MESSAGE-*-SEVERE-.[Connector] Exception Type:java.io.FileNotFoundException http://172.x.x.x:8080/xmlapi/invoke sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) com.smarts.asac.ems.AlcSamHttpConnection.makeXmlStreamRequest(AlcSamHttpConnection.java:240) com.smarts.asac.ems.AlcSamHttpConnection.makeXmlDirectRequest(AlcSamHttpConnection.java:112) com.smarts.asac.SmAsAlarmEmsInterface.checkEmsVersion(SmAsAlarmEmsInterface.java:1054) com.smarts.asac.SmAsAlarmEmsInterface.jmsConnect(SmAsAlarmEmsInterface.java:432) com.smarts.asac.SmAsAlarmEmsInterface.jmsConnect(SmAsAlarmEmsInterface.java:425) com.smarts.asac.Connector.run(SmAsAlarmEmsInterface.java:1412) [May 18, 2012 9:01:56 AM GMT+03:00 +425ms] t@1258785088 ASAM_MESSAGE-*-INFO-.[Connector] Stopping JMS monitor [May 18, 2012 9:01:56 AM GMT+03:00 +530ms] t@1258785088 ASAM_MESSAGE-*-INFO-.[Connector] topicConnection closed.


Environment

VMware Smart Assurance - SMARTS

Cause

The above issue can occur if the Primary and Secondary Alcatel SAM 5620 EMS servers are not set up correctly in the emsConfig.import file.

Resolution

If you encounter this issue in your environment, do the following:

  1. Check Adapter log for Primary Alcatel SAM server reference as in the following:

    systemInfo PrimaryIP: <name of server>

  2. If this entry incorrectly refers to the back-up (Secondary) server, there is an issue identifying Primary and Secondary 5620 EMS in the emsConfig.import file.
  3. Open the emsConfig.import file in the following directory:

    <BASEDIR>/ASAM/smarts/conf/alcatel-sam

     
  4. Check and ensure that Primary and Secondary servers are set up correctly in the file.
  5. Save and close the emsConfig.import file.
  6. Restart the Primary and Secondary servers.