Geoff Howard dijo:
>
> Antonio, you've hit on an interesting issue. I am still using a 1.4.0x
> version of java. I have 1.4.1 downloaded but haven't even bothered to
> extract it yet. I wonder if there's something there?
>
> Geoff
I think yes, there must be "something" bacause if you check the
snapshot download date jan 22 2003 - gives me out of
> memory error
>
>
>Thanks for the responses. My compile was getting stuck near
> the very end, creating the war file. Anyhow, after setting the
> env varexport ANT_OPTS="-Xms100m -Xmx228m" and rerunning
&g
in later after the
>> compiling
>> > is already done.
>> >
>> > I only needed step one, but depending on your systems memory
>> you'll have
>> > options. There is also a very recent (within the last 12
>> hours) patch
>> > that may mak
t; tried it yet.
> >
> > Geoff Howard
> >
> >> -Original Message-
> >> From: e nio [mailto:[EMAIL PROTECTED]]
> >> Sent: Thursday, January 23, 2003 6:19 PM
> >> To: [EMAIL PROTECTED]
> >> Subject: cvs2.1 snapshot dow
t; Sent: Thursday, January 23, 2003 6:19 PM
>> To: [EMAIL PROTECTED]
>> Subject: cvs2.1 snapshot download date jan 22 2003 - gives me out of
>> memory error
>>
>>
>> Anyone else experiencing this OutOfMemory when compiling the
&g
PROTECTED]]
> Sent: Thursday, January 23, 2003 6:19 PM
> To: [EMAIL PROTECTED]
> Subject: cvs2.1 snapshot download date jan 22 2003 - gives me out of
> memory error
>
>
> Anyone else experiencing this OutOfMemory when compiling the
> development snapshot dated Jan 22 2003
Anyone else experiencing this OutOfMemory when compiling the
development snapshot dated Jan 22 2003 -
xml-cocoon2_2003012305238_tar.gz ? I compiled it as such:
./build.sh -Dinclude.webapp.libs=yes
-Dinclude.installscratchpadwar.libs=yes webapp
Didnt have this problem on a download 1st week
Executive summary:
I think "Out of memory error" is in fact a bug.
Frequently it has nothing to do with your actual
available memory.
Blurb:
I had this problem before (see the details below), and
I searched the mailing lists and have been following
it on the mailing lists for a whil
My immediate reaction is to check the memory heap size of Jetty or Tomcat.
I think Java defaults to a maximum of 64MB per process unless otherwise
specified. With memory hungry operations like XSLT, 64MB really is not
enough, and I have had the "out of memory error" because of that.
I've been using Cocoon 2.0.2 in Tomcat 4.03 and also in Jetty. In both
instances, I frequently get out of memory error. I've tried few tuning
measures like turning off debugging but still I get this error, especially
when it comes to calls that make database connection(hsql). How i
t (50 thread in
JMeter), i get some "out of memory" error (wich are displayed without
stacktrace). Winnt 4 indicate that java.exe uses around 80Mo of memory (the
server has 1Go, and more than 500Mo of physical memory aviable)
I tryed to add -Xmx268435456 -Xms 268435456 in %catalina_opt%,
11 matches
Mail list logo