Sorry -- I didn't notice this post before I sent my reply -- I'll see if
I can repro this on my system.
On Fri, 2008-11-21 at 12:19 -0500, Steve Huston wrote:
> Hi Gordon,
>
> This is the change that triggered the link diagnostics. Why? I don't
> know... Will look into that next, but any ideas are welcome.
>
> -Steve
>
> [EMAIL PROTECTED] broker]$ svn diff -r{2008-11-14} Broker.cpp
> Index: Broker.cpp
> ===================================================================
> --- Broker.cpp (revision 713916)
> +++ Broker.cpp (working copy)
> @@ -240,11 +240,10 @@
> queueCleaner.start(conf.queueCleanInterval *
> qpid::sys::TIME_SEC);
> }
>
> - //initialize known broker urls:
> - try {
> - knownBrokers.push_back ( qpid::Url::getIpAddressesUrl (
> getPort(TCP_TRANSPORT) ) );
> - } catch (const NoSuchTransportException& e) {
> - QPID_LOG(error, "Could not send client known broker urls for
> cluster: " << e.what());
> + //initialize known broker urls (TODO: add support for urls for
> other transports (SSL, RDMA)):
> + boost::shared_ptr<ProtocolFactory> factory =
> getProtocolFactory(TCP_TRANSPORT);
> + if (factory) {
> + knownBrokers.push_back ( qpid::Url::getIpAddressesUrl (
> factory->getPort() ) );
> }
> }
>
> > -----Original Message-----
> > From: Gordon Sim [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, November 20, 2008 9:35 AM
> > To: [email protected]
> > Subject: Re: Linking problems on RHEL 4 starting between
> > Friday and Monday
> >
> >
> > Steve Huston wrote:
> > > Hi Gordon,
> > >
> > > Yes, it is puzzling... FYI, it fails the same way on a clean svn
> > > checkout.
> > > Not sure what to make of it...
> >
> > Does reverting back to a revision from last week fix it? If
> > so trying to
> > narrow down the revision where it first appears might help.
> >
> > We have automated rhel4 builds also, but they are using the standard
>
> > boost version (1.32) which is quite old (and requires the
> > special patch
> > as checked in under boost-1.32-support. Haven't seen the
> > problem you are
> > describing.
> >
>
