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

Error occurred during the SSL handshake after P4 plugin is upgraded to 1.11.0 from 1.10.14

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Minor Minor
    • p4-plugin
    • Jenkins Version: 2.235.5 docker image jenkins/jenkins:2.235.5
      P4 plugin version that has issue: 1.11.0

      Error occurred during the SSL handshake after P4 plugin is upgraded to 1.11.0 from 1.10.14

      Error:

      [Pipeline] p4sync
11:43:26  WARNING: Unknown parameter(s) found for class type 'org.jenkinsci.plugins.p4.populate.ForceCleanImpl': modtime,replace,tidy
11:43:29  Executor number at runtime: 0
11:43:29  P4: Connection retry: 1
11:43:32  Error occurred during the SSL handshake: invalid SSL session

          [JENKINS-63489] Error occurred during the SSL handshake after P4 plugin is upgraded to 1.11.0 from 1.10.14

          Shivaji Thanneeru created issue -
          jesus fernandez made changes -
          Comment [ I have been using Jenkins on windows as a service (v.2.235) and also I am using P4 plugin. But I need to stop the service and start using jenkins from the cmd so I can have access to execute GUI applications in my pipeline. I downladed the latest jenkins.war(2.263.2 ) and execute it from the cmd, but now again I have the same issue of the SSL handshake, I have check the jenkins.xml file and it is the same as it was:

          <executable>C:\Program Files\Java\jdk1.8.0_261\bin\java.exe</executable>
          <arguments>-DsecureSocketEnabledProtocols=TLSv1 -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "C:\Program Files\Jenkins\jenkins.war" --httpPort=8080 --webroot="%LocalAppData%\Jenkinswar"</arguments>

          Actually if closing the cmd and starting the service back again the handshake works just fine. So I am wondering if I need to change the configuration in any other file when running it from the cmd maybe? any help is much appreciated. Thanks ]
          Karl Wirth made changes -
          Comment [ Hi [~latalavera] ,

          "Now and again" seems strange. If it didnt work at the command line I would say that either the correct SSL libaries were not installed in the Java you were using or it was not picking up the correct arguments from the config file.

          Can you please raise a case with 'support@perforce.com' and include the full console output where it fails and the output from 'p4 -Ztag info' run against your P4D server.

          Thanks in advance,

          Karl

           

            ]
          Karl Wirth made changes -
          Labels Original: p4-plugin New: P4_A P4_VERIFY p4-plugin
          Karl Wirth made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            shivaji_thanneeru Shivaji Thanneeru
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: