OmmPool.acquireCopy() - does it copy everything exactly?
During the client.processEvent() handler, we take a copy of the OMMMsg using OMMPool.acquireCopy() and store it for later processing on a separate thread.
When we come to parse this message, we seem to see a problem with parsing OmmTypes.TIME, specifically we end up with the wrong date.
Code sample:
case OMMTypes.TIME:
OMMDateTime ommdateTime = (OMMDateTime) value;
if (!ommdateTime.isBlank()) {
if (fidDef.getMaxOMMLengthAsInt() == 8) {
long millisSinceEpoch = ommdateTime.toSeconds();
int microS = ommdateTime.getMicrosecond();
int nanoS = ommdateTime.getNanosecond();
long nanosSinceEpoc = millisSinceEpoch*1000000 + (microS<1000 ? microS*1000 : 0) + (nanoS<1000 ? nanoS : 0);
.....
An example field would be QUOTIM_NS
When we look at nanosSinceEpoc as a DataTime, it has a plausible time component, but that the date component appears to stick to the date that the process started. It doesn't change at 00:00:00 as might be expected.
When we DO NOT copy the message using OMMPool.acquireCopy() , but instead parse the original message, we see the date behaving as expected.
This is with Java RFA version 8.1.3.E2
Best Answer
-
Hello @d.hancock ,
I think you are reporting a suspected issue on Java RFA version 8.1.3.E2.
The suspected issue would need to be reproduced, verified and investigated in detail as the next step.
JRFA has underwent mandatory rebranding. To learn more of RFA rebranding, please see Product Change Notification (PCN) detailing the changes and requirements. Any suspected issue report would be eligible for a prioritization to a fix in a re-branded version, and need to be reproduced in the re-branded version.
Would like to suggest to try re-test the scenario in the latest re-branded version 8.2, and if the issue does not manifest, to migrate to the latest, while if it continues to manifest, as your organization is a Premium Support member, to submit the suspected issue as Premium support case, by one of your organization's Premium Support members, for the detailed verification and investigation, further action dependent on the findings.
0
Answers
-
(I notice in the docs for acquireCopy(), it says
"This may not be an exact copy of the internal wire format, based on readOnlyCopy and optimizations."0 -
Could it be that the Calendar uses in OMMDateTime.toSeconds() isn't being copied/updated correctly?
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.8K Refinitiv Data Platform
- 622 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