Problem while uninitializing the ommconsumer

Question

question

sagar.s

25 ●6 ●5 ●11

Problem while uninitializing the ommconsumer

Hi Team,

I'm getting concurrent modification exception issue when trying to close the ommcomsumer. Can you please take a look at the issue? Is it a known issue in the api?

Nov 20, 2017 5:11:54 PM com.thomsonreuters.ema.access.ChannelDictionary processCallback WARNING: loggerMsg ClientName: ChannelDictionary Severity: Warning Text: RDMDictionary stream was closed with status message streamId 3 Reason State: Closed/Suspect/None - text: "Login stream was closed." loggerMsgEnd Nov 20, 2017 5:11:54 PM com.thomsonreuters.ema.access.ChannelDictionary processCallback

WARNING: loggerMsg ClientName: ChannelDictionary Severity: Warning Text: RDMDictionary stream was closed with status message streamId 4 Reason State: Closed/Suspect/None - text: "Login stream was closed." loggerMsgEnd

Exception in thread "main" java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.remove(HashMap.java:1451) at com.thomsonreuters.ema.access.OmmBaseImpl.rsslReactorDispatchLoop(Unknown Source) at com.thomsonreuters.ema.access.OmmBaseImpl.uninitialize(Unknown Source)

elektron refinitiv-realtime elektron-sdk ema-api rrt elektron-message-api

Nov 20, 2017 at 05:58 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.

Alex Putkov.1 Dec 05, 2017 at 01:50 PM

@sagar.s
Thank you for your participation in the forum.
Are the replies below satisfactory in resolving your query? If yes please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.
Thanks,
-AHS

pimchaya.wongrukun01 Jan 14, 2018 at 10:04 PM

Hello @sagar.s

Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If yes, please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.

Thanks,
AHS

chavalit-jintamalit Mar 01, 2018 at 01:50 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 · 2017-11-21T11:00:45Z

Michal Frajt

136 ●3 ●3 ●3

Note that the OMMConsumer.uninitialize() method call will very likely fail if there are many items still registered receiving updates. Unregistering all items, waiting a bit, calling OMMConsumer.uninitialize() might mitigate the risk of failure, but still you might hit the moment when the dispatch thread is processing some heartbeat or info messages and get into the same CME error.
The OMMBaseConsumer synchronization model between caller threads and dispatch thread is wrong or rather not existing at all causing CME and other errors being thrown randomly (more you use it, more error situations you get).

Nov 21, 2017 at 11:00 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.

Answer 2 · 2017-11-20T22:12:43Z

Nipat Kunvutipongsak

1.9k ●7 ●10 ●16

Hello @sagar.s,

There was a similar exception message and this problem has been submitted to the developer already.

Reference:

Question - ConcurrentModificationException in EMA

Git Hub Issue - https://github.com/thomsonreuters/Elektron-SDK/issues/34

Nov 20, 2017 at 10:12 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.

sagar.s Jan 09, 2018 at 08:58 AM

Hi Nipat,

When will the ESDK-1.1.2.G1 version be released? I beleive the concurrent modification exception is addressed in that version.

Thanks,

Sagar

Answer 3 · 2017-11-21T09:59:45Z

sagar.s

25 ●6 ●5 ●11

What is the difference between unregister and uninitialize functions in ommconsumer?

Is it necessary to call unregister fuction prior to calling uninitialize function?

Nov 21, 2017 at 09:59 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.

Answer 4 · 2017-11-21T10:20:22Z

may.du

121 ●1 ●0 ●1

You don't have to call unregister function before calling uninitialized. Once the application calls uninitialize(), EMA will close user login, close channel and shutdown reactor and ommConsumer ...everything. Unregister call is for user to close an uninterested item request.

Nov 21, 2017 at 10:20 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.

Answer 5 · 2018-01-16T08:34:03Z

sagar.s

25 ●6 ●5 ●11

Hi @Nipat Kunvutipongsak

When will the ESDK-1.1.2.G1 version be released? I beleive the concurrent modification exception is addressed in that version.

Thanks,

Sagar

Jan 16, 2018 at 08:34 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.

warat.boonyanit Feb 15, 2018 at 01:01 AM

@sagar.s

It's been released as open source version on Github.

https://github.com/thomsonreuters/Elektron-SDK/releases

sagar.s warat.boonyanit Feb 15, 2018 at 08:41 AM

@Warat B.

Is the concurrent modification issue resolved in below version ?

Elektron SDK - Java - 1.1.1.E1

Thanks,

Sagar

Nipat Kunvutipongsak sagar.s Feb 19, 2018 at 05:59 AM

@sagar.s

Elektron SDK - Java - 1.1.1.E1 contains a fix of the ConcurrentModificationException issue. Please see the excerpt of the latest EMA's README file below:

    Product Name: Elektron Message API - Java Edition
    Release Number: 3.1.1
    Load ID: ema3.1.1.E1.java
    Release Status: ELOAD
    Release Type: ELOAD
...
2.1.1 Service Requests Resolved In This Release
[ESDK-1120] Investigate ConcurrentModificationException in EMA (GitHub #34)
[ESDK-1220] ConcurrentModificationException while invoking dispatch() (Case No. 06107164)

Answer 6 · 2018-03-26T11:50:17Z

abdoulaye.1.ouattara

1 ●0 ●0 ●0

Hello Dev Team,

Currently I have the version Elektron-SDK1.1.1.java in my application, but I got somethink like a deadlock :

"main" prio=6 tid=0x0000000002cf4000 nid=0xb38 waiting on condition [0x0000000002cee000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00000000cf1d2440> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082) at java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1468) at java.util.concurrent.Executors$DelegatedExecutorService.awaitTermination(Executors.java:635) at com.thomsonreuters.ema.access.OmmBaseImpl.uninitialize(OmmBaseImpl.java:300) at com.thomsonreuters.ema.access.OmmConsumerImpl.uninitialize(OmmConsumerImpl.java:102)

Could you advice please ?

Mar 26, 2018 at 11:50 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

Problem while uninitializing the ommconsumer

6 Answers

Write an Answer

question

Problem while uninitializing the ommconsumer

6 Answers

Write an Answer

Related Questions