Thanks for confirming this isn't an error. We'll reduce log levels as appropriate.
-----Original Message----- From: Robbie Gemmell <robbie.gemm...@gmail.com> Sent: Monday, October 4, 2021 10:26 AM To: users <users@qpid.apache.org> Subject: Re: Stuck Delivery Detection: Starting detection cycle Exercise Caution: This email is from an external source. "Stuck Delivery Detection: Starting detection cycle" isnt an error message. It is a debug-level log message about the routers operation: https://github.com/apache/qpid-dispatch/blob/1.16.0/src/router_core/modules/stuck_delivery_detection/delivery_tracker.c#L94 https://issues.apache.org/jira/browse/DISPATCH-1463 It is noting the start of a process around checking messages are continuing to flow, i.e checking that messages have not appeared to become stuck. Unless you meant to paste something else, there doesn't seem to be an issue except perhaps the log level configured. On Mon, 4 Oct 2021 at 15:43, Lohman, Richard <richard.loh...@cmegroup.com> wrote: > > Hi, all: > > I recently attempted an upgrade from 1.9.0 to 1.16.0. After bringing the app > back up, I began receiving these in the log: > > Stuck Delivery Detection: Starting detection cycle > > These messages were not in logs prior to the update. We build some additional > tooling around qpid, and we are able to watch messages flow through. While > the message wording gives the impression that there is a problem delivering > messages, I could see responses coming back from the other side after the > upgrade: > > 2021-09-29 11:26:03,668-0500 INFO APP=969 COMP=977 [main] > AMQPtoMQBridge Received message: <?xml version="1.0" encoding="UTF-8" > standalone="yes"?> <RespMsg> > <H> > <MemberId>VN</MemberId> > <userId>VN_TRREP</userId> > <isMoreRcdsToReceive>false</isMoreRcdsToReceive> > </H> > <B> > <respMsgs> > <respMsg> > <respCode>00000</respCode> > <respText>Success</respText> > <pwdExpDate>1970-01-01</pwdExpDate> > > <lastLoginDateTime>2021-09-29T15:30:06.000000</lastLoginDateTime> > </respMsg> > </respMsgs> > </B> > </RespMsg> > > So, > 1. What exactly is this message trying to indicate? > 2. Are there some methods to drill deeper into this error & better understand > what is triggering it? > > > Thanks for considering, > Richard J. Lohman > > ________________________________ > NOTICE: This message, and any attachments, are for the intended recipient(s) > only, may contain information that is privileged, confidential and/or > proprietary and subject to important terms and conditions available at > E-Communication > Disclaimer<http://www.cmegroup.com/tools-information/communications/e-communication-disclaimer.html>. > If you are not the intended recipient, please delete this message. CME Group > and its subsidiaries reserve the right to monitor all email communications > that occur on CME Group information systems. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
