Repository navigation
Conversation
2b06745 to
698462b
Compare
theghost5800
left a comment
There was a problem hiding this comment.
Some of comments are repeatable or not but overall do the checks through all the code again if possible
theghost5800
left a comment
There was a problem hiding this comment.
Some of comments are repeatable or not but overall do the checks through all the code again if possible
LMCROSSITXSADEPLOY-3563
… from poms LMCROSSITXSADEPLOY-3054
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
19c69f8 to
e7fa4e6
Compare
…operations limiting LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
| Duration interval = Constants.JOB_POLL_MIN_INTERVAL; | ||
|
|
||
| while (true) { | ||
| V3Job asyncJob = get(CloudControllerV3Endpoints.JOBS + jobGuid, V3Job.class); |
There was a problem hiding this comment.
I don't see this changed, I expect to use similar structures as this method postForObject(String uri, Object body, Class<T> responseType, Object... uriVars). jobGuid to be passed as uriVar, not as concatenated String.
| long timeoutNanos = timeout.toNanos(); | ||
| Duration interval = Constants.JOB_POLL_MIN_INTERVAL; | ||
|
|
||
| while (true) { |
There was a problem hiding this comment.
while (asyncJob == null || !asyncJob.isTerminal()) {
long elapsedNanos = determineElapsedTime(startTimeNanos, timeout, jobGuid);
long remainingNanos = timeoutNanos - elapsedNanos;
Duration sleepDuration = interval.toNanos() > remainingNanos ? Duration.ofNanos(remainingNanos) : interval;
sleep(sleepDuration);
interval = nextInterval(interval);
asyncJob = get(CloudControllerV3Endpoints.JOBS + jobGuid, V3Job.class);
}
if (asyncJob.isFailed()) {
throw jobFailed(asyncJob);
}
return asyncJob;
Here is one solution which can avoid this.
Also I have notice in the current behaviour that there is no exit from the loop due to exceeded timeout which means if job doesn't return any success or failed state in expected timeout frame, then it will stuck indefinitely.
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
LMCROSSITXSADEPLOY-3563
|


Migration of the cf-java-client dependency