Verbose logging for BIRT engine
We have some long-running BIRT reports running overnight. Sometimes result is suddenly "cut" and generated Excel file has 5-6 times less data than "usual". Looks like some external outage, but no clues. Is there a way to enable verbose BIRT logging to find out what happens to its engine while generating report?
Thanks in advance!
One answer
Hi Vladimir,
You can check when exactly your report is fetching the data:
java.lang.System.out.println("ROW: " + row["WHATEVER_COLUMN"] + ", " + row["WHATEVER_COLUMN"]);
(in onFetch column).
This is only what comes to my head.
Best regards,
Krzysztof Kazmierczyk.
You can check when exactly your report is fetching the data:
java.lang.System.out.println("ROW: " + row["WHATEVER_COLUMN"] + ", " + row["WHATEVER_COLUMN"]);
(in onFetch column).
This is only what comes to my head.
Best regards,
Krzysztof Kazmierczyk.
Comments
Worth trying, thanks.
There are log4j ways, but would require your Jazz Admin to configure and to be on a "good" version of RTC:
https://jazz.net/forum/questions/108730/how-to-troubleshoot-birt-reports-that-consume-excessive-timecpu
By "good" I mean one that can accept the log4j setting for DEBUG at configurations other than the 'root' logger.