Hi Wasim,
Wasim Ansari wrote:
It never reaches to JCoServerFunctionHandler() when confirmTID() is called.
This is the way, the tRFC protocol is designed. The R/3 system calls confirmTID(), after the actual function call has been processed successfully (and the ok code which indicates this has arrived back at the R/3 system successfully!). In fact, the Confirm step may happen hours/days later, if network problems occur between the successful execution of the FM and the Confirm step.
It is your responsibility to keep the transaction ID, that you get in the checkTID() step, in a permanent storage, like a database or a file, so you can later correlate the handleRequest() and any Rollback, Commit or Confirm step that may happen on this TID. For a good explanation of how the tRFC protocol works (and how to guarantee "once and only once" execution of a transaction!) see https://scn.sap.com/docs/DOC-52888. This describes it for C/C++ programs using the NetWeaver RFC library, but the same logic also applies to Java programs using JCo.
Best Regards, Ulrich