[
https://issues.apache.org/jira/browse/THRIFT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694804#action_12694804
]
Jonathan Ellis commented on THRIFT-416:
---------------------------------------
> Then let's add JUL configuration to the example server setup in the
> documentation. I'm sure everyone just copies from that anyway.
I'm pretty sure even the most "enterprise" developers would prefer to only
manage one set of logs.
> java.util.logging eats exceptions without warning
> -------------------------------------------------
>
> Key: THRIFT-416
> URL: https://issues.apache.org/jira/browse/THRIFT-416
> Project: Thrift
> Issue Type: Bug
> Components: Library (Java)
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Attachments:
> 0001-allow-exceptions-to-propagate-up-where-feasible.-on.patch,
> 0002-switch-to-log4j.patch
>
>
> Using java.util.logging has two related problems.
> One is that virtually no java project in the wild uses it. Everyone uses the
> more advanced log4j.
> Two is that unlike log4j, java.util.logging does not warn you when it is
> swallowing errors because it has not been configured.
> So thrift exceptions vanish without a trace which is bad.
> Here is a patch to switch to log4j.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
