• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: core
• Labels:

  None
• Environment:

  Hide

  Jenkins 2.257
  
  Server version: Apache Tomcat/9.0.37
  Server built: Jun 30 2020 20:09:49 UTC
  Server number: 9.0.37.0
  OS Name: Linux
  OS Version: 2.6.32-754.33.1.el6.x86_64
  Architecture: amd64
  JVM Version: 11.0.8+10
  JVM Vendor: AdoptOpenJDK
  
  Proxy via AJP through Apache/2.2.15 (latest CentOS patches) and mod_jk/1.2.41
  
  CentOS release 6.10
  

  Show

  Jenkins 2.257 Server version: Apache Tomcat/9.0.37 Server built: Jun 30 2020 20:09:49 UTC Server number: 9.0.37.0 OS Name: Linux OS Version: 2.6.32-754.33.1.el6.x86_64 Architecture: amd64 JVM Version: 11.0.8+10 JVM Vendor: AdoptOpenJDK Proxy via AJP through Apache/2.2.15 (latest CentOS patches) and mod_jk/1.2.41 CentOS release 6.10

1. jenkins-update-failure.log

   10 kB

   2020-09-17 22:13

[JENKINS-63721] Unable to update plugins for Jenkins 2.257 running in a Tomcat container

Collapse comment: Mark Waite added a comment - 2020-09-20 18:35

Mark Waite added a comment - 2020-09-20 18:35

This is likely a problem in your local configuration rather than any problem that Jenkins can resolve. It is definitely not an issue with the plugin installation manager command line tool. It may be related to outdated SSL certificate support. It may be related to some other topic.

Refer to JENKINS-63515 as a possibly related issue that includes several different alternatives that you can investigate in your local infrastructure. This type of issue is generally not something that the Jenkins project can resolve.

Expand comment: Mark Waite added a comment - 2020-09-20 18:35

Mark Waite added a comment - 2020-09-20 18:35 This is likely a problem in your local configuration rather than any problem that Jenkins can resolve. It is definitely not an issue with the plugin installation manager command line tool. It may be related to outdated SSL certificate support. It may be related to some other topic. Refer to JENKINS-63515 as a possibly related issue that includes several different alternatives that you can investigate in your local infrastructure. This type of issue is generally not something that the Jenkins project can resolve.

Collapse comment: Mark Eggers added a comment - 2020-09-20 19:05

Mark Eggers added a comment - 2020-09-20 19:05

I have a work-around that doesn't seem to be very optimal.

Normally, I use the Tomcat manager to update applications. I did that on going from 2.256 to 2.257 and ran into the issue I reported.

Restarting the underlying Tomcat service has cleared the error. I was able to both update plugins and check for new updates.

This is probably something getting pinned to memory that shouldn't be. I may be able to work around this with org.apache.catalina.core.JreMemoryLeakPreventionListener in Tomcat's server.xml.

Expand comment: Mark Eggers added a comment - 2020-09-20 19:05

Mark Eggers added a comment - 2020-09-20 19:05 I have a work-around that doesn't seem to be very optimal. Normally, I use the Tomcat manager to update applications. I did that on going from 2.256 to 2.257 and ran into the issue I reported. Restarting the underlying Tomcat service has cleared the error. I was able to both update plugins and check for new updates. This is probably something getting pinned to memory that shouldn't be. I may be able to work around this with org.apache.catalina.core.JreMemoryLeakPreventionListener in Tomcat's server.xml.