Unnecessary stack trace in case of authentication failure
Environment
- Red Hat JBoss A-MQ 6.1.0
Issue
- When an authentication failure occurs, we do get a warning in the logs.
- However, we also get an unnecessary stack trace, even on the INFO logging level. It would be best to keep stack traces for unexpected problems that could be linked to bugs in the ActiveMQ code. A simple misconfigured messaging client should not trigger a stack trace in case of authentication failure.
Resolution
The issue has been resolved and included in Fuse 6.2.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
