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 2010/12/22 22:23:01 UTC

[jira] Closed: (UIMA-1979) UIMA AS allows concurrent access to JMS Session instance

     [ https://issues.apache.org/jira/browse/UIMA-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-1979.
-------------------------------

    Resolution: Fixed

> UIMA AS allows concurrent access to JMS Session instance
> --------------------------------------------------------
>
>                 Key: UIMA-1979
>                 URL: https://issues.apache.org/jira/browse/UIMA-1979
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.3.1AS
>
>
> JmsEndpointConnection_impl does not synchronize access to JMS Session object to prevent multiple threads from accessing it. Per JMS spec. Section 4.4.6:
>  
> "Sessions are designed for serial use by one thread at a time."
> There are four methods in the above class where access to the JMS Session is not synchronized:
> produceTextMessage()
> produceByteMessage()
> produceObjectMessage()
> isOpen()

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.