Uncaught NPE in EMA thread

Question

question

pengshuolin

5 ●1 ●2 ●6

Uncaught NPE in EMA thread

We are working with below EMA SDK:

<dependency>
    <groupId>com.refinitiv.ema</groupId>
    <artifactId>ema</artifactId>
    <version>3.6.3.1</versio
</dependency>

These days we found some uncaught NulllPointerException in not .log file but standard output.

Exception in thread "pool-25-thread-1" java.lang.NullPointerException
        at com.refinitiv.ema.access.ItemCallbackClientConsumer.notifyOnAllMsg(ItemCallbackClient.java:2555)
        at com.refinitiv.ema.access.ItemCallbackClient.processRefreshMsg(ItemCallbackClient.java:1788)
        at com.refinitiv.ema.access.ItemCallbackClient.defaultMsgCallback(ItemCallbackClient.java:1626)
        at com.refinitiv.eta.valueadd.reactor.Reactor.sendDefaultMsgCallback(Reactor.java:1942)
        at com.refinitiv.eta.valueadd.reactor.Reactor.sendAndHandleDefaultMsgCallback(Reactor.java:1957)
        at com.refinitiv.eta.valueadd.reactor.WlItemHandler.callbackUser(WlItemHandler.java:2935)
        at com.refinitiv.eta.valueadd.reactor.WlItemHandler.readRefreshMsg(WlItemHandler.java:2186)
        at com.refinitiv.eta.valueadd.reactor.WlItemHandler.readMsg(WlItemHandler.java:1900)
        at com.refinitiv.eta.valueadd.reactor.Watchlist.readMsg(Watchlist.java:292)
        at com.refinitiv.eta.valueadd.reactor.Reactor.processRwfMessage(Reactor.java:2995)
        at com.refinitiv.eta.valueadd.reactor.Reactor.performChannelRead(Reactor.java:3317)
        at com.refinitiv.eta.valueadd.reactor.Reactor.dispatchChannel(Reactor.java:2529)
        at com.refinitiv.eta.valueadd.reactor.ReactorChannel.dispatch(ReactorChannel.java:601)
        at com.refinitiv.ema.access.OmmBaseImpl.rsslReactorDispatchLoop(OmmBaseImpl.java:1510)
        at com.refinitiv.ema.access.OmmBaseImpl.run(OmmBaseImpl.java:1652)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

After discussing with Elektron Supports , we assume it should be a EMA SDK Bug.

Please help us check it out.

Thanks.

ema-api

Apr 13, 2022 at 04:44 AM

10 |1500

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

wasin.w Apr 22, 2022 at 05:10 AM

Hello @pengshuolin

Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?

If so please can you click the 'Accept' text next to the appropriate reply? This will guide all community members who have a similar question.

Thanks,

AHS

wasin.w Apr 29, 2022 at 07:52 AM

Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.

Thanks,

AHS

Answer 1 · 2022-04-18T07:15:28Z

Jirapongse

78.8k ●250 ●52 ●74

@pengshuolin

I checked the call stack and found that it is similar to the issue that has been fixed in RTSDK Java 2.0.5.L1 aka EMA/ETA 3.6.5.L1 aka 3.6.5.0.

[Case Number: 11101002] - [RTSDK-6069] - Fixed null pointer exception with request timeout

Please upgrade to the latest version of EMA.

<dependency>
    <groupId>com.refinitiv.ema</groupId>
    <artifactId>ema</artifactId>
    <version>3.6.5.0</version>
</dependency>

Apr 18, 2022 at 07:15 AM

10 |1500

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

JasonS Sep 17, 2022 at 07:40 PM

I am currently using version 3.6.5.0 but am getting the same error.

Answer 2 · 2022-04-13T14:07:46Z

Gurpreet

22k ●58 ●14 ●21

Hi @pengshuolin,

Can you please update the EMA to latest version and try again - the dev team has fixed two NPE bugs in the SDK.

For the team to investigate, they would need to be able to reproduce the exception. Can you also document the steps required that led to this uncaught null pointer.

Apr 13, 2022 at 02:07 PM

10 |1500

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

Answer 3 · 2022-04-14T05:33:31Z

pengshuolin

5 ●1 ●2 ●6

Hi @Gurpreet ,

Such situation occurred when there are some ADS error.

And we thing the client should notify user properly instead just throwing the NEP and exit the thread.

Apr 14, 2022 at 05:33 AM

10 |1500

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

Gurpreet Apr 14, 2022 at 01:36 PM

Hi @pengshuolin,

I agree, if it is an exception condition, it should be raised up to the application layer for user code to react to it. Unfortunately, it becomes very hard for dev team to advise or fix an issue which they are unable to reproduce. So, I would recommend that you capture all the logs from EMA and ADS when it happens next time.

The Realtime SDK is supported by development team at this github site - https://github.com/Refinitiv/Real-Time-SDK. You can directly interact with developers by opening an issue there.

Answer 4 · 2022-04-14T05:37:11Z

pengshuolin

5 ●1 ●2 ●6

Hi @Gurpreet ,

we can't upload picture, please check it in <img src="xxx"/>

92333-1.png (70.1 KiB)

Apr 14, 2022 at 05:37 AM

10 |1500

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

Q&A Forum

question

Uncaught NPE in EMA thread

4 Answers

Write an Answer

question

Uncaught NPE in EMA thread

4 Answers

Write an Answer

Related Questions