Unexpected Proton Event Link_REMOTE_CLOSE causes MessageProducer to close and then never start again

I am using Qpid AMQP in Spring Route. JMS Message Queue is on Azure Service Bus.

Once Spring app is started and couple of messages are consumed from queue, processed and forwarded to next queue destination, I am seeing below events in logs. After the events MessageProducer is closed.

The App is still able to consume the message and process it, but its no more able to forward  the message on Queue.

How can these events be avoided ?

2019-02-28 07:58:46.425 TRACE 1 — [windows.net:-1]] o.a.qpid.jms.provider.amqp.AmqpProvider : New Proton Event: LINK_REMOTE_CLOSE
2019-02-28 07:58:46.425 TRACE 1 — [windows.net:-1]] o.a.q.j.t.netty.NettyTcpTransport : Attempted write of: 17 bytes
2019-02-28 07:58:46.426 TRACE 1 — [windows.net:-1]] o.a.qpid.jms.provider.amqp.AmqpProvider : New Proton Event: LINK_LOCAL_CLOSE
2019-02-28 07:58:46.426 TRACE 1 — [windows.net:-1]] o.a.qpid.jms.provider.amqp.AmqpProvider : New Proton Event: LINK_FINAL
2019-02-28 07:58:46.426 INFO 1 — [-5f7cc449aefd:1] org.apache.qpid.jms.JmsSession : A JMS MessageProducer has been closed: JmsProducerInfo { ID:0df49cdb-8e6d-4d33-9b56-5f7cc449aefd:1:1:1, destination = ZIP_INCOMING_QA }
2019-02-28 07:59:12.705 TRACE 1 — [ntLoopGroup-2-1] o.a.q.j.t.netty.NettyTcpTransport : New data read: 8 bytes incoming: PooledUnsafeDirectByteBuf(ridx: 0, widx: 8, cap: 37)
2019-02-28 07:59:30.511 TRACE 1 — [windows.net:-1]] o.a.qpid.jms.provider.amqp.AmqpProvider : IdleTimeoutCheck rescheduling with delay: 60000
2019-02-28 07:59:39.057 TRACE 1 — [ntLoopGroup-2-1] o.a.q.j.t.netty.NettyTcpTransport : New data read: 8 bytes incoming: PooledUnsafeDirectByteBuf(ridx: 0, widx: 8, cap: 37)