I apologize if my previous message wasn't clear. What you're seeing is the expected behavior. However, that can be changed so that the stack-trace for the underlying ActiveMQException is logged at DEBUG level. Please open a JIRA and I'll add the DEBUG logging.
Justin On Mon, Jun 17, 2019 at 7:47 AM progMetal <[email protected]> wrote: > These are my log settings: > # Root logger level > logger.level=INFO > # ActiveMQ Artemis logger levels > logger.org.apache.activemq.artemis.core.server.level=TRACE > logger.org.apache.activemq.artemis.journal.level=INFO > logger.org.apache.activemq.artemis.utils.level=INFO > logger.org.apache.activemq.artemis.jms.level=INFO > logger.org.apache.activemq.artemis.integration.bootstrap.level=INFO > logger.org.eclipse.jetty.level=DEBUG > > I had "logger.org.apache.activemq.artemis.core.server.level" set to DEBUG > and only got the WARNing level output, then i changed it to TRACE and got > the same output. > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
