Hi All - Do you know if MQ Adapter caches connections? If so, how can one ensure this doesn’t happen? My suspicion is that wM will cache MQ connection information, even after you bounce the IS.
Here’s the behavior we noticed during a Disaster Recover test. Our Production IS712 was connected to Production MQ (version 188.8.131.52). The MQ Admin failed over from their PROD to their DR environment. From that point onwards, wM could no longer connect to MQ; even after it was bounced. I suspect this is because wM has cached the MQ connection information and is not robust enough to recognize that MQ is running on a different server.
Has anyone seen this behavior? Or am I missing something?