[JIRA] [core] (JENKINS-23193) UI blocked frequently
Saulo Alvarado Mateos commented on JENKINS-23193 UI blocked frequently Two weeks with Tomcat and without problems detected. The only thing we see is memory usage. Although the garbage collector runs and frees up memory very often, the minimum memory usage increases every day and never come down from that value. There are still 200 MB to peak, and we can further increase the maximum memory available. But are we in front of possible memory leaks? Is it necessary to periodically restart Jenkins to restart the minimum use of memory? However I understand that this is a different problem. Currently we use Tomcat 8 running on JDK 1.7. Max memory = 764 MB, Max PermGen 256 MB. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Daniel Beck resolved JENKINS-23193 as Not A Defect UI blocked frequently Based on discussion in the comments, this seems to be a JDK 6/7 bug on Windows systems, not a Jenkins issue. Regarding the memory issue on Tomcat, consider asking on the jenkinsci-users list for help. Change By: Daniel Beck (21/Jul/14 7:06 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Saulo Alvarado Mateos commented on JENKINS-23193 UI blocked frequently Yes, there are. But not so good news as we will like. After upgrade to the last LTS (1.554.2), problems starts again. With more virulence if it is possible. The same day, our Jenkins stops working suddenly three times. And suddenly works fine for four days long. Then stops again. Currently we are studying to start to work with other application server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Daniel Beck commented on JENKINS-23193 UI blocked frequently Saulo Alvarado Mateos: Any news? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Saulo Alvarado Mateos
commented on JENKINS-23193
UI blocked frequently
There are two exceptions that appears very much in the log, but not necessarily always the UI stops working. In fact both appear (only) when everything seems to work perfectly (both exceptions are associated with UI actions by users):
The first one:
{pre}
04-jun-2014 13:18:35 org.eclipse.jetty.util.log.JavaUtilLog warn
ADVERTENCIA: /ajaxExecutors
org.apache.commons.jelly.JellyTagException: jar:file:/C:/Users/usrJenkins/AppData/Local/Temp/jetty-0.0.0.0-80-jenkins.war--any-/webapp/WEB-INF/lib/instance-identity-1.3.jar!/org/jenkinsci/main/modules/instance_identity/PageDecoratorImpl/httpHeaders.jelly:2:74: st:header finished
at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:25)
at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:63)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:370)
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949)
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Saulo Alvarado Mateos edited a comment on JENKINS-23193 UI blocked frequently There are two exceptions that appears very much in the log, but not necessarily always the UI stops working. In fact both appear (only) when everything seems to work perfectly (both exceptions are associated with UI actions by users): The first one: 04-jun-2014 13:18:35 org.eclipse.jetty.util.log.JavaUtilLog warn ADVERTENCIA: /ajaxExecutors org.apache.commons.jelly.JellyTagException: jar:file:/C:/Users/usrJenkins/AppData/Local/Temp/jetty-0.0.0.0-80-jenkins.war--any-/webapp/WEB-INF/lib/instance-identity-1.3.jar!/org/jenkinsci/main/modules/instance_identity/PageDecoratorImpl/httpHeaders.jelly:2:74: st:header finished at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:25) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:63) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Saulo Alvarado Mateos edited a comment on JENKINS-23193 UI blocked frequently There are two exceptions that appears very much in the log, but not necessarily always the UI stops working. In fact both appear (only) when everything seems to work perfectly (both exceptions are associated with UI actions by users): The first one: 04-jun-2014 13:18:35 org.eclipse.jetty.util.log.JavaUtilLog warn ADVERTENCIA: /ajaxExecutors org.apache.commons.jelly.JellyTagException: jar:file:/C:/Users/usrJenkins/AppData/Local/Temp/jetty-0.0.0.0-80-jenkins.war--any-/webapp/WEB-INF/lib/instance-identity-1.3.jar!/org/jenkinsci/main/modules/instance_identity/PageDecoratorImpl/httpHeaders.jelly:2:74: st:header finished at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:25) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:63) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Daniel Beck commented on JENKINS-23193 UI blocked frequently Could be a Java bug: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7130796 Consider upgrading to Java 8 (which seems to have this Java bug resolved) or using a different container (Jetty is mentioned in the description, so it's possible others do better here). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Saulo Alvarado Mateos commented on JENKINS-23193 UI blocked frequently Yes indeed, we use Jetty. Currently (after two years) we still use Jenkins as out of the box (as a Windows Service that includes Jetty). Yesterday we have decided to schedule an upgrade of the Service to the latest long-term version. After that we will consider the suggestions you make, especially use other container; regardless of whether this particular situation is resolved. Thank you very much for the suggestions and we will continue reporting from the battlefield. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Saulo Alvarado Mateos commented on JENKINS-23193 UI blocked frequently Hi, K.P. Sure, we assumed that was the cause and change it some time ago (in March, if my memory serves me). Currently we use the next configuration in our jenkins.xml config file: executable%BASE%\jre\bin\java/executable arguments-Xrs -XX:PermSize=100m -Xmx768m -Dhudson.slaves.WorkspaceList="_" -Djava.rmi.server.hostname=10.0.100.90 -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port= -Dcom.sun.management.jmxremote.local._only_=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -jar "%BASE%\jenkins.war" --httpPort=80 -Xloggc:D:\Jenkins\loggcjenkins.txt/arguments For four weeks we also add parameters for monitoring Jenkins with jconsole. Assuming that these parameters are correct, we have never seen that used memory exceeds 200 MB of occupation. And PermGem has never exceeded 66 MB of occupation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Daniel Beck commented on JENKINS-23193 UI blocked frequently There should be something relevant in the log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
K P commented on JENKINS-23193 UI blocked frequently Had similar issues in the past. Finally resolved by adding more heap space (if I remember well); just set the appropriate Java startup options in your jenkins.xml (and if it weren't the heap space options, it must have been the PermSize ones) So try increasing the memory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Saulo Alvarado Mateos updated JENKINS-23193 UI blocked frequently Change By: Saulo Alvarado Mateos (26/May/14 3:12 PM) Description: InFebruaryweupdateourJenkinstoversion1.540withautomaticupdatetoolandwereunabletostartagain.Manuallywesteppedbacktoversion1.539weholdsince.Howeversinceweareusingversion1.539wehaveseriousproblemsofblockingofthewebuserinterface.Initiallytheuserinterfacestopstorespondeventuallyonceadayoreverycoupleofdays,andlastedabout30or40minutes;butinrecentweeksthefrequencywithwhichthewebinterfacestopsrespondinghasincreaseddramatically;andthewaitingtimehasbecomeexcessive,exceedingthehourorhourandahalfofwaitingtime,andrequiringinmostcasesforcetheshutdownandrestarttheservicebyhand.ThissituationseemsawkwardtoholdupbecausethenumberofprojectsgrowsweeklyandJenkinshavetomanageit.AndthenumberofdevelopersusingJenkins - ( andwebrequests - ) alsogrows.ThesymptomisthatwhenweaskedanyURLtoJenkinsserver,thebrowserwaitsforeverforthereply.Answerthatneverreceives.Curiously,therestoftheserviceisstillrunning.LookingatthelogoutputinrealtimestillappearactivitystartandcompletionoftaskswhenchangesaredetectedintheSubversionrepository.LookingforsimilarissuesrecordedneartheapproximatedatethatweupdateJenkins,Ifound[https://issues.jenkins-ci.org/browse/JENKINS-21487]and[https://issues.jenkins-ci.org/browse/JENKINS-21487].However,inourcasetheservicecontinuestorunscheduledtasks.Justdonotanswerthewebinterface.Anyideawhatwecando?Ialsouploadadumpofthethreadsthatwererunningthismorningafterwaitinghalfanhourforthewebinterfacetorespond.FinallywehadtomanuallystoptheWindowsserviceandrunitagain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Saulo Alvarado Mateos created JENKINS-23193 UI blocked frequently Issue Type: Bug Assignee: Unassigned Attachments: threaddump-1401097350129.tdump Components: core Created: 26/May/14 3:12 PM Description: In February we update our Jenkins to version 1.540 with automatic update tool and were unable to start again. Manually we stepped back to version 1.539 we hold since. However since we are using version 1.539 we have serious problems of blocking of the web user interface. Initially the user interface stops to respond eventually once a day or every couple of days, and lasted about 30 or 40 minutes; but in recent weeks the frequency with which the web interface stops responding has increased dramatically; and the waiting time has become excessive, exceeding the hour or hour and a half of waiting time, and requiring in most cases force the shutdown and restart the service by hand. This situation seems awkward to hold up because the number of projects grows weekly and Jenkins have to manage it. And the number of developers using Jenkins and web requests also grows. The symptom is that when we asked any URL to Jenkins server, the browser waits forever for the reply. Answer that never receives. Curiously, the rest of the service is still running. Looking at the log output in real time still appear activity start and completion of tasks when changes are detected in the Subversion repository. Looking for similar issues recorded near the approximate date that we update Jenkins, I found https://issues.jenkins-ci.org/browse/JENKINS-21487 and https://issues.jenkins-ci.org/ browse/JENKINS-21487. However, in our case the service continues to run scheduled tasks. Just do not answer the web interface. Any idea what we can do? I also upload a dump of the threads that were running this morning after waiting half an hour for the web interface to respond. Finally we had to manually stop the Windows service and run it again. Environment: Windows Server 2008 R2 Project: Jenkins Priority: Blocker Reporter: Saulo Alvarado Mateos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
