Hi Support, For our application design, the program called register and unregister data field sequentially. The problem unregister all registered FID before registering new FID. For example, we need FID 1,2,3 * register FID 1 * unregister FID 1 * register FID 1,2 * unregister FID 1,2 * register FID 1,2,3 The steps above is executed within short period of time. Let say 1 second. We found that some of FID cannot be registered after all step is done. The missing FID is random. Could you help for the investigation?

Java EMA Ommconsumer missing FID field update

hsisupportswd

Hi Support,

For our application design, the program called register and unregister data field sequentially.

The problem unregister all registered FID before registering new FID.

For example, we need FID 1,2,3

register FID 1
unregister FID 1
register FID 1,2
unregister FID 1,2
register FID 1,2,3

The steps above is executed within short period of time. Let say 1 second.

We found that some of FID cannot be registered after all step is done.

The missing FID is random.

Could you help for the investigation?

Find more posts tagged with

java

#technology

Accepted answers

All comments

Jirapongse

@hsisupportswd

Thank you for reaching out to us.

What version of EMA and Java are you using?

Can you enable the XML tracing in the EMA and then share the tracing file?

You can enable the XML tracing by using setting the XmlTraceToFile in the Consumer configuration.

hsisupportswd

EMA version 3.8.1

Could we attach the XML trace file for your checking?

Jirapongse

@hsisupportswd

Yes, please.

hsisupportswd

Hi Jirapongse,

I attached the XML trace of 20251217 and a screendump of our application log of the event.

After field registering completed, we expect refresh message should have 14 fields but only got 12 fields.

refresh, 2HSI26000L5.HF, TRDPRC_1:85.0 SETTLE:82.0 T

RDVOL_1:1.0 SETTLEDATE:16 DEC 2025 INSPRC:(blank data) INSVOL:(blank data) TRD_IND_1:1 LSTSALCOND:0 CAN_PRC:(blank data) CAN_VOL:(blank data) CAN_TRD_ID:(blank data) CTRDTIM_MS:(blank data)

20251217_missingFIDissue.png

EmaTrace_148719_1765953170091.zip

Jirapongse

@hsisupportswd

I checked the trace file.

I found four requests sent consecutively for the same item with different views. This means that the server will receive these four item requests.

<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/130.51.102.167:55426 remote=hkl25150138-clientfeed.hk.hsbc/130.209.17.55:14002] -->
<!-- Wed Dec 17 14:32:53 HKT 2025 -->

<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<REQUEST domainType="MARKET_PRICE" streamId="5" containerType="ELEMENT_LIST" flags="0x446 (HAS_PRIORITY|STREAMING|HAS_QOS|HAS_VIEW)" Qos: Realtime/TickByTick/Static - timeInfo: 0 - rateInfo: 0 priorityClass="1" priorityCount="2" dataSize="50">
    <key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="11065" name="2HSI26000L5.HF"/>
    <dataBody>
        <elementList flags="0x08 (HAS_STANDARD_DATA)">
            <elementEntry name=":ViewType" dataType="UINT" data="1"/>
            <elementEntry name=":ViewData" dataType="ARRAY">
                <array itemLength="2" primitiveType="INT">
                    <arrayEntry data="6"/>
                    <arrayEntry data="178"/>
                    <arrayEntry data="288"/>
                    <arrayEntry data="376"/>
                    <arrayEntry data="377"/>
                    <arrayEntry data="4756"/>
                    <arrayEntry data="6584"/>
                    <arrayEntry data="6624"/>
                </array>
            </elementEntry>
        </elementList>
    </dataBody>
</REQUEST>

<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/130.51.102.167:55426 remote=hkl25150138-clientfeed.hk.hsbc/130.209.17.55:14002] -->
<!-- Wed Dec 17 14:32:53 HKT 2025 -->

