IndexOutOfBoundsException publishing a large RFA SymbolList

The following exception appears in RFA/Java when publishing a symbol list with ~3,000 instruments as the constituents of NYSE:
2016-06-22 13:04:19,034 ERROR [main] Shinboru(Shinboru.java:466): catching
java.lang.IndexOutOfBoundsException
at com.reuters.io.ArrayWriter.checkRemaining(Unknown Source)
at com.reuters.io.DataArrayWriterWireFormatV1.writeByte(Unknown Source)
at com.reuters.io.DataArrayWriter.writeByte(Unknown Source)
at com.reuters.rfa.internal.rwf.RwfEncoder.encodeFieldListInit(Unknown Source)
at Shinboru.OnRequest(Shinboru.java:510)
at Provider.republish(Provider.java:749)
at Provider.OnDictionaryResponse(Provider.java:735)
at Provider.OnRespMsg(Provider.java:588)
at Provider.OnOMMItemEvent(Provider.java:565)
at Provider.processEvent(Provider.java:534)
at com.reuters.rfa.internal.common.ResponseMessage.dispatchToClient(Unknown Source)
at com.reuters.rfa.internal.common.ResponseMessage.dispatch(Unknown Source)
at com.reuters.rfa.internal.common.EventQueueImpl.localDispatch(Unknown Source)
at com.reuters.rfa.internal.common.EventQueueImpl.dispatch(Unknown Source)
at Shinboru.mainloop(Shinboru.java:460)
at Shinboru.run(Shinboru.java:432)
at Shinboru.main(Shinboru.java:570)
Re-implementing the provider in UPA/Java did not encounter similar issues.
RFA/Java provider source code, UPA/Java provider source code (please note the line numbers differ from the above trace).
edit: With additional trace the symbol list fails at item #2957.
edit #2: Tried with increased buffer 65,535 bytes to no avail.
The actual source code used above, basically adds DSS/REST request: shinborujava.txt
Best Answer
-
What happens if your increase the size of your encoder ?
Currently you have it at 5000 bytes. (OMM_PAYLOAD_SIZE)
0
Answers
-
RFA/Java is unlike C++ technically supposed to take the payload size as a hint and automatically increase the buffer as needed. I have however tried with a buffer size of 65535 bytes with no change in result.
0 -
I guess the RFA encoder is simply a lot more inefficient than the UPA one, increasing to 100,000 bytes worked.
0 -
Yeah, well, I'm not sure what the downside is of allocating say 100K to the encoder always. I guess what happens in the background is that some byte array of the size of 100K is allocated. Most applications will tend to say: so what? Personally this is what I would do to avoid getting obscure errors - even if my real requirement is a lot smaller.
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
- 724 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 中文论坛