You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Oleg Konovalov <ol...@yahoo.com> on 2006/07/07 16:06:59 UTC

OutOfMemoryError

Hi,

We are getting OutOfMemoryError 
16:26:41,011 ERROR [STDERR] java.lang.OutOfMemoryError
in our production server (which has 4GB of RAM, javaVM - max 2GB)
every other day. All applications stop responding.
We have a bunch of Cocoon applications [mostly 2.0.4] running on JBoss3.0.7.
It is totally unclear which application is causing the problem.

I don't remember that problem happening in our Development or Testing environment
(where max JavaVM=512MB), but I guess it has a much lighter load.

Is there any known memory problem with Cocoon ?

Is there a way to do memory profiling of Cocoon Apps ? Any particular tool ?
(I have done memory profiling of Java applets with JProbe years ago)
 
Any advice is very appreciated.



Thank you in advance,
 Oleg.

Re: AW: AW: OutOfMemoryError

Posted by Ralph Goers <Ra...@dslextreme.com>.
Dan Durkin wrote:

> Ralph,
>
> Can you elaborate on how you see that a given pool size is too low?
>
> Thanks,
>
> Dan
>
This happened just last week. We were doing CPU profiling with YourKit 
and when I drilled down I saw the resource limiting pool was creating 
XML serializers. You would never see this (in a warmed up system) if the 
pool size was OK.  Its harder to see in production. I've had our 
operations folks periodically take thread dumps and then I look at 
them.  Usually, you will see the resource limiting pool if some pool 
size is too low, but you usually won't see what the object is.

Ralph


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: AW: AW: OutOfMemoryError

Posted by Dan Durkin <du...@macchine.com>.
Ralph Goers wrote:
> Christofer Dutz wrote:
>>
>> Hi Oleg
>>
>> Well exactly this is why I used JRockit, because I didn’t want to 
>> bother finding out how to tweak it ;) I know that the way the 
>> Garbagecollector works can be configured using command-line 
>> parameters, but I don’t know which ones and if they have the desired 
>> effect.
>>
>> I just wanted to give you the hint that you will not find any real 
>> memory-leaks, because there aren’t any and that the problems you are 
>> having result of a garbage collection problem in the VM … realizing 
>> this earlier would have made many many days of code-checking and 
>> profiling obsolete L
>>
>> Good luck,
>>
>> Chris
>>
> I have to disagree. While you may not find any memory leaks, profiling 
> should always be recommended. First, it helps you understand how your 
> application operates. Second, you may find that you have pool sizes that 
> are too low or that you need to modify some pipelines or make some other 
> modifications.
> 
> However, we have found significant improvements by modifying the JVM 
> settings. Unfortunately, I don't have them in front of me at the moment.
> 
> Ralph

Ralph,

Can you elaborate on how you see that a given pool size is too low?

Thanks,

Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

AW: AW: AW: OutOfMemoryError

Posted by Christofer Dutz <du...@c-ware.de>.
Hi Raplh,

what I wanted to say is that memory is not always freed in the default VM
settings. Otherwise hitting the "Garbage Collect" Button in the VM Monitor
application wouldn't be able to free GBs of unused memory.

Chris

-----Ursprüngliche Nachricht-----
Von: Ralph Goers [mailto:Ralph.Goers@dslextreme.com] 
Gesendet: Dienstag, 11. Juli 2006 15:54
An: users@cocoon.apache.org
Betreff: Re: AW: AW: OutOfMemoryError

Christofer Dutz wrote:
>
> Hi Oleg
>
> Well exactly this is why I used JRockit, because I didn’t want to 
> bother finding out how to tweak it ;) I know that the way the 
> Garbagecollector works can be configured using command-line 
> parameters, but I don’t know which ones and if they have the desired 
> effect.
>
> I just wanted to give you the hint that you will not find any real 
> memory-leaks, because there aren’t any and that the problems you are 
> having result of a garbage collection problem in the VM … realizing 
> this earlier would have made many many days of code-checking and 
> profiling obsolete L
>
> Good luck,
>
> Chris
>
I have to disagree. While you may not find any memory leaks, profiling 
should always be recommended. First, it helps you understand how your 
application operates. Second, you may find that you have pool sizes that 
are too low or that you need to modify some pipelines or make some other 
modifications.

However, we have found significant improvements by modifying the JVM 
settings. Unfortunately, I don't have them in front of me at the moment.

Ralph

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: AW: AW: OutOfMemoryError

Posted by Ralph Goers <Ra...@dslextreme.com>.
Christofer Dutz wrote:
>
> Hi Oleg
>
> Well exactly this is why I used JRockit, because I didn’t want to 
> bother finding out how to tweak it ;) I know that the way the 
> Garbagecollector works can be configured using command-line 
> parameters, but I don’t know which ones and if they have the desired 
> effect.
>
> I just wanted to give you the hint that you will not find any real 
> memory-leaks, because there aren’t any and that the problems you are 
> having result of a garbage collection problem in the VM … realizing 
> this earlier would have made many many days of code-checking and 
> profiling obsolete L
>
> Good luck,
>
> Chris
>
I have to disagree. While you may not find any memory leaks, profiling 
should always be recommended. First, it helps you understand how your 
application operates. Second, you may find that you have pool sizes that 
are too low or that you need to modify some pipelines or make some other 
modifications.

However, we have found significant improvements by modifying the JVM 
settings. Unfortunately, I don't have them in front of me at the moment.

Ralph

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

AW: AW: AW: OutOfMemoryError

Posted by Christofer Dutz <du...@c-ware.de>.
Hi Oleg,

 

We had the problems with a JDK 1.5_02 (I think) on a Windows 2003 server. As
far as I remember (this was a few months ago) this is no real bug in the
sense of not working correctly. For performance reasons the default GC
doesn’t walk through the entire reference Tree, it only checks a few levels.
If you have circular references that’s “size” exceeds the maximum scanning
depth of the GC, it won’t detect that. As far as I know this is not limited
to only this VM since it is a basic Algorithm problem. Mabe Dan can help you
with the VM settings (since I did’t it the lazy way ;) ) 

 

Regards,

    Chris

 

[ c h r i s t o f e r   d u t z ]

 

IT-Berater

univativ GmbH & Co. KG

Robert-Bosch-Str. 7, 64293 Darmstadt

 

fon: 0 61 51 / 66 717 - 21

fax: 0 61 51 / 66 717 - 29

email: christofer.dutz@univativ.de

http://www.univativ.de

 

Darmstadt, Stuttgart, Karlsruhe, Düsseldorf

 

 

  _____  

Von: Oleg Konovalov [mailto:olegkon@yahoo.com] 
Gesendet: Dienstag, 11. Juli 2006 23:21
An: users@cocoon.apache.org
Betreff: Re: AW: AW: OutOfMemoryError

 

Christofer,

Which version of Sun JavaVM did you have the problem with 
("default Garbage Collection Settings seem to have problems with circular
references")? 
On which  platform ?
Is there open issue you can refer me to ?

Our Production environment runs on JDK1.4.2_04 on Solaris 9 (32 bit) on
SPARC.
I was thinking, maybe upgrade to the latest one (1.4.2_12?) might have that
problem fixed?
Any info on that ?

 

Thank you,
Oleg.

 

----- Original Message ----
From: Christofer Dutz <du...@c-ware.de>
To: users@cocoon.apache.org; Oleg Konovalov <ol...@yahoo.com>
Sent: Tuesday, July 11, 2006 4:28:03 AM
Subject: AW: AW: OutOfMemoryError

Hi Oleg

 

Well exactly this is why I used JRockit, because I didn’t want to bother
finding out how to tweak it ;) I know that the way the Garbagecollector
works can be configured using command-line parameters, but I don’t know
which ones and if they have the desired effect. 

