[
https://issues.apache.org/jira/browse/UIMA-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745369#comment-13745369
]
Jerry Cwiklik commented on UIMA-2685:
-------------------------------------
Defer beyond 2.4.2 Release
> Add support for deploying co-located remote UIMA-AS services
> -------------------------------------------------------------
>
> Key: UIMA-2685
> URL: https://issues.apache.org/jira/browse/UIMA-2685
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Affects Versions: 2.4.0AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.4.2AS
>
>
> Add support for deploying remote UIMA-AS service in the same jvm as its
> client. This co-location will eliminate serialization/deserialization
> overhead as well as the network overhead. The service will be deployed using
> jms queue managed by an internal AMQ broker. The client and the service will
> connect to the internal broker using vm protocol. To facilitate the above, we
> need changes to dd2spring.xsl as well changes in the UIMA_Service and
> ServiceDeployer. In dd2spring we need:
> 1) internal AMQ broker and ConnectionFactory for vm-style connections
> 2) JMS Queue for the service
> 3) Listener on the input queue, associated InputChannel and request handler
> chain
> 4) For aggregate deployment descriptor, need a Listener on service reply
> queue, associated InputChannel and request+reply handler chain
> The UIMA_Service is already setup for accepting multiple deployment
> descriptors, but needs works to support deployments of multiple services into
> Spring containers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
