New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WFCORE-587] Wildfly does not log stack trace of an exception #546
Conversation
Linux Build 1340 is now running using a merge of 3197d48 |
Windows Build 1012 is now running using a merge of 3197d48 |
Linux Build 1340 outcome was SUCCESS using a merge of 3197d48 |
Windows Build 1012 outcome was FAILURE using a merge of 3197d48 Build problems:Execution timeout |
This doesn't fix the problem (the "report" method doesn't log anything) and it unnecessarily rearranges imports to not follow the WildFly standard. |
This fix is completely wrong anyway. If you want the stack trace to be logged, just add |
I don't want the stack trace in the output to report(...) though. That's an out-of-band message theoretically back to the client, which currently goes nowhere. I don't want to be sending server side stack traces to the client. There just needs to be a new log method to log this. |
OK, I will direct it into log instead. Thanks for comments! |
So I left the original report message without change but also logged it with a stack trace. |
Linux Build 1369 is now running using a merge of cd484e4 |
Windows Build 1040 is now running using a merge of cd484e4 |
Windows Build 1040 outcome was SUCCESS using a merge of cd484e4 |
Linux Build 1369 outcome was SUCCESS using a merge of cd484e4 |
Core - Full Integration Build 620 outcome was FAILURE using a merge of cd484e4 Build problems:Failed tests detected Failed tests
|
[WFCORE-587] Wildfly does not log stack trace of an exception
Issue: https://issues.jboss.org/browse/WFCORE-587