While the thread is not blocked, it still looks suspiciously like http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7130796
On 28.10.2014, at 20:57, Isaac Cohen <[email protected]> wrote: > Attached is a thread dump taken when jenkins was unresponsive. I couldnt find > anything suspicious, but maybe I missed something? > > Thanks, > Isaac > > On Wednesday, October 22, 2014 7:10:43 AM UTC-4, Rupali wrote: > Hi James, > > Thanks for your reply. > We are using Windows server. > I will try jstack as you suggested and will post my findings. > > Thanks, > Rupali > > On Tuesday, October 21, 2014 4:05:31 PM UTC+5:30, James Nord (jnord) wrote: > Are you on Linux and are you using the embedded container? > > If so have you upped the number of file descriptors available from Jenkins – > I have see in the past that is was not uncommon for the HTTP receiving thread > to die due to not being able to handle a connection correctly. > > > Otherwise – jstack will likely be your friend – will show any deadlocks and > show what threads are running. > > > /james > > > From: [email protected] [mailto:[email protected]] On > Behalf Of Rupali Chorghe > Sent: 21 October 2014 04:11 > To: [email protected] > Subject: RE: Jenkins become unresponsive > > > Hi Terrence, > > Thanks for reply. > Problem we are facing is when Jenkins becomes unresponsive, everything that > needs Jenkins URL, becomes inaccessible. So we decided to use Jconsole. But > we didn't find abnormalities in CPU and memory usage when monitored using > jconsole. > > Regards, > Rupali > > On 21-Oct-2014 2:49 am, "Dunnigan, Terrence J" <[email protected]> > wrote: > > Are you using the Jenkins Monitoring plugin? > > > https://wiki.jenkins-ci.org/display/JENKINS/Monitoring > > > It might help to provide some context and additional information when Jenkins > is not responding. > > > Terry > > > From: [email protected] [mailto:[email protected]] On > Behalf Of Rupali > Sent: Monday, October 20, 2014 6:46 AM > To: [email protected] > Subject: Jenkins become unresponsive > > > Hi, > > We are facing one weird issue. > Intermittently, our Jenkins URL becomes inaccessible. Only restarting Jenkins > service resolves the issue. > > We are using Jenkins 1.565. We tried to analyses memory and CPU usage when > such state appears. But CPU usage looked very low around 2% and memory usage > by Jenkins Java process also was around 1.7 GB which is the case usually. We > have Master-Slave setup containing 8 slave machines of which 2 slaves have > dedicated jobs to run. > > Can you advise on how to analyze this issue to find out the root cause of > Jenkins becoming inaccessible? > > Regards, > Rupali > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/FLJye7YDTr8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > <thread_dump_24OCT2014.txt> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
