You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On OpenJDK the delivery very often (but not always) has an empty body, but the container id arrives in the second delivery.
I noticed it running the SDK/Platfrom locally, where I have openJDK (due to licence changes of Oracle Java). On travis server the Oracle java is used, so there is no such a problem.
The fix would be to add the loop:
QueueingConsumer.Delivery delivery = responseConsumer.nextDelivery(cmdResponseTimeout);
Objects.requireNonNull(delivery, "Didn't got a response for a create container message.");
while(delivery.getBody().length==0) {
LOGGER.debug("The delivery was empty. Waiting for the next one");
delivery = responseConsumer.nextDelivery(cmdResponseTimeout);
Thread.sleep(1000);
}
The text was updated successfully, but these errors were encountered:
Hi!
On OpenJDK the delivery very often (but not always) has an empty body, but the container id arrives in the second delivery.
I noticed it running the SDK/Platfrom locally, where I have openJDK (due to licence changes of Oracle Java). On travis server the Oracle java is used, so there is no such a problem.
The fix would be to add the loop:
The text was updated successfully, but these errors were encountered: