You can send a PR to tweak the log to not output the stacktrace. We could potentially log including stacktrace in DEBUG mode so end users can turn on that logging level in case the stacktrace is needed during troubleshooting
On Fri, Jan 6, 2023 at 12:22 PM Mark Webb <elihusma...@gmail.com> wrote: > Sure, I could tweak the logger. I was hoping to not have the stack trace > get logged, but a more user-friendly log generated. > > On Fri, Jan 6, 2023 at 12:56 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > > > Hi > > > > Do you want that WARN to not be logged - or the logging to NOT include > the > > stacktrace? > > The log is hardcoded and it can happened when using temporary reply > queues. > > > > You can tweak the logger to set logging level to ERROR > > for TemporaryQueueReplyManager etc > > > > > > On Thu, Jan 5, 2023 at 8:51 PM Mark Webb <elihusma...@gmail.com> wrote: > > > > > I'm starting up a project that will use the request/response with > > ActiveMQ > > > AMQP. When I try to send a message that I expect a response to and > > > ActiveMQ is down, I can't seem to catch or prevent the stack trace from > > > getting logged for the TemporaryQueueReplyManager. The error is: > > > > > > Exception inside the DMLC for Temporary ReplyTo Queue for destination > > XXXX, > > > refreshing ReplyTo destination > > > > > > How can I go about handling this error in the temporary response > > > processing? Any help would be appreciated. > > > > > > Thanks, > > > Mark > > > > > > > > > -- > > Claus Ibsen > > ----------------- > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
