CECORBACommunicationAdapter.request() Throwable - The request timed

[former_member501426]

running report using java application getting this exception

CECORBACommunicationAdapter.request() Throwable - The request timed out because there has been no reply from the server for 600,000 milliseconds.

[Former Member · Accepted solution]

Do you see the error with all the reports or only with long running reports?

The SDK timeout setting by default is 10 mins which is stated in the error, if there is no response from the RAS server for 10 mins the connection timeout.

This can be raised to an upper limit however you need to get to the cause whether this happened for only the long running reports of this happens for every call you make from your application.

Thanks,

Prithvi

[former_member501426 · Accepted solution]

not for all reports only couple of reports this is happening... when ran those reports whole server goes not responding mode.. any other report run thereafter will give same error... I have to restart all CR servers.... to run other reports properly...

[Former Member · Accepted solution]

The error states that the SDK listener timed out as there is no response back from RAS server in 10 mins(default timeout value)

The reasons could be the report takes more than 10 mins to run or there is some issue with the report for example a printer configuration of the report which the RAS server is unable to find and ultimately the request times out.

As it is only happening with specific reports, you can check whether

1) Is the report query take more than 10 mins to render the results

2) Are you able to run those reports from crystal designer without any issues? Check the No printer option for those reports publish it to enterprise and run the reports from your application again.

Refer to the below link for best practices, its an old one however it still applies.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b02de5c2-2548-2f10-14b7-a70665be2...

[former_member501426 · Accepted solution]

yes the issue was with printer setup... once checked No Printer checkbox (File> page Setup) it started working thanks prithivi