What the best way to handle receiving a closed stream notification in EMA?

Craig.Tait
Craig.Tait Newcomer
edited 9:39AM in EMA

When receiving a closed stream notification in EMA/J:

WARN 2025-04-18 22:44:11,618 u.c.i.o.p.t.TrepPriceStreamSource pool-27-thread-1- trace_id='' span_id='' Received [StatusMsgImpl] message for [hostname: xconprices.ads1.prod2.iggroup.local;IP address: not available for OmmConsumer connections;port: 14032;connected component info: ads3.8.0.L1.linux.rrg 64-bit;channel state: active;connection type: socket;protocol type: Refinitiv wire format;major version: 14;minor version: 1;ping timeout: 10;max fragmentation size: 6142;max output buffers: 5000;guaranteed output buffers: 5000;number input buffers: 100;system send buffer size: 65535;system receive buffer size: 65535;compression type: none;compression threshold: 0;security protocol: None]: StatusMsg streamId="1911" domain="MarketPrice Domain" state="Closed / Suspect / Not found / '*Unknown Item'" name="<ITEM>" nameType="1" serviceId="9001" serviceName="<SERVICE>" StatusMsgEnd

Is it necessary to unregister the subscription for the handle, as follows?

consumer.unregister(hnd);

Or is it the case that the handle is invalid, and does not need to be unregistered?

Tagged:

Answers

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @Craig.Tait

    Thank you for reaching out to us.

    The unregister(long handle) method is used to relinquish interest in an open item stream. However, if the item stream has already been closed though the status message, this method must not be called.

Categories