<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<REQUEST domainType="MARKET_PRICE" streamId="5" containerType="ELEMENT_LIST" flags="0x446 (HAS_PRIORITY|STREAMING|HAS_QOS|HAS_VIEW)" Qos: Realtime/TickByTick/Static - timeInfo: 0 - rateInfo: 0 priorityClass="1" priorityCount="3" dataSize="52">
    <key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="11065" name="2HSI26000L5.HF"/>
    <dataBody>
        <elementList flags="0x08 (HAS_STANDARD_DATA)">
            <elementEntry name=":ViewType" dataType="UINT" data="1"/>
            <elementEntry name=":ViewData" dataType="ARRAY">
                <array itemLength="2" primitiveType="INT">
                    <arrayEntry data="6"/>
                    <arrayEntry data="178"/>
                    <arrayEntry data="288"/>
                    <arrayEntry data="376"/>
                    <arrayEntry data="377"/>
                    <arrayEntry data="4756"/>
                    <arrayEntry data="6583"/>
                    <arrayEntry data="6584"/>
                    <arrayEntry data="6624"/>
                </array>
            </elementEntry>
        </elementList>
    </dataBody>
</REQUEST>

<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/130.51.102.167:55426 remote=hkl25150138-clientfeed.hk.hsbc/130.209.17.55:14002] -->
<!-- Wed Dec 17 14:32:53 HKT 2025 -->

<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<REQUEST domainType="MARKET_PRICE" streamId="5" containerType="ELEMENT_LIST" flags="0x446 (HAS_PRIORITY|STREAMING|HAS_QOS|HAS_VIEW)" Qos: Realtime/TickByTick/Static - timeInfo: 0 - rateInfo: 0 priorityClass="1" priorityCount="4" dataSize="54">
    <key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="11065" name="2HSI26000L5.HF"/>
    <dataBody>
        <elementList flags="0x08 (HAS_STANDARD_DATA)">
            <elementEntry name=":ViewType" dataType="UINT" data="1"/>
            <elementEntry name=":ViewData" dataType="ARRAY">
                <array itemLength="2" primitiveType="INT">
                    <arrayEntry data="6"/>
                    <arrayEntry data="178"/>
                    <arrayEntry data="288"/>
                    <arrayEntry data="376"/>
                    <arrayEntry data="377"/>
                    <arrayEntry data="4465"/>
                    <arrayEntry data="4756"/>
                    <arrayEntry data="6583"/>
                    <arrayEntry data="6584"/>
                    <arrayEntry data="6624"/>
                </array>
            </elementEntry>
        </elementList>
    </dataBody>
</REQUEST>

<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/130.51.102.167:55426 remote=hkl25150138-clientfeed.hk.hsbc/130.209.17.55:14002] -->
<!-- Wed Dec 17 14:32:53 HKT 2025 -->

<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<REQUEST domainType="MARKET_PRICE" streamId="5" containerType="ELEMENT_LIST" flags="0x446 (HAS_PRIORITY|STREAMING|HAS_QOS|HAS_VIEW)" Qos: Realtime/TickByTick/Static - timeInfo: 0 - rateInfo: 0 priorityClass="1" priorityCount="5" dataSize="56">
    <key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="11065" name="2HSI26000L5.HF"/>
    <dataBody>
        <elementList flags="0x08 (HAS_STANDARD_DATA)">
            <elementEntry name=":ViewType" dataType="UINT" data="1"/>
            <elementEntry name=":ViewData" dataType="ARRAY">
                <array itemLength="2" primitiveType="INT">
                    <arrayEntry data="6"/>
                    <arrayEntry data="178"/>
                    <arrayEntry data="288"/>
                    <arrayEntry data="376"/>
                    <arrayEntry data="377"/>
                    <arrayEntry data="4465"/>
                    <arrayEntry data="4756"/>
                    <arrayEntry data="6583"/>
                    <arrayEntry data="6584"/>
                    <arrayEntry data="6587"/>
                    <arrayEntry data="6624"/>
                </array>
            </elementEntry>
        </elementList>
    </dataBody>
</REQUEST>

Then, the API received the following refresh from the server. I think this is a response for the first item request.

<!-- Incoming Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/130.51.102.167:55426 remote=hkl25150138-clientfeed.hk.hsbc/130.209.17.55:14002] -->
<!-- Wed Dec 17 14:32:53 HKT 2025 -->

