Heapspace Grenzen



Hallo,

ich habe hier eine Webanwendung unter Win2k Server, Tomcat7 und Java 1.6.31 laufen, die beim Kopieren einer Datenbank aussteigt: OutOfMemoryError: Java heap space

Die Argumente, mit denen Tomcat gestartet wird sind:

-Xmx1336m
-Xms512m
-Xss64k
-XX:MaxPermSize=256m

Nun habe ich versucht den -Xmx-Parameter höher zu setzen, mit dem Ergebnis, daß dann gar nix mehr geht (3 Beispielversuche):


[2012-08-30 08:27:52] [debug] ( javajni.c:660 ) Jvm Option[7] -Xmx3000m
[2012-08-30 08:27:52] [debug] ( javajni.c:660 ) Jvm Option[8] -Xms512m
[2012-08-30 08:27:53] [debug] ( javajni.c:660 ) Jvm Option[9] -Xss64k
[2012-08-30 08:27:53] [debug] ( javajni.c:660 ) Jvm Option[10]
-XX:MaxPermSize=256m
[2012-08-30 08:27:53] [debug] ( javajni.c:660 ) Jvm Option[11]
-Djava.class.path=D:\Programme\Tomcat7\bin\bootstrap.jar;D:\Programme\Tomcat7\bin\tomcat-juli.jar
[2012-08-30 08:27:53] [error] ( javajni.c:670 ) CreateJavaVM Failed


[2012-08-30 08:29:07] [debug] ( javajni.c:660 ) Jvm Option[7] -Xmx1536m
[2012-08-30 08:29:07] [debug] ( javajni.c:660 ) Jvm Option[8] -Xms512m
[2012-08-30 08:29:07] [debug] ( javajni.c:660 ) Jvm Option[9] -Xss64k
[2012-08-30 08:29:07] [debug] ( javajni.c:660 ) Jvm Option[10]
-XX:MaxPermSize=256m
[2012-08-30 08:29:07] [debug] ( javajni.c:660 ) Jvm Option[11]
-Djava.class.path=D:\Programme\Tomcat7\bin\bootstrap.jar;D:\Programme\Tomcat7\bin\tomcat-juli.jar
[2012-08-30 08:29:07] [error] ( javajni.c:670 ) CreateJavaVM Failed


[2012-08-30 08:31:59] [debug] ( javajni.c:660 ) Jvm Option[7] -Xmx1336m
[2012-08-30 08:31:59] [debug] ( javajni.c:660 ) Jvm Option[8] -Xms512m
[2012-08-30 08:31:59] [debug] ( javajni.c:660 ) Jvm Option[9] -Xss64k
[2012-08-30 08:31:59] [debug] ( javajni.c:660 ) Jvm Option[10]
-XX:MaxPermSize=256m
[2012-08-30 08:31:59] [debug] ( javajni.c:660 ) Jvm Option[11]
-Djava.class.path=D:\Programme\Tomcat7\bin\bootstrap.jar;D:\Programme\Tomcat7\bin\tomcat-juli.jar
[2012-08-30 08:31:59] [debug] ( javajni.c:844 ) argv[0] = start
[2012-08-30 08:31:59] [debug] ( javajni.c:891 ) Java Worker thread started
org/apache/catalina/startup/Bootstrap:main
[2012-08-30 08:32:00] [debug] ( prunsrv.c:1058) Java started
org/apache/catalina/startup/Bootstrap
[2012-08-30 08:32:00] [info] ( :0 ) Service started in 1468 ms.

(einzige Änderung war der -Xmx-Parameter)
Gibt es da irgendwelche Limits? Eine Suche nach "java heap space limit -Xmx" brachte mir nix erhellendes (außer daß in irgendwelchen Webforen Leute durchaus mit -Xmx2048m arbeiten konnten).
Wo könnte ich mit der Suche nach der Ursache für obiges Problem weitermachen?

Gruß

Werner
.



Relevant Pages

  • Re: Excessive paging problem
    ... the proc quotas to be adjusted accordingly. ... after a day of uptime the working set grows far beyond the Java heap size until WSEXTENT is reached. ... to keep more than max heap sized data in memory, ...
    (comp.os.vms)
  • Re: What uses the Java heap?
    ... I increased my max java heap to 756MB using the java.opts file, and this only gave me a couple hours more of runtime. ... Also, free memory decreases in a stepwise pattern, but then after a while suddenly decreases in huge bursts. ... One potential debugging step would be to look around iteration 2000 where there's a large drop in free memory. ...
    (comp.soft-sys.matlab)
  • Re: Excessive paging problem
    ... the Java programmer slowly turning into a VMS system admin:-I ... > Having settled the problems with starting the app detached, ... > working set grows far beyond the Java heap size ... Unofficial OpenVMS Hobbyist Support Page: ...
    (comp.os.vms)
  • Re: Excessive paging problem
    ... >> Bernhard Dorninger wrote: ... >>> I have read HP's Optimizing Java Guide for the OpenVMS platform carefully and ordered ... >>> I cannot understand, why the process keeps demanding pages, although Java heap has been ... > to keep more than max heap sized data in memory, ...
    (comp.os.vms)
  • Excessive paging problem
    ... the Java programmer slowly turning into a VMS system admin:-I ... Java 1.4.2-04p2. ... Our main app is started with a Java heap of max 96MB, the WSEXTENT is set to 160MB for that user. ...
    (comp.os.vms)