Description
If there is a Java problem encountered that produces a long warning message, that warning message will be truncated in the given container's logs. This is an issue as it makes it painful to solve as issue that could otherwise be solved simply by reading the full Java warning message.
An example of what I am talking about can be found in one of my logs, here (scroll down a few lines until you see the recurring truncated warning message):
https://gist.github.com/poltak/8745919/raw/7990b0199fafde9bf6da00aa4b87b2e14fb0e717/gistfile1.txt