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.
"Unable to connect to broker" indicates that Qpid may be down and needs to be restarted. Check the log files in /awips2/qpid/log/ and if you see Java heap memory error messages then you'll need to stop qpid and remove the message queue before starting again: service qpidd stop rm -rf /awips2/qpid/messageStore/edex service qpidd start Michael James Unidata Program Center Boulder, CO On Wed, Feb 25, 2015 at 3:17 PM, <admin@xxxxxxxx> wrote: > Grid and some other data stopped storing. Getting this error in the edex > log: > > > > INFO 2015-02-25 22:15:26,426 [edex.alerts.utility-1] > FailoverSingleServer: Delay between connect retries:5000 > INFO 2015-02-25 22:15:26,654 [practiceActiveTable-1] AMQConnection: > Unable to connect to broker at > tcp://awips2-edex:5672?connectdelay='5000'&connecttimeout='5000'&heartbeat='0'&retries='9999' > > > > Nothing showing in netstat using 5672 what stopped running? > > > > > > Ray Weber > > > > > > _______________________________________________ > awips2-users mailing list > awips2-users@xxxxxxxxxxxxxxxx > For list information, to unsubscribe, or change your membership options, > visit: http://www.unidata.ucar.edu/mailing_lists/ > >
awips2-users
archives: