[SAMZA-1112] BrokerProxy does not log fatal errors

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.12.0
• Fix Version/s: 0.13.0
• Assignee: Tommy Becker
• Reporter: Tommy Becker
• Created: 01/Mar/17 16:49
• Updated: 17/Apr/17 02:24
• Resolved: 17/Apr/17 02:24

Description

We hit an issue today where having a large backlog of messages to process caused an OutOfMemoryError in one our our jobs, presumably due to the BrokerProxy's default buffer size of 50k messages being too large. The issue though was that the error was not logged, and from the logs it appeared that the job just spontaneously exited.

Looking at the BrokerProxy, there is no UncaughtExceptionHandler set for its thread, so any fatal errors only go to stderr.

Issue Links

• links to: GitHub Pull Request #80