Extend the MkRuntimeS wie pymqmsgque specific features … More...
#include <LibMqMsgque_mq.h>
Data Fields | ||
union { | ||
struct MkObjectS obj | ||
struct MkExtensionS ext | ||
struct MkRtExtS rtext | ||
} | super | |
is the MqRuntimeS initialized? | ||
struct MqErrorS | error_mq | |
struct MkSuperTypeS | _MqErrorC_T | |
struct MkSuperTypeS | _MqRuntimeC_T | |
struct MkTypeS | _MqCtxTypeC_TT | |
struct MqCtxTypeS | _MqContextC_T | |
struct MkSuperTypeS | _MqDumpC_T | |
struct MkSuperTypeS | _MqFactoryC_T | |
struct MkSuperTypeS | _MqEnvC_T | |
MK_BINB | private_variables [290776] | |
Extend the MkRuntimeS wie pymqmsgque specific features …
Definition at line 9125 of file LibMqMsgque_mq.h.
struct MqCtxTypeS MqRuntimeS::_MqContextC_T |
Definition at line 9159 of file LibMqMsgque_mq.h.
struct MkTypeS MqRuntimeS::_MqCtxTypeC_TT |
Definition at line 9158 of file LibMqMsgque_mq.h.
struct MkSuperTypeS MqRuntimeS::_MqDumpC_T |
Definition at line 9160 of file LibMqMsgque_mq.h.
struct MkSuperTypeS MqRuntimeS::_MqEnvC_T |
Definition at line 9162 of file LibMqMsgque_mq.h.
struct MkSuperTypeS MqRuntimeS::_MqErrorC_T |
Definition at line 9156 of file LibMqMsgque_mq.h.
struct MkSuperTypeS MqRuntimeS::_MqFactoryC_T |
Definition at line 9161 of file LibMqMsgque_mq.h.
struct MkSuperTypeS MqRuntimeS::_MqRuntimeC_T |
Definition at line 9157 of file LibMqMsgque_mq.h.
struct MqErrorS MqRuntimeS::error_mq |
Definition at line 9149 of file LibMqMsgque_mq.h.
struct MkExtensionS MqRuntimeS::ext |
Definition at line 9142 of file LibMqMsgque_mq.h.
struct MkObjectS MqRuntimeS::obj |
Definition at line 9141 of file LibMqMsgque_mq.h.
MK_BINB MqRuntimeS::private_variables[290776] |
Definition at line 9167 of file LibMqMsgque_mq.h.
struct MkRtExtS MqRuntimeS::rtext |
Definition at line 9143 of file LibMqMsgque_mq.h.
union { ... } MqRuntimeS::super |
is the MqRuntimeS initialized?
On "smart" systems like "csharp"… threads are created "on-the-fly" not only on user-demand… The problem is the "cleanup" code from the garbage-collection is controlled by "csharp" and sometimes "csharp" choose a new thread for this task. a "new" thread start with an empty MqRuntimeS… we need to handle this.