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/07/01 21:26:25 UTC

[jira] [Comment Edited] (UIMA-3919) UIMA-AS should support deployment with a colocated AMQ broker

    [ https://issues.apache.org/jira/browse/UIMA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14049224#comment-14049224 ] 

Jerry Cwiklik edited comment on UIMA-3919 at 7/1/14 7:26 PM:
-------------------------------------------------------------

closed by mistake


was (Author: cwiklik):
Modified common code to prevent starting admin channel for JDs. 

> UIMA-AS should support deployment with a colocated AMQ broker
> -------------------------------------------------------------
>
>                 Key: UIMA-3919
>                 URL: https://issues.apache.org/jira/browse/UIMA-3919
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.6.1AS
>
>
> Re-enable support for running UIMA-AS service with a co-located (same jvm) AMQ broker. This used to be supported but was disabled when we switched to using java queues for communicating between AEs deployed in the same jvm. 
> There are other scenarios are considered where the use of a co-located broker would be necessary:
> 1) Support for sharing common services in the same JVM
> 2) Integrating UIMA-AS with systems that dont support/use JMS.
> Modify java sources and dd2spring related scripts/xsl to allow vm://localhost protocol and deployment of colocated broker. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)