JCo client calls as background processes (avoiding timeouts)

[Former Member]

Hi Guys!

Could you please assist us to resolve a simple issue:

Our JCo Client call takes sometimes longer than the given timout for sap dialog processes (so, it's now clear, the jco client simply uses the dialog processes and not something smarter/more flexible).

My question is, ho to entice the jco client call to run without runtime timeout and take as long time as necessary. If the only possibility is, to use the tRFC, does anybody have an example for tRFC usage from JCo Client?

Is also a JCo server component needed to implement some callback functionality from SAP system by using the tRFC, or it could be enough to poll the server and implement the timeout on the client level (it could be for us the best solution if we realy must use the tRFC).

Once again, we want to run the JCo client calls unlimited time (as long as needed) without the annoying dialog process timeout. The tRFC is not necessary by use cases now.

Any help would be appreciated!

Many thanks, Gena

[Former Member]

Hi Guys!

Could you please assist us to resolve a simple issue:

Our JCo Client call takes sometimes longer than the given timout for sap dialog processes (so, it's now clear, the jco client simply uses the dialog processes and not something smarter/more flexible).

My question is, ho to entice the jco client call to run without runtime timeout and take as long time as necessary. If the only possibility is, to use the tRFC, does anybody have an example for tRFC usage from JCo Client?

Is also a JCo server component needed to implement some callback functionality from SAP system by using the tRFC, or it could be enough to poll the server and implement the timeout on the client level (it could be for us the best solution if we realy must use the tRFC).

Once again, we want to run the JCo client calls unlimited time (as long as needed) without the annoying dialog process timeout. The tRFC is not necessary by use cases now.

Any help would be appreciated!

Many thanks, Gena

[Former Member]

Hi Gena,

so, it's now clear, the jco client simply uses the dialog processes and not something smarter/more flexible

Well, that's a feature of the underlying RFC protocol: All RFC calls are executed in dialog work processes, thus also the runtime limitations for dialog processes apply.

My question is, ho to entice the jco client call to run without runtime timeout and take as long time as necessary. If the only possibility is, to use the tRFC, does anybody have an example for tRFC usage from JCo Client?

The JCo client cannot do anything about it, it's a profile parameter in SAP, i.e. rdisp/max_wprun_time. But as this parameter applies to all dialog processes (so dialog users and RFC calls), so it shouldn't be changed to make a single RFC application work. Anyhow, tRFC won't help you in this case, because all RFC calls are processed in a dialog process no matter of the type of RFC.

Once again, we want to run the JCo client calls unlimited time (as long as needed) without the annoying dialog process timeout.

Impossible without making any changes in SAP. In theory one could modify the RFC function so that it resets the "runtime counter" and thus having the capability to run longer than rdisp/max_wprun_time. I'd recommend though not to do that, especially since a very long running RFC seems rather questionable. Long running tasks should be processed in background.

Cheers, harald