You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2008/10/14 19:31:44 UTC
[jira] Created: (UIMA-1205) When Handling Invalid Message Uima AS
Service Needs to Log Which Property Makes The Message Invalid
When Handling Invalid Message Uima AS Service Needs to Log Which Property Makes The Message Invalid
---------------------------------------------------------------------------------------------------
Key: UIMA-1205
URL: https://issues.apache.org/jira/browse/UIMA-1205
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
Priority: Minor
Uima AS needs to log the reason why the message is invalid. Currently the log just shows the InvalidMessageException with no detail at all. It is most likely due to a missing property in the message header. Also there is no information about where the invalid message came from.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1205) When Handling Invalid Message Uima AS
Service Needs to Log Which Property Makes The Message Invalid
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1205:
--------------------------------
Fix Version/s: 2.3AS
> When Handling Invalid Message Uima AS Service Needs to Log Which Property Makes The Message Invalid
> ---------------------------------------------------------------------------------------------------
>
> Key: UIMA-1205
> URL: https://issues.apache.org/jira/browse/UIMA-1205
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Priority: Minor
> Fix For: 2.3AS
>
>
> Uima AS needs to log the reason why the message is invalid. Currently the log just shows the InvalidMessageException with no detail at all. It is most likely due to a missing property in the message header. Also there is no information about where the invalid message came from.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1205) When Handling Invalid Message Uima AS
Service Needs to Log Which Property Makes The Message Invalid
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1205.
-------------------------------
Resolution: Fixed
Added log messages to identify the reason why a message is invalid
> When Handling Invalid Message Uima AS Service Needs to Log Which Property Makes The Message Invalid
> ---------------------------------------------------------------------------------------------------
>
> Key: UIMA-1205
> URL: https://issues.apache.org/jira/browse/UIMA-1205
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Priority: Minor
>
> Uima AS needs to log the reason why the message is invalid. Currently the log just shows the InvalidMessageException with no detail at all. It is most likely due to a missing property in the message header. Also there is no information about where the invalid message came from.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.