You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 30, 2020. It is now read-only.
I'm trying to use WMQ in a multi-threaded Ruby environment. While I can do this fine provided I open and close connections within the same thread, I cannot sensible structure my code around e.g. Connection Pooling.
I see that WMQ itself does support multi-threaded environments, with MQCNO_HANDLE_SHARE_BLOCK, but since GenerateConst explicitly excludes the HANDLE_SHARE options, it's not available out of the box.
I have manually tested with the value of MQCNO_HANDLE_SHARE_BLOCK and everything works as expected (at least from what I can see) and this resolves a whole lot of issues for me. Is there a strong reason why this constant has been excluded, or is it a mistake, or untested?
I'm reluctant to copy and paste the value into our code, since it may change if cmqc.h is updated in a future release.
I'm trying to use WMQ in a multi-threaded Ruby environment. While I can do this fine provided I open and close connections within the same thread, I cannot sensible structure my code around e.g. Connection Pooling.
I see that WMQ itself does support multi-threaded environments, with
MQCNO_HANDLE_SHARE_BLOCK, but sinceGenerateConstexplicitly excludes theHANDLE_SHAREoptions, it's not available out of the box.I have manually tested with the value of
MQCNO_HANDLE_SHARE_BLOCKand everything works as expected (at least from what I can see) and this resolves a whole lot of issues for me. Is there a strong reason why this constant has been excluded, or is it a mistake, or untested?I'm reluctant to copy and paste the value into our code, since it may change if cmqc.h is updated in a future release.