Re: Integrated Application Server problem with memory settings, and with where to find logs for BIRT

James,

I can tell you that on our i (5.4.0), running Java 1.6.0, I can only set
Xms and Xmx (minimum and maximum heap size.) Attempting to set any of the
other garbage collection values causes Tomcat to abend during startup.
The recommendation is to make Xms about 20% of Xmx, but it takes some
playing and log watching to identify what the best settings are. They are
set in tomcat by adding a value to JAVA_OPTS in catalina.sh (I'm running
tomcat 3.7.0, and I use a setting like this:
JAVA_OPTS="-verbose:gc -Xms900m -Xmx4000m"
That puts the garbage collection stats in catalina.out. I use the count
of "Stop the world" messages, and the maximum value of "collect
(milliseconds)" values as metrics for tuning. Of the two, "Stop the
world" is the more significant, since it identifies instances when the
app has actually frozen during garbage collection.

I'm running BIRT too (3.7.0), but I'm using the report engine APIs, so I
can explicitly set where the BIRT logs go like this:
EngineConfig config = new EngineConfig();
config.setLogConfig(logPath, Level.ALL);
config.setLogFile(logFileName);

I do find it useful to run a dummy report during startup, so the BIRT
runtime classes get instantiated. The report engine instance is cached in
the application object, because startup is a real pig on the i.

If you're using the WebViewerExample application or a derivitave as a
report server, there's a logs directory in that application. I assume
that's where they'd be, but I haven't used the WebViewer beyond some
initial playing, way back. It seemed like too much overhead to me,
although it does have a pretty animated "busy" graphic.

hth