[omniORB] Enabling ZIOP makes resolving the NameService fail

[Ruben Smits]

Hi Duncan,

On Fri, Apr 10, 2015 at 6:42 PM, Duncan Grisby <duncan at grisby.org> wrote:

> On Tue, 2015-02-24 at 19:45 +0100, Ruben Smits wrote:
>
> > I'm currently testing the ZIOP feature. I got it perfectly working by
> > using
> > omniZIOP::setGlobalPolicies(CORBA::PolicyList());
>
> Sorry for taking ages to reply to this...
>
> [...]
> > omniORB: Assertion failed.  This indicates a bug in the application
> > using omniORB, or maybe in omniORB itself.
> >  file: omniZIOP.cc
> >  line: 937
> >  info: pvseq.length() == 2
>
> The assertion is correct. It's spotting that the connection state has
> been mis-handled earlier. The connection thinks it can support ZIOP,
> when actually it can't. The assertion is checking that a compressor has
> been chosen, which should always be the case for a connection that
> really can support compression, but isn't the case here.
>
> I've attached a small patch that fixes it. I'll check it in to trunk.
>
>
I tested the attached patch and it solves my issue. Thanks for looking into
this and solving it.

R.


> Cheers,
>
> Duncan.
>
> --
>  -- Duncan Grisby         --
>   -- duncan at grisby.org     --
>    -- http://www.grisby.org --
>
>


-- 
Ruben Smits, Roboticist - Founder
+32 479 511 786
Intermodalics - Kapeldreef 60, 3001 Heverlee - BELGIUM
www.intermodalics.eu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20150415/f56bc37d/attachment.html>