Stack Trace for an Exception in EAP ends with ... x more rather than printing the complete stack trace .

Solution Verified - Updated -

Issue

  • Stacktrace within logmessages published by CONSOLE handle of logging framework are truncated.
  • Why do we have the stacktrace for an Exception ending with "... x more" as like below rather than complete stack trace ?
Caused by: java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(abc Method) [abc.jar:1.x.79]
    .........
        ........
    at abc.def.<init>(test.java:331)
    ... 16 more

Environment

  • Red Hat Enterprise Application Platform(EAP).
    • 6.x
    • 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.