-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
1.8.4 plugin, jenkins 2.89.2
Trying to debug why we receive so many of these in our log files.
Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect
SEVERE: P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher
Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry
SEVERE: P4: Connection retry: 1
Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect
SEVERE: P4: Unable to login: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher
Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry
SEVERE: P4: Connection retry: 1
Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry
SEVERE: P4: Connection retry giving up...
Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask
WARNING:
P4 Task: Unable to connect.
Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry
SEVERE: P4: Connection retry giving up...
Is there any way we can get the 'job name' or any other info?
According to the source we shouldn't ever be seeing release2 messages.
Are there any p4 plugin settings we can change / get more debug? Are there other jenkins settings that would give us more info?
[JENKINS-51954] p4 plugin release2 messages
| Description |
Original:
Trying to debug why we receive so many of these in our log files. {{Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect SEVERE: P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Connection retry: 1 Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect SEVERE: P4: Unable to login: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Connection retry: 1 Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Connection retry giving up... Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask WARNING: P4 Task: Unable to connect. Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Connection retry giving up... }} Is there any way we can get the 'job name' or any other info? According to the source we shouldn't ever be seeing release2 messages. Are there any p4 plugin settings we can change / get more debug? Are there other jenkins settings that would give us more info? |
New:
Trying to debug why we receive so many of these in our log files. {{Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect}} {{ SEVERE: P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher}} {{ Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry}} {{ SEVERE: P4: Connection retry: 1}} {{ Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect}} {{ SEVERE: P4: Unable to login: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher}} {{ Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry}} {{ SEVERE: P4: Connection retry: 1}} {{ Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry}} {{ SEVERE: P4: Connection retry giving up...}} {{ Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask}} {{ WARNING: }} {{ P4 Task: Unable to connect.}} {{ Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry}} {{ SEVERE: P4: Connection retry giving up...}} Is there any way we can get the 'job name' or any other info? According to the source we shouldn't ever be seeing release2 messages. Are there any p4 plugin settings we can change / get more debug? Are there other jenkins settings that would give us more info? |
| Description |
Original:
Trying to debug why we receive so many of these in our log files. {{Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect}} {{ SEVERE: P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher}} {{ Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry}} {{ SEVERE: P4: Connection retry: 1}} {{ Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect}} {{ SEVERE: P4: Unable to login: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher}} {{ Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry}} {{ SEVERE: P4: Connection retry: 1}} {{ Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry}} {{ SEVERE: P4: Connection retry giving up...}} {{ Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask}} {{ WARNING: }} {{ P4 Task: Unable to connect.}} {{ Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry}} {{ SEVERE: P4: Connection retry giving up...}} Is there any way we can get the 'job name' or any other info? According to the source we shouldn't ever be seeing release2 messages. Are there any p4 plugin settings we can change / get more debug? Are there other jenkins settings that would give us more info? |
New:
Trying to debug why we receive so many of these in our log files. Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect SEVERE: P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Connection retry: 1 Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect SEVERE: P4: Unable to login: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher Jun 14, 2018 2:35:23 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Connection retry: 1 Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Connection retry giving up... Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask WARNING: P4 Task: Unable to connect. Jun 14, 2018 2:35:26 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Connection retry giving up... Is there any way we can get the 'job name' or any other info? According to the source we shouldn't ever be seeing release2 messages. Are there any p4 plugin settings we can change / get more debug? Are there other jenkins settings that would give us more info? |
Only other thing of note is that there are ~300 jobs using 'H/15 * * * * ' poll spec.
| Assignee | New: Paul Allen [ p4paul ] |
W Basu Perforce
made changes -
| Assignee | Original: Paul Allen [ p4paul ] |
W Basu Perforce
made changes -
| Assignee | New: Karl Wirth [ p4karl ] |
W Basu Perforce
made changes -
| Labels | New: P4_SUPPORT |
Karl Wirth
added a comment - Hi mhall4
Are you still seeing these? We have sometimes seen this error with networking problems but it can also sometimes occur with parallel syncs.
Do you have a Perforce support contract? If you do can you please send an email into support@perforce.com
for attention of me and I can then get some confidential information about your setup, logs etc.
Thanks in advance,
Karl
Karl Wirth
added a comment - Hi mhall4
Are you still seeing these? We have sometimes seen this error with networking problems but it can also sometimes occur with parallel syncs.
Do you have a Perforce support contract? If you do can you please send an email into support@perforce.com for attention of me and I can then get some confidential information about your setup, logs etc.
Thanks in advance,
Karl 
Getting full stacktraces.
Jun 14, 2018 2:48:22 PM org.jenkinsci.plugins.p4.client.ClientHelper clientLogin
SEVERE: P4: Unable to use Workspace: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher
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:1408)
at org.jenkinsci.plugins.p4.client.ClientHelper.clientLogin(ClientHelper.java:123)
at org.jenkinsci.plugins.p4.client.ClientHelper.<init>(ClientHelper.java:108)
at org.jenkinsci.plugins.p4.tasks.AbstractTask.getConnection(AbstractTask.java:161)
at org.jenkinsci.plugins.p4.tasks.AbstractTask.setWorkspace(AbstractTask.java:78)
at org.jenkinsci.plugins.p4.PerforceScm.pollWorkspace(PerforceScm.java:388)
at org.jenkinsci.plugins.p4.PerforceScm.compareRemoteRevisionWith(PerforceScm.java:328)
at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:391)
at hudson.scm.SCM.poll(SCM.java:408)
at hudson.model.AbstractProject._poll(AbstractProject.java:1384)
at hudson.model.AbstractProject.poll(AbstractProject.java:1287)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:594)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:640)
at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
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)
... 23 more
Jun 14, 2018 2:48:22 PM org.jenkinsci.plugins.p4.tasks.AbstractTask setWorkspace
SEVERE: P4: Unable to setup workspace: com.perforce.p4java.exception.ConnectionException: Unexpected release2 message in protocol dispatcher