Re: How know when "Session is closed" after establish connections between uima-as client and ActiveMQ?
Please can you give me the url to source code with the changes, to test. 2017-07-05 16:19 GMT-04:00, Jaroslaw Cwiklik : > Just delivered a few changes to deal with a stale Session. Can you build > from source and test. > Jerry > > On Wed, Jul 5, 2017 at 2:21 PM, Jaroslaw Cwiklik > wrote: > >> Thanks. Will check the code and work on a fix >> >> Jerry >> >> On Wed, Jul 5, 2017 at 2:10 PM, nelson rivera >> wrote: >> >>> Here the stack trace for the error that asked me: >>> jul 05, 2017 2:08:50 PM >>> org.apache.uima.adapter.jms.client.ActiveMQMessageSender run >>> ADVERTENCIA: >>> javax.jms.IllegalStateException: The Session is closed >>> at org.apache.activemq.ActiveMQSession.checkClosed(ActiveMQSess >>> ion.java:771) >>> at org.apache.activemq.ActiveMQSession.configureMessage(ActiveM >>> QSession.java:759) >>> at org.apache.activemq.ActiveMQSession.createTextMessage(Active >>> MQSession.java:440) >>> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.cre >>> ateTextMessage(ActiveMQMessageSender.java:184) >>> at org.apache.uima.adapter.jms.client.BaseMessageSender.run(Bas >>> eMessageSender.java:307) >>> at java.lang.Thread.run(Thread.java:748) >>> >>> 2017-07-05 12:16 GMT-04:00, nelson rivera : >>> > This behavior is random, not occurs always. In the most of the simple >>> > programs and simple test case tested, after restart the UIMA-AS Broker >>> > without restart service uima-as, the instruccion to uima-as client >>> > "BaseUIMAAsynchronousEngine_impl.connectionOpen()" return "false" and >>> > correctly i initialize the client again. >>> > >>> > The incorrect behavior is most frequently with many uima-as client >>> > instances. Is the case of my general application in which i have many >>> > service uima-as, and for each one creates one instace of uima-as >>> > client (BaseUIMAAsynchronousEngine_impl) and keep it alive to process >>> > all requests of the service uima-as. >>> > >>> > Is in this scenario with many instancies of uima-as client >>> > (BaseUIMAAsynchronousEngine_impl) in the same program (a monolithic >>> > application web in tomcat) where after restart the UIMA-AS Broker >>> > without restart any service uima-as, many uima-as client returns >>> > "true" to the instruccion >>> > "BaseUIMAAsynchronousEngine_impl.connectionOpen()" but them throw >>> > "javax.jms.IllegalStateException: The Session is closed" >>> > when proces the request. >>> > >>> > 2017-07-04 16:13 GMT-04:00, nelson rivera : >>> >> One peculiarity is that, is a primitive annotator implented in c++, >>> >> but is deployed with de deployAsyncService.sh de uima-as directly. >>> >> >>> >> 2017-07-04 14:53 GMT-04:00, nelson rivera : >>> >>> 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 after 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. >>> >>> >>> >>> Wich is the best way to know when connections betewen cliente >>> >>> uima-as >>> >>> and ActiveMQ is broken? and i should restart uima-as client. >>> >>> >>> >> >>> > >>> >> >> >
Re: How know when "Session is closed" after establish connections between uima-as client and ActiveMQ?
Just delivered a few changes to deal with a stale Session. Can you build from source and test. Jerry On Wed, Jul 5, 2017 at 2:21 PM, Jaroslaw Cwiklik wrote: > Thanks. Will check the code and work on a fix > > Jerry > > On Wed, Jul 5, 2017 at 2:10 PM, nelson rivera > wrote: > >> Here the stack trace for the error that asked me: >> jul 05, 2017 2:08:50 PM >> org.apache.uima.adapter.jms.client.ActiveMQMessageSender run >> ADVERTENCIA: >> javax.jms.IllegalStateException: The Session is closed >> at org.apache.activemq.ActiveMQSession.checkClosed(ActiveMQSess >> ion.java:771) >> at org.apache.activemq.ActiveMQSession.configureMessage(ActiveM >> QSession.java:759) >> at org.apache.activemq.ActiveMQSession.createTextMessage(Active >> MQSession.java:440) >> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.cre >> ateTextMessage(ActiveMQMessageSender.java:184) >> at org.apache.uima.adapter.jms.client.BaseMessageSender.run(Bas >> eMessageSender.java:307) >> at java.lang.Thread.run(Thread.java:748) >> >> 2017-07-05 12:16 GMT-04:00, nelson rivera : >> > This behavior is random, not occurs always. In the most of the simple >> > programs and simple test case tested, after restart the UIMA-AS Broker >> > without restart service uima-as, the instruccion to uima-as client >> > "BaseUIMAAsynchronousEngine_impl.connectionOpen()" return "false" and >> > correctly i initialize the client again. >> > >> > The incorrect behavior is most frequently with many uima-as client >> > instances. Is the case of my general application in which i have many >> > service uima-as, and for each one creates one instace of uima-as >> > client (BaseUIMAAsynchronousEngine_impl) and keep it alive to process >> > all requests of the service uima-as. >> > >> > Is in this scenario with many instancies of uima-as client >> > (BaseUIMAAsynchronousEngine_impl) in the same program (a monolithic >> > application web in tomcat) where after restart the UIMA-AS Broker >> > without restart any service uima-as, many uima-as client returns >> > "true" to the instruccion >> > "BaseUIMAAsynchronousEngine_impl.connectionOpen()" but them throw >> > "javax.jms.IllegalStateException: The Session is closed" >> > when proces the request. >> > >> > 2017-07-04 16:13 GMT-04:00, nelson rivera : >> >> One peculiarity is that, is a primitive annotator implented in c++, >> >> but is deployed with de deployAsyncService.sh de uima-as directly. >> >> >> >> 2017-07-04 14:53 GMT-04:00, nelson rivera : >> >>> 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 after 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. >> >>> >> >>> Wich is the best way to know when connections betewen cliente uima-as >> >>> and ActiveMQ is broken? and i should restart uima-as client. >> >>> >> >> >> > >> > >
Re: How know when "Session is closed" after establish connections between uima-as client and ActiveMQ?
Thanks. Will check the code and work on a fix Jerry On Wed, Jul 5, 2017 at 2:10 PM, nelson rivera wrote: > Here the stack trace for the error that asked me: > jul 05, 2017 2:08:50 PM > org.apache.uima.adapter.jms.client.ActiveMQMessageSender run > ADVERTENCIA: > javax.jms.IllegalStateException: The Session is closed > at org.apache.activemq.ActiveMQSession.checkClosed( > ActiveMQSession.java:771) > at org.apache.activemq.ActiveMQSession.configureMessage( > ActiveMQSession.java:759) > at org.apache.activemq.ActiveMQSession.createTextMessage( > ActiveMQSession.java:440) > at org.apache.uima.adapter.jms.client.ActiveMQMessageSender. > createTextMessage(ActiveMQMessageSender.java:184) > at org.apache.uima.adapter.jms.client.BaseMessageSender.run( > BaseMessageSender.java:307) > at java.lang.Thread.run(Thread.java:748) > > 2017-07-05 12:16 GMT-04:00, nelson rivera : > > This behavior is random, not occurs always. In the most of the simple > > programs and simple test case tested, after restart the UIMA-AS Broker > > without restart service uima-as, the instruccion to uima-as client > > "BaseUIMAAsynchronousEngine_impl.connectionOpen()" return "false" and > > correctly i initialize the client again. > > > > The incorrect behavior is most frequently with many uima-as client > > instances. Is the case of my general application in which i have many > > service uima-as, and for each one creates one instace of uima-as > > client (BaseUIMAAsynchronousEngine_impl) and keep it alive to process > > all requests of the service uima-as. > > > > Is in this scenario with many instancies of uima-as client > > (BaseUIMAAsynchronousEngine_impl) in the same program (a monolithic > > application web in tomcat) where after restart the UIMA-AS Broker > > without restart any service uima-as, many uima-as client returns > > "true" to the instruccion > > "BaseUIMAAsynchronousEngine_impl.connectionOpen()" but them throw > > "javax.jms.IllegalStateException: The Session is closed" > > when proces the request. > > > > 2017-07-04 16:13 GMT-04:00, nelson rivera : > >> One peculiarity is that, is a primitive annotator implented in c++, > >> but is deployed with de deployAsyncService.sh de uima-as directly. > >> > >> 2017-07-04 14:53 GMT-04:00, nelson rivera : > >>> 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 after 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. > >>> > >>> Wich is the best way to know when connections betewen cliente uima-as > >>> and ActiveMQ is broken? and i should restart uima-as client. > >>> > >> > > >
Re: How know when "Session is closed" after establish connections between uima-as client and ActiveMQ?
Here the stack trace for the error that asked me: jul 05, 2017 2:08:50 PM org.apache.uima.adapter.jms.client.ActiveMQMessageSender run ADVERTENCIA: javax.jms.IllegalStateException: The Session is closed at org.apache.activemq.ActiveMQSession.checkClosed(ActiveMQSession.java:771) at org.apache.activemq.ActiveMQSession.configureMessage(ActiveMQSession.java:759) at org.apache.activemq.ActiveMQSession.createTextMessage(ActiveMQSession.java:440) at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.createTextMessage(ActiveMQMessageSender.java:184) at org.apache.uima.adapter.jms.client.BaseMessageSender.run(BaseMessageSender.java:307) at java.lang.Thread.run(Thread.java:748) 2017-07-05 12:16 GMT-04:00, nelson rivera : > This behavior is random, not occurs always. In the most of the simple > programs and simple test case tested, after restart the UIMA-AS Broker > without restart service uima-as, the instruccion to uima-as client > "BaseUIMAAsynchronousEngine_impl.connectionOpen()" return "false" and > correctly i initialize the client again. > > The incorrect behavior is most frequently with many uima-as client > instances. Is the case of my general application in which i have many > service uima-as, and for each one creates one instace of uima-as > client (BaseUIMAAsynchronousEngine_impl) and keep it alive to process > all requests of the service uima-as. > > Is in this scenario with many instancies of uima-as client > (BaseUIMAAsynchronousEngine_impl) in the same program (a monolithic > application web in tomcat) where after restart the UIMA-AS Broker > without restart any service uima-as, many uima-as client returns > "true" to the instruccion > "BaseUIMAAsynchronousEngine_impl.connectionOpen()" but them throw > "javax.jms.IllegalStateException: The Session is closed" > when proces the request. > > 2017-07-04 16:13 GMT-04:00, nelson rivera : >> One peculiarity is that, is a primitive annotator implented in c++, >> but is deployed with de deployAsyncService.sh de uima-as directly. >> >> 2017-07-04 14:53 GMT-04:00, nelson rivera : >>> 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 after 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. >>> >>> Wich is the best way to know when connections betewen cliente uima-as >>> and ActiveMQ is broken? and i should restart uima-as client. >>> >> >
Re: Broken conections after ACTIVEMQ restart with service uima-as CasMultiplier and delegate remote
Hi, i know that the behavior that you described should be the correct. But no is the case, because the broker is restarted the both times after that a request is completely successful, all uima-as service are finished and none are running. After second restart, the logs of remote delegate service add the following lines continuously(the log file grows continuously) until the next request that cause the error is make: 01:32:19.611 - 19: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException: WARNING: Jms Listener Failed. Endpoint: XLangDetector Managed By: tcp://127.0.0.1:61616 Reason: javax.jms.IllegalStateException: The Session is closed 01:32:19.611 - 20: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException: WARNING: Service: XLangDetector Runtime Exception 01:32:19.611 - 19: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure: WARNING: Uima AS Service:XLangDetector Listener Unable To Connect To Broker: tcp://127.0.0.1:61616 Retrying Until Successful ... 01:32:19.611 - 20: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException: WARNING: Jms Listener Failed. Endpoint: XLangDetector Managed By: tcp://127.0.0.1:61616 Reason: javax.jms.IllegalStateException: The Session is closed 01:32:19.613 - 18: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException: WARNING: Service: XLangDetector Runtime Exception 01:32:19.613 - 18: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException: WARNING: Jms Listener Failed. Endpoint: XLangDetector Managed By: tcp://127.0.0.1:61616 Reason: javax.jms.IllegalStateException: The Consumer is closed 01:32:19.613 - 18: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure: WARNING: Uima AS Service:XLangDetector Listener Unable To Connect To Broker: tcp://127.0.0.1:61616 Retrying Until Successful ... 01:32:19.613 - 19: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure: WARNING: Uima AS Service:XLangDetector Listener Recovered Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again 01:32:19.615 - 20: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure: WARNING: Uima AS Service:XLangDetector Listener Recovered Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again 01:32:19.616 - 18: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure: WARNING: Uima AS Service:XLangDetector Listener Recovered Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again 01:32:19.617 - 17: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException: WARNING: Service: XLangDetector Runtime Exception 01:32:19.617 - 17: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException: WARNING: Jms Listener Failed. Endpoint: XLangDetector Managed By: tcp://127.0.0.1:61616 Reason: javax.jms.IllegalStateException: The Consumer is closed 01:32:19.617 - 17: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure: WARNING: Uima AS Service:XLangDetector Listener Unable To Connect To Broker: tcp://127.0.0.1:61616 Retrying Until Successful ... 01:32:19.623 - 17: org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure: WARNING: Uima AS Service:XLangDetector Listener Recovered Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again With the last request that cause the error, the casmultipler process the input CAS and create the new CASes and when are sent to remote service delegate (this service has 4 instances) it process the child CASes y them shows this error: Recovered Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again 01:33:17.619 - 19: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : Begin -> XLangDetector::process --- OK 01:33:17.619 - 19: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End -> XLangDetector::process --- OK 01:33:17.622 - 17: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : Begin -> XLangDetector::process --- OK 01:33:17.623 - 17: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End -> XLangDetector::process --- OK 01:33:17.632 - 8783: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send: WARNING: Controller: XLangDetector Failed To Send Message to Delegates Queue: null 01:33:17.635 - 8783: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException(): INFO: Service:XLangDetector JMS unable to Deliver CAS:-7a178caa:15d13c3484d:-7874 - Error:temp-queue://ID:nelson-XPS-8700-37197-1499275152544-13:1:1 01:33:17.635 - 8783: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_imp
Re: How know when "Session is closed" after establish connections between uima-as client and ActiveMQ?
This behavior is random, not occurs always. In the most of the simple programs and simple test case tested, after restart the UIMA-AS Broker without restart service uima-as, the instruccion to uima-as client "BaseUIMAAsynchronousEngine_impl.connectionOpen()" return "false" and correctly i initialize the client again. The incorrect behavior is most frequently with many uima-as client instances. Is the case of my general application in which i have many service uima-as, and for each one creates one instace of uima-as client (BaseUIMAAsynchronousEngine_impl) and keep it alive to process all requests of the service uima-as. Is in this scenario with many instancies of uima-as client (BaseUIMAAsynchronousEngine_impl) in the same program (a monolithic application web in tomcat) where after restart the UIMA-AS Broker without restart any service uima-as, many uima-as client returns "true" to the instruccion "BaseUIMAAsynchronousEngine_impl.connectionOpen()" but them throw "javax.jms.IllegalStateException: The Session is closed" when proces the request. 2017-07-04 16:13 GMT-04:00, nelson rivera : > One peculiarity is that, is a primitive annotator implented in c++, > but is deployed with de deployAsyncService.sh de uima-as directly. > > 2017-07-04 14:53 GMT-04:00, nelson rivera : >> 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 after 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. >> >> Wich is the best way to know when connections betewen cliente uima-as >> and ActiveMQ is broken? and i should restart uima-as client. >> >
Re: Broken conections after ACTIVEMQ restart with service uima-as CasMultiplier and delegate remote
Hi, the above problem is a different issue from the Session Closed reported earlier which occurs in the uima-as client. Please provide a stack trace for that. The issue you are reporting above is an expected behavior. The remote is trying to deliver msgs to a temp reply queue which no longer exists due to a broker restart. JMS temp queues are transient and not recoverable. If a broker is restarted while uima-as service is processing a CAS, that service will not be able to reply. Any new CASes (sent after broker restart) will have a valid temp queue and replies will succeed. Jerry On Wed, Jul 5, 2017 at 9:55 AM, nelson rivera wrote: > i have a aggregate service uima-as that it contains a CasMultiplier, > after this casmultiplier in the flow one of the delegates is remote. > The delegate remote is a primitive annotator implented in c++,but is > deployed with de deployAsyncService.sh de uima-as directly. > > With these step i get the error that shows > > 1- Start all components (broker , agregate service, remote service). > 2- First request, process ok > 3- Restart broker (without restart services uima-as). //Logs shows > Ready to Process Again > 4- Second request, process ok > 5- Restart broker, second (without restart services uima-as). //Logs > show Ready to Process Again > 6- I get a error, shows following lines in the log of the delegate > sevice uima-as remote. > Attachs images of the queues created at all time in case it is of > help. The remote service delegate is XLangdetector and service > agregate casmultiplier is XClusterAnalyzerAggregate. > > Errors Lines: > Recovered Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process > Again > 09:27:19.705 - 18: > org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : > Begin -> XLangDetector::process --- OK > 09:27:19.707 - 18: > org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End > -> XLangDetector::process --- OK > 09:27:19.710 - 3645: > org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send: > WARNING: Controller: XLangDetector Failed To Send Message to Delegates > Queue: null > 09:27:19.721 - 3645: > org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl. > UimaAsAsyncCallbackListener.onException(): > INFO: Service:XLangDetector JMS unable to Deliver > CAS:-4f7adbed:15d12e82d61:-7fc7 - > Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1 > 09:27:19.721 - 3645: > org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl. > UimaAsAsyncCallbackListener.onException(): > INFO: Controller: XLangDetector Handling Release CAS Request. > Releasing CAS Reference Id: -4f7adbed:15d12e82d61:-7fc7 > 09:27:19.722 - 3645: > org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send: > WARNING: Controller: XLangDetector Failed To Send Message to Delegates > Queue: null > 09:27:19.722 - 19: > org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : > Begin -> XLangDetector::process --- OK > 09:27:19.723 - 3645: > org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send: > WARNING: Controller: XLangDetector Failed To Send Message to Delegates > Queue: null > 09:27:19.724 - 17: > org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : > Begin -> XLangDetector::process --- OK > 09:27:19.725 - 17: > org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End > -> XLangDetector::process --- OK > 09:27:19.727 - 19: > org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End > -> XLangDetector::process --- OK > 09:27:19.732 - 20: > org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : > Begin -> XLangDetector::process --- OK > 09:27:19.734 - 20: > org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End > -> XLangDetector::process --- OK > 09:27:19.737 - 3645: > org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send: > WARNING: Controller: XLangDetector Failed To Send Message to Delegates > Queue: null > 09:27:19.738 - 3645: > org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl. > UimaAsAsyncCallbackListener.onException(): > INFO: Service:XLangDetector JMS unable to Deliver > CAS:-4f7adbed:15d12e82d61:-7fc8 - > Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1 > 09:27:19.738 - 3645: > org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl. > UimaAsAsyncCallbackListener.onException(): > INFO: Controller: XLangDetector Handling Release CAS Request. > Releasing CAS Reference Id: -4f7adbed:15d12e82d61:-7fc8 > 09:27:19.738 - 3645: > org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl. > UimaAsAsyncCallbackListener.onException(): > INFO: Service:XLangDetector JMS unable to Deliver > CAS:-4f7adbed:15d12e82d61:-7fc5 - > Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1 > 09:27:19.739 - 3645: > org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl. > UimaAsAsyncCallbackListener.onException(): > INFO: Controller: XLangDe
Broken conections after ACTIVEMQ restart with service uima-as CasMultiplier and delegate remote
i have a aggregate service uima-as that it contains a CasMultiplier, after this casmultiplier in the flow one of the delegates is remote. The delegate remote is a primitive annotator implented in c++,but is deployed with de deployAsyncService.sh de uima-as directly. With these step i get the error that shows 1- Start all components (broker , agregate service, remote service). 2- First request, process ok 3- Restart broker (without restart services uima-as). //Logs shows Ready to Process Again 4- Second request, process ok 5- Restart broker, second (without restart services uima-as). //Logs show Ready to Process Again 6- I get a error, shows following lines in the log of the delegate sevice uima-as remote. Attachs images of the queues created at all time in case it is of help. The remote service delegate is XLangdetector and service agregate casmultiplier is XClusterAnalyzerAggregate. Errors Lines: Recovered Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again 09:27:19.705 - 18: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : Begin -> XLangDetector::process --- OK 09:27:19.707 - 18: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End -> XLangDetector::process --- OK 09:27:19.710 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send: WARNING: Controller: XLangDetector Failed To Send Message to Delegates Queue: null 09:27:19.721 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException(): INFO: Service:XLangDetector JMS unable to Deliver CAS:-4f7adbed:15d12e82d61:-7fc7 - Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1 09:27:19.721 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException(): INFO: Controller: XLangDetector Handling Release CAS Request. Releasing CAS Reference Id: -4f7adbed:15d12e82d61:-7fc7 09:27:19.722 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send: WARNING: Controller: XLangDetector Failed To Send Message to Delegates Queue: null 09:27:19.722 - 19: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : Begin -> XLangDetector::process --- OK 09:27:19.723 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send: WARNING: Controller: XLangDetector Failed To Send Message to Delegates Queue: null 09:27:19.724 - 17: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : Begin -> XLangDetector::process --- OK 09:27:19.725 - 17: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End -> XLangDetector::process --- OK 09:27:19.727 - 19: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End -> XLangDetector::process --- OK 09:27:19.732 - 20: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : Begin -> XLangDetector::process --- OK 09:27:19.734 - 20: org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End -> XLangDetector::process --- OK 09:27:19.737 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send: WARNING: Controller: XLangDetector Failed To Send Message to Delegates Queue: null 09:27:19.738 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException(): INFO: Service:XLangDetector JMS unable to Deliver CAS:-4f7adbed:15d12e82d61:-7fc8 - Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1 09:27:19.738 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException(): INFO: Controller: XLangDetector Handling Release CAS Request. Releasing CAS Reference Id: -4f7adbed:15d12e82d61:-7fc8 09:27:19.738 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException(): INFO: Service:XLangDetector JMS unable to Deliver CAS:-4f7adbed:15d12e82d61:-7fc5 - Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1 09:27:19.739 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException(): INFO: Controller: XLangDetector Handling Release CAS Request. Releasing CAS Reference Id: -4f7adbed:15d12e82d61:-7fc5 09:27:19.739 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException(): INFO: Service:XLangDetector JMS unable to Deliver CAS:-4f7adbed:15d12e82d61:-7fc6 - Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1 09:27:19.739 - 3645: org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException(): INFO: Controller: XLangDetector Handling Release CAS Request. Releasing CAS Reference Id: -4f7adbed:15d12e82d61:-7fc6.