[omniORB] ORB.destroy() takes ten seconds -- speed it up?

[Jim Bell]

My app takes a long time to stop.  It seems that there are two different 
long waits during ORB.destroy():

Instrumenting it a bit, here's a 4-second wait in ORB::destroy().

omniORB: (5) 2020-05-05 16:33:22.096000: AsyncInvoker: thread id 5 
finished immediate server task.

omniORB: (7) 2020-05-05 16:33:26.003000: Error in network receive (start 
of message): giop:tcp:[::ffff:172.21.30.100]:15217

And another:

omniORB: (10) 2020-05-05 16:33:26.037000: Deactivate bidirectional 
monitors...

omniORB: (6) 2020-05-05 16:33:29.005000: No remaining bidir monitors.

Any guesses on what's happening here? The 172.21.30.100 address is 
OpenVPN, fwiw.

This is on Windows 10, omniORBpy w/ omniORB 4.2.3.

Thanks,

-Jim


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20200505/576a0754/attachment.html>