11 messages in org.apache.roller.devRe: JRoller Blows up with Roller 3.1
FromSent OnAttachments
Matthew SchmidtJul 25, 2007 7:23 am 
Anil GangolliJul 25, 2007 8:38 am 
Matthew SchmidtJul 25, 2007 8:40 am 
Matthew SchmidtJul 25, 2007 8:40 am 
Matthew SchmidtJul 25, 2007 8:41 am 
Allen GillilandJul 25, 2007 9:17 am 
DaveJul 25, 2007 9:48 am 
Allen GillilandJul 25, 2007 11:20 am 
henr...@gsa.govJul 25, 2007 12:23 pm 
DaveJul 26, 2007 8:00 am 
henr...@gsa.govJul 26, 2007 8:42 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: JRoller Blows up with Roller 3.1Actions...
From:Matthew Schmidt (ma@dzone.com)
Date:Jul 25, 2007 8:40:12 am
List:org.apache.roller.dev

We have heap dumps both before and after it goes sour. The primarily point to a large increase in strings, with many references to velocity tokens. We didn't really notice any significant change in the traffic when it happened. It happens so fast that the system is quickly non-responsive.

-Matt

Anil Gangolli wrote:

Can you get a heap image at a point when things have gone sour?

Do you have async referrer processing enabled?

If you are capturing access logs, can you see if there is an increase in any bot/crawler activity at the times when the heap grows?

--a.

Matthew Schmidt wrote:

Hi guys. Since our upgrade to Roller 3.1, things have not been good in the land of JRoller. The system will occasionally run for a few hours and then suddenly add nearly a gig of objects to the heap, all of which are instanly pushed to the old gen space and cannot be garbage collected. Restarting the application server does not correct this problem, as it often comes right back immediately. We can see nothing in the access logs that are different from when its running fine and then its suddenly not. The search is currenly disabled, so that's not causing it. The referer processing is also disabled and our caches in Roller are not too large. We've upgraded both Velocity and Hibernate to their latest released versions and that had no effect. Looking into the heap dump, it seems that most of the space is in Strings, probably related to Velocity. We've disabled velocity caching completely right now so see if that is the cause. Has anyone else seen anything like this? We're running in a 1.5G heap and it just runs normally for a while then flakes out and then won't even operate normally after a restart for a while. Eventually, enough restarts get is back into regular operation. I'd appreciate any help you guys can give as without something, JRoller will likely plunge even further into dispair.

Thanks, Matt