on 2017 Aug 14 11:42 AM
HI Experts,
We have a very strange scenario going on in our production system. We have a JMS to IDOC scenario. Whenever a message fails in JMS sender channel due to XML validation issue or network related issue we expect message to get backed out in the configured IBM MQ Backout queue. Above scenario is working perfectly in lower environments but in production system instead message backing out it is going into uncommitted state at the IBM MQ level and when I do a stop start of the channel instead of backing out to the backout Queue, message is getting lost. This is very very strange, SAP recommended a patch update but even after that issue still persisting. This issue happening in production system as well which is making everyone nervous as it might result it valuable business data loss. Requesting your help and direction to solve this issue.
Above issue accouring in all JMS channles not specific to one scenario.
Thanks,
Dhanvanttri.P
Hi dhanvanttri,
Could you please let me know if this issue resolved. We have also same issue with serious data loss in production system with Tibco JMS queue. Kindly help us what action done to resolve this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
66 | |
11 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.