On May 8, 2008, at 10:21 AM, Doug Cutting wrote:
> I'd go with something closer to an accidental policy. My suspicion
> is that logging framework didn't print nested exceptions well.
> Owen is the father of stringifyException and may have more insight.
Yeah, it was my fault. The log4j was misconfigured, so we didn't get
the exception traces out of the messages. I didn't realize it was a
misconfiguration until much later and it had become standard practice
within Hadoop. *sigh* I've fixed a couple of them, but there are a
lot more.
-- Owen
|