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)" <de...@uima.apache.org> on 2014/01/21 16:13:19 UTC

[jira] [Created] (UIMA-3572) Fix UIMA-AS race condition

Jerry Cwiklik created UIMA-3572:
-----------------------------------

             Summary: Fix UIMA-AS race condition 
                 Key: UIMA-3572
                 URL: https://issues.apache.org/jira/browse/UIMA-3572
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
    Affects Versions: 2.4.2AS
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
             Fix For: 2.5.0AS


Looks like there is a race condition when handling multiple CASes coming in at the same time from the same client. The first thread creates a Connection and sets up a Session then the second thread sees the Connection made and proceeds to send a reply. The Connection has not yet started though, resulting in 

20 Jan 2014 14:32:18,426  WARN DUCC.ActiveMQSessionExecutor - Received a message on a connection which is not yet started. Have you forgotten to call Connection.start()? Connection: ActiveMQConnection 

Start the Connection as soon as it is created in a synchronized block.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)