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

Nelson RIvera commented on UIMA-5477:
-------------------------------------

this is not my uima-as deployment, i have a client by uima-as service.  
The aggregate uima-as service  have two Cas Multiplier delegate in it flow , 
but are colocated, at the beginning and the middle. The remote delegate of 
aggregate uima-as service is at the end of the flow and is  a primitive 
annotator, implemented in c++ and deploy with deployAsyncService.sh.

> javax.jms.IllegalStateException: The Session is closed after establish 
> connections between uima-as client and ActiveMQ
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-5477
>                 URL: https://issues.apache.org/jira/browse/UIMA-5477
>             Project: UIMA
>          Issue Type: Access
>          Components: Async Scaleout
>    Affects Versions: 2.9.0AS
>         Environment: ubuntu xenial, openjdk-8-jdk
>            Reporter: Nelson RIvera
>         Attachments: screenshot-1.png
>
>
> In my program main, i initialize a uimas-as client only once and I use
> this client to consume all requests to a displayed service uima-as.
> Before process a request i ask to uima-as client with:
> BaseUIMAAsynchronousEngine_impl.connectionOpen()
> and if the result es "false", i stop the uima-as client and initialize it 
> again.
> With some steps, still undefined, but basically when restart the UIMA-AS 
> Broker
> without restart service uima-as.
> The instruccion to uima-as client
> BaseUIMAAsynchronousEngine_impl.connectionOpen() return "true", but
> them i get a "javax.jms.IllegalStateException: The Session is closed"
> when proces the request.
> One peculiarity is that, is a primitive annotator implented in c++,
> but is deployed with de deployAsyncService.sh de uima-as directly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to