NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: [awips2-users] AMQException Timeout Warning/Error

  • To: Keith Latteri <keith@xxxxxxxxxxxxxxxxx>
  • Subject: Re: [awips2-users] AMQException Timeout Warning/Error
  • From: Brian Bernard <bbernard@xxxxxxxxxxxx>
  • Date: Wed, 1 Feb 2017 20:38:41 +0000
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=bbernard@xxxxxxxxxxxx;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
Hi Keith,

I did an edex status, and it showed qpidd running. However, I stopped and 
re-started the qpidd service, but then it showed neither qpidd or grib ingest 
was started. Finally I did an edex stop, deleted edexMessageStore, then 
restarted edex, and all is now well.

-Brian Bernard

From: Keith Latteri [mailto:keith@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, February 01, 2017 10:08 AM
To: Brian Bernard <bbernard@xxxxxxxxxxxx>
Cc: awips2-users@xxxxxxxxxxxxxxxx
Subject: Re: [awips2-users] AMQException Timeout Warning/Error

Brian,

Verify that qpid is running by doing “edex status”, or just restart by doing 
“service qpidd restart”. I usually restart qpidd when I have this issue.


On Feb 1, 2017, at 9:20 AM, Brian Bernard 
<bbernard@xxxxxxxxxxxx<mailto:bbernard@xxxxxxxxxxxx>> wrote:

Hello,

I'm getting this error in my edex-ingestGrib log files:

"
INFO  2017-02-01 13:53:25,644 [Ingest.GribDecode-3] JmsPooledConsumer: EDEX - 
Closing AMQ consumer Ingest.GribDecode
INFO  2017-02-01 13:53:25,648 [Ingest.GribDecode-6] JmsPooledConsumer: EDEX - 
Closing AMQ consumer Ingest.GribDecode
INFO  2017-02-01 14:00:07,101 [Camel (camel) thread #5 - 
timer://jmsPooledResourceCheck] AMQConnection: Not a hard-error connection not 
closing: org.apache.qpid.AMQException: timed out waiting for sync: complete = 
611, point = 613 [error code 541: internal error]
INFO  2017-02-01 14:00:07,103 [Ingest.GribDecode-1] AMQConnection: Not a 
hard-error connection not closing: org.apache.qpid.AMQException: timed out 
waiting for sync: complete = 1224013, point = 1224015 [error code 541: internal 
error]
INFO  2017-02-01 14:00:07,103 [Ingest.GribDecode-4] AMQConnection: Not a 
hard-error connection not closing: org.apache.qpid.AMQException: timed out 
waiting for sync: complete = 1257603, point = 1257605 [error code 541: internal 
error]
INFO  2017-02-01 14:00:07,103 [Ingest.GribDecode-8] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@5270916d<mailto:com.raytheon.uf.common.jms.JmsPooledSession@5270916d>
INFO  2017-02-01 14:00:07,103 [Ingest.GribDecode-7] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@16d07fb6<mailto:com.raytheon.uf.common.jms.JmsPooledSession@16d07fb6>
INFO  2017-02-01 14:00:07,103 [Ingest.ncGrib-2] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@16563aba<mailto:com.raytheon.uf.common.jms.JmsPooledSession@16563aba>
INFO  2017-02-01 14:00:07,103 [Ingest.GribDecode-5] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@2a637927<mailto:com.raytheon.uf.common.jms.JmsPooledSession@2a637927>
INFO  2017-02-01 14:00:07,103 [edex.alerts.utility-1] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@4ae796e4<mailto:com.raytheon.uf.common.jms.JmsPooledSession@4ae796e4>
INFO  2017-02-01 14:00:07,103 [Ingest.ncGrib-1] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@2d4544af<mailto:com.raytheon.uf.common.jms.JmsPooledSession@2d4544af>
INFO  2017-02-01 14:00:07,103 [Grid.PostProcess-1] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@7713e415<mailto:com.raytheon.uf.common.jms.JmsPooledSession@7713e415>
INFO  2017-02-01 14:00:07,103 [grid-staticdata-generate-1] JmsPooledSession: 
EDEX - Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@3003bbfc<mailto:com.raytheon.uf.common.jms.JmsPooledSession@3003bbfc>
INFO  2017-02-01 14:00:07,103 [Ingest.GribSplit-2] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@249e425e<mailto:com.raytheon.uf.common.jms.JmsPooledSession@249e425e>
INFO  2017-02-01 14:00:07,103 [Ingest.GribSplit-2] JmsPooledProducer: EDEX - 
Closing AMQ producer Ingest.GribDecode
INFO  2017-02-01 14:00:07,103 [Ingest.GribDecode-2] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@336ad83d<mailto:com.raytheon.uf.common.jms.JmsPooledSession@336ad83d>
INFO  2017-02-01 14:00:07,103 [Ingest.GribSplit-1] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@3654ccc3<mailto:com.raytheon.uf.common.jms.JmsPooledSession@3654ccc3>
INFO  2017-02-01 14:00:07,103 [Ingest.GribSplit-1] JmsPooledProducer: EDEX - 
Closing AMQ producer Ingest.GribDecode
INFO  2017-02-01 14:00:07,103 [purgeGridInfoCache-1] JmsPooledSession: EDEX - 
Closing session: 
com.raytheon.uf.common.jms.JmsPooledSession@3e6079f6<mailto:com.raytheon.uf.common.jms.JmsPooledSession@3e6079f6>
WARN  2017-02-01 14:00:07,103 [Ingest.GribDecode-4] JmsPooledConsumer: EDEX - 
Failed to close consumer 
org.apache.qpid.client.BasicMessageConsumer_0_10@11c7ae1c<mailto:org.apache.qpid.client.BasicMessageConsumer_0_10@11c7ae1c>
org.apache.qpid.client.JMSAMQException: Error closing consumer: 
org.apache.qpid.AMQException: timed out waiting for sync: complete = 1257603, 
point = 1257605 [error code 541: internal error]
    at 
org.apache.qpid.client.BasicMessageConsumer.close(BasicMessageConsumer.java:627)
 ~[qpid-client-0.32.jar:0.32]
    at 
org.apache.qpid.client.BasicMessageConsumer.close(BasicMessageConsumer.java:578)
 ~[qpid-client-0.32.jar:0.32]
    at 
com.raytheon.uf.common.jms.JmsPooledConsumer.close(JmsPooledConsumer.java:185) 
[com.raytheon.uf.common.jms.jar:na]
    at 
com.raytheon.uf.common.jms.JmsPooledConsumer.removeReference(JmsPooledConsumer.java:222)
 [com.raytheon.uf.common.jms.jar:na]
    at 
com.raytheon.uf.common.jms.wrapper.JmsConsumerWrapper.close(JmsConsumerWrapper.java:106)
 [com.raytheon.uf.common.jms.jar:na]
    at 
org.springframework.jms.support.JmsUtils.closeMessageConsumer(JmsUtils.java:151)
 [spring-jms-4.1.6.RELEASE.jar:4.1.6.RELEASE]
    at 
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:348)
 [spring-jms-4.1.6.RELEASE.jar:4.1.6.RELEASE]
    at 
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:246)
 [spring-jms-4.1.6.RELEASE.jar:4.1.6.RELEASE]
    at 
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1144)
 [spring-jms-4.1.6.RELEASE.jar:4.1.6.RELEASE]
    at 
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1136)
 [spring-jms-4.1.6.RELEASE.jar:4.1.6.RELEASE]
    at 
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1033)
 [spring-jms-4.1.6.RELEASE.jar:4.1.6.RELEASE]
    at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
[na:1.7.0_80]
    at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
[na:1.7.0_80]
    at java.lang.Thread.run(Thread.java:745) [na:1.7.0_80]
Caused by: org.apache.qpid.AMQException: timed out waiting for sync: complete = 
1257603, point = 1257605
    at 
org.apache.qpid.client.AMQSession_0_10.setCurrentException(AMQSession_0_10.java:1082)
 ~[qpid-client-0.32.jar:0.32]
    at 
org.apache.qpid.client.BasicMessageConsumer_0_10.sendCancel(BasicMessageConsumer_0_10.java:175)
 ~[qpid-client-0.32.jar:0.32]
    at 
org.apache.qpid.client.BasicMessageConsumer.close(BasicMessageConsumer.java:620)
 ~[qpid-client-0.32.jar:0.32]
    ... 13 common frames omitted

It just cropped up over the past few days.

Thank you,

Brian Bernard

_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web.  Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.


awips2-users mailing list
awips2-users@xxxxxxxxxxxxxxxx<mailto:awips2-users@xxxxxxxxxxxxxxxx>
For list information, to unsubscribe, or change your membership options, visit: 
http://www.unidata.ucar.edu/mailing_lists/
  • 2017 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the awips2-users archives: