Viewing JDENET message contents

[peterbentley]

Hi,
I'm getting the following: Feb 01 14:58:12 ** 8060/6504 msgType 1156 not processed by dispatch Function '_JDEK_DispatchCallObjectMessage@28'
Feb 01 14:58:12 ** 8060/6504 putQueue 6179C318,msg-35,reqpid-0

Can anyone please tell me what settings I need to change to see the CONTENTS of the message?
Thanks,Peter.

 

[Alex_Pastuhov]

That's all you can get ;-(

Check the logs on the Server - there should be more there...

Regards,
Alex.

 

[WhippingBoy]

From JDEKDCL.h

/* Call Object- kernel type 7, Range 901-1156*/
typedef enum tagJDENETCallObjectMsgType {
JDEMSGCALLOBJ=901,
JDEMSGINITREMOTEUSER,
JDEMSGFREEREMOTEUSER,
JDEMSGINITREMOTEENV,
JDEMSGFREEREMOTEENV,
JDEMSGGETSZUSERLIST,
JDEMSGCUSTOMRUN,
JDEMSGCUSTOMLOAD,
JDEMSGCUSTOMUNLOAD,
JDEMSGTAMSEND,
JDEMSGREFRESHCACHE,
JDEMSGREFRESHPOCACHE,
JDEMSGCOMMITREMOTEUSER, /*jh5906952*/
JDEMSGROLLBACKREMOTEUSER, /*jh5906952*/
JDEMSGPREPAREREMOTEUSER,
JDEMSGGETUSERLIST,
JDEMSGCLEARCACHE,


/*MJL-NLS FOR JAS, need to assign a number since more msg in cum3 */
JDEMSGERRORITEM=950

} JDENETCallObjectMsgType;


What do you think? That last one (JDEMSGCLEARCACHE) seems a good candidate for message 1156. I can offer SWAGs with the best of'em.

 

[Alex_Pastuhov]

Hardly: it would be only #917, the very last one there (JDEMSGERRORITEM) is only #950...

Anyway, this all is happening on the client and the client does not run CallObject kernel, hence the error...

Regards,
Alex.