You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jonathan Poltak Samosir (JIRA)" <ji...@apache.org> on 2014/02/05 00:30:08 UTC
[jira] [Created] (SAMZA-137) Fix how long warning messages get
truncated in container logs
Jonathan Poltak Samosir created SAMZA-137:
---------------------------------------------
Summary: Fix how long warning messages get truncated in container logs
Key: SAMZA-137
URL: https://issues.apache.org/jira/browse/SAMZA-137
Project: Samza
Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Jonathan Poltak Samosir
Priority: Minor
Fix For: 0.7.0
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
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)