[JIRA] [gerrit-trigger-plugin] (JENKINS-27741) Jenkins fails to receive gerrit notifications spontaneously and on restart.
Sam Xiao commented on JENKINS-27741 Jenkins fails to receive gerrit notifications spontaneously and on restart. +1 was seeing it multiple times, and was force to reboot the system 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] [android-emulator-plugin] (JENKINS-25322) EnvInject channel is already closed when used with ec2 autoscaling plugin
Sam Xiao commented on JENKINS-25322 EnvInject channel is already closed when used with ec2 autoscaling plugin Is there any update on this? 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] [envinject-plugin] (JENKINS-25683) EnvInjectException: hudson.remoting.ChannelClosedException: channel is already closed
Sam Xiao created JENKINS-25683 EnvInjectException: hudson.remoting.ChannelClosedException: channel is already closed Issue Type: Bug Assignee: Gregory Boissinot Components: envinject-plugin Created: 19/Nov/14 8:12 AM Description: 2014-11-14 12:41:02 [EnvInject] - Loading node environment variables. 2014-11-14 12:41:02 ERROR: SEVERE ERROR occurs 2014-11-14 12:41:02 org.jenkinsci.lib.envinject.EnvInjectException: hudson.remoting.ChannelClosedException: channel is already closed 2014-11-14 12:41:02 at org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:75) 2014-11-14 12:41:02 at org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:81) 2014-11-14 12:41:02 at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:39) 2014-11-14 12:41:02 at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:581) 2014-11-14 12:41:02 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:487) 2014-11-14 12:41:02 at hudson.model.Run.execute(Run.java:1706) 2014-11-14 12:41:02 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 2014-11-14 12:41:02 at hudson.model.ResourceController.execute(ResourceController.java:88) 2014-11-14 12:41:02 at hudson.model.Executor.run(Executor.java:232) 2014-11-14 12:41:02 Caused by: hudson.remoting.ChannelClosedException: channel is already closed 2014-11-14 12:41:02 at hudson.remoting.Channel.send(Channel.java:540) 2014-11-14 12:41:02 at hudson.remoting.Request.call(Request.java:129) 2014-11-14 12:41:02 at hudson.remoting.Channel.call(Channel.java:742) 2014-11-14 12:41:02 at hudson.FilePath.act(FilePath.java:1009) 2014-11-14 12:41:02 at org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:44) 2014-11-14 12:41:02 ... 8 more 2014-11-14 12:41:02 Caused by: java.io.IOException 2014-11-14 12:41:02 at hudson.remoting.Channel.close(Channel.java:1030) 2014-11-14 12:41:02 at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110) 2014-11-14 12:41:02 at hudson.remoting.PingThread.ping(PingThread.java:120) 2014-11-14 12:41:02 at hudson.remoting.PingThread.run(PingThread.java:81) 2014-11-14 12:41:02 Caused by: java.util.concurrent.TimeoutException: Ping started on 1415995733541 hasn't completed at 1415995973541 Project: Jenkins Priority: Critical Reporter: Sam Xiao 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-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Sam Xiao
reopened JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Change By:
Sam Xiao
(12/Nov/14 9:39 PM)
Resolution:
Fixed
Status:
Resolved
Reopened
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-20892) /{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Sam Xiao
updated JENKINS-20892
/{view,computer,user}/*/builds /job/*/buildTimeTrend block HTTP response on build record loading
Can we port this back to LTS?
Change By:
Sam Xiao
(12/Nov/14 9:39 PM)
Labels:
1.532.3-fixedlazy-loading
lts-candidate
performance
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-22648) SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Sam Xiao edited a comment on JENKINS-22648 SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput still reproducible on 1.565.3 Oct 29, 2014 2:54:45 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.565.3.jar!/lib/layout/layout.jelly:75:72: st:include failed to deflate: error=-2 avail_out=512 at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:636) at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:27) 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 org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.565.3.jar!/lib/layout/layout.jelly:75:72: st:include failed to deflate: error=-2 avail_out=512 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.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
[JIRA] [core] (JENKINS-22648) SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Sam Xiao
updated JENKINS-22648
SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Change By:
Sam Xiao
(29/Oct/14 10:04 PM)
Description:
Afterupgradedto1.532.2LTS,startseeingthiserror{noformat}Apr16,20142:54:40PMwinstone.LoggerlogInternalSEVERE:Errorintheerrorservletjavax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.3.jar!/lib/layout/layout.jelly:143:68:st:includeCouldnotwritetoXMLOutput atorg.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:45) atwinstone.ServletConfiguration.execute(ServletConfiguration.java:248) atwinstone.RequestDispatcher.include(RequestDispatcher.java:199) atwinstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:251) atwinstone.RequestHandlerThread.run(RequestHandlerThread.java:150) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask.run(FutureTask.java:262) atwinstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:744)Causedby:org.apache.commons.jelly.JellyTagException:jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.3.jar!/lib/layout/layout.jelly:143:68:st:includeCouldnotwritetoXMLOutput atorg.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:72) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) atorg.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) atorg.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) atorg.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) atorg.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) ...22moreCausedby:org.xml.sax.SAXException:Failedtowritetoclientwinstone.ClientSocketException:Failedtowritetoclient atorg.dom4j.io.XMLWriter.handleException(XMLWriter.java:1888) atorg.dom4j.io.XMLWriter.characters(XMLWriter.java:791)
[JIRA] [ec2] (JENKINS-25029) Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID.NotFound; Request ID: abcdef)
Sam Xiao
created JENKINS-25029
Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID.NotFound; Request ID: abcdef)
Issue Type:
Bug
Assignee:
Francis Upton
Components:
ec2
Created:
07/Oct/14 7:39 PM
Description:
Oct 07, 2014 11:41:27 AM hudson.plugins.ec2.EC2Cloud addProvisionedSlave
INFO: Provisioning for AMI ami-abcda06b; Estimated number of total slaves: 241; Estimated number of slaves for ami ami-abcda06b: 30
Launching ami-abcda06b for template aws builder
Oct 07, 2014 11:41:27 AM hudson.plugins.ec2.SlaveTemplate provisionOndemand
INFO: Launching ami-abcda06b for template aws builder
Looking for existing instances with describe-instance: {InstanceIds: [],Filters: [{Name: image-id,Values: [ami-abcda06b]}, {Name: availability-zone,Values: [us-east-1a]}, {Name: subnet-id,Values: [subnet-1a2bce59]}, {Name: instance.group-id,Values: [sg-e9bb378c, sg-1237d80c]}, {Name: key-name,Values: [jenkins-builder]}, {Name: instance-type,Values: [m3.large]}, {Name: tag:Name,Values: [jenkins-builder.elastic]}, {Name: tag:created_by,Values: [ci.corp.mydomain.com]}, {Name: tag:Service,Values: [jenkins]}, {Name: tag:Team,Values: [releng]}, {Name: tag:Stage,Values: [prod]}, {Name: instance-state-name,Values: [stopped, stopping]}],}
Oct 07, 2014 11:41:28 AM hudson.plugins.ec2.EC2Cloud addProvisionedSlave
INFO: Provisioning for AMI ami-abcda06b; Estimated number of total slaves: 242; Estimated number of slaves for ami ami-abcda06b: 31
Launching ami-abcda06b for template aws builder
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:14.0
Oct 07, 2014 11:41:28 AM hudson.plugins.ec2.SlaveTemplate provisionOndemand
INFO: Launching ami-abcda06b for template aws builder
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:13.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:12.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:11.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:10.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:9.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:8.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:7.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:6.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:5.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:4.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:3.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started provisioning aws builder (ami-abcda06b) from ec2-us-east-1 with 1 executors. Remaining excess workload:2.0
Oct 07, 2014 11:41:28 AM hudson.slaves.NodeProvisioner update
INFO: Started
[JIRA] [ec2] (JENKINS-25029) Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID.NotFound; Request ID: abcdef)
Sam Xiao updated JENKINS-25029 Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID.NotFound; Request ID: abcdef) Change By: Sam Xiao (07/Oct/14 7:43 PM) Description:
[JIRA] [ec2] (JENKINS-25029) Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID.NotFound; Request ID: abcdef)
Sam Xiao updated JENKINS-25029 Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID.NotFound; Request ID: abcdef) Change By: Sam Xiao (07/Oct/14 7:43 PM) Description:
[JIRA] [naginator] (JENKINS-22459) NullPointerException in NaginatorActionFactory caused by empty Managed windows batch build step
Sam Xiao commented on JENKINS-22459 NullPointerException in NaginatorActionFactory caused by empty Managed windows batch build step +1 same bug on 1.565.1 LTS 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] [cli] (JENKINS-20400) jenkins-cli.jar have issues with commands
Sam Xiao commented on JENKINS-20400 jenkins-cli.jar have issues with commands +1 I can reproduce it at latest LTS 1.565.2, please fix! 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] [ec2] (JENKINS-23935) Allow tags for all instances in an EC2 cloud configuration
Sam Xiao commented on JENKINS-23935 Allow tags for all instances in an EC2 cloud configuration +1 nice feature! 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] [ec2] (JENKINS-24691) importing own private/pub to AWS ec2 doesn't work
Sam Xiao created JENKINS-24691 importing own private/pub to AWS ec2 doesnt work Issue Type: Bug Assignee: Francis Upton Components: ec2 Created: 12/Sep/14 8:08 PM Description: Hello, I'm on Jenkins LTS v1.565.2 + ec2 plugin v1.24 I already have my own key pair as we now are trying migrate to using ec2 plugin for autoscaling, so I import my own keypairs on AWS EC2 console, but now supplying the same private key to ec2 plugin don't seem to work. I do see an ec2 instance is created and running, just can't get Jenkins ssh into that slave. Node aws builder (i-83605288)(i-83605288) is still stopping, waiting 5s Node aws builder (i-83605288)(i-83605288) is still stopping, waiting 5s Node aws builder (i-83605288)(i-83605288) is still stopping, waiting 5s Node aws builder (i-83605288)(i-83605288) is ready Connecting to ip-1-2-3-4.us-west-2.compute.internal on port 22, with timeout 1. Waiting for SSH to come up. Sleeping 5. Connecting to ip-1-2-3-4.us-west-2.compute.internal on port 22, with timeout 1. Connected via SSH. bootstrap() Getting keypair... Using key: jenkins-builder 0f:64:0d:18:40:d3:f0:04:45:de:84:ab:39:20:7f:42 -BEGIN RSA PRIVATE KEY- MIIEoQIBAAKCAQEAzEibczy885OzrUb4DCsPueOSok1uUgSAMPLEabcdefgehef UzGGq+6qVCSHtGpjJXlK+DFDBADFEWRX+W7CifKEspRasZsC3hhHC3BnCbH7fuB Authenticating as 4g ruby dummy dummy2 aws m3.medium Authentication failed. Trying again... Authenticating as 4g ruby dummy dummy2 aws m3.medium Authentication failed. Trying again... Authenticating as 4g ruby dummy dummy2 aws m3.medium Authentication failed. Trying again... Authenticating as 4g ruby dummy dummy2 aws m3.medium Authentication failed. Trying again... Authenticating as 4g ruby dummy dummy2 aws m3.medium Authentication failed. Trying again... Authenticating as 4g ruby dummy dummy2 aws m3.medium ERROR: Publickey authentication failed. java.io.IOException: Publickey authentication failed. at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:315) at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:467) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:194) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launch(EC2UnixLauncher.java:82) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:101) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: The connection is closed. at com.trilead.ssh2.auth.AuthenticationManager.deQueue(AuthenticationManager.java:63) at com.trilead.ssh2.auth.AuthenticationManager.getNextMessage(AuthenticationManager.java:86) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:290) ... 10 more Caused by: java.io.IOException: Peer sent DISCONNECT message (reason code 2): Too many authentication failures for 4g ruby dummy dummy2 aws m3.medium at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:755) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:480) ... 1 more Project: Jenkins Priority: Major Reporter: Sam Xiao This message is automatically generated by JIRA.
[JIRA] [core] (JENKINS-20612) Hitting /api/json endpoint returns JSON + some malformed HTML content
Sam Xiao commented on JENKINS-20612 Hitting /api/json endpoint returns JSON + some malformed HTML content This is a bad assessment, if it is related to permission issue, why not report the actual error instead of some broken HTML text with no obvious clue to interact from a restful endpoint ?? 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] [envinject] (JENKINS-23905) Jenkins Slaves launched with the incorrect environment variables
Sam Xiao commented on JENKINS-23905 Jenkins Slaves launched with the incorrect environment variables +1 We had the same issue on 1.89. 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] [artifactdeployer] (JENKINS-24140) ArtifactDeployer migration breaks lazy-load on Jenkins initialization
Sam Xiao commented on JENKINS-24140 ArtifactDeployer migration breaks lazy-load on Jenkins initialization This is a total blocker for us. Thread 3092: (state = IN_NATIVE) - java.io.FileInputStream.readBytes(byte[], int, int) @bci=0 (Compiled frame; information may be imprecise) - java.io.FileInputStream.read(byte[], int, int) @bci=16, line=272 (Compiled frame) - sun.nio.cs.StreamDecoder.readBytes() @bci=135, line=283 (Compiled frame) - sun.nio.cs.StreamDecoder.implRead(char[], int, int) @bci=112, line=325 (Compiled frame) - sun.nio.cs.StreamDecoder.read(char[], int, int) @bci=180, line=177 (Compiled frame) - java.io.InputStreamReader.read(char[], int, int) @bci=7, line=184 (Compiled frame) - java.io.BufferedReader.fill() @bci=145, line=154 (Compiled frame) - java.io.BufferedReader.readLine(boolean) @bci=44, line=317 (Compiled frame) - java.io.BufferedReader.readLine() @bci=2, line=382 (Compiled frame) - org.jenkinsci.lib.envinject.service.EnvInjectSavable.fromTxt(java.io.FileReader, java.util.Map) @bci=10, line=75 (Compiled frame) - org.jenkinsci.lib.envinject.service.EnvInjectSavable.getEnvironment(java.io.File) @bci=85, line=33 (Compiled frame) - org.jenkinsci.lib.envinject.EnvInjectAction.getEnvironment(hudson.model.AbstractBuild) @bci=30, line=107 (Compiled frame) - org.jenkinsci.lib.envinject.EnvInjectAction.readResolve() @bci=31, line=122 (Compiled frame) - sun.reflect.GeneratedMethodAccessor60.invoke(java.lang.Object, java.lang.Object[]) @bci=36 (Compiled frame) - sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) @bci=6, line=43 (Compiled frame) - java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[]) @bci=57, line=606 (Compiled frame) - com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(java.lang.Object) @bci=28, line=66 (Compiled frame) - hudson.util.RobustReflectionConverter.unmarshal(com.thoughtworks.xstream.io.HierarchicalStreamReader, com.thoughtworks.xstream.converters.UnmarshallingContext) @bci=20, line=229 (Compiled frame) - com.thoughtworks.xstream.core.TreeUnmarshaller.convert(java.lang.Object, java.lang.Class, com.thoughtworks.xstream.converters.Converter) @bci=15, line=72 (Compiled frame) - com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(java.lang.Object, java.lang.Class, com.thoughtworks.xstream.converters.Converter) @bci=175, line=65 (Compiled frame) - com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(java.lang.Object, java.lang.Class, com.thoughtworks.xstream.converters.Converter) @bci=82, line=66 (Compiled frame) - com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(java.lang.Object, java.lang.Class) @bci=4, line=50 (Compiled frame) - com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(com.thoughtworks.xstream.io.HierarchicalStreamReader, com.thoughtworks.xstream.converters.UnmarshallingContext, java.lang.Object) @bci=14, line=71 (Compiled frame) - hudson.util.RobustCollectionConverter.populateCollection(com.thoughtworks.xstream.io.HierarchicalStreamReader, com.thoughtworks.xstream.converters.UnmarshallingContext, java.util.Collection) @bci=19, line=83 (Compiled frame) - com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(com.thoughtworks.xstream.io.HierarchicalStreamReader, com.thoughtworks.xstream.converters.UnmarshallingContext) @bci=18, line=80 (Compiled frame) - hudson.util.RobustCollectionConverter.unmarshal(com.thoughtworks.xstream.io.HierarchicalStreamReader, com.thoughtworks.xstream.converters.UnmarshallingContext) @bci=35, line=74 (Interpreted frame) - com.thoughtworks.xstream.core.TreeUnmarshaller.convert(java.lang.Object, java.lang.Class, com.thoughtworks.xstream.converters.Converter) @bci=15, line=72 (Compiled frame) - com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(java.lang.Object, java.lang.Class, com.thoughtworks.xstream.converters.Converter) @bci=175, line=65 (Compiled frame) - com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(java.lang.Object, java.lang.Class, com.thoughtworks.xstream.converters.Converter) @bci=82, line=66 (Compiled frame) - hudson.util.RobustReflectionConverter.unmarshalField(com.thoughtworks.xstream.converters.UnmarshallingContext, java.lang.Object, java.lang.Class, java.lang.reflect.Field) @bci=26, line=349 (Compiled frame) - hudson.util.RobustReflectionConverter.doUnmarshal(java.lang.Object,
[JIRA] [core] (JENKINS-22648) SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Sam Xiao reopened JENKINS-22648 SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput I think I can still reproduce this on Jenkins ver. 1.554.3 Sorry, I'm on LTS, and will probably never use the newest Jenkins version to verify this. Change By: Sam Xiao (12/Aug/14 12:29 AM) Resolution: Incomplete Status: Resolved Reopened 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] [slave-setup] (JENKINS-24107) Expose $NODE_NAME as part of the slave setup to help itself to be self-identifiable
Sam Xiao created JENKINS-24107 Expose $NODE_NAME as part of the slave setup to help itself to be self-identifiable Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 04/Aug/14 10:18 PM Description: It would be very beneficial for each Jenkins node to be self-identifiable, during the setup init() step. The reason is because we also want to run some maintenance/init task before the node can be considered to be added onto Jenkins. So as part of the "connecting/reconnecting" step, it is important for the node to be self-identify and know who is who without running any job to obtain the $NODE_NAME. Project: Jenkins Priority: Major Reporter: Sam Xiao 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-24052) REST API for manipulating collection of labels assigned on a node
Sam Xiao commented on JENKINS-24052 REST API for manipulating collection of labels assigned on a node If this can be made as applying for all exposed API, then I'm happy to close the related ticket JENKINS-24054 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-24054) REST API endpoint should have consistent prefix
Sam Xiao commented on JENKINS-24054 REST API endpoint should have consistent prefix I'm happy to have this closed if related ticket JENKINS-24052 can be work on for all exposed API. And have all the exposed API properly documented. When that's not available, I believe we are left with this option of using undocumented API calls. 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-24054) REST API endpoint should have consistent prefix
Sam Xiao commented on JENKINS-24054 REST API endpoint should have consistent prefix It is probably never advertised, but it's there and it works! (yeah i know, it needs to be better documented.) 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] [discard-old-build] (JENKINS-24072) Should allow to set global defaults retention policy for all jobs
Sam Xiao created JENKINS-24072 Should allow to set global defaults retention policy for all jobs Issue Type: New Feature Assignee: nkns165 Components: discard-old-build Created: 31/Jul/14 9:26 PM Description: Although this is a very nice plugin, but it would be nice if this setting can take 1 step further into the global default settings, so if we have 1000 jobs, we don't have to manually set it for 1000 jobs for each job on the retention policy Project: Jenkins Priority: Major Reporter: Sam Xiao 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-24054) REST API endpoint should have consistent prefix
Sam Xiao created JENKINS-24054 REST API endpoint should have consistent prefix Issue Type: Improvement Assignee: Unassigned Components: core Created: 30/Jul/14 11:23 PM Description: the endpoint prefix is sometimes inconsistent even when we deal with the same class/object for example, the /computer object. To get the information on /computer, you normally invoke the restful call like this: https://jenkins.mydomain.com/computer/foobar/api/json To take it offline https://jenkins.mydomain.com/computer/foobar/toggleOffline?offlineMessage="taking it disconnected via jenkins.go as part of the maintenance" But when we are talking about writing restful api lib for Jenkins and the endpoint inconsistency is making developers writing case-by-case basis. And could very well end up with something broken without printing verbose message in the log: https://jenkins.mydomain.com/computer/foobar/toggleOffline?offlineMessage="taking it disconnected via jenkins.go as part of the maintenance"/api/json Project: Jenkins Priority: Major Reporter: Sam Xiao 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-24026) Exposing Labels via the JSON API endpoint via GET/POST
Sam Xiao created JENKINS-24026 Exposing Labels via the JSON API endpoint via GET/POST Issue Type: New Feature Assignee: Unassigned Components: core Created: 30/Jul/14 12:18 AM Description: It would be nice to expose it via a /api/json and we can post/get to change the labels programmatically. This is lot clearer approach than manipulating `config.xml` https://jenkins.mydomain.com/computer/node01/api/json?depth=1 Project: Jenkins Priority: Major Reporter: Sam Xiao 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] [www] (JENKINS-10649) remote api node action: get/set labels
Sam Xiao commented on JENKINS-10649 remote api node action: get/set labels +1 May I know why this important feature is still not implemented? Thanks, Sam. 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] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Sam Xiao commented on JENKINS-20492 Re-Execute promotion button is gone +1 with Scott Roberts What does it even mean by "Badge"?? 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-22648) SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput
Sam Xiao created JENKINS-22648 SEVERE: Error in the error servlet /lib/layout/layout.jelly Could not write to XMLOutput Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Apr/14 10:04 PM Description: After upgraded to 1.532.2 LTS, start seeing this error Apr 16, 2014 2:54:40 PM winstone.Logger logInternal SEVERE: Error in the error servlet javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.3.jar!/lib/layout/layout.jelly:143:68: st:include Could not write to XMLOutput at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) 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 org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.include(RequestDispatcher.java:199) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:251) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.3.jar!/lib/layout/layout.jelly:143:68: st:include Could not write to XMLOutput at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:72) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.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.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) 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
[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Sam Xiao commented on JENKINS-22334 plugin thinks emulator always crashes using sdk 22.6.1 This becomes a blocker for us, can someone quickly review this and merge it? 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] [monitoring] (JENKINS-14750) Unprivileged view permissions for monitoring
Sam Xiao commented on JENKINS-14750 Unprivileged view permissions for monitoring +1 for this feature 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] [android-emulator] (JENKINS-21319) Provide retry option to Android-emulator plugin when the emulator fails to boot
Sam Xiao commented on JENKINS-21319 Provide retry option to Android-emulator plugin when the emulator fails to boot +1 for this feature 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] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Sam Xiao commented on JENKINS-22334 plugin thinks emulator always crashes using sdk 22.6.1 Is JENKINS-22555 related to this? We didn't use Gradle yet, but it seems like very much similar issue. Our tests are start failing since we upgraded our SDK to 22.6.1 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] [android-emulator] (JENKINS-22555) android.util.AndroidException: Can't connect to activity manager; is the system running?
Sam Xiao
updated JENKINS-22555
android.util.AndroidException: Cant connect to activity manager; is the system running?
Change By:
Sam Xiao
(10/Apr/14 9:27 PM)
Description:
Startseeingsomeweirdrandomfailureafterupgradedto22.6.2AndroidSDK.
Idontthink`getpropdev.bootcomplete`(https://github.com/jenkinsci/android-emulator-plugin/search?q=%22dev.bootcomplete%22ref=cmdform)worksanymorewiththenewSDKtodeterminetheandroiddeviceisbootfinishedornot.
Shouldweusethis`adbshellgetpropinit.svc.bootanim`?http://stackoverflow.com/questions/3634041/detect-when-android-emulator-is-fully-booted
{noformat}2014-04-0911:43:022093KB/s(2968898bytesin1.384s)2014-04-0911:43:04Error:CouldnotaccessthePackageManager.Isthesystemrunning?2014-04-0911:43:04=success!2014-04-0911:43:04$adblogcat-c2014-04-0911:43:04=success!2014-04-0911:43:04$adbshellaminstrument-w-elookout.packagecom.lookout-elookout.notAnnotationcom.lookout.annotations.ExcludeFromDefault,-elookout.stride3-elookout.initial0-elookout.annotationcom.lookout.annotations.UnitTestcom.lookout.tests/com.lookout.LookoutInstrumentationTestRunner2014-04-0911:43:06Errortype22014-04-0911:43:06android.util.AndroidException:Cantconnecttoactivitymanager;isthesystemrunning?2014-04-0911:43:06=success!2014-04-0911:43:06$echotestsuites/testsuitestest-report.xml;adbpull/data/data/com.lookout/app_test_report/test-report.xmltest-report.xml2014-04-0911:43:06remoteobject/data/data/com.lookout/app_test_report/test-report.xmldoesnotexist2014-04-0911:43:06=failure:#Process::Status:pid=30984,exited(1)2014-04-0911:43:06CouldnotfetchJUnittestreportfromdevice/emulator.Outputtingemptytestreport{noformat}
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] [android-emulator] (JENKINS-22555) android.util.AndroidException: Can't connect to activity manager; is the system running?
Sam Xiao
updated JENKINS-22555
android.util.AndroidException: Cant connect to activity manager; is the system running?
Change By:
Sam Xiao
(10/Apr/14 9:31 PM)
Description:
Startseeingsomeweirdrandomfailureafterupgradedto22.6.2AndroidSDK.Idontthink`getpropdev.bootcomplete`(https://github.com/jenkinsci/android-emulator-plugin/search?q=%22dev.bootcomplete%22ref=cmdform)worksanymorewiththenewSDKtodeterminetheandroiddeviceisbootfinishedornot.Shouldweusethis`adbshellgetpropinit.svc.bootanim`?http://stackoverflow.com/questions/3634041/detect-when-android-emulator-is-fully-booted{noformat}2014-04-0911:43:022093KB/s(2968898bytesin1.384s)2014-04-0911:43:04Error:CouldnotaccessthePackageManager.Isthesystemrunning?2014-04-0911:43:04=success!2014-04-0911:43:04$adblogcat-c2014-04-0911:43:04=success!2014-04-0911:43:04$adbshellaminstrument-w-e
lookout
abc
.packagecom.
lookout
abc
-e
lookout
abc
.notAnnotationcom.
lookout
abc
.annotations.ExcludeFromDefault,-e
lookout
abc
.stride3-e
lookout
abc
.initial0-e
lookout
abc
.annotationcom.
lookout
abc
.annotations.UnitTestcom.
lookout
abc
.tests/com.
lookout
abc
.
LookoutInstrumentationTestRunner
AbcInstrumentationTestRunner
2014-04-0911:43:06Errortype22014-04-0911:43:06android.util.AndroidException:Cantconnecttoactivitymanager;isthesystemrunning?2014-04-0911:43:06=success!2014-04-0911:43:06$echotestsuites/testsuitestest-report.xml;adbpull/data/data/com.
lookout
abc
/app_test_report/test-report.xmltest-report.xml2014-04-0911:43:06remoteobject/data/data/com.
lookout
abc
/app_test_report/test-report.xmldoesnotexist2014-04-0911:43:06=failure:#Process::Status:pid=30984,exited(1)2014-04-0911:43:06CouldnotfetchJUnittestreportfromdevice/emulator.Outputtingemptytestreport{noformat}
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] [android-emulator] (JENKINS-22555) android.util.AndroidException: Can't connect to activity manager; is the system running?
Sam Xiao created JENKINS-22555 android.util.AndroidException: Cant connect to activity manager; is the system running? Issue Type: Bug Assignee: Unassigned Components: android-emulator Created: 09/Apr/14 9:26 PM Description: Start seeing some weird random failure after upgraded to 22.6.2 Android SDK. 2014-04-09 11:43:02 2093 KB/s (2968898 bytes in 1.384s) 2014-04-09 11:43:04 Error: Could not access the Package Manager. Is the system running? 2014-04-09 11:43:04 = success! 2014-04-09 11:43:04 $ adb logcat -c 2014-04-09 11:43:04 = success! 2014-04-09 11:43:04 $ adb shell am instrument -w -e lookout.package com.lookout -e lookout.notAnnotation com.lookout.annotations.ExcludeFromDefault, -e lookout.stride 3 -e lookout.initial 0 -e lookout.annotation com.lookout.annotations.UnitTest com.lookout.tests/com.lookout.LookoutInstrumentationTestRunner 2014-04-09 11:43:06 Error type 2 2014-04-09 11:43:06 android.util.AndroidException: Can't connect to activity manager; is the system running? 2014-04-09 11:43:06 = success! 2014-04-09 11:43:06 $ echo 'testsuites/testsuites' test-report.xml; adb pull /data/data/com.lookout/app_test_report/test-report.xml test-report.xml 2014-04-09 11:43:06 remote object '/data/data/com.lookout/app_test_report/test-report.xml' does not exist 2014-04-09 11:43:06 = failure: #Process::Status: pid=30984,exited(1) 2014-04-09 11:43:06 Could not fetch JUnit test report from device/emulator. Outputting empty test report Environment: Updated to Android SDK Release 22.6.2 Ubuntu 12.04 Jenkins LTS: Jenkins ver. 1.532.2 Android Emulator Plugin: 2.10 Project: Jenkins Priority: Major Reporter: Sam Xiao 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] [android-emulator] (JENKINS-22555) android.util.AndroidException: Can't connect to activity manager; is the system running?
Sam Xiao updated JENKINS-22555 android.util.AndroidException: Cant connect to activity manager; is the system running? Change By: Sam Xiao (09/Apr/14 9:30 PM) Priority: Major Critical 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] [monitoring] (JENKINS-22475) Add an option to allow Monitor Plugin to be display without having 'admin' account login
Sam Xiao commented on JENKINS-22475 Add an option to allow Monitor Plugin to be display without having admin account login We used similar refresher extension on Chrome to do this: https://chrome.google.com/webstore/detail/refresher/gpnlhhinnkacdmalpmkcaijdododlooa?hl=en We want to turn off the security only for read-only and this monitoring plugin, don't think it's a good idea to do that for all plugin-authentication Any other workaround for this? 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] [monitoring] (JENKINS-22475) Add an option to allow Monitor Plugin to be display without having 'admin' account login
Sam Xiao created JENKINS-22475 Add an option to allow Monitor Plugin to be display without having admin account login Issue Type: New Feature Assignee: Unassigned Components: monitoring Created: 02/Apr/14 8:04 PM Description: We used Monitoring plugin as a wall display for our Jenkins master node status, but often time Jenkins have a session timeout and it logout our 'admin' user and Monitoring plugin becomes useless. Is there a way to add an option to allow anonymous user to check the monitoring status , and used primarily for wall display. Project: Jenkins Priority: Major Reporter: Sam Xiao 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-20769) Failed to execute command Pipe.EOF
Sam Xiao commented on JENKINS-20769 Failed to execute command Pipe.EOF It happens to me as well: Jenkins ver. 1.532.2 Ubuntu 12.04 SEVERE: Failed to execute command Pipe.EOF(165) (channel bob-10.69) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Mar 26, 2014 1:04:48 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(165) created at at hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at hudson.remoting.ProxyWriter$EOF.init(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101) at java.lang.ref.Finalizer.access$100(Finalizer.java:32) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190) Mar 26, 2014 1:04:48 PM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.EOF(386) (channel bob-10.16) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Mar 26, 2014 1:04:48 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(386) created at at hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at hudson.remoting.ProxyWriter$EOF.init(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101) at java.lang.ref.Finalizer.access$100(Finalizer.java:32) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190) 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-22371) Promoted step job process stuck in a waiting loop, hang forever, can't abort
Sam Xiao updated JENKINS-22371 Promoted step job process stuck in a waiting loop, hang forever, cant abort Change By: Sam Xiao (26/Mar/14 8:17 PM) Component/s: core 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-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao commented on JENKINS-20640 Jenkins become very slow and had proxy error I don't think these are monitor plugin specific bugs, I've seen the proxy errors almost every endpoints. I think there's an upstream bug somewhere caused this, and only when Jenkins is under heavy load. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao updated JENKINS-20640 Jenkins become very slow and had proxy error Change By: Sam Xiao (12/Dec/13 12:03 AM) Priority: Major Critical Description: Wehavetorestartouthangingjenkinsinstancebecauseofthisissue.ImnotchangingittoCriticalpriority.
[JIRA] [core] (JENKINS-20975) NPE on 1.539
Sam Xiao created JENKINS-20975 NPE on 1.539 Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Dec/13 12:16 AM Description: Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) 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 org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.NullPointerException at hudson.util.ErrorObject.doDynamic(ErrorObject.java:41) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at
[JIRA] [core] (JENKINS-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao updated JENKINS-20640 Jenkins become very slow and had proxy error Change By: Sam Xiao (21/Nov/13 6:00 PM) Attachment: http_session.png 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/groups/opt_out.
[JIRA] [core] (JENKINS-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao commented on JENKINS-20640 Jenkins become very slow and had proxy error evernat Thanks, but I thought the HTTP session problem is different than the proxy error. Or are they actually the same or related? 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/groups/opt_out.
[JIRA] [core] (JENKINS-20612) Hitting /api/json endpoint returns JSON + some malformed HTML content
Sam Xiao
updated JENKINS-20612
Hitting /api/json endpoint returns JSON + some malformed HTML content
Change By:
Sam Xiao
(22/Nov/13 1:43 AM)
Description:
Jenkinsver.1.539UbuntuAsimplecurlcalltotheRESTJSONAPIreturnswithcontentcombinedwithJSON+malformedHTMLCallitonthebrowserandonPostmanworks,butnotviajenkins_api_clientgemfromrubyoracurlcall:curl-v-k-XGET-HAccept:application/jsonhttps://ci.corp.abc.local/api/json
Itseemstobeworkingifyouvelogged,butnotifyouhaventlogin.Canthesefailuresbeclearlystateithassomethingtodowiththesecurityandlogin?
syslog:{noformat}WARNING:Errorwhileservinghttp://127.0.0.1:8080/api/jsonjava.lang.reflect.InvocationTargetException atsun.reflect.GeneratedMethodAccessor824.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:616) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:208) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) atnet.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) atorg.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) athudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:91) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
[JIRA] [core] (JENKINS-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao commented on JENKINS-20640 Jenkins become very slow and had proxy error evernat See attached screenshot, you can clearly see the spike on the http session right after our upgrade to 1.539 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/groups/opt_out.
[JIRA] [core] (JENKINS-20639) Jenkins is very slow and something hit proxy error when opening a configuration page
Sam Xiao resolved JENKINS-20639 as Duplicate Jenkins is very slow and something hit proxy error when opening a configuration page Change By: Sam Xiao (20/Nov/13 9:28 PM) Status: Open Resolved Resolution: Duplicate 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/groups/opt_out.
[JIRA] [core] (JENKINS-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao commented on JENKINS-20640 Jenkins become very slow and had proxy error Copied from a dup: JENKINS-20639 WARNING: /job/ABC/buildHistory/ajax org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-127.0.0.1-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.539.jar!/lib/layout/layout.jelly:75:72: st:include 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.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 org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.io.IOException: finished at com.jcraft.jzlib.DeflaterOutputStream.write(DeflaterOutputStream.java:90) at org.kohsuke.stapler.compression.FilterServletOutputStream.write(FilterServletOutputStream.java:31) at
[JIRA] [core] (JENKINS-20639) Jenkins is very slow and something hit proxy error when opening a configuration page
Sam Xiao closed JENKINS-20639 as Duplicate Jenkins is very slow and something hit proxy error when opening a configuration page Duplicate of JENKINS-20640 Change By: Sam Xiao (20/Nov/13 9:29 PM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [core] (JENKINS-20532) HTTP session count
Sam Xiao updated JENKINS-20532 HTTP session count Change By: Sam Xiao (20/Nov/13 12:36 AM) Component/s: core 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/groups/opt_out.
[JIRA] [core] (JENKINS-20664) radiator-view plugin stop work after upgrade to 1.539
Sam Xiao created JENKINS-20664 radiator-view plugin stop work after upgrade to 1.539 Issue Type: Bug Affects Versions: current Assignee: howama Components: core, radiatorview, radiatorviewplugin Created: 20/Nov/13 3:57 AM Description: Caused by: java.lang.ClassCastException Nov 19, 2013 7:47:10 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.items in /view/iOS%20Radiator/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor305.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) 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.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) 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
[JIRA] [core] (JENKINS-20664) radiator-view plugin stop work after upgrade to 1.539
Sam Xiao
updated JENKINS-20664
radiator-view plugin stop work after upgrade to 1.539
Change By:
Sam Xiao
(20/Nov/13 6:47 AM)
Description:
Goesto[https://ci.abc.local/view/Radiator/]
ItalwayssaidThisviewhasnojobsassociatedwithit.Youcaneitheraddsomeexistingjobstothisvieworcreateanewjobinthisview.ButIaddedexistingjobsandstillnojobisdisplayedontheview.NotsurewhetheritsrelatedtoJENKINS-20262ornot
{noformat}Causedby:java.lang.ClassCastExceptionNov19,20137:47:10PMhudson.ExpressionFactory2$JexlExpressionevaluateWARNING:Caughtexceptionevaluating:it.itemsin/view/iOS%20Radiator/.Reason:java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetException atsun.reflect.GeneratedMethodAccessor305.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:616) atorg.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) atorg.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) atorg.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) atorg.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) atorg.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) atorg.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) atorg.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) atorg.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) athudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) atorg.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) atorg.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) atorg.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) atorg.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) atorg.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) atorg.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44) atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) atorg.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) atorg.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) atorg.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) atorg.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717)
[JIRA] [core] (JENKINS-20639) Jenkins is very slow and something hit proxy error when opening a configuration page
Sam Xiao created JENKINS-20639 Jenkins is very slow and something hit proxy error when opening a configuration page Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 18/Nov/13 9:33 PM Description: Jenkins version: 1.539 WARNING: /job/ABC/buildHistory/ajax org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-127.0.0.1-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.539.jar!/lib/layout/layout.jelly:75:72: st:include 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.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 org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at
[JIRA] [core] (JENKINS-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao created JENKINS-20640 Jenkins become very slow and had proxy error Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, monitoring Created: 18/Nov/13 9:40 PM Description: Jenkins version : 1.539 Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /monitoring. Reason: Error reading from remote server WARNING: /monitoring org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-127.0.0.1-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.539.jar!/lib/layout/layout.jelly:75:72: st:include org.eclipse.jetty.io.EofException 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.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
