uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Reopened: (UIMA-1297) Uima AS Service Not Handling Send Failures Correctly
Date Fri, 14 Aug 2009 19:56:15 GMT

     [ 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.


Mime
View raw message