Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.2.6 and later
Information in this document applies to any platform.
***Checked for relevance on 09-Jun-2015***
Experiencing slow performance / wait times when printing multiple reports from OTM.
Technically speaking, the steps to create a report are roughly as follows:
Step 1. OTM calls BI Publisher to generate the report.
Step 2. BI Publisher calls the CUPS server to process the print request.
It is in the second step that bad performance is observed.
When looking at the BI Publisher log files, it turns out that during the call from BI Publisher to the CUPS server, there is a delay of several seconds. This delay occurs on each job, therefore when printing numerous jobs, the delays will add up to long delays.
This is where the delay takes place:
- Run a report
- Check the logfile "bipublisher.log" file in the "logs" directory of the OTM filesystem.
- The log file shows a large delay in the class HTTPSession.
See an excerpt from an example log file:
[082012_135731862][oracle.apps.xdo.delivery.http.HTTPClient][STATEMENT] submitRequest() called
[082012_135743897][oracle.apps.xdo.delivery.http.HTTPClient][STATEMENT] submitRequest(): pIn.available(): 387
In this case there is a delay of 135731862-135743897=12035 milliseconds (over 12 seconds).
- Looking closer at the code, it becomes clear that the method 'waitResponse' will ALWAYS wait for at least 1000x10=10000 milliseconds, even if the response has been received.
Hence, even if the CUPS server responds very quickly (e.g. within 1 second), there will be a minimum delay of 10 seconds.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms