Hi Team,
we are trying to configure MQV9+ Migration in Datapower , after the migration we are facing issue with below error logs in Splunk
2024-11-07T14:20:54+11:00,10.17.197.178,err,0x8d200055,[mq][error] source-idg-mq(*******FSH_V9): trans(102643136) gtid(aadd9dd9672c3ddd****): Failed to put message to (A001F0.**.**.**_COMMON03_***.REPLY.UAT), reason: 2142.
2025-03-17T18:31:06+11:00,10.17.197.179,err,0x80e00616,[mpgw][error] mpgw(MediationRouter01): trans(74663)[10.17.197.217] gtid(8e43863e67d7cfa6010ff333): Network Error (Connection timed out) on Back interface (URL: idgmq://ESB2_MQQMGroup01/?RequestQueue=A0028E.**.***.***.REQUEST.EUAT;ReplyQueue=GN.**.DP.***.CV.REPLY.EUAT1;SetReplyTo=true;ParseHeaders=off) when processing the server response
2025-03-17T18:31:06+11:00,10.104.176.63,err,E*B2_EU*T1,[0x80e00648][mq][error] mpgw(MediationRouter01): trans(48305346)[10.17.197.217] gtid(8e43863e67d7cfa6010ff333): internal error, IBM MQ Reason Code = 901, IBM MQ URL = idgmq://ESB2_MQQMGroup01/?RequestQueue=A0028E.**.***.GESB.REQUEST.EUAT;ReplyQueue=GN.QA.DP.ESB.CV.REPLY.EUAT1;SetReplyTo=true;ParseHeaders=off
We are on 10.6.0.4, we thought the issues will be fixed when we migration from 10.6.0.3
when we revert back the changes to older MQ ( Deprecated object ) it is working fine.
anyone faced similar issue ?
Regards,
Mahesh