Details
-
Type:
Task
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: p4-plugin
-
Environment:Jenkins Version: 2.235.5 docker image jenkins/jenkins:2.235.5
P4 plugin version that has issue: 1.11.0
-
Similar Issues:
Description
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
Attachments
Activity
Hi Kevin Dethoor,
Thanks and happy to help. Also this has highlighted a problem with our older release notes so we've got the developers investigating so thanks again.
Regards,
Karl
Karl Wirth
added a comment - Hi Kevin Dethoor ,
Thanks and happy to help. Also this has highlighted a problem with our older release notes so we've got the developers investigating so thanks again.
Regards,
Karl Hey there, I'm currently experiencing a similar issue.
Java 1.80_281, Jenkins 2.276, P4 Plugin 1.11.2 and p4d version ( P4D/NTX64/2018.1/1957529 (2020/05/06) )
I still have to provice the java args_-DsecureSocketEnabledProtocols=TLSv1_ in order to get the ssl connection running to our main perforce server.
Changing it to TLSv1.2 or 1.1 will give an ssl session error. ssl.tls.version of our p4d is *.min:10 *.max:12
Joscha
added a comment - Hey there, I'm currently experiencing a similar issue.
Java 1.80_281, Jenkins 2.276, P4 Plugin 1.11.2 and p4d version ( P4D/NTX64/2018.1/1957529 (2020/05/06) )
I still have to provice the java args_-DsecureSocketEnabledProtocols=TLSv1_ in order to get the ssl connection running to our main perforce server.
Changing it to TLSv1.2 or 1.1 will give an ssl session error. ssl.tls.version of our p4d is *.min:10 *.max:12 Hi Joscha - Sorry I missed your message last week. This works OK for me. I'm using:
Server version: P4D/NTX64/2018.1/1957529 (2020/05/06)
Jenkins 2.235.1
P4-Plugin 1.11.2
C:\> p4 configure show P4ROOT=E:\filestore\ws\18.1\p4root (-r) P4PORT=ssl:6749 (-p) P4NAME=p4d.exe.18.1.1957529 (services registry) P4LOG=log (-L) server: 1 (P4DEBUG) ssl.tls.version.min: 10 (configure) ssl.tls.version.max: 12 (configure)
The Java I have is the one shipped with Jenkins - 1.8.0 (252).
If you are still having problems can you please email 'support@perforce.com' so we can investigate further.
Karl Wirth
added a comment - Hi Joscha - Sorry I missed your message last week. This works OK for me. I'm using:
Server version: P4D/NTX64/2018.1/1957529 (2020/05/06)
Jenkins 2.235.1
P4-Plugin 1.11.2
C:\> p4 configure show
P4ROOT=E:\filestore\ws\18.1\p4root (-r)
P4PORT=ssl:6749 (-p)
P4NAME=p4d.exe.18.1.1957529 (services registry)
P4LOG=log (-L)
server: 1 (P4DEBUG)
ssl.tls.version.min: 10 (configure)
ssl.tls.version.max: 12 (configure)
The Java I have is the one shipped with Jenkins - 1.8.0 (252).
If you are still having problems can you please email 'support@perforce.com' so we can investigate further.
Hi Karl,
yeah sorry that one is my fault. I totally missed that our main server is on an older p4d version still, its our replica that has a more recent 2018.1 version.
Can I easily update the minor versions without too much worries?
I'd really love to update at least the minor version (honestly also the major version) but I'm too scared about that 
'
Greetings
Joscha
added a comment - Hi Karl,
yeah sorry that one is my fault. I totally missed that our main server is on an older p4d version still, its our replica that has a more recent 2018.1 version.
Can I easily update the minor versions without too much worries?
I'd really love to update at least the minor version (honestly also the major version) but I'm too scared about that
'
Greetings 
Hi Paul and Karl,
Thank you very much for your help.
It was indeed an issue with our server version (2018.1 patch 1715250). I was able to establish a connection using Java 1.8.0_261, Jenkins 2.235.5, P4 Plugin 1.11.0 and adding -DsecureSocketEnabledProtocols=TLSv1 to my Java arguments as prescribed in Perforce Knowledgebase (https://community.perforce.com/s/article/2620). I thought I had tried that previously but I made the mistake of specifying TLSv1.0 instead of TLSv1. With TLSv1, everything works as expected.
Many thanks again.