uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <...@uima.apache.org>
Subject [jira] [Updated] (UIMA-4546) UIMA-AS client not recovering when broker connection is lost
Date Fri, 11 Dec 2015 14:23:11 GMT

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

Jerry Cwiklik updated UIMA-4546:
--------------------------------
    Fix Version/s:     (was: 2.8.1AS)
                   2.8.2AS

> UIMA-AS client not recovering when broker connection is lost
> ------------------------------------------------------------
>
>                 Key: UIMA-4546
>                 URL: https://issues.apache.org/jira/browse/UIMA-4546
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.6.0AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.8.2AS
>
>
> The UIMA-AS client reports:
> Jul 31, 2015 1:35:50 PM org.apache.uima.adapter.jms.client.ActiveMQMessageSender reject
> INFO: UIMA AS Client Message Dispatcher Rejecting Process Request - the Broker Is Not
Available.
> Jul 31, 2015 1:35:50 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl
handleException
> INFO: Received Exception In Message From Service on Queue:UimaASClient Broker: tcp://broker1:61616
Cas Identifier:94c42d8:14ee51d8e71:-783c Exception:org.a\
> pache.uima.jms.error.handler.BrokerConnectionException: Unable To Deliver Message To
Destination. Connection To Broker tcp://broker1:61616 Has Been Lost
> Jul 31, 2015 1:35:50 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$SharedConnection
retryConnectionUntilSuccessfull
> WARNING: UIMA AS Client Has Lost Connection To Broker:tcp://broker1:61616 Retrying Connection
every 5secs until successful. Is Client Stopped:
> Jul 31, 2015 1:35:50 PM 
> Jul 31, 2015 1:35:50 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl
sendCAS
> INFO: Uima AS Client Sent PING Message To Service: fastqa-2015-28
> Jul 31, 2015 1:35:50 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
initializeConsumer
> INFO: Initializing JMS Message Consumer. Broker: tcp://broker1:61616 Queue Name: ID:XXX-35499-1438363236054-1:2:1
> Jul 31, 2015 1:35:50 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
initializeConsumer
> INFO: Initializing JMS Message Consumer. Broker: tcp://broker1:61616 Queue Name: ID:XXX-35499-1438363236054-1:2:2
> Jul 31, 2015 1:35:50 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
initializeConsumer
> INFO: Initializing JMS Message Consumer. Broker: tcp://broker1:61616 Queue Name: ID:XXX-35499-1438363236054-1:2:3
> Jul 31, 2015 1:35:50 PM org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$SharedConnection
retryConnectionUntilSuccessfull
> INFO: UIMA AS Client Recovered Connection to Broker: tcp://broker1:61616
> Jul 31, 2015 1:36:21 PM org.apache.uima.aae.delegate.Delegate$2 Delegate.TimerTask.run
> WARNING: Timeout While Waiting For Reply From Delegate:fastqa-2015-28 GetMeta Request
Timed Out. Configured Reply Window Of 30,000.
> Jul 31, 2015 1:36:21 PM org.apache.uima.adapter.jms.client.ClientServiceDelegate handleError
> WARNING:
>         ***** WARNING: Service: fastqa-2015-28 Didn't Respond To Ping. PendingDispatchList
Size:1 PendingReplyList size:9
> Jul 31, 2015 1:36:21 PM org.apache.uima.adapter.jms.client.ClientServiceDelegate handleError
> WARNING: UIMA AS Client Forcing Timeout on CAS: 94c42d8:14ee51d8e71:-783b (Hashcode:-1865482558)
from PendingDispatch list. Unable to Dispatch the CAS Due \
> to Service Not Responding to a GetMeta ping.
> It looks like the connection is being recovered but the subsequent GetMet Ping requests
timed out for some reason. This was not caused by a broker since I was able to connect a test
client to the service and GetMeta worked just fine.Strange that this client fails since there
are jUnit tests in extended test that force recovery after connection loss. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message