What is this state meant by "(409) String Too Big"

I am trying to POST data to reuters using Postconsumer example and I am getting below response message.
Msg Type: MsgType.ACK_RESP
Msg Model Type: MARKET_PRICE
Indication Flags:
Hint Flags: HAS_ATTRIB_INFO | HAS_ID | HAS_STATE
State: UNSPECIFIED, NO_CHANGE, NACK_DENIED_BY_SRC, "(409) String Too Big"
Id: 1
When I try to Post one field entry getting ACK successful, when trying to Post 10 fieldentries is not successful and getting above message.
UPDATE:
Below is the data we want to post and we are
receiving “(409) String Too Big”.
With RFA 7 Java we are available to post it but with RFA 8 Java getting above message
FID
ACRONYM
DATA
LENGTH
--------------------------------------------------------------------------------------------------------------
[ 316 ] [ ROW80_2 ] '
' 80
[ 318 ] [ ROW80_4 ]
'|DAYS |RATE
|TARGET AMOUNT ||DAYS
|RATE |TARGET AMOUNT ' 80
[ 317 ] [ ROW80_3 ]
' PROGRAM FOR
xx/xx/xx
' 80
[ 332 ] [ ROW80_18 ] '[ FOR MORE
INFORMATION CALL xxx-xxx-xxx SUBJECT TO DISCLAIMER ON
PG xxxxx ]' 80
[ 323 ] [ ROW80_9 ]
'|
| |
||
|
|
' 80
[ 328 ] [ ROW80_14 ]
'|
|
|
||
|
|
' 80
[ 320 ] [ ROW80_6 ]
'|
|
|
||
| |
' 80
[ 329 ] [ ROW80_15 ]
'|
|
|
||
| |
' 80
[ 319 ] [ ROW80_5 ]
'|x/xx-xx |x.xxx
| x.xxx N/A
||
| |
' 80
[ 330 ] [ ROW80_16 ]
'|
|
|
||
|
|
' 80
[ 322 ] [ ROW80_8 ]
'|
|
|
||
|
|
' 80
[ 331 ] [ ROW80_17 ]
'|
|
|
||
|
|
' 80
[ 321 ] [ ROW80_7 ]
'|
|
|
||
|
|
' 80
[ 325 ] [ ROW80_11 ]
'|
|
|
||
|
|
' 80
[ 324 ] [ ROW80_10 ]
'|
|
|
||
|
|
' 80
[ 327 ] [ ROW80_13 ]
'|
|
|
||
|
|
' 80
[ 326 ] [ ROW80_12 ]
'|
|
|
||
|
|
' 80
From RDMFieldDictionary
!ACRONYM DDE ACRONYM FID RIPPLES TO FIELD TYPE LENGTH RWF TYPE RWF LEN
!------- ----------- --- ---------- ---------- ------ -------- -------
ROW80_2 "IRGROW 2" 316 NULL ALPHANUMERIC 80 RMTES_STRING 80
In dictionary also it is specified to be length of 80 and Data String we trying to POST is also length of 80. We are not trying to POST a Data String of greater than 80.
Best Answer
-
The case 05145983 has been created for this question. The cause is using encodeRmtesString(..) to encode one-byte ASCII. The method adds additional 3 characters while encoding. Since the length of string is 80, the total length of the string after encoding with this method exceeds the maximum(80) defined in the dictionary. That's why the application receives "(409) String Too Big" error from the feed.
To fix the problem, encodeString(String, OMMTypes.RMTES_STRING) should be used for encoding one-byte ASCII instead. Normally, encodeRmtesString(..) is used when the string includes international data. For more detail of both methods, please refer to Interface OMMEncoder in RFAJ document: <RFAJ
package>\Docs\refman\rfajava\com\reuters\rfa\omm\OMMEncoder.html0
Answers
-
Hello @applicationdevelopment
"(409) String Too Big" is generated
from the provider i.e. Marketlink-IP that you post data to via TREP. This means
a post message contains a string, which is too long for the FID definition.
Check the post message for long or incorrect strings that has
the same sequence number as this error message.0 -
@Pimchaya.Wongrukun
Updated the question with data we are trying to POST. All FID data String length is 80. I don't understand what's the issue. Explain what difference between RFA 7 Java Contribute vs RFA 8 JAVA PostingConsumer.
0 -
Hello @applicationdevelopment
Please see my response in the email "Please submit the query for applicationdevelopment@fhlb-of.com question: "What is this state meant by "(409) String Too Big""" which I have sent to you(applicationdevelopment@fhlb-of.com)
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.4K 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
- 559 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
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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 中文论坛