search

nats-io / nats-jms-bridge

NATS to JMS Bridge for request/reply
12 stars 3 forks source link

CCDT fix now reconnect not working #233

Closed RichardHightower closed 4 years ago

RichardHightower commented 4 years ago

We tried with json ccdt file and bridge is starting successfully. However, it behaves exactly same when we configured connectionnamelist in nats-bridge.yaml config file which means failover is NOT happening once we stop the queue manager to which bridge process gets connected initially. The queue managers configured in CCDT file are independent queue managers(and not the multi instance queue managers). Below are the properties configured under mq cluster. Also attaching CCDT.json file with this email which is used in this example. Please let me know your thoughts on this one.

nats.ibm.mq.queueManager: "*ganesh"

nats.ibm.mq.ccdtUrl: "file:/home/dc-user/ccdttabfiles/CCDT.json"

io.nats.ibm.mq.jms.prop.string.CLIENTRECONNECTOPTIONS: "ANY"

io.nats.ibm.mq.jms.prop.int.CLIENTRECONNECTTIMEOUT: 2

RichardHightower commented 4 years ago

A quick fix might be to add the MQCNO_RECONNECT option on the MQCONN call. --- Paul

RichardHightower commented 4 years ago

We were not able to reproduce this. It works for us. Wih and with/out MQCNO_RECONNECT equiv

gstaware commented 4 years ago

We verified and it works fine. Issue was with the way we were stopping the queue manager. It should be stopped with endmqm -r instead of endmqm . We can close this defect now.