In the commercial development of a stream processing application, it’s frequently required to connect to external existing services or applications from it in order to, for example, retrieve data from a data store server. If we connect them through message queues (MQs) adopting exactly-once (EO) message delivery semantics to avoid duplicate processing of the same messages caused by a failure recovery of the upstream backup technique that involves rereading of messages stored in MQs, it causes serious performance degradation on the inquiries. This becomes a major obstacle in realizing real-time applications.This paper investigates the kind of problems that practically happen in failure recovery of a stream processing application that inquires to external services or applications through MQs adopting at-least-once (ALO) message delivery semantics instead of EO to avoid the latency overhead. The efforts revealed three typical consistency problems on message sequencing that happen in failure recovery. By solving each of the three problems, our developed R3CM technique to inquire to external services/applications from a stream processing application turns the adoption of ALO semantics in MQs into an attractive option to avoid latency overhead.