Issues with Solace standard Version
I am facing below issues is solace software standard version. Help needed urgently.
1. Posting messages to Solace topic using REST API I am giving the expiry as Solace-Time-To-Live-In-ms:10800000 but when I browse the queue (using java sdkperf tool) I see that in headers it is changing to this: 10800000.
2. I am testing the error scenario where Boomi listener is bind to solace queue. The JMS listener is able to pick messages from Solace queue but at later point of time the process fails. In this case solace should try to redeliver the message to Boomi 5 times (max redelivery attempts configured as 5 on the queue) and after all the attempts are failed message should move to Dead message queue. But here messages are still on the queue and maximum unacknowledged messages count is increasing and messages are not moving to DMQ.
3. Once the same boomi listener error is fixed and re-connected to Solace , Solace is not trying to send the previous (old) messages to the same listener. The messages are just sitting on the queue even though the consumers are available on the queue . How to fix this ? or Is this a expected behavior ?
4. What is the value accepted by solace for the REST header: Solace-Timestamp ?
My Solace software (ova) is installed on Houston servers.