<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<REFRESH domainType="MARKET_PRICE" streamId="5" containerType="FIELD_LIST" flags="0x1FA (HAS_PERM_DATA|HAS_MSG_KEY|HAS_SEQ_NUM|SOLICITED|REFRESH_COMPLETE|HAS_QOS|CLEAR_CACHE)" groupId="12" seqNum="64608" permData="032B 3990 17C0" Qos: Realtime/TickByTick/Static - timeInfo: 0 - rateInfo: 0 State: Open/Ok/None - text: "*accPhk_a**lseg_a*All is well" dataSize="40">
    <key flags="0x07 (HAS_SERVICE_ID|HAS_NAME|HAS_NAME_TYPE)" serviceId="11065" name="2HSI26000L5.HF" nameType="1"/>
    <dataBody>
        <fieldList flags="0x09 (HAS_FIELD_LIST_INFO|HAS_STANDARD_DATA)" fieldListNum="0" dictionaryId="1">
            <fieldEntry fieldId="6" data="0E55"/>
            <fieldEntry fieldId="178" data="0E01"/>
            <fieldEntry fieldId="288" data="100C 07E9"/>
            <fieldEntry fieldId="376" data=""/>
            <fieldEntry fieldId="377" data=""/>
            <fieldEntry fieldId="4756" data="30"/>
            <fieldEntry fieldId="6584" data=""/>
            <fieldEntry fieldId="6624" data=""/>
        </fieldList>
    </dataBody>
</REFRESH>

After that, the API closed the stream.

<!-- Outgoing Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/130.51.102.167:55426 remote=hkl25150138-clientfeed.hk.hsbc/130.209.17.55:14002] -->
<!-- Wed Dec 17 14:32:53 HKT 2025 -->

<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<CLOSE domainType="MARKET_PRICE" streamId="5" containerType="NO_DATA" flags="0x00" dataSize="0">
    <dataBody>
    </dataBody>
</CLOSE>

However, the API still received the following response. I believe this message remained in the buffer and belongs to the fourth request. It’s likely that the API may not forward it to the application because the stream had already been closed.

<!-- Incoming Reactor message -->
<!-- java.nio.channels.SocketChannel[connected local=/130.51.102.167:55426 remote=hkl25150138-clientfeed.hk.hsbc/130.209.17.55:14002] -->
<!-- Wed Dec 17 14:32:53 HKT 2025 -->

<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<REFRESH domainType="MARKET_PRICE" streamId="5" containerType="FIELD_LIST" flags="0x1FA (HAS_PERM_DATA|HAS_MSG_KEY|HAS_SEQ_NUM|SOLICITED|REFRESH_COMPLETE|HAS_QOS|CLEAR_CACHE)" groupId="12" seqNum="64608" permData="032B 3990 17C0" Qos: Realtime/TickByTick/Static - timeInfo: 0 - rateInfo: 0 State: Open/Ok/None - text: "*accPhk_a**lseg_a*All is well" dataSize="50">
    <key flags="0x07 (HAS_SERVICE_ID|HAS_NAME|HAS_NAME_TYPE)" serviceId="11065" name="2HSI26000L5.HF" nameType="1"/>
    <dataBody>
        <fieldList flags="0x09 (HAS_FIELD_LIST_INFO|HAS_STANDARD_DATA)" fieldListNum="0" dictionaryId="1">
            <fieldEntry fieldId="6" data="0E55"/>
            <fieldEntry fieldId="178" data="0E01"/>
            <fieldEntry fieldId="288" data="100C 07E9"/>
            <fieldEntry fieldId="376" data=""/>
            <fieldEntry fieldId="377" data=""/>
            <fieldEntry fieldId="4465" data="31"/>
            <fieldEntry fieldId="4756" data="30"/>
            <fieldEntry fieldId="6583" data=""/>
            <fieldEntry fieldId="6584" data=""/>
            <fieldEntry fieldId="6587" data=""/>
            <fieldEntry fieldId="6624" data=""/>
        </fieldList>
    </dataBody>
</REFRESH>

The API is asynchronous and the requests are processed by the server. The API can't control how the server processes those same request messages. According to the log, the server can process the first and the last request properly.

To update the view, you can use consumer.reissue with the same handle rather than calling unregister and register for the same item.

void reissue(ReqMsg reqMsg, long handle)
Changes the interest in an open item stream. The first formal parameter houses a ReqMsg. ReqMsg attributes that may change are Priority(), InitialImage(), InterestAfterRefresh(), Pause() and Payload ViewData(). The second formal parameter is a handle that identifies the open stream to be modified. This method is ObjectLevelSafe.

EXPLORE OUR SITES