Jump to content


p4 client throwing "TCP receive exceeded maximum configured duration of 300 seconds"

p4 TCP error

  • Please log in to reply
7 replies to this topic

#1 Bruce Mc

Bruce Mc

    Advanced Member

  • Members
  • PipPipPip
  • 84 posts
  • LocationSeattle Area

Posted 15 April 2014 - 08:22 PM

I've got a distant user connecting to our server over a VPN connection. He reported very slow / unresponsive interactions with the server. Looking in the monitor window in p4admin, he had few syncs of some fairly small code trees that had been running for about 30 minutes.

While we were looking at his connection, the processes in the monitor window cleared and he reported p4 throwing some error messages...
p4 sync /Users/joecool/Documents/Development/some_ver/...#head
TCP receive exceeded maximum configured duration of 300 seconds.
TCP receive exceeded maximum configured duration of 300 seconds.
no files updated
2 errors reported
TCP receive exceeded maximum configured duration of 300 seconds.
TCP receive exceeded maximum configured duration of 300 seconds.
Before I go talking to our network guy I am hoping to have a better understanding of this message beyond "the connection timed out".

Anyone have some insight?

Thanks,

Bruce

#2 P4Matt

P4Matt

    Advanced Member

  • Members
  • PipPipPip
  • 1383 posts

Posted 17 April 2014 - 06:11 AM

I'll check in the morning to see if that message has any special meaning. I'm not familiar with it.

#3 Tank

Tank

    Advanced Member

  • Members
  • PipPipPip
  • 112 posts

Posted 17 April 2014 - 08:41 PM

I've seen something similar, I think I've had it trigger when you fire of a task in p4v then fire off another task. When you get this message ( I've had it when resolving) the dialog goes in limbo and sits there indefinatley unable to gracefully handle itself.

#4 P4Matt

P4Matt

    Advanced Member

  • Members
  • PipPipPip
  • 1383 posts

Posted 17 April 2014 - 10:42 PM

Are either of you going though a proxy? Or are these direct server connections?

#5 Bruce Mc

Bruce Mc

    Advanced Member

  • Members
  • PipPipPip
  • 84 posts
  • LocationSeattle Area

Posted 17 April 2014 - 11:04 PM

In our configuration, all of our local users (and a few remote ones) connect to a proxy server housed in the same lab as the primary server.

This particular user has had a history of poor connectivity to our server here. Long integrate times, syncs with pauses, etc... have been typical for this user. We talked to this user who is located about 150 miles north of us and found that he was using a deprecated VPN solution to connect to an office about 200 miles south of us. We passed him over to our IT people to get him setup with a recommended VPN solution to connect to this office. I expect his experience to improve substantially.

My primary interest at this point is to understand this error message (that I have not encountered before) so that I can add it my knowledge pool for supporting my users.

Bruce

#6 P4Matt

P4Matt

    Advanced Member

  • Members
  • PipPipPip
  • 1383 posts

Posted 17 April 2014 - 11:57 PM

It has to do with the net.maxwait configurable. Here are the relevant docs:

http://www.perforce....e.html#d0e20496
http://www.perforce...._configure.html

#7 Tank

Tank

    Advanced Member

  • Members
  • PipPipPip
  • 112 posts

Posted 18 April 2014 - 12:36 AM

I've had it both direct server in the same building but have experienced it more via a proxy.

#8 Bruce Mc

Bruce Mc

    Advanced Member

  • Members
  • PipPipPip
  • 84 posts
  • LocationSeattle Area

Posted 18 April 2014 - 06:07 PM

Thank you for looking at this Matt.

Bruce





Also tagged with one or more of these keywords: p4, TCP error

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users