I just wanted to give you the hint that you will not find any real
memory-leaks, because there aren’t any and that the problems you are having
result of a garbage collection problem in the VM … realizing this earlier
would have made many many days of code-checking and profiling obsolete :-(

 

Good luck,

     Chris

 

[ c h r i s t o f e r   d u t z ]

 

IT-Berater

univativ GmbH & Co. KG

Robert-Bosch-Str. 7, 64293 Darmstadt

 

fon: 0 61 51 / 66 717 - 21

fax: 0 61 51 / 66 717 - 29

email: christofer.dutz@univativ.de

http://www.univativ.de

 

Darmstadt, Stuttgart, Karlsruhe, Düsseldorf

 

 

  _____  

Von: Oleg Konovalov [mailto:olegkon@yahoo.com] 
Gesendet: Montag, 10. Juli 2006 18:12
An: users@cocoon.apache.org
Betreff: Re: AW: OutOfMemoryError

 

Christofer, 

Could you please elaborate on "We could have solved this by tweaking the GC
settings of the VM..."
I do not think we have an option of switching to BEA Jrockit VM.
We can only use Sun's JavaVM (1.4.2)

Also I found out (from another dev group) that the primary suspect is a new
application 
which is not a Cocoon one, but WebWorks.
Any know memory issues for WebWorks apps ?

(I do realize that's a Cocoon mailing list, sorry...  All other apps there
are Cocoon ones.)
 

Thank you,
Oleg.

 

----- Original Message ----
From: Christofer Dutz <du...@c-ware.de>
To: users@cocoon.apache.org; Oleg Konovalov <ol...@yahoo.com>
Sent: Monday, July 10, 2006 3:50:27 AM
Subject: AW: OutOfMemoryError

Hi Oleg,

 

we encountered similar problems and fortunately found our that these
problems were VM related. I assume you are using a standard Sun JDK
installation (This was the case with our system). When looking at the VM
memory consumption, we could see an increasing memory consumption. Whenever
we manually triggered a “big garbage-collection” most of this was freed
again. The problem is that the default Garbage Collection Settings seem to
have problems with circular references. Memory, which is not accessible, is
not freed because of this. We could have solved this by tweaking the GC
settings of the VM, but we got rid of the problems by using the BEA Jrockit
VM instead (I knew this would work and I didn’t want to dig into all the
switches an leavers of the sun GC) 

 

Hope this helps.

 

Regards,

            Christofer

 

[ c h r i s t o f e r   d u t z ]

 

IT-Berater

univativ GmbH & Co. KG

Robert-Bosch-Str. 7, 64293 Darmstadt

 

fon: 0 61 51 / 66 717 - 21

fax: 0 61 51 / 66 717 - 29

email: christofer.dutz@univativ.de

http://www.univativ.de

 

Darmstadt, Stuttgart, Karlsruhe, Düsseldorf

 

 

  _____  

Von: Oleg Konovalov [mailto:olegkon@yahoo.com] 
Gesendet: Freitag, 7. Juli 2006 16:07
An: cocoon list
Betreff: OutOfMemoryError

 

Hi,

We are getting OutOfMemoryError 
16:26:41,011 ERROR [STDERR] java.lang.OutOfMemoryError
in our production server (which has 4GB of RAM, javaVM - max 2GB)
every other day. All applications stop responding.
We have a bunch of Cocoon applications [mostly 2.0.4] running on JBoss3.0.7.
It is totally unclear which application is causing the problem.

I don't remember that problem happening in our Development or Testing
environment
(where max JavaVM=512MB), but I guess it has a much lighter load.

Is there any known memory problem with Cocoon ?

Is there a way to do memory profiling of Cocoon Apps ? Any particular tool ?
(I have done memory profiling of Java applets with JProbe years ago)

 
Any advice is very appreciated.

Thank you in advance,
 Oleg.

Re: AW: AW: OutOfMemoryError

Posted by Oleg Konovalov <ol...@yahoo.com>.
Christofer,

Which version of Sun JavaVM did you have the problem with 
("default Garbage Collection Settings seem to have problems with circular references")? 
On which  platform ?
Is there open issue you can refer me to ?

Our Production environment runs on JDK1.4.2_04 on Solaris 9 (32 bit) on SPARC.
I was thinking, maybe upgrade to the latest one (1.4.2_12?) might have that problem fixed?
Any info on that ?
 
Thank you,
Oleg.

----- Original Message ----
From: Christofer Dutz <du...@c-ware.de>
To: users@cocoon.apache.org; Oleg Konovalov <ol...@yahoo.com>
Sent: Tuesday, July 11, 2006 4:28:03 AM
Subject: AW: AW: OutOfMemoryError

              Hi Oleg
     
   Well exactly this is why I used JRockit, because I didn’t want to bother finding out how to tweak it ;) I know that the way the Garbagecollector works can be configured using command-line parameters, but I don’t know which ones and if they have the desired effect. 
   I just wanted to give you the hint that you will not find any real memory-leaks, because there aren’t any and that the problems you are having result of a garbage collection problem in the VM … realizing this earlier would have made many many days of code-checking and profiling obsolete L
     
   Good luck,
        Chris
     
   [ c h r i s t o f e r   d u t z ]
    
   IT-Berater
   univativ GmbH & Co. KG
   Robert-Bosch-Str. 7, 64293 Darmstadt
    
   fon: 0 61 51 / 66 717 - 21
   fax: 0 61 51 / 66 717 - 29
   email: christofer.dutz@univativ.de
   http://www.univativ.de
    
   Darmstadt, Stuttgart, Karlsruhe, Düsseldorf
     
     
         
  Von: Oleg Konovalov [mailto:olegkon@yahoo.com] 
 Gesendet: Montag, 10. Juli 2006 18:12
 An: users@cocoon.apache.org
 Betreff: Re: AW: OutOfMemoryError
   
    
     Christofer, 
 
 Could you please elaborate on "We could have solved this by tweaking the GC settings of the VM..."
 I do not think we have an option of switching to BEA Jrockit VM.
 We can only use Sun's JavaVM (1.4.2)
 
 Also I found out (from another dev group) that the primary suspect is a new application 
 which is not a Cocoon one, but WebWorks.
 Any know memory issues for WebWorks apps ?
     (I do realize that's a Cocoon mailing list, sorry...  All other apps there are Cocoon ones.)
  
   
  Thank you,
 Oleg.
       
     ----- Original Message ----
 From: Christofer Dutz <du...@c-ware.de>
 To: users@cocoon.apache.org; Oleg Konovalov <ol...@yahoo.com>
 Sent: Monday, July 10, 2006 3:50:27 AM
 Subject: AW: OutOfMemoryError
     Hi Oleg,
    
   we encountered similar problems and fortunately found our that these problems were VM related. I assume you are using a standard Sun JDK installation (This was the case with our system). When looking at the VM memory consumption, we could see an increasing memory consumption. Whenever we manually triggered a “big garbage-collection” most of this was freed again. The problem is that the default Garbage Collection Settings seem to have problems with circular references. Memory, which is not accessible, is not freed because of this. We could have solved this by tweaking the GC settings of the VM, but we got rid of the problems by using the BEA Jrockit VM instead (I knew this would work and I didn’t want to dig into all the switches an leavers of the sun GC) 
    
   Hope this helps.
    
   Regards,
               Christofer
    
   [ c h r i s t o f e r   d u t z ]
    
   IT-Berater
   univativ GmbH & Co. KG
   Robert-Bosch-Str. 7, 64293 Darmstadt
    
   fon: 0 61 51 / 66 717 - 21
   fax: 0 61 51 / 66 717 - 29
   email: christofer.dutz@univativ.de
   http://www.univativ.de
    
   Darmstadt, Stuttgart, Karlsruhe, Düsseldorf
    
    
         
  Von: Oleg Konovalov [mailto:olegkon@yahoo.com] 
 Gesendet: Freitag, 7. Juli 2006 16:07
 An: cocoon list
 Betreff: OutOfMemoryError
   
   
     Hi,
 
 We are getting OutOfMemoryError 
 16:26:41,011 ERROR [STDERR] java.lang.OutOfMemoryError
 in our production server (which has 4GB of RAM, javaVM - max 2GB)
 every other day. All applications stop responding.
 We have a bunch of Cocoon applications [mostly 2.0.4] running on JBoss3.0.7.
 It is totally unclear which application is causing the problem.
 
 I don't remember that problem happening in our Development or Testing environment
 (where max JavaVM=512MB), but I guess it has a much lighter load.
 
 Is there any known memory problem with Cocoon ?
 
 Is there a way to do memory profiling of Cocoon Apps ? Any particular tool ?
 (I have done memory profiling of Java applets with JProbe years ago)
      
 Any advice is very appreciated.
   
  Thank you in advance,
  Oleg.

AW: AW: OutOfMemoryError

Posted by Christofer Dutz <du...@c-ware.de>.
Hi Oleg

 

Well exactly this is why I used JRockit, because I didn’t want to bother
finding out how to tweak it ;) I know that the way the Garbagecollector
works can be configured using command-line parameters, but I don’t know
which ones and if they have the desired effect. 

