Hi Sarath,
There are a couple of possible reasons for this error:
(1) A short dump has occurred in the backend system,
Please check in ST22 at the time the error occurs to see if a short dump has occurred, if not then....
OR
(2) Please see SAP Note#1863563.
Check the developer trace files on the application server in the backend where the JCO is connecting to, you should find the following message:
M *** ERROR => ThRqInCheck: bad request (step 3, th_errno 3, action 1, level
1) [thxxhead.c 11313]
(The message could be in ANY of the DIA developer trace files).
We implemented WCEM 2.0 at a customer (went live end of 2012). Starting from during the implementation project we started receiving error messages as you have described (CM_NO_DATA_RECEIVED). In addition, just like you these messages occurred randomly. We could not produce any consistent scenarios to reproduce the problem occurring. A repeat of a specific scenario that produced the error would not produce the same error a second time.
Finally after 8+ months of back and forth with SAP they have produced SAP Note#1863563 which is a SAP Kernel patch for the backend system.
We have recently (a couple of weeks ago) applied the Kernel into the dev & test systems and will shortly migrate to Production. As we cannot consistently reproduce the error to check that the kernel patch actually fixes the problem, we will be monitoring to check the problem does not reoccur (and is actually resolved).
If you believe that this is the same problem you are having and decided to apply the kernel patch I would also be interested in your feedback as to whether it fixes your problem (or not).
Thanks.