[omniORB] Threads hanging in OMNI ORB 4.2.1 with mutex lock

[Agarwal, Shelendra]

Hi,
We are using c++ implementation of OMNI ORB 4.2.1 on RHEL 7.x.
We have a process that sometime hangs and stops responding to other processes for CORBA calls. We collected the gstack of the process and from the thread dumps we see most of the threads are in omni_mutex_lock::omni_mutex_lock condition.

We collected multiple snaps of gstack and we see that there is no changes happening over a period of time. Attached are 2 snaps taken 10 minutes apart.

We understand that threads are waiting for some resources but we are unable to understand which resource. May be they are in kind of deadlock state waiting for each other or something else, can you please throw some lights?

We noted that omniTransportLock is often involved in many mutex locks in the thread dump. Are there any details about this omniTransportLock not being released available?

Thanks in advance for your help!!


With Best Regards,

Shelendra Agarwal
Telco Big Data Analytics
Communications & Media Solutions
Hewlett Packard Enterprise
+91-9945056319
shelendra.agarwal at hpe.com<mailto:shelendra.agarwal at hpe.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20181207/82f2440e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2018-12-06-17-50-00_GSTACK.log
Type: application/octet-stream
Size: 553773 bytes
Desc: 2018-12-06-17-50-00_GSTACK.log
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20181207/82f2440e/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2018-12-06-18-00-47_GSTACK.log
Type: application/octet-stream
Size: 553773 bytes
Desc: 2018-12-06-18-00-47_GSTACK.log
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20181207/82f2440e/attachment-0003.obj>