[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0

[delikat.mate...@gmail.com (JIRA)]

Title: Message Title

Mateusz Delikat edited a comment on JENKINS-57870   Re: Request too large for server memory since 10.1.0 [~p4karl]{color:#172b4d}, {color}[~p4paul]{color:#172b4d}: Why are we actually seeing {color} {code:java} 02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...02:02:59 02:02:59 Change 2688516 on 2019/06/05 by sj8282.park@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg'{code} {color:#009100}and then{color} { color:#172b4d} {color} { code:java} 02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.__02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516*{code} {color:#172b4d} when we already know the change number from the first call? On our end we don't have "Request too large" errors but the first command on our stream takes about 1 second to complete and the second often takes more than 10 minutes. Does the plugin really needs to re-verify that changelist? Won't it be always the same?{color} {color:#172b4d} {color:#009100}  {color} {color} Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.11569.1561718040532%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.