Hi Clint
The TTL on messages is set to either 10 or 15 minutes, I can’t quite remember which. Disconnecting every 110 seconds and reconnecting again will work fine, but bear in mind the following:
* Your consumer will need to reconnect promptly, within a couple of minutes, otherwise you risk not being able to process the backlog of messages plus any new ones queued
* If your consumer fails to reconnect and messages expire on your queue, you’ll need to download the logs from the FTP server for the duration you missed
There is probably a message header set with the time messages were queued, and/or the time at which a particular message expires. Have a look at these and if your clock is set correctly on your local machine, you may be able to see when you’re receiving messages with a dangerously low time-to-live.
A better option for you might be to use an ActiveMQ bridge - where ActiveMQ running on your side is permanently connected to the NRDP server and re-queues messages locally on to either a queue or a topic. This way, you can buffer more than 10/15 minutes worth of messages locally. It also has the advantage that you can split out the incoming messages in to multiple queues, or a single topic with multiple subscribers, and use the same feed for your live, pre-prod and development environments.
Kind regards,
Peter
--