Good morning,
we've noticed that some UPS shipments receive the error message since yesterday afternoon:
Failed to route event via endpoint: DefaultOutboundEndpoint{endpointUri=https://onlinetools.ups.com:443/ups.app/xml/ShipConfirm, connector=NiklasHttpsConnector
{
name=NIKLAS.CONN.3
lifecycle=start
this=4b502aea
numberOfConcurrentTransactedReceivers=4
createMultipleTransactedReceivers=true
connected=true
supportedProtocols=[https]
serviceOverrides=
response.transformer=nl.copernicus.niklas.builders.support.NiklasMuleMessageToHttpResponse
outbound.transformer=nl.copernicus.niklas.mule.convert.ObjectToHttpMethod
dispatcher.factory=nl.copernicus.niklas.builders.connectors.dispatcher.HttpsMessageDispatcherFactory
session.handler=org.mule.session.NullSessionHandler
message.factory=nl.copernicus.niklas.builders.support.HttpExtendedMuleMessageFactory
}
, name='endpoint.https.onlinetools.ups.com.443.ups.app.xml.ShipConfirm', mep=REQUEST_RESPONSE, properties={}, transactionConfig=Transaction{factory=null, action=INDIFFERENT, timeout=0}, deleteUnacceptedMessages=false, initialState=started, responseTimeout=10000, endpointEncoding=UTF-8, disableTransportTransformer=false}. Message payload is of type: PostMethod (org.mule.api.transport.DispatchException). Message payload is of type: ReleasingInputStream
We are in contact with UPS to try and solve this as quickly as possible and will report it here when this is done.
Please Follow this thread to keep yourself updated on any further developments.
Kind regards,
Team nShift
1 comment
Good morning,
after contact with UPS it has become clear that this booking error triggers when a time-out happens in the connection to the carrier, and this happens only very rarely. Rebooking your shipment should solve this issue.
If it does not, please send us a new ticket through the customer portal.