On Tue, May 27, 2025, 2:16 PM James Perkins <jperkins(a)redhat.com> wrote:
What appears to be missing from the stack trace?
Seeing more of the exception call stack would give more context as to why
the failure occurred.
The output should match what you'd see from Throwable.printStackTrace().
Thanks, will look there.
> James R. Perkins
> Principal Software Engineer
> Red Hat <
https://www.redhat.com/
> <
https://www.redhat.com/
> On Mon, May 19, 2025 at
10:50 AM Scott Marlow via wildfly-dev <
> wildfly-dev(a)lists.jboss.org> wrote:
>> I do not recall any way to configure WildFly to show
the entire exception
>> call stack in the console logger output. Does anyone have an example of
>> doing that?
>
>> Thanks,
>> Scott
>> _______________________________________________
>> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
>> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
>> Privacy Statement:
https://www.redhat.com/en/about/privacy-policy
>> List Archives:
>>
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
>