-
Bug
-
Resolution: Unresolved
-
Major
-
OS: Ubuntu 18.04
JDK 1.8.0_181
P4 Plugin v
Jenkins v2.222.3
P4 Plugin v1.10.12
Jenkins master in container (image: jenkins/jenkins:2.222.3)
Jenkin slaves in container (image: jenkins/jnlp-slave:3.27-1)
ERROR: P4: Task Exception: Unexpected release2 message in protocol dispatcher when using multiple View Mapping
Testing jenkins upgrade from v1.651 to v2.222.3 on a P4 job with multiple View Mapping.
On jenkins v.1651 multiple View Mapping works with the following:
//depot/kernel/05.00/... //ci-kernel-5.0/... -//depot/kernel/05.00/sna/... //ci-kernel-5.0/sna/... -//depot/kernel/05.00/proactor/... //ci-kernel-5.0/proactor/... -//depot/kernel/05.00/spm/... //ci-kernel-5.0/spm/... -//depot/kernel/05.00/ws/mox/... //ci-kernel-5.0/ws/mox/...
On jenkins2 v 2.222.3 with the following view mapping for P4 Plugin v1.10.12
//depot/kernel/05.00/... //${P4_CLIENT}/... //depot/kernel/05.00/sna/... //${P4_CLIENT}/... //depot/kernel/05.00/proactor/... //${P4_CLIENT}/... //depot/kernel/05.00/spm/... //${P4_CLIENT}/... //depot/kernel/05.00/ws/mox/... //${P4_CLIENT}/...
Get the following:
Date 2020/05/20 19:41:44:Date 2020/05/20 19:41:44:Operation: flush2SSL receive failed.read: socket: Connection timed out P4: Unable to setup workspace: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher at com.perforce.p4java.impl.mapbased.rpc.packet.RpcPacketDispatcher.dispatch(RpcPacketDispatcher.java:225) at com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmdList(OneShotServerImpl.java:363) at com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmdList(OneShotServerImpl.java:203) at com.perforce.p4java.impl.mapbased.server.cmd.BaseDelegator.execMapCmdList(BaseDelegator.java:138) at com.perforce.p4java.impl.mapbased.server.cmd.ClientDelegator.getClient(ClientDelegator.java:62) at com.perforce.p4java.impl.mapbased.server.Server.getClient(Server.java:1394) at org.jenkinsci.plugins.p4.client.ClientHelper.updateClient(ClientHelper.java:176) at org.jenkinsci.plugins.p4.client.ClientHelper.clientLogin(ClientHelper.java:160) at org.jenkinsci.plugins.p4.client.ClientHelper.<init>(ClientHelper.java:100) at org.jenkinsci.plugins.p4.tasks.AbstractTask.tryTask(AbstractTask.java:166) at org.jenkinsci.plugins.p4.tasks.CheckoutTask.invoke(CheckoutTask.java:157) at org.jenkinsci.plugins.p4.tasks.CheckoutTask.invoke(CheckoutTask.java:32) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3069) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117) at java.lang.Thread.run(Thread.java:748)Caused by: com.perforce.p4java.exception.ProtocolError: Unexpected release2 message in protocol dispatcher at com.perforce.p4java.impl.mapbased.rpc.func.proto.ProtocolFunctionDispatcher.dispatch(ProtocolFunctionDispatcher.java:110) at com.perforce.p4java.impl.mapbased.rpc.packet.RpcPacketDispatcher.dispatch(RpcPacketDispatcher.java:189) ... 21 more ERROR: P4: Task Exception: Unexpected release2 message in protocol dispatcher
Hi drodspike,
Strange that's an SSL communication error not a P4-Plugin error. Usually these are because of network problems.
A couple of things. First on my SSL environement that workspace definition with v1.10.12 works OK. From my console output:
NOTE: You probably know this already but the basic multiline mapping above will only get you the contents of "//depot/kernel/05.00/ws/mox/..." so its not really a valid mapping but is OK for testing.
Next a couple of questions:
(1) Is this a new job? If not please try creating a new job with the same mapping. Does that also fail?
(2) What happens if you log onto the Jenkins machine, install a copy of P4 and then try to manually create the same workspace using the same P4USER that Jenkins uses. Does it work or do you get an error back (possibly related to triggers)?
(3) Do any jobs work from this slave?
(4) What happens if you make the client spec smaller (for example only first two lines). Does it work?
(5) What happens if you run the build on the Jenkins master?
(6) Where is this error? Console log or polling log?
If none of those work, please get me the following:
(1) Screenshots of the job definition.
(2) Jenkinsfile if it's a pipeline job.
(3) Polling log (if relevant).
(4) Full console log for the job.
(5) Output from 'p4 -Ztag info'.
Note: As some of this information is confidential it can also be sent to 'support@perforce.com' if you prefer.