Plz Help! : Internal Error. Failed to allocated TransportBuffer in TunnelItem.submitSubItemMsg
ClientName: TunnelItem
Severity: Error
Text: Internal Error. Failed to allocated TransportBuffer in TunnelItem.submitSubItemMsg
Best Answer
-
Hello Khun @Jirapongse,
I'm Ohm from the same team with @lenny.cm.
How can we call the value of GuaranteedOutputBuffers in EmaConfig.xml to be used in tsr in our code?
This is our code when creating a tunnel connection
val consumer = EmaFactory
.createOmmConsumer(
EmaFactory
.createOmmConsumerConfig("/path/to/EmaConfig.xml")
.tunnelingKeyStoreFile(emaConfig.privateKey)
.tunnelingKeyStorePasswd(emaConfig.privateKeyPassword)
)
val tsr: TunnelStreamRequest = EmaFactory
.createTunnelStreamRequest()
.classOfService(
EmaFactory.createClassOfService
.authentication(EmaFactory.createCosAuthentication.`type`(CosAuthentication.CosAuthenticationType.NOT_REQUIRED))
.dataIntegrity(EmaFactory.createCosDataIntegrity.`type`(CosDataIntegrity.CosDataIntegrityType.RELIABLE))
.flowControl(EmaFactory.createCosFlowControl.`type`(CosFlowControl.CosFlowControlType.BIDIRECTIONAL).recvWindowSize(1200))
.guarantee(EmaFactory.createCosGuarantee.`type`(CosGuarantee.CosGuaranteeType.NONE))
)
.domainType(EmaRdm.MMT_SYSTEM)
.name("tunnel")
.serviceName("DDS_TRCE")
//tunnel stream handle (a.k.a. parentHandle)
val tunnelStreamHandle = consumer.registerClient(tsr, this)And this is our EmaConfig.xml
<?xml version="1.0" encoding="UTF-8"?>
<EmaConfig>
<!-- see EMAJ_ConfigGuide.pdf for details -->
<ConsumerGroup>
<DefaultConsumer value="Consumer_TRCC"/>
<ConsumerList>
<Consumer>
<Name value="TRCC_CONSUMER"/>
<Channel value="Channel_TRCC"/>
<Dictionary value="Dictionary_TRCC"/>
<XmlTraceToStdout value="0" />
</Consumer>
</ConsumerList>
</ConsumerGroup>
<ChannelGroup>
<ChannelList>
<Channel>
<Name value="Channel_TRCC"/>
<ChannelType value="ChannelType::RSSL_ENCRYPTED"/>
<TcpNodelay value="1"/>
<GuaranteedOutputBuffers value="5000"/>
<ConnectionPingTimeout value="30000"/>
<Host value="contrib01-apac1.platform.refinitiv.biz"/>
<Port value="443"/>
</Channel>
</ChannelList>
</ChannelGroup>
<DictionaryGroup>
<DictionaryList>
<Dictionary>
<Name value="Dictionary_TRCC"/>
<DictionaryType value="DictionaryType::FileDictionary"/>
<RdmFieldDictionaryFileName value="/path/to/RDMFieldDictionary"/>
<EnumTypeDefFileName value="/path/to/enumtype.def"/>
</Dictionary>
</DictionaryList>
</DictionaryGroup>
</EmaConfig>0
Answers
-
Hello Refinitiv Team, please kindly help with these errors we got the errors to message multiple times, our application using EMA java
Is this something about the limitation with the message size and rate? would be great if you could shed the light on this issue for us, many thanks.
0 -
0
-
FYI : not sure this would related or not, in my EMA config file the current setup
<TcpNodelay value="1"/>
<GuaranteedOutputBuffers value="5000"/>
<ConnectionPingTimeout value="30000"/>0 -
Thank you khun Jiraponse for the quick reply, I will share this with our Dev team
0 -
If you are using TunnelStreamRequest, you need to set it in the TunnelStreamRequest.
0 -
As I know, OmmConsumerConfig is designed for a client to set config info, not for reading. You can't use OmmConsumerConfig to access the value.
You need to develop a function to parse that EmaConfig.xml file and read the GuaranteedOutputBuffers and then set it to tsr.guaranteedOutputBuffers(int outBuffers);
0 -
I noticed that your <DefaultConsumer value="Consumer_TRCC"/> and the consumer name configurations are not matching.
I have tried your EmaConfig.xml file with the Contribution example (from this article) and the following code and it works fine.
OmmConsumer consumer = EmaFactory.createOmmConsumer(
EmaFactory.createOmmConsumerConfig("C:\drive_d\Project\APIs\EMA_Code\EMA_Java_200_Maven\src\main\java\com\refinitiv\ema\examples\training\consumer\series300\ex342_MP_RCC\\EmaConfigAHS.xml")
.consumerName("TRCC_CONSUMER").tunnelingKeyStoreFile(keyStoreFileName)
.tunnelingKeyStorePasswd(keyStorePassword)
);0 -
Kob khun krub,
This is very helpful. We'll let our dev team know this info.
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
- 3 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
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