[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AWIPS #CZX-735454]: Awips2 ldm/edexBridge question

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [AWIPS #CZX-735454]: Awips2 ldm/edexBridge question
  • Date: Wed, 14 Dec 2016 12:53:31 -0700
> Sorry to bother you again about this, but just wanted to see if you found
> out anything about this edexBridge issue I'm seeing.
>

I don't experience this on my servers, though I do see edexBridge sending
in 1000 messages sets here and there, I do not see any long latencies.  The
most obvious solution is to reduce the amount on data being processed by
EDEX, but you may want to re-build the edexBridge binary with a greater max
number of messages and see if you notice a performance benefit.  You can
grab the source from
https://raw.githubusercontent.com/Unidata/awips2/unidata_16.2.2/nativeLib/edexBridge/edexBridge.cpp
and issue the command

g++ edexBridge.cpp -I/usr/local/ldm/src/pqact \
   -I/usr/local/ldm/include \
   -I/usr/local/ldm/src \
   -I/awips2/qpid/include \
   -L/usr/local/ldm/lib \
   -L/awips2/qpid/lib \
   -l ldm -l xml2 -l qpidclient -l qpidmessaging -l qpidcommon -l qpidtypes
-o edexBridge

You'll need awips2-qpid-lib, gcc, libtool, and maybe other packages
installed.

Again, your EDEX is the Raytheon deployment and I'm not experiencing this
problem with Unidata EDEX.  You may want to contact someone at Raytheon or
NWS to ask more about this since Raytheon authored edexBridge.



Ticket Details
===================
Ticket ID: CZX-735454
Department: Support AWIPS
Priority: High
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.