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 2009/02/27 18:47:12 UTC
[jira] Created: (UIMA-1297) Uima AS Service Not Handling Send
Failures Correctly
Uima AS Service Not Handling Send Failures Correctly
----------------------------------------------------
Key: UIMA-1297
URL: https://issues.apache.org/jira/browse/UIMA-1297
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
When a send requst fails due to a lost broker connection, the uima AS aggregate removes the CAS from the outstanding list. Subsequently, when a timer pops the Timeout Exception is reported against the wrong CAS.
Fix the code so that the CAS remains in the outstanding list until the timer pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1297) Uima AS Service Not Handling Send
Failures Correctly
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor reassigned UIMA-1297:
------------------------------------
Assignee: Burn Lewis (was: Jerry Cwiklik)
> Uima AS Service Not Handling Send Failures Correctly
> ----------------------------------------------------
>
> Key: UIMA-1297
> URL: https://issues.apache.org/jira/browse/UIMA-1297
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Burn Lewis
> Attachments: uimaj-as-activemq_1297.patch
>
>
> When a send requst fails due to a lost broker connection, the uima AS aggregate removes the CAS from the outstanding list. Subsequently, when a timer pops the Timeout Exception is reported against the wrong CAS.
> Fix the code so that the CAS remains in the outstanding list until the timer pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1297) Uima AS Service Not Handling Send
Failures Correctly
Posted by "Burn Lewis (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677496#action_12677496 ]
Burn Lewis commented on UIMA-1297:
----------------------------------
In one of our logs I noticed that even though the a send to a remote service failed, later sends appeared to work and we continued to use the same temp reply queue, so presumably its listener didn't lose connection to the broker!?
> Uima AS Service Not Handling Send Failures Correctly
> ----------------------------------------------------
>
> Key: UIMA-1297
> URL: https://issues.apache.org/jira/browse/UIMA-1297
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> When a send requst fails due to a lost broker connection, the uima AS aggregate removes the CAS from the outstanding list. Subsequently, when a timer pops the Timeout Exception is reported against the wrong CAS.
> Fix the code so that the CAS remains in the outstanding list until the timer pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (UIMA-1297) Uima AS Service Not Handling Send
Failures Correctly
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik reopened UIMA-1297:
---------------------------------
New code seems to have broken the fix. Getting NPE during retry while trying to create a new listener for a new temp reply queue. Current code spins a thread in which recovery takes place on send failures. In this new thread, a new listener is created and it attempts to use properties from the old listener, like number of concurrent consumers and brokerURL. The problem is that the old listener is being stopped and its state cannot be trusted. The code needs to change to prevent referencing old listener properties while creating a new one. Required attributes like number of concurrent consumers and broker URL which are necessary for the new listener must come from static data kept in Delegate objects.
> Uima AS Service Not Handling Send Failures Correctly
> ----------------------------------------------------
>
> Key: UIMA-1297
> URL: https://issues.apache.org/jira/browse/UIMA-1297
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> When a send requst fails due to a lost broker connection, the uima AS aggregate removes the CAS from the outstanding list. Subsequently, when a timer pops the Timeout Exception is reported against the wrong CAS.
> Fix the code so that the CAS remains in the outstanding list until the timer pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1297) Uima AS Service Not Handling Send
Failures Correctly
Posted by "Burn Lewis (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Burn Lewis closed UIMA-1297.
----------------------------
Resolution: Fixed
> Uima AS Service Not Handling Send Failures Correctly
> ----------------------------------------------------
>
> Key: UIMA-1297
> URL: https://issues.apache.org/jira/browse/UIMA-1297
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Burn Lewis
> Attachments: uimaj-as-activemq_1297.patch
>
>
> When a send requst fails due to a lost broker connection, the uima AS aggregate removes the CAS from the outstanding list. Subsequently, when a timer pops the Timeout Exception is reported against the wrong CAS.
> Fix the code so that the CAS remains in the outstanding list until the timer pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1297) Uima AS Service Not Handling Send
Failures Correctly
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679748#action_12679748 ]
Jerry Cwiklik commented on UIMA-1297:
-------------------------------------
Fixed the code so that send() errors are handled in the error handler. The send error is treated as a timeout. A listener on a reply queue associated with the failed delegate is terminated and the status of the delegate is changed to Failed. Subsequent CAS will force creation of a new temp reply queue and a new listener.
> Uima AS Service Not Handling Send Failures Correctly
> ----------------------------------------------------
>
> Key: UIMA-1297
> URL: https://issues.apache.org/jira/browse/UIMA-1297
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> When a send requst fails due to a lost broker connection, the uima AS aggregate removes the CAS from the outstanding list. Subsequently, when a timer pops the Timeout Exception is reported against the wrong CAS.
> Fix the code so that the CAS remains in the outstanding list until the timer pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1297) Uima AS Service Not Handling Send
Failures Correctly
Posted by "Burn Lewis (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677488#action_12677488 ]
Burn Lewis commented on UIMA-1297:
----------------------------------
We've discussed an "optimization" that would immediately execute the error handling as if a timeout had occurred (since that's what would happen if the request was lost later in the network) but decided to postpone that for now until we understand its impact on the new single-timer-per-delegate implementation.
> Uima AS Service Not Handling Send Failures Correctly
> ----------------------------------------------------
>
> Key: UIMA-1297
> URL: https://issues.apache.org/jira/browse/UIMA-1297
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> When a send requst fails due to a lost broker connection, the uima AS aggregate removes the CAS from the outstanding list. Subsequently, when a timer pops the Timeout Exception is reported against the wrong CAS.
> Fix the code so that the CAS remains in the outstanding list until the timer pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1297) Uima AS Service Not Handling Send
Failures Correctly
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1297:
--------------------------------
Fix Version/s: 2.3AS
> Uima AS Service Not Handling Send Failures Correctly
> ----------------------------------------------------
>
> Key: UIMA-1297
> URL: https://issues.apache.org/jira/browse/UIMA-1297
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Burn Lewis
> Fix For: 2.3AS
>
> Attachments: uimaj-as-activemq_1297.patch
>
>
> When a send requst fails due to a lost broker connection, the uima AS aggregate removes the CAS from the outstanding list. Subsequently, when a timer pops the Timeout Exception is reported against the wrong CAS.
> Fix the code so that the CAS remains in the outstanding list until the timer pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1297) Uima AS Service Not Handling Send
Failures Correctly
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1297.
-------------------------------
Resolution: Fixed
> Uima AS Service Not Handling Send Failures Correctly
> ----------------------------------------------------
>
> Key: UIMA-1297
> URL: https://issues.apache.org/jira/browse/UIMA-1297
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
>
> When a send requst fails due to a lost broker connection, the uima AS aggregate removes the CAS from the outstanding list. Subsequently, when a timer pops the Timeout Exception is reported against the wrong CAS.
> Fix the code so that the CAS remains in the outstanding list until the timer pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1297) Uima AS Service Not Handling Send
Failures Correctly
Posted by "Burn Lewis (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Burn Lewis updated UIMA-1297:
-----------------------------
Attachment: uimaj-as-activemq_1297.patch
Two of the JUnit test descriptors need to be modified to ignore the new ForcedMessageTimeoutException
> Uima AS Service Not Handling Send Failures Correctly
> ----------------------------------------------------
>
> Key: UIMA-1297
> URL: https://issues.apache.org/jira/browse/UIMA-1297
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Attachments: uimaj-as-activemq_1297.patch
>
>
> When a send requst fails due to a lost broker connection, the uima AS aggregate removes the CAS from the outstanding list. Subsequently, when a timer pops the Timeout Exception is reported against the wrong CAS.
> Fix the code so that the CAS remains in the outstanding list until the timer pops.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.