Re: [xmlblaster-devel] no nameservice broken

[Marcel Ruff <mr at marcelruff.info>]

Michael Atighetchi wrote:

> Marcel,
>
> your fix worked.
If have added a second fix so that the same problem for other protocol types
is fixed as well, it is available in the current cvs.

regards

Marcel

> Thanks again
> Michael
>
>
> On Sat, Jun 14, 2003 at 08:22:59AM -0400, Michael Atighetchi wrote:
>  
>
> > Marcel,
> >
> > thanks for fixing this - I'll check it out on Monday.
> >
> > Michael
> >
> >
> > On Fri, Jun 13, 2003 at 11:58:45PM +0200, Marcel Ruff wrote:
> >    
> >
> > > Michael Atighetchi wrote:
> > >
> > >      
> > >
> > > > I set
> > > >
> > > > dispatch/ior/useNameService=false
> > > > plugin/ior/useNameService=false
> > > >
> > > > in my server node configuration file, and am still getting the
> > > > following printouts in regular intervals (see below).
> > > >
> > > > This only seems to happen if I'm adding
> > > >
> > > > cluster.node[psq_xxx.xxx.xxx.xxx]=\
> > > > <clusternode id='psq_xxx.xxx.xxx.xxx'>\
> > > >     <info>\
> > > >        <address type='IOR' bootstrapHostname='xxx.xxx.xxx.xxx' 
> > > >        bootstrapPort='7601'/>\
> > > >     </info>\
> > > > </clusternode>
> > > >
> > > > to the configuration file.
> > > >
> > > > What is the right way to turn the nameservice off in a clustering
> > > > environment ?
> > > >
> > > >        
> > > Hi Michael,
> > >
> > > this is a bug in our configuration parsing in cluster environments.
> > > It is fixed now (see cvs),
> > >
> > >  plugin/ior/useNameService=false
> > >
> > > is the setting to use,
> > >
> > > regards
> > >
> > > Marcel
> > >
> > >      
>
>