We're actively developing a wowza application and at times we're having trouble finding out where our code is failing by throwing an exception. The default configuration for logging on WowzaStreamingEngine doesn't provide much help as stack traces get truncated. Here's an example:
As you can see, the logs are missing the root cause of the exception. Is there any way we can configure the logs so we get the full stack trace? I hate having to surround all code in Wowza's entry points with try catches just to make sure we can pinpoint where exceptions originate from.