[omniORB] deadlock in omniORBpy-3

[Luke Deller]

Teemu Torma wrote:
> I have had to deal this in the past (omniorb-4.0.x/omniORBpy-2.x) when
> doing converters of _var variables for Boost.Python.  You need to
> release the python interpreter lock before calling the release.

Thanks Teemu. I suppose I was just lucky to avoid problems in the past.

I have added a note to the bottom of the UsefulTips wiki page, with the
heading "Avoiding deadlock with omniORBpy in a C/C++ extension module".
This is editable by anyone.
 
    http://www.omniorb-support.com/omniwiki/UsefulTips

Thanks,
Luke.


**********************************************************************************************

Important Note
This email (including any attachments) contains information which is
confidential and may be subject to legal privilege.  If you are not
the intended recipient you must not use, distribute or copy this
email.  If you have received this email in error please notify the
sender immediately and delete this email. Any views expressed in this
email are not necessarily the views of XPlan Technology.

It is the duty of the recipient to virus scan and otherwise test the
information provided before loading onto any computer system.
Xplan Technology does not warrant that the
information is free of a virus or any other defect or error.
**********************************************************************************************