MQSeries.net :: View topic

Andyh · Posted: Sun May 16, 2021 10:43 am Post subject:

With shared memory bindings the application processes with MQ hCon's have MQ shared memory segments attached and MQ has no guaranteed opportunity to detach those segments until the apps make their next MQI calls. The QMgr wants to delete all of the shared memory segments used by the old instance before restarting and the semantics of deleting shared memory segments from underneath processes with those segments attached are not well defined on all unixes.

The MQ_CONNECT_TYPE environment variable allows a "standard" binding to be mapped to a client binding for applications that bind via libmqm.

Another alternative could be to set the default bind type to "Isolated" which can result in locally bound apps using unix domain sockets rather than shared memory to communicate with the QMgr.

Also note the potential security implications of using client, shared, or isolated bindings.