| BIRT 2.2 Recommendations on JVM tuning parameters for Webapps embedding the reporting engine [message #250285] |
Sun, 29 July 2007 19:15  |
Eclipse User |
|
|
|
Originally posted by: shaun.methodmaker.co.nz
Hi,
As mentioned in a few previous posts the memory and permgen errors are
being reported in webapps embedding the reporting engine. The same types
of memory errors have initially been reported in Tomcat/JBoss.
Can anyone more knowledgeable suggest a recommended formula for
estimating the require memory requirements of the BIRT 2.2 run-time
environment. It would certainly help if -Xmx and -Xms and -XX:PermSize
-XX:MaxPermSize settings could be worked out.
At this stage the suggested workaround is to set the perm size to 1Gb+.
Regards
--
Shaun Forgie
Principal - Method Maker Ltd
Mobile [64] 21-666-910 http://www.methodmaker.co.nz
PO Box 1513, Auckland, New Zealand
|
|
|
| Re: BIRT 2.2 Recommendations on JVM tuning parameters for Webapps embedding the reporting engine [message #250297 is a reply to message #250285] |
Mon, 30 July 2007 00:05  |
| Eclipse User |
|
|
|
Originally posted by: shaun.methodmaker.co.nz
In continuation....
[this discussion is in reference to the following server environment -
Java 1.6.0 / Tomcat 6.0.13 / Birt 2.2]
After reading the comments on why JVM permgen errors where occurring on
Tomcat the suggested solution concerns the location of specified library
files. The location of jdbc drivers and commons logging jar files need
to be placed soley into the tomcat/lib directory. As this is a major
source of permgen issues occurring during redeployment; requiring the
server to be restarted. Additional configuration options surrounding the
use of the jdbc drivers needs to be configured in META-INF/context.xml
at an application level.
The problem is that Tomcat does not garbage collect the Classloader and
the classes it loads. Each time you reload the webapp context, more
copies of these classes are loaded, and as these are stored in the
permanent heap generation, it will eventually run out of memory. The
same issue could affect (and affects) a number containers. You just have
to restart the container instead of restarting the context. It's easy to
reproduce this problem by reloading the context over and over again
until you get an OutOfMemoryError (10 times was enough for a simple app)
In summary third party libraries should if possible be placed into the
tomcat/lib directory. Notice that there is only one lib directory for
Tomcat 6.0. This raises the question of where required JDBC
drivers/third party libraries are placed for BIRT 2.2 web apps.
Regards
Shaun
Shaun Forgie wrote:
> Hi,
>
> As mentioned in a few previous posts the memory and permgen errors are
> being reported in webapps embedding the reporting engine. The same types
> of memory errors have initially been reported in Tomcat/JBoss.
>
> Can anyone more knowledgeable suggest a recommended formula for
> estimating the require memory requirements of the BIRT 2.2 run-time
> environment. It would certainly help if -Xmx and -Xms and -XX:PermSize
> -XX:MaxPermSize settings could be worked out.
>
> At this stage the suggested workaround is to set the perm size to 1Gb+.
>
> Regards
>
--
Shaun Forgie
Principal - Method Maker Ltd
Mobile [64] 21-666-910 http://www.methodmaker.co.nz
PO Box 1513, Auckland, New Zealand
|
|
|
Powered by
FUDForum. Page generated in 0.05037 seconds
Home