You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@santuario.apache.org by Matteo Artuso <ma...@unimaticaspa.it> on 2002/11/28 15:37:28 UTC
out of memory error, depneds on static object in XMLSeignature?
Hi,
I verify after 2 signature verification fail in a big xml (500kb), program explode in an java.lang.OutOfMemofyError.
I redefine object XMLSecurity every time into verfing cicle and call System.gc to clear memory, unfortunally, I can't solve the problem.
Probably because there's a static method in XMLSignature and so garbage collector can't clear it.
Any suggestions?
M@
----------------------------------------------------------------------------
Ing. Matteo Artuso
Unimatica SpA
e-mail martuso@unimaticaspa.it
tel. 051 7790331
centralino 051 7790311
fax 051 7790350
----------------------------------------------------------------------------
RE: out of memory error, depneds on static object in XMLSeignature?
Posted by Michael Czapski <mc...@seebeyond.com>.
Hello,
try:
-- --
C:\>java -X -?
-Xmixed mixed mode execution (default)
-Xint interpreted mode execution only
-Xbootclasspath:<directories and zip/jar files separated by ;>
set search path for bootstrap classes and resources
-Xbootclasspath/a:<directories and zip/jar files separated by ;>
append to end of bootstrap class path
-Xbootclasspath/p:<directories and zip/jar files separated by ;>
prepend in front of bootstrap class path
-Xnoclassgc disable class garbage collection
-Xincgc enable incremental garbage collection
-Xbatch disable background compilation
-Xms<size> set initial Java heap size
-Xmx<size> set maximum Java heap size
-Xss<size> set java thread stack size
-Xprof output cpu profiling data
-Xrunhprof[:help]|[:<option>=<value>, ...]
perform JVMPI heap, cpu, or monitor profiling
-Xdebug enable remote debugging
-Xfuture enable strictest checks, anticipating future default
-Xrs reduce use of OS signals by Java/VM (see documentation)
The -X options are non-standard and subject to change without notice.
++ ++
Take note of the -Xms and -Xmx - these are the parameters that affect the amount of heap jvm uses. By defaults it is 64Mb, which in many cases is _not_ enough. This is the reason for the out of memory failure.
Regards
-----Original Message-----
From: Matteo Artuso [mailto:martuso@unimaticaspa.it]
Sent: Friday, 29 November 2002 01:37 AM
To: security-dev@xml.apache.org
Cc: geuer-pollmann@nue.et-inf.uni-siegen.de
Subject: out of memory error, depneds on static object in XMLSeignature?
Hi,
I verify after 2 signature verification fail in a big xml (500kb), program explode in an java.lang.OutOfMemofyError.
I redefine object XMLSecurity every time into verfing cicle and call System.gc to clear memory, unfortunally, I can't solve the problem.
Probably because there's a static method in XMLSignature and so garbage collector can't clear it.
Any suggestions?
M@
----------------------------------------------------------------------------
Ing. Matteo Artuso
Unimatica SpA
e-mail martuso@unimaticaspa.it
tel. 051 7790331
centralino 051 7790311
fax 051 7790350
----------------------------------------------------------------------------