Unable to start the Java Message Service (JMS) receiver

Unable to start or stop the messaging receiver, also known as the Java Message Service (JMS) receiver, in Global Data Synchronization for Product Master.

Symptoms

When you run the application command gdsmsg.sh start the message Couldn't start GDS Message Receiver! appears. When you start the application, you can notice that the message receiver is not processing the messages.

Resolving the problem

Verify that the following product configurations are set correctly:

Go to the $TOP/etc/default/ product installation directory, and in the gds_system.properties file verify that the value of the SEND_TO_JMS variable is set to TRUE.
Go to the $TOP/etc/messaging/xml/ product installation directory, choose the /demand or /supply directory based on the application that is installed, and go to the /datapool directory regarding your requirement, and find the properties.xml file. Open the file properties.xml, and set the correct values for the <inBoundQueueName>, <outBoundQueueName>, and <queueConnectionFactory> parameters.

In addition, to start, stop, or check the status of the JMS receiver, use the following scripts that can be found in the $TOP/bin product installation directory:

To start JMS receiver:
```
 gdsmsg.sh start
```
To abort the JMS receiver:
```
gdsmsg.sh abort 
```
To check the status of the JMS receiver:
```
 gdsmsg.sh status
```

Note: Before starting the JMS receiver, make sure the .binding file in the $TOP/etc/default product installation directory has been updated with the queue that is configured previously.