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

p4.exe where -G consumes all ports on large changelists

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
      None
    • Environment:
      Windows slave, but 79000 connections will exhaust all ports on any system that I know of
    • Similar Issues:

      Description

      For each file in the given changelist used for sync - a connection is created through p4.exe. The object of this less that optimal solution is issue #7618 where a 'p4 where' command is issued for ever file in the changelist and that quickly yields an error:
      P4 Where Parsing Error: TCP connect to perforce:1666 failed.
      connect: perforce:1666: WSAEADDRINUSE
      com.tek42.perforce.PerforceException: P4 Where Parsing Error: TCP connect to perforce:1666 failed.
      connect: perforce:1666: WSAEADDRINUSE
      Because all ports have been used

      We reverted to perforce plugin version 1.2.5 - that seem to have solved the problem as no where -G's are issued

        Attachments

          Activity

            People

            • Assignee:
              rpetti Rob Petti
              Reporter:
              jonasb Jonas Bovin
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: