EMA Java - Open / Suspect / None / 'Request timeout'

astaphorsius

When trying to connect to our local instance of TREP, we continuously receive these 'Request timeout' messages.

We see in TREP that the connection is established, and the serviceName and ticker that we use are correct, but it does not seem to result in any messages.

If we try to use the ChannelDictionary we receive the same timeouts on that request, and with a FileDictionary we get the timeouts as Status messages from trying to connect to a ticker. The message looks like:

StatusMsg
    streamId="5"
    domain="MarketPrice Domain"
    state="Open / Suspect / None / 'Request timeout'"
    name="TICKER"
    serviceId="10"
    serviceName="BBG"
StatusMsgEnd

I have changed the ticker name here, but are certainly using a valid one when we are testing.

Does anyone have a clue what we could be missing that causes these 'Request timeout's?

Thanks in advance

Jirapongse

It seems that the request has been timed out according to the configuration.

After sending an item request, if the provider doesn't provide any response back within 15 seconds (default value), EMA will re-request and notify the application with this status message.

StatusMsg
    streamId="5"
    domain="MarketPrice Domain"
    state="Open / Suspect / None / 'Request timeout'"
    name="IBMxx.N"
    serviceId="1"
    serviceName="DIRECT_FEED"
StatusMsgEnd

This could be the problem in TREP or data feed. You can verify this by enable XML tracing in EMA by using the following configuration (XmlTraceToStdout).

<ConsumerList>
		<Consumer>
			<Name value="Consumer_1"/>
			<Channel value="Channel_1"/>
			<Dictionary value="Dictionary_1"/>
			<XmlTraceToStdout value="1"/>
		</Consumer>
...

From the XML trace, you will see that the request has been sent but there is no response back from TREP or data feed.

<REQUEST domainType="MARKET_PRICE" streamId="7" containerType="NO_DATA" flags="0x46 (HAS_PRIORITY|STREAMING|HAS_QOS)" Qos: Realtime/TickByTick/Static - timeInfo: 0 - rateInfo: 0 priorityClass="1" priorityCount="1" dataSize="0">
    <key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="1" name="IBMxx.N"/>
    <dataBody>
    </dataBody>
</REQUEST>

Then, EMA will close the request and send a new request for the same item.

<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/127.0.0.1:5005 remote=/127.0.0.1:14002] -->
<!-- Wed Dec 13 10:20:46 ICT 2017 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<CLOSE domainType="MARKET_PRICE" streamId="7" containerType="NO_DATA" flags="0x00" dataSize="0">
    <dataBody>
    </dataBody>
</CLOSE>
StatusMsg
    streamId="5"
    domain="MarketPrice Domain"
    state="Open / Suspect / None / 'Request timeout'"
    name="IBMxx.N"
    serviceId="1"
    serviceName="DIRECT_FEED"
StatusMsgEnd
<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/127.0.0.1:5005 remote=/127.0.0.1:14002] -->
<!-- Wed Dec 13 10:20:46 ICT 2017 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<REQUEST domainType="MARKET_PRICE" streamId="8" containerType="NO_DATA" flags="0x46 (HAS_PRIORITY|STREAMING|HAS_QOS)" Qos: Realtime/TickByTick/Static - timeInfo: 0 - rateInfo: 0 priorityClass="1" priorityCount="1" dataSize="0">
    <key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="1" name="IBMxx.N"/>
    <dataBody>
    </dataBody>
</REQUEST>

If you see this same behavior in the XML tracing, please contact your TREP administrator to verify the problem.