TNotifier

Expand / Collapse All

MQListener Connection to TNotifier failed

a) Issue Description:

MQListener logs show the following error

INFO [0001187700155438] Entered sendDetailsToNotifier method ...

ERROR [0001187700155438] Exception Trace: Unable to connect to remote server at http://<ip>:<port>/NotifierWCFService/postjson

b) Cause

MQListener is not able to connect to TNotifier Service when processing a message to social media user

c) Troubleshooting

  1. Ensure TNotifier service is up and running. If not, start the TNotifier service and process the message again.
  2. Ensure the TNotifier API endpoint in MQListener config is mentioned correctly.
  3. Are MQListener and TNotifier running on different servers? if so, ensure port on which TNotifier is running is opened in its server firewall for inbound connections. Telnet to that server and port from a different machine to verify.

ValidateResponse Response content from SMM API: {"isSuccess":false,"message":"Bad Request","result":{"message":"Request failed with status code 400"}

a) Issue Description:

TNotifier logs show the following error

SendBySMManager.ValidateResponse Response content from SMM API: {"isSuccess":false,"message":"Bad Request","result":{"message":"Request failed with status code 400"}........

b) Cause

TNotifier received back an error from SMM Management API while processing a message to Line User

c) Troubleshooting

  1. Statuscode 400 error could be sent by ManagementAPI to TNotifier when processing a message to Line User due to an invalid MID sent in the request (MID which is not recognized by LINE as a valid Line user).
  2. The MID data to TNotifier is coming from either MQListener or BatchProcessor.
  3. MQListener or BatchProcessor would have picked up MID from DB based on the CIF that they received in real time notification raw message of batch file record respectively.
  4. Check and correct in DB to see if there is any corrupted data of MID for a valid CIF.

ValidateResponse Response content from SMM API: {"isSuccess":false,"message":"StatusCodeError: 404

a) Issue Description:

TNotifier logs show the following error

SendBySMManager.ValidateResponse Response content from SMM API: {"isSuccess":false,"message":"StatusCodeError: 404 - \"<!DOCTYPE html>........

b) Cause

TNotifier received back an error from SMM Management API while processing a message to Line User

c) Troubleshooting

  1. Statuscode 404 error could be sent by ManagementAPI to TNotifier when processing a message to Line User due to an invalid LineSMMAccount Id configured in TNotifier Config.
  2. In TNotifier Config, ensure LineSMMAccountId Key has correct Line Account Id mentioned. This account id should be the account id which SMM Callback recognises and the one which is configured in Line bot channel webhook configuration

PostDataToSMM exception: Unable to connect to the remote server

a) Issue Description:

TNotifier logs show the following error

PostDataToSMM exception: Unable to connect to the remote server

b) Cause

TNotifier is not able to connect to Social Media Connector ManagementAPI Service when processing a message to social media user

c) Troubleshooting

  1. Ensure Management API service is up and running. If not, start the Management API service and process the message again.
  2. Ensure the Management API endpoint in TNotifier config is mentioned correctly.
  4. Are ManagementAPI and TNotifier running on different servers? if so, ensure port on which ManagementAPI is running is opened in its server firewall for inbound connections. Telnet to that server and port from different machine to verify.

Exception while processing: DBNotification[Line-110719_20192510154631854].GetSMMTemplate: No SMM Template found with TemplateId: VSA0048 for Channel: LINE

a) Issue Description:

TNotifier logs show the following error

NotifyAlertAsync[Line-110719_20192510154631854].Exception while processing: DBNotification[Line-110719_20192510154631854].GetSMMTemplate: No SMM Template found with TemplateId: VSA0048 for Channel: LINE

b) Cause

TNotifier is not able to find the templateid in DB using which it needs to process the outgoing message to Line user.

c) Troubleshooting

  1. Either the Template Id sent to TNotifier is incorrect or Message has been sent for processing with a Template Id before the template has been added to DB.
  2. If the template id sent to TNotifier is incorrect, ensure to correct this in the message file before processing through TNotifier.
  3. If the template Id is correct, then ensure to add the message template using Chat template module of OCM with the particular Template Id so that the message template with that template id gets added to AGT_SMS_Template table in the DB.

TNotifier: sendSMS Exception: Unable to connect to the remote server

Issue:

TNotifier recieves "Unable to connect to the remote server" exception in logs.

Fix:

This error occurs when the TNotifier has received the SMS request, successfully processed and trying to send to MQ API, where MQ API is not reachable.

Troubleshooting Steps:

  1. Check the MQ API Url configured in the TNotifier config file "ManagerAPIURL1"
  2. Make sure the config keys are not duplicate and the value provided is in format "eg: http://127.0.0.1:9500/mqapi"
  3. Check whether the MQ API service is running and is accessible. If deployed in the same server, provide the end point url in notifier as localhost.
  4. Run the below netstat command in the command prompt to check if the service is listening
    Open Command Prompt
    Run netstat -ano | findStr "PortNumberOfMQAPI"
    Check if the service is listening on port

Resolution:
In the above scenario, duplicate config keys were provided in the TNotifier config file where each key had different value, due to which TNotifier was unable to connect and caused "Unable to connect to remote server exception"

TNotifier: WebSphere MQ error occurred : MQJE001: Completion Code 2 Reason 2196

 

Issue:

TNotifier received the below error while sending out a SMS through MQ API.

A WebSphere MQ error occurred : Completion code 2 Reason code 2196error message: MQJE001: Completion Code 2 Reason 2196 .

Description:

TNotifier integrates to different Manager API's where for SMS its integrated to IBM MQ via a Tetherfi MQ API service. Once a message request is received, after processing the validations, when notifier tries to push the data to IBM MQ, following error occurs.

Fix:

This error code 2196 means "Unknown Transmission Queue." describing that when a message is tried to be sent to remote Queue Manager, the queue is not identified and failed to push.

Troubleshooting steps:

  1. TNotifier is configured with a key "MQlegalIdCountry" in config file, which is sent to Tetherfi MQ API service in the request to push to remote queue manager
  2. Tetherfi MQ API service identifies the configuration of remote queue manager from its properties file based on the the country sent in request
  3. Check if the country configured in the TNotifier and Tetherfi MQ API configs are in sync
  4. Check if the Queue is up and running. If MQ is managed by client, please ask them if its UP for connectivity.

Resolution:

In the above scenario, queue is managed by client and was not UP, due to which TNotifier was receiving error code 2196.