question

Upvotes
Accepted
mangesh avatar image
5 ●2 ●2 ●6

IOException related to RFA internal sendPing call

We have noticed a number of Broken Pipe messages (see below) in the logs along with Channel Disconnected msgs. Has anyone encountered something similar followed by client losing a connection to the ADS. RFA versions used for tests ( RFA 7.6, RFA 8.0.0.E1)

OMMMsg.MsgType=MsgType.STATUS_RESP, OMMState.Stream=OPEN, OMMState.Data=SUSPECT, OMMState.Code=NONE, stateText=Connection to servDev1:14002 failed in connection

servDev1; Channel disconnected

java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
at sun.nio.ch.IOUtil.write(IOUtil.java:51)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:492)
at com.reuters.mainloop.channel.ChannelSession.write(Unknown Source)
at com.reuters.ipc.ConnectionImpl.sendMessage(Unknown Source)
at com.reuters.ipc.SubConnection.sendPing(Unknown Source)
at com.reuters.rfa.internal.rssl.RsslClientConnection.sendPing(Unknown Source)
at com.reuters.rfa.internal.rssl.PingTimer.timerDispatch(Unknown Source)
at com.reuters.mainloop.channel.SelectTimerCmd.fireTimer(Unknown Source)
at com.reuters.mainloop.channel.ChannelMainLoop.fireExpiredTimers(Unknown Source)
at com.reuters.mainloop.channel.ChannelMainLoop.run(Unknown Source)
at com.reuters.rfa.internal.common.EventQueueMLThread.runImpl(Unknown Source)
at com.reuters.rfa.internal.common.InterruptibleThread.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)

treprfarfa-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

2 Answers

Upvote
Accepted
Lars-at-Addicticks avatar image
1.5k ●3 ●5 ●7

Your error message means that someone / something has closed the socket connection between your application (the client) and the ADS (the server). It hasn't been closed by the client-side, so what else can it be?

The most likely cause is that the ADS has deliberately closed the connection, possibly because it can see your application is not processing messages fast enough in order to keep up. You'll see this in the ADS logs if that's the case. Or perhaps simply the ADS process has crashed?. Or the host on which it runs has crashed?. In any case you'll need to investigate what you can see from the server-side.

Another likely cause is that something between your application and the server has obstructed the network path. This may be due to an intermittent problem with routers, firewalls, etc, in your network.

The possible causes I mention above can all give the symptom you describe.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Upvotes
wasin.w avatar image
11.5k ●16 ●7 ●10

Hi @mangesh, can you replicate the issue on demand? If can you enable the RFA trace file and share us the trace file when the problem occur?

You can configure the following RFA Java configurations to enable the log file

  • <namespace>/Connections/<Connection Name>/ipcTraceFlags = 23
  • <namespace>/ Connections/<Connection Name>/mountTrace = True
  • <namespace>/ Connections/<Connection Name>/logFileName=<path to log file>
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 5.0 MiB each and 10.0 MiB total.

Click below to post an Idea Post Idea