You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2010/08/26 02:00:16 UTC
[jira] Created: (AVRO-632) Responder should log stack traces for
user exceptions
Responder should log stack traces for user exceptions
-----------------------------------------------------
Key: AVRO-632
URL: https://issues.apache.org/jira/browse/AVRO-632
Project: Avro
Issue Type: Bug
Components: java
Reporter: Doug Cutting
Assignee: Doug Cutting
Fix For: 1.4.0
Responder currently does not log the stack trace for exceptions in user code, making it hard to debug server-side problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AVRO-632) Responder should log stack traces for
user exceptions
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated AVRO-632:
------------------------------
Attachment: AVRO-632.patch
Here's a patch for this. It does not include a test, but I validated it by looking at the logged output.
> Responder should log stack traces for user exceptions
> -----------------------------------------------------
>
> Key: AVRO-632
> URL: https://issues.apache.org/jira/browse/AVRO-632
> Project: Avro
> Issue Type: Bug
> Components: java
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 1.4.0
>
> Attachments: AVRO-632.patch
>
>
> Responder currently does not log the stack trace for exceptions in user code, making it hard to debug server-side problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AVRO-632) Responder should log stack traces for
user exceptions
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting resolved AVRO-632.
-------------------------------
Hadoop Flags: [Reviewed]
Resolution: Fixed
I committed this.
> Responder should log stack traces for user exceptions
> -----------------------------------------------------
>
> Key: AVRO-632
> URL: https://issues.apache.org/jira/browse/AVRO-632
> Project: Avro
> Issue Type: Bug
> Components: java
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 1.4.0
>
> Attachments: AVRO-632.patch
>
>
> Responder currently does not log the stack trace for exceptions in user code, making it hard to debug server-side problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AVRO-632) Responder should log stack traces for
user exceptions
Posted by "Philip Zeyliger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902722#action_12902722 ]
Philip Zeyliger commented on AVRO-632:
--------------------------------------
+1.
> Responder should log stack traces for user exceptions
> -----------------------------------------------------
>
> Key: AVRO-632
> URL: https://issues.apache.org/jira/browse/AVRO-632
> Project: Avro
> Issue Type: Bug
> Components: java
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 1.4.0
>
> Attachments: AVRO-632.patch
>
>
> Responder currently does not log the stack trace for exceptions in user code, making it hard to debug server-side problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.