Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-51326

JEP-200 long data type rejected after upgrade to 2.107.3

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • hockeyapp-plugin

      Trying to install Jenkins 2.107.3 and when i apply config and jobs from backup (Jenkins 2.89.3). All plugins are up to date. 

      Because of below warning we cannot proceed with higher environments since may affect multiple jobs:

      May 14, 2018 11:59:15 AM jenkins.security.ClassFilterImpl lambda$isBlacklisted$1
      WARNING: long in JRE might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/

       

       

        1. jenkins.log
          6 kB
        2. config.xml
          5 kB
        3. config.xml
          1 kB

          [JENKINS-51326] JEP-200 long data type rejected after upgrade to 2.107.3

          Orest Smoleac created issue -
          Orest Smoleac made changes -
          Description Original: Trying to install Jenkins 2.107.3 and when i apply config and jobs from backup (Jenkins 2.89.3) i get:

          May 14, 2018 11:59:15 AM jenkins.security.ClassFilterImpl lambda$isBlacklisted$1
          WARNING: long in JRE might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/
          New: Trying to install Jenkins 2.107.3 and when i apply config and jobs from backup (Jenkins 2.89.3). All plugins are up to date. 

          Because of below warning we cannot proceed with higher environments since may affect multiple jobs:

          May 14, 2018 11:59:15 AM jenkins.security.ClassFilterImpl lambda$isBlacklisted$1
           WARNING: long in JRE might be dangerous, so rejecting; see [https://jenkins.io/redirect/class-filter/]

           

           

          Daniel Beck added a comment -

          oleg_nenashev Any idea? long isn't a class…

          Daniel Beck added a comment - oleg_nenashev Any idea? long isn't a class…

          Oleg Nenashev added a comment -

          I'd guess there is no stacktrace, right?
          Would it be possible to get a full log starting from the startup? Maybe the core's whitelist didn't get loaded somehow (e.g. resource loading issue).

          Also, do you run Jenkins in a web container? or do you use the built-in Jetty?

          Oleg Nenashev added a comment - I'd guess there is no stacktrace, right? Would it be possible to get a full log starting from the startup? Maybe the core's whitelist didn't get loaded somehow (e.g. resource loading issue). Also, do you run Jenkins in a web container? or do you use the built-in Jetty?
          Oleg Nenashev made changes -
          Assignee New: Oleg Nenashev [ oleg_nenashev ]

          Orest Smoleac added a comment - - edited

          I run Jenkins in a VM under VirtualBox, is not a container.

          I attached a log file (Removed jobs load part for security reasons).

           

          Orest Smoleac added a comment - - edited I run Jenkins in a VM under VirtualBox, is not a container. I attached a log file (Removed jobs load part for security reasons).  
          Orest Smoleac made changes -
          Attachment New: jenkins.log [ 42595 ]

          Oleg Nenashev added a comment -

          Web Container is something like Apache Tomcat, JBoss, etc. It is orthogonal to VMs/containers

          Oleg Nenashev added a comment - Web Container is something like Apache Tomcat, JBoss, etc. It is orthogonal to VMs/containers

          Oleg Nenashev added a comment -

          Anyway, according to the log you are running in Jetty.
          I do not see anything specific there.

          Would be great to understand what is the config file causing it.
          It may be a glitch in primitive type handling, corrupted config or maybe a plugin conflicting with the converter being used for XStream. Anyway, it's strange to not see the full stacktrace

          Oleg Nenashev added a comment - Anyway, according to the log you are running in Jetty. I do not see anything specific there. Would be great to understand what is the config file causing it. It may be a glitch in primitive type handling, corrupted config or maybe a plugin conflicting with the converter being used for XStream. Anyway, it's strange to not see the full stacktrace

          Oleg Nenashev added a comment -

          Yes, it seems the code in the core does not process primitive types correctly. It's unclear how it gets there tho.
          I will create a small patch to add some diagnostics

          Oleg Nenashev added a comment - Yes, it seems the code in the core does not process primitive types correctly. It's unclear how it gets there tho. I will create a small patch to add some diagnostics

            Unassigned Unassigned
            sorests Orest Smoleac
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: