EMA error after running for 2 hours (Error text SocketChannel.read returned -1 (end-of-stream))
I subscribed few hundreds RIC (stock + options) for MARKET_PRICE & MARKET_BY_PRICE.
Running fine and after an hour or 2, it stopped with following message from log.
Using EMA Java 1.2.1 on windows 7.
Oct 23, 2018 10:39:18 AM com.thomsonreuters.ema.access.ChannelCallbackClient reactorChannelEventCallback WARNING: loggerMsg ClientName: ChannelCallbackClient Severity: Warning Text: Received ChannelDownReconnecting event on channel Channel_2 RsslReactor @7744ad0d RsslChannel @2bb02195 Error Id 0 Internal sysError 0 Error Location null Error text SocketChannel.read returned -1 (end-of-stream) loggerMsgEnd Oct 23, 2018 10:39:23 AM com.thomsonreuters.ema.access.ChannelCallbackClient reactorChannelEventCallback INFO: loggerMsg ClientName: ChannelCallbackClient Severity: Info Text: Received ChannelUp event on channel Channel_1 Instance Name Consumer_2_1 Component Version ads3.2.2.L1.linux.tis.rrg 64-bit loggerMsgEnd Oct 23, 2018 10:39:38 AM com.thomsonreuters.ema.access.LoginCallbackClient rdmLoginMsgCallback WARNING: loggerMsg ClientName: LoginCallbackClient Severity: Warning Text: RDMLogin stream state was changed to suspect with status message username <not set> usernameType <not set> State: Open/Suspect/None - text: "" loggerMsgEnd
Best Answer
-
The “SocketChannel.read returned -1 (end-of-stream)”
indicates a failure condition, often that the connection is no longer
available. Typically, the disconnection is from the server side.Server log indicates that the disconnections were due to buffer overflow condition on server side. The Buffer Overflow condition generally occurs once
Consumer application cannot keep up with the amount of data that it received, so server needs to store data in its outbound buffer and disconnect the
Consumer client once the buffer exceeds limitation.To avoid this slow consumer condition, you should first minimize
the time for processing incoming data in the callback methods i.e.
onRefreshMsg(..) and onUpdateMsg(..). Avoid accessing to database and/or other
blocking calls which typically consume significant time. The application can
also create an separated thread for data processing. For example, once the
application processes incoming events in the callback methods, it decodes data
and put it to an internal queue. The new thread then get data from the queue
and process it.0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