With those settings, jvm still crashes. Maybe I should try with Tomcat? I am still sure it's a memory thing, since I have 2gb of ram on openvz and no swap. Any other suggestions?
On Fri, Feb 24, 2012 at 10:06 PM, Jeff <predato...@gmail.com> wrote: > My experience with Jenkins, Archiva and SONAR web applications is that the > default JVM settings regarding memory allocation and PermGen sizes are not > sufficient. I experienced weird hanging/nonresponsive issues at various > times where there were no errors/exceptions, but things just stopped > responding. This was on Windows running Tomcat as a service. > > My Windows VM's are configured with 4 GB memory and have set the JVM > settings as: > > -Xmx2048m > -Xms512m > -XX:MaxPermSize=256m > -XX:+CMSClassUnloadingEnabled > -XX:+UseConcMarkSweepGC > > The PermGen size was one of the bigger helps. I actually caught an error > in the logs that referenced an issue with PermGen space when trying to shut > down tomcat in one of my attempts to find the cause. These settings have > performed well so far for all three web applications I'm running. Maybe > this will help. > > On Fri, Feb 24, 2012 at 1:01 PM, Domen Kožar <do...@dev.si> wrote: > >> It is a bare debian 6 with jenkins installed. Is there any reason jenkins >> would recieve signal 15? I guess it's time to dig into Linux and find out a >> way where the signal is coming from. >> >> On Fri, Feb 24, 2012 at 7:59 PM, Mark Waite <markwa...@yahoo.com> wrote: >> >>> I'm a little surprised at that message. When I stop the Jenkins process >>> with "kill" (which defaults to sending SIGTERM), I think it reports killing >>> a process named "java", not a process named "jenkins". >>> >>> Is it possible that you have another program named jenkins which is >>> being started (and killed) instead of "java -jar jenkins.war"? >>> >>> Mark Waite >>> >>> *From:* Richard Mortimer <ri...@oldelvet.org.uk> >>> *To:* Domen Kožar <do...@dev.si> >>> *Cc:* jenkinsci-users@googlegroups.com >>> *Sent:* Friday, February 24, 2012 11:26 AM >>> *Subject:* Re: Jenkins (JVM) crashes after few minutes after start >>> >>> >>> On 24/02/2012 16:54, Domen Kožar wrote: >>> > That's the issue, java just exists, no stacktrace, even if ran in >>> > non-daemon mode. >>> > >>> From you serverfault page it shows syslog output of >>> >>> "Jan 31 17:50:02 cherry jenkins: jenkins: fatal: client (pid 16189) >>> killed by signal 15, exiting" >>> >>> That says that jenkins received signal 15 (SIGTERM in most universes). >>> Now it is possible that jenkins sent itself that but unlikely. >>> >>> Can you check for cron jobs that might be sending signals. If there is >>> nothing obvious you might want to look at the timing of jenkins >>> terminating. That might give some pattern to allow you to identify a >>> specific job killing things. >>> >>> Richard >>> >>> >>> > On Fri, Feb 24, 2012 at 5:51 PM, Didier Durand < >>> durand.did...@gmail.com >>> > <mailto:durand.did...@gmail.com>> wrote: >>> > >>> > Hi, >>> > >>> > Do you have the Java stack trace of the crash? >>> > >>> > regards >>> > >>> > didier >>> > >>> > On Feb 24, 4:04 pm, Domen Kožar <do...@dev.si <mailto:do...@dev.si >>> >> >>> > wrote: >>> > > I have been fighting with this one for a month, would be really >>> > > pleased if someone can give tips or request more data: >>> > > >>> > > >>> > Crosspost: >>> http://serverfault.com/questions/355516/jenkins-jvm-crashes-after-few... >>> > >>> > >>> >>> >>> >> > > > -- > Jeff Vincent > predato...@gmail.com > See my LinkedIn profile at: > http://www.linkedin.com/in/rjeffreyvincent > I ♥ DropBox <http://db.tt/9O6LfBX> !! > >
