You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Paul Lindner (JIRA)" <ji...@apache.org> on 2009/10/16 06:06:31 UTC
[jira] Created: (SHINDIG-1197) ProtocolErrors should denote the app
and request that caused the problem
ProtocolErrors should denote the app and request that caused the problem
------------------------------------------------------------------------
Key: SHINDIG-1197
URL: https://issues.apache.org/jira/browse/SHINDIG-1197
Project: Shindig
Issue Type: Bug
Affects Versions: 1.1-BETA3
Reporter: Paul Lindner
One very hard problem is finding the root cause of protocol exceptions. With batching requests are not in the access log -- they're in the post body. To help find these errors we should add the source appUrl and the request that generated the protocol error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SHINDIG-1197) ProtocolErrors should denote the
app and request that caused the problem
Posted by "Paul Lindner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Lindner reassigned SHINDIG-1197:
-------------------------------------
Assignee: Paul Lindner
> ProtocolErrors should denote the app and request that caused the problem
> ------------------------------------------------------------------------
>
> Key: SHINDIG-1197
> URL: https://issues.apache.org/jira/browse/SHINDIG-1197
> Project: Shindig
> Issue Type: Bug
> Affects Versions: 1.1-BETA3
> Reporter: Paul Lindner
> Assignee: Paul Lindner
>
> One very hard problem is finding the root cause of protocol exceptions. With batching requests are not in the access log -- they're in the post body. To help find these errors we should add the source appUrl and the request that generated the protocol error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-1197) ProtocolErrors should denote the app
and request that caused the problem
Posted by "Paul Lindner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Lindner updated SHINDIG-1197:
----------------------------------
Component/s: Java
> ProtocolErrors should denote the app and request that caused the problem
> ------------------------------------------------------------------------
>
> Key: SHINDIG-1197
> URL: https://issues.apache.org/jira/browse/SHINDIG-1197
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 1.1-BETA3
> Reporter: Paul Lindner
> Assignee: Paul Lindner
>
> One very hard problem is finding the root cause of protocol exceptions. With batching requests are not in the access log -- they're in the post body. To help find these errors we should add the source appUrl and the request that generated the protocol error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.