I just wanted to give you the hint that you will not find any real
memory-leaks, because there aren’t any and that the problems you are having
result of a garbage collection problem in the VM … realizing this earlier
would have made many many days of code-checking and profiling obsolete :-(

 

Good luck,

     Chris

 

[ c h r i s t o f e r   d u t z ]

 

IT-Berater

univativ GmbH & Co. KG

Robert-Bosch-Str. 7, 64293 Darmstadt

 

fon: 0 61 51 / 66 717 - 21

fax: 0 61 51 / 66 717 - 29

email: christofer.dutz@univativ.de

http://www.univativ.de

 

Darmstadt, Stuttgart, Karlsruhe, Düsseldorf

 

 

  _____  

Von: Oleg Konovalov [mailto:olegkon@yahoo.com] 
Gesendet: Montag, 10. Juli 2006 18:12
An: users@cocoon.apache.org
Betreff: Re: AW: OutOfMemoryError

 

Christofer, 

Could you please elaborate on "We could have solved this by tweaking the GC
settings of the VM..."
I do not think we have an option of switching to BEA Jrockit VM.
We can only use Sun's JavaVM (1.4.2)

Also I found out (from another dev group) that the primary suspect is a new
application 
which is not a Cocoon one, but WebWorks.
Any know memory issues for WebWorks apps ?

(I do realize that's a Cocoon mailing list, sorry...  All other apps there
are Cocoon ones.)
 

Thank you,
Oleg.

 

----- Original Message ----
From: Christofer Dutz <du...@c-ware.de>
To: users@cocoon.apache.org; Oleg Konovalov <ol...@yahoo.com>
Sent: Monday, July 10, 2006 3:50:27 AM
Subject: AW: OutOfMemoryError

Hi Oleg,

 

we encountered similar problems and fortunately found our that these
problems were VM related. I assume you are using a standard Sun JDK
installation (This was the case with our system). When looking at the VM
memory consumption, we could see an increasing memory consumption. Whenever
we manually triggered a “big garbage-collection” most of this was freed
again. The problem is that the default Garbage Collection Settings seem to
have problems with circular references. Memory, which is not accessible, is
not freed because of this. We could have solved this by tweaking the GC
settings of the VM, but we got rid of the problems by using the BEA Jrockit
VM instead (I knew this would work and I didn’t want to dig into all the
switches an leavers of the sun GC) 

 

Hope this helps.

 

Regards,

            Christofer

 

[ c h r i s t o f e r   d u t z ]

 

IT-Berater

univativ GmbH & Co. KG

Robert-Bosch-Str. 7, 64293 Darmstadt

 

fon: 0 61 51 / 66 717 - 21

fax: 0 61 51 / 66 717 - 29

email: christofer.dutz@univativ.de

http://www.univativ.de

 

Darmstadt, Stuttgart, Karlsruhe, Düsseldorf

 

 

  _____  

Von: Oleg Konovalov [mailto:olegkon@yahoo.com] 
Gesendet: Freitag, 7. Juli 2006 16:07
An: cocoon list
Betreff: OutOfMemoryError

 

Hi,

We are getting OutOfMemoryError 
16:26:41,011 ERROR [STDERR] java.lang.OutOfMemoryError
in our production server (which has 4GB of RAM, javaVM - max 2GB)
every other day. All applications stop responding.
We have a bunch of Cocoon applications [mostly 2.0.4] running on JBoss3.0.7.
It is totally unclear which application is causing the problem.

I don't remember that problem happening in our Development or Testing
environment
(where max JavaVM=512MB), but I guess it has a much lighter load.

Is there any known memory problem with Cocoon ?

Is there a way to do memory profiling of Cocoon Apps ? Any particular tool ?
(I have done memory profiling of Java applets with JProbe years ago)

 
Any advice is very appreciated.

Thank you in advance,
 Oleg.

Re: AW: OutOfMemoryError

Posted by Oleg Konovalov <ol...@yahoo.com>.
Christofer, 

Could you please elaborate on "We could have solved this by tweaking the GC settings of the VM..."
I do not think we have an option of switching to BEA Jrockit VM.
We can only use Sun's JavaVM (1.4.2)

Also I found out (from another dev group) that the primary suspect is a new application 
which is not a Cocoon one, but WebWorks.
Any know memory issues for WebWorks apps ?
(I do realize that's a Cocoon mailing list, sorry...  All other apps there are Cocoon ones.)
 
Thank you,
Oleg.

----- Original Message ----
From: Christofer Dutz <du...@c-ware.de>
To: users@cocoon.apache.org; Oleg Konovalov <ol...@yahoo.com>
Sent: Monday, July 10, 2006 3:50:27 AM
Subject: AW: OutOfMemoryError

              Hi Oleg,
     
   we encountered similar problems and fortunately found our that these problems were VM related. I assume you are using a standard Sun JDK installation (This was the case with our system). When looking at the VM memory consumption, we could see an increasing memory consumption. Whenever we manually triggered a “big garbage-collection” most of this was freed again. The problem is that the default Garbage Collection Settings seem to have problems with circular references. Memory, which is not accessible, is not freed because of this. We could have solved this by tweaking the GC settings of the VM, but we got rid of the problems by using the BEA Jrockit VM instead (I knew this would work and I didn’t want to dig into all the switches an leavers of the sun GC) 
     
   Hope this helps.
     
   Regards,
               Christofer
     
   [ c h r i s t o f e r   d u t z ]
     
   IT-Berater
   univativ GmbH & Co. KG
   Robert-Bosch-Str. 7, 64293 Darmstadt
     
   fon: 0 61 51 / 66 717 - 21
   fax: 0 61 51 / 66 717 - 29
   email: christofer.dutz@univativ.de
   http://www.univativ.de
     
   Darmstadt, Stuttgart, Karlsruhe, Düsseldorf
     
     
         
  Von: Oleg Konovalov [mailto:olegkon@yahoo.com] 
 Gesendet: Freitag, 7. Juli 2006 16:07
 An: cocoon list
 Betreff: OutOfMemoryError
   
    
     Hi,
 
 We are getting OutOfMemoryError 
 16:26:41,011 ERROR [STDERR] java.lang.OutOfMemoryError
 in our production server (which has 4GB of RAM, javaVM - max 2GB)
 every other day. All applications stop responding.
 We have a bunch of Cocoon applications [mostly 2.0.4] running on JBoss3.0.7.
 It is totally unclear which application is causing the problem.
 
 I don't remember that problem happening in our Development or Testing environment
 (where max JavaVM=512MB), but I guess it has a much lighter load.
 
 Is there any known memory problem with Cocoon ?
 
 Is there a way to do memory profiling of Cocoon Apps ? Any particular tool ?
 (I have done memory profiling of Java applets with JProbe years ago)
      
 Any advice is very appreciated.
   
  Thank you in advance,
  Oleg.

AW: OutOfMemoryError

Posted by Christofer Dutz <du...@c-ware.de>.
Hi Oleg,

 

we encountered similar problems and fortunately found our that these
problems were VM related. I assume you are using a standard Sun JDK
installation (This was the case with our system). When looking at the VM
memory consumption, we could see an increasing memory consumption. Whenever
we manually triggered a “big garbage-collection” most of this was freed
again. The problem is that the default Garbage Collection Settings seem to
have problems with circular references. Memory, which is not accessible, is
not freed because of this. We could have solved this by tweaking the GC
settings of the VM, but we got rid of the problems by using the BEA Jrockit
VM instead (I knew this would work and I didn’t want to dig into all the
switches an leavers of the sun GC) 

 

Hope this helps.

 

Regards,

            Christofer

 

[ c h r i s t o f e r   d u t z ]

 

IT-Berater

univativ GmbH & Co. KG

Robert-Bosch-Str. 7, 64293 Darmstadt

 

fon: 0 61 51 / 66 717 - 21

fax: 0 61 51 / 66 717 - 29

email: christofer.dutz@univativ.de

http://www.univativ.de

 

Darmstadt, Stuttgart, Karlsruhe, Düsseldorf

 

 

  _____  

Von: Oleg Konovalov [mailto:olegkon@yahoo.com] 
Gesendet: Freitag, 7. Juli 2006 16:07
An: cocoon list
Betreff: OutOfMemoryError

 

Hi,

We are getting OutOfMemoryError 
16:26:41,011 ERROR [STDERR] java.lang.OutOfMemoryError
in our production server (which has 4GB of RAM, javaVM - max 2GB)
every other day. All applications stop responding.
We have a bunch of Cocoon applications [mostly 2.0.4] running on JBoss3.0.7.
It is totally unclear which application is causing the problem.

I don't remember that problem happening in our Development or Testing
environment
(where max JavaVM=512MB), but I guess it has a much lighter load.

Is there any known memory problem with Cocoon ?

Is there a way to do memory profiling of Cocoon Apps ? Any particular tool ?
(I have done memory profiling of Java applets with JProbe years ago)

 
Any advice is very appreciated.

Thank you in advance,
 Oleg.