Deadlock at OMMConsumer

vikas.chaudhary

There is deadlock at OMMConsumer while un-registering ric. Please advise.

Below are logs from application.   

at sun.misc.Unsafe.park(Native Method)

    at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)

    at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)

    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)

    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)

    at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209)

    at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)

    at com.refinitiv.ema.access.OmmBaseImpl.unregister(OmmBaseImpl.java:622)

    at com.refinitiv.ema.access.OmmConsumerImpl.unregister(OmmConsumerImpl.java:279)

Jirapongse

@vikas.chaudhary

Thank you for reaching out to us.

Typically, the deadlock happens with two threads and two resources. Please share the full call stack of all threads.

Moreover, please check the version of EMA Java that you are using. The current version is RTSDK Java 2.3.0.L2 aka EMA/ETA 3.9.0.L2. You may check the CHANGELOG.md file for the deadlock issues fixed in the previous releases.

You can download the lastest version of EMA Java from the Software Download. It is in the Product family: MDS API and Products: LSEG Real-Time SDK.