UPA NIProvider channelInactive portno=<[channel failure] socket channel is not in the active state for getBuffer>.

Question

Question by mreina · Nov 01, 2018 at 02:16 PM · elektron elektron-sdk rrt eta-api elektron-transport-api pricing non-interactive-provider channel

UPA NIProvider channelInactive portno=<[channel failure] socket channel is not in the active state for getBuffer>.

We have a NIprovider application that provide Market by voulume. For some reason, we received a channel failure, exact error message below.

[ChannelSession]channelInactive portno=49504<[channel failure] socket channel is not in the active state for getBuffer>.

Any idea what could cause the issue?

version:

productVersion: upaj7.4.0.L1.all.rrg

productInternalVersion: upaj7.4.F9

productDate: Fri May 16 12:00:00 CST 2014 Thomson Reuters

0

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2018-11-04T23:32:00Z

REFINITIV

Best Answer

Answer by Jirapongse · Nov 04, 2018 at 11:32 PM

@mreina

If the application calls the Channel.getBuffer method on the inactive channel, UPA will return the null buffer with this error.

It is possible that the connection between the application and ADH has been lost. You may need to verify the ADH log for disconnection.

0 Show 2 · Share

10 |1500 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

mreina · Nov 05, 2018 at 02:04 PM 0

Share

Because we are using a Private Stream to pricing into the Reuters Electronic Trading software, where should we look to identify the cause of the disconnection? We have no ADH that our NIProvider connects to...

REFINITIV

Jirapongse ♦♦ mreina · Nov 06, 2018 at 04:19 AM 0

Share

It should be the server that the UPA NIProvider is connecting to.

UPA NIProvider channelInactive portno=<[channel failure] socket channel is not in the active state for getBuffer>.

1 Reply

Watch this question

Related Questions