How to verify that compression is being used?
Hi,
I have configured an OMM Consumer application to use zlib compression using the compressionType parameter set to ZLib in the configuration file.
In the RFA logs I can see a message like the following:
(ComponentName) RSSL_Cons_Adapter: (Severity) Information: Using
the following configuration for RSSL_Cons_Connection
"Default::Connection_EMEA `treprt1:14003": hostName =
"localhost", rsslPort = "14003", interfaceName = "treprt1", compressionType = 1,
channelBlocking = false, recvBufSize = 65535, sendBufSize =
65535, writeBufferMaxFragmentLength = 6144,
connectionWaitTimeout = 30000, connectionPingTimeout = 30000,
guaranteedOutputBuffers = 400, numInputBuffers = 20, tcp_nodelay
= True, throttleEnabled = True, throttleType = count,
throttleMaxCount = 250, throttleBatchCount = 10, traceMsg =
False, traceMsgToFile = True, dictionaryRequestTimeout = 45
The message indicates that the compression parameter was read correctly from the configuration file.
Using the 'adsmon' utility under "Sink Mount Statistic" I see that the connection is using ZLib or using Wireshark/tcpdump.
But on the client side I have not seen a way to verify if compression is being used or not.
Is there any way via logging or otherwise to do so?
Best Answer
-
From my finding, the compression information is not available in RFA log and the application is unable to access it.
RFA has a session layer used to manage all connections used by the application. The consumer application is unable to directly access connections to get the compression information. The connection events that the session layer can provide to the application are:
- OMMConnectionEvent contains connection information, such as connection status, active host name, port, and the version information of connected component
- OMMConnectionStatsEvent contains information on connection statistics (bytes on wire)
In conclusion, RFA client side is unable to get compression information of the connection.
0
Answers
-
@Steven
I am not sure if I understand the question.
Do you mean if it possible to programmatically verify if compression is being used? Like function call that check compression type or event that gives compression type?
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 722 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