jdenet error messages

Ever wanted to know what jdenet error 11 or jdenet error 29 actually means…

Sending a message failed, netErr=29.

We’ll let me tell you:

The jdenet.h file has a network error datatype defined with the following values. The array starts a 0, I numbered the first few of them.

Mike and I just saw a error 29, we follow that down to “eIPCMsgQueueFull” – good information. On windows IPC ranges are only controlled by the INI – not the OS (unlike unix). We went to the JDENET section of the JDE.INI and found that [JDENET] maxIPCQueueMsgs=100.

Wow, this make the error message much more understandable:
3092/4028 SYS:XMLDispatch Thu Feb 12 09:57:54.776000 Netqueue.c2511
Can't put msg on kernel queue (pid=588), OutStand Requests = 101

3092/4028 SYS:XMLDispatch Thu Feb 12 09:57:54.776001 Dispatcher.cpp714
Sending a message failed, netErr=29.

3092/4028 SYS:XMLDispatch Thu Feb 12 09:57:54.776002 Dispatcher.cpp714
ProcessDoc (processResquest): Dispatch Exception, state=2

3092/4028 SYS:XMLDispatch Thu Feb 12 09:57:54.776003 Dispatcher.cpp714
XMLDispatcher error report:


The network communication is broken.




typedef enum tagJDENetError {
eNoError, 0
eNetNotInitialized, 1
eInvalidMsgHandle, 2…
eInvalidRequest,
eInvalidParm,
eInvalidHostName,
eMallocFailed,
eFileOpenError,
eConnectionFailed,
eConnectionClose,
eMsgQueueFull,
eTimeOut, 11
eIPCError,
eMsgTypeOutOfRange,
eTimerError,
eGDMUndeliverable,
eFileWriteError,
eAssociateKernelNotExist, /*MJL-S2S*/
eMaxKernelTooLow,
eMaxKernelTooHigh,
eMaxNetTooLow,
eMaxNetTooHigh,
eKernelDisabled,
eKernelNotFound,
eOneUserOnlyKernelDisAllowed,
eCanNotStartNewKernel,
eTestNetCoreDump,
eMsgInternallyQueued, /* Used for call object manual commit queueing */
eWouldBlock,
eIPCMsgQueueFull, 29 /* Used when a message can't be put to a IPC
* queue, because a limit has been reached. */
eRemoveMsgData
} JDENetError;