[omniORB] Memory leak on orb shutdown due to giopServer 'Closed 0 connections out of 1.'

Martin B. 0xCDCDCDCD at gmx.at
Thu Jan 6 17:34:26 GMT 2011


On 06.01.2011 13:28, Duncan Grisby wrote:
> On Wed, 2011-01-05 at 15:02 +0100, Martin B. wrote:
>
>> [omniORB 4.1.2] (But note that a diff of the 4.1.2 sources vs. the
>> newest 4.1.5 sources did not show any differences in the code I have
>> problems with.)
>
> There have been a few changes since 4.1.2 that might be relevant. Also,
> it will be much easier to help you track down what's going on if you use
> the latest version, so please upgrade and try again.
>
> If you still see the problem, please try to come up with a minimal
> example that shows the problem and send the whole trace from traceLevel
> 25 traceInvocations 1 traceInvocationReturns 1.
>

Yes. I guess I'll have to do that. Just wanted to make sure it isn't a 
known problem somehow before I dig deeper. (That's also why I asked 
about scanGranularity and ORBconnectionWatchPeriod, even if I run on all 
defaults at the moment.)

cheers,
Martin



More information about the omniORB-list mailing list