Re: ParNew promotion failed in verbose GC logs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Vidyadhar, On 4/17/13 2:22 PM, Techienote com wrote: > We are in the plan of upgrading the tomcat with the JVM version. It > is in process but before that we need to stablize it on Tomcat 6 Tomcat is definitely not the problem, here. You can run To

Re: ParNew promotion failed in verbose GC logs

Chris, First of all thanks for the infor. On Wed, Apr 17, 2013 at 11:31 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Vidyadhar, > > On 4/17/13 10:56 AM, Techienote com wrote: > > Chris, > > > > On Wed, Apr 17, 2013 at 1:11 A

Re: ParNew promotion failed in verbose GC logs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Vidyadhar, On 4/17/13 10:56 AM, Techienote com wrote: > Chris, > > On Wed, Apr 17, 2013 at 1:11 AM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > > Vidyadhar, > > On 4/16/13 1:14 PM, Techienote com wrote: With default setti

Re: ParNew promotion failed in verbose GC logs

Chris, On Wed, Apr 17, 2013 at 1:11 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Vidyadhar, > > On 4/16/13 1:14 PM, Techienote com wrote: > > With default setting we were getting frequent OOM errors. After > > analyzing the

Re: ParNew promotion failed in verbose GC logs

On 16 Apr 2013, at 20:42, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Vidyadhar, > > On 4/16/13 1:14 PM, Techienote com wrote: >> With default setting we were getting frequent OOM errors. After >> analyzing the heap dump we found >> org.apache.poi.hssf.userm

Re: ParNew promotion failed in verbose GC logs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Vidyadhar, On 4/16/13 1:14 PM, Techienote com wrote: > With default setting we were getting frequent OOM errors. After > analyzing the heap dump we found > org.apache.poi.hssf.usermodel.HSSFSheet is accumulating more heap > memory. As per the applic

Re: ParNew promotion failed in verbose GC logs

On 16 Apr 2013, at 09:23, Techienote com wrote: > On Tue, Apr 16, 2013 at 12:33 PM, Pïd stèr wrote: > >> On 16 Apr 2013, at 06:35, Techienote com wrote: >> >>> Hi Team, >>> >>> Recently I am seeing concurrent mode failure errors in my Verbose GC >> logs. >>> For the same I have set NewSize to 5

Re: ParNew promotion failed in verbose GC logs

On Tue, Apr 16, 2013 at 3:00 PM, André Warnier wrote: > Techienote com wrote: > >> On Tue, Apr 16, 2013 at 12:33 PM, Pïd stèr wrote: >> >> On 16 Apr 2013, at 06:35, Techienote com >>> wrote: >>> >>> Hi Team, Recently I am seeing concurrent mode failure errors in my Verbose GC >>

Re: ParNew promotion failed in verbose GC logs

On Tue, Apr 16, 2013 at 7:11 AM, David kerber wrote: > On 4/16/2013 5:30 AM, André Warnier wrote: > > > "Premature optimization is the root of all evil" >> http://en.wikiquote.org/wiki/**Donald_Knuth >> > > No doubt; I learned that one long ago. Get it

Re: ParNew promotion failed in verbose GC logs

On 4/16/2013 5:30 AM, André Warnier wrote: ... "Premature optimization is the root of all evil" http://en.wikiquote.org/wiki/Donald_Knuth No doubt; I learned that one long ago. Get it working correctly first, and only then start trying to optimize pieces that aren't working well enough.

Re: ParNew promotion failed in verbose GC logs

Techienote com wrote: On Tue, Apr 16, 2013 at 12:33 PM, Pïd stèr wrote: On 16 Apr 2013, at 06:35, Techienote com wrote: Hi Team, Recently I am seeing concurrent mode failure errors in my Verbose GC logs. For the same I have set NewSize to 512MB, still I am seeing concurrent mode failur

Re: ParNew promotion failed in verbose GC logs

On Tue, Apr 16, 2013 at 12:33 PM, Pïd stèr wrote: > On 16 Apr 2013, at 06:35, Techienote com wrote: > > > Hi Team, > > > > Recently I am seeing concurrent mode failure errors in my Verbose GC > logs. > > For the same I have set NewSize to 512MB, still I am seeing concurrent > mode > > failure in

Re: ParNew promotion failed in verbose GC logs

On 16 Apr 2013, at 06:35, Techienote com wrote: > Hi Team, > > Recently I am seeing concurrent mode failure errors in my Verbose GC logs. > For the same I have set NewSize to 512MB, still I am seeing concurrent mode > failure in the Verbose GC logs Where have you set these JVM attributes and how

ParNew promotion failed in verbose GC logs

Hi Team, Recently I am seeing concurrent mode failure errors in my Verbose GC logs. For the same I have set NewSize to 512MB, still I am seeing concurrent mode failure in the Verbose GC logs 62230.611: [ParNew (promotion failed) Desired survivor size 32768 bytes, new threshold 0 (max 0) : 28481K-