You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Bryan Duxbury (JIRA)" <ji...@apache.org> on 2009/04/01 22:57:13 UTC
[jira] Assigned: (THRIFT-416) java.util.logging eats exceptions
without warning
[ https://issues.apache.org/jira/browse/THRIFT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Duxbury reassigned THRIFT-416:
------------------------------------
Assignee: Jonathan Ellis
> 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.