Seeing error "WARNING com.boomi.restlet.client.ClientUtil handle Request: https://platform.boomi.com/container/....Communication Error (1001) Unable to complete the HTTP call due to a communication timeout error. Read timed out

Document created by pete_mccoy1.3055586893899446E12 Employee on Oct 7, 2014Last modified by dave_lesshafft on Mar 2, 2016
Version 2Show Document
  • View in full screen mode
Looking through container log file and notice the following messages:

 

WARNING [com.boomi.restlet.client.ClientUtil handle] [Request: https://platform.boomi.com/container/<nnnn-nnnnnnn-nnnn>/message/download Attempt: 1]: Hit retry loop. Executing backoff strategy: Communication Error (1001) Unable to complete the HTTP call due to a communication timeout error. Read timed out in container log

 

WARNING [com.boomi.message.SendMessageTask sendMessages] [SendMultiSolrMessageTask[connector-track] Request: https://platform.boomi.com/container/<nnn-nnn>/account/<account-ID>/solr/update Attempt: 1]: Hit retry loop.  Executing backoff strategy.
java.io.IOException: Unable to post messages: Internal Server Error (500) Internal Server Error
These types of messages are indicative of an issue attempting to load information from the local atom/molecule to the platform.
If the message takes too long to transmit, usually caused by an interruption in connectivity between the local atom and the platform, or a resourcing issue either at the sending, or receiving end, the read timeout is generated, (a 1001 HTTP error).
If a message is being sent to the platform and if the platform can't digest it, the platform will generate a 500 internal error (HTTP code).
The atom will continue to attempt to send the messages until the message is successfully received by the platform.

 

There is no production impact related to these errors.

Attachments

    Outcomes