You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Alan Conway <ac...@redhat.com> on 2007/05/01 00:12:20 UTC

Re: [C++] Build

On Mon, 2007-04-30 at 13:02 -0400, Alan Conway wrote:
> I've been working on the M2 branch also and haven't seen the problem.
> Soon as I finish my current commit I'll make an RPM for you to try.

Martin, if you're still looking for an M2 x86_64 build try these RPMs:
http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.x86_64.rpm
http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm

Cheers,
Alan.


Re: [C++] Build

Posted by Martin Ritchie <ri...@apache.org>.
On 02/05/07, Alan Conway <ac...@redhat.com> wrote:
> On Wed, 2007-05-02 at 12:35 +0100, Martin Ritchie wrote:
> > Ok found the problem.
> >
> > our box didn't have an ipv4 lookup for localhost in /etc/hosts
> >
> > The python script kinda gave it away by saying 'Name or service not known'
> >
> > It wouldn't connect to the java broker either but 127.0.0.1 would
> > connect to the java broker (though the python takes the -b host value
> > as the vhost value aswell) this led us to /etc/hosts which only had
> > the ipv6 value for localhost.
> >
> > Thanks for all your help getting to the bottom of this one.
> >
> > I wonder where the C++ was listening?
>
> Could you connect to the C++ broker with 127.0.0.1? I'm not much up on
> ipv6 config etc. do you think there's something more the broker needs to
> do to play nice with ipv6?
>
> Cheers,
> Alan.

I didn't try and specify the ip to connect to with python -> C++. I
made the python -> java work and it then just worked with python ->
C++.

If I get some spare time on the box then I'll try and remove the ipv4
localhost entry in hosts and see if we can specify it by ip.

However if virtual hosts are implemented on C++ then it is likely it
won't work. The java broker refused the connection as vhost 127.0.0.1
doesn't exist. In the java the vhosts are arbitrary strings so there
is no correlation between '127.0.0.1' and 'localhost'.

-- 
Martin Ritchie

Re: [C++] Build

Posted by Alan Conway <ac...@redhat.com>.
On Wed, 2007-05-02 at 12:35 +0100, Martin Ritchie wrote:
> Ok found the problem.
> 
> our box didn't have an ipv4 lookup for localhost in /etc/hosts
> 
> The python script kinda gave it away by saying 'Name or service not known'
> 
> It wouldn't connect to the java broker either but 127.0.0.1 would
> connect to the java broker (though the python takes the -b host value
> as the vhost value aswell) this led us to /etc/hosts which only had
> the ipv6 value for localhost.
> 
> Thanks for all your help getting to the bottom of this one.
> 
> I wonder where the C++ was listening?

Could you connect to the C++ broker with 127.0.0.1? I'm not much up on
ipv6 config etc. do you think there's something more the broker needs to
do to play nice with ipv6?

Cheers,
Alan.


Re: [C++] Build

Posted by Martin Ritchie <ri...@apache.org>.
Alan,

yum installed apr apr-devel boost boost-devel to get the i386 versions.
Then Installed the i386 RPMs.
Ran
/usr/sbin/qpidd -t

Get a waiting qpidd as shown by pstack at the bottom of the email.
All looks well

But same as with 64bit version.
- Can't telnet locahost 5672
- Can't run python tests. fail to connect.

Just to be sure there isn't a networking related problem I rebuilt the
Java broker and ,,,,

Ok found the problem.

our box didn't have an ipv4 lookup for localhost in /etc/hosts

The python script kinda gave it away by saying 'Name or service not known'

It wouldn't connect to the java broker either but 127.0.0.1 would
connect to the java broker (though the python takes the -b host value
as the vhost value aswell) this led us to /etc/hosts which only had
the ipv6 value for localhost.

Thanks for all your help getting to the bottom of this one.

I wonder where the C++ was listening?

On 02/05/07, Martin Ritchie <ri...@apache.org> wrote:
> Thanks Alan,
> I'll check them out later today.
>
> On 01/05/07, Alan Conway <ac...@redhat.com> wrote:
> > I thought I had but clearly I goofed. They're there now:
> > http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.i386.rpm
> > http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.i386.rpm
> >
> > On Tue, 2007-05-01 at 17:12 +0100, Martin Ritchie wrote:
> > > Just to be clear.
> > >
> > > Did you put the 32bit rpms up in the same location as the 64bit ones?
> > >
> > > Thanks
> > >
> > > On 01/05/07, Martin Ritchie <ri...@apache.org> wrote:
> > > > Hi,
> > > >
> > > > http://rhm.et.redhat.com/download/
> > > > Did you put just the src rpms up?
> > > >
> > > > On 01/05/07, Alan Conway <ac...@redhat.com> wrote:
> > > > > On Tue, 2007-05-01 at 07:56 +0100, Martin Ritchie wrote:
> > > > > > On 30/04/07, Alan Conway <ac...@redhat.com> wrote:
> > > > > > > On Mon, 2007-04-30 at 13:02 -0400, Alan Conway wrote:
> > > > > > > > I've been working on the M2 branch also and haven't seen the problem.
> > > > > > > > Soon as I finish my current commit I'll make an RPM for you to try.
> > > > > > >
> > > > > > > Martin, if you're still looking for an M2 x86_64 build try these RPMs:
> > > > > > > http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.x86_64.rpm
> > > > > > > http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Alan.
> > > > > > >
> > > > > >
> > > > > > Thanks for the RPMs Alan. I wish I had better news, but the behaviour
> > > > > > is the same. I must have some incompatible item installed. Do you have
> > > > > > 32Bit rpm's to hand. Perhaps I can try and narrow down the problem.
> > > > > >
> > > > > > Cheers
> > > > >
> > > > > I just put x86 RPMs up in the same location.
> > > > >
> > > > > I'm a bit worried about what you're seeing, I'd like to pin it down. Let
> > > > > me know if things work OK on 32 bit, and I'll think about how to get
> > > > > some more info out of your stalled daemon. The ptrace you have looks
> > > > > normal for a qpidd waiting for connections.
> > > > >
> > > > > Cheers,
> > > > > Alan.
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Martin Ritchie
> > > >
> > >
> > >
> >
> >
>
>
> --
> Martin Ritchie
>


-- 
Martin Ritchie
Thread 7 (Thread 4158659472 (LWP 19576)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xf7e6a42c in pthread_cond_timedwait@@GLIBC_2.3.2 ()
#2  0xf7e8e799 in apr_thread_cond_timedwait () from /usr/lib/libapr-1.so.0
#3  0xf7f96430 in qpid::broker::AutoDelete::run ()
#4  0xf7f08ab4 in qpid::sys::Thread::runRunnable ()
#5  0xf7e99e06 in apr_threadkey_private_create () from /usr/lib/libapr-1.so.0
#6  0xf7e663db in start_thread () from /lib/libpthread.so.0
#7  0x43c9806e in clone () from /lib/libc.so.6
Thread 6 (Thread 4148169616 (LWP 19577)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0x43c986e6 in __epoll_wait_nocancel () from /lib/libc.so.6
#2  0xf7e957f1 in apr_pollset_poll () from /usr/lib/libapr-1.so.0
#3  0xf7f04f12 in qpid::sys::LFProcessor::poll ()
#4  0xf7f04f48 in qpid::sys::LFProcessor::getNextEvent ()
#5  0xf7f05698 in qpid::sys::LFProcessor::run ()
#6  0xf7f08ab4 in qpid::sys::Thread::runRunnable ()
#7  0xf7e99e06 in apr_threadkey_private_create () from /usr/lib/libapr-1.so.0
#8  0xf7e663db in start_thread () from /lib/libpthread.so.0
#9  0x43c9806e in clone () from /lib/libc.so.6
Thread 5 (Thread 4137679760 (LWP 19578)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xf7e6c98e in __lll_mutex_lock_wait () from /lib/libpthread.so.0
#2  0xf7e68820 in _L_mutex_lock_776 () from /lib/libpthread.so.0
#3  0xf7e686f1 in pthread_mutex_lock () from /lib/libpthread.so.0
#4  0xf7e8d2e0 in apr_thread_mutex_lock () from /usr/lib/libapr-1.so.0
#5  0xf7f0566b in qpid::sys::LFProcessor::run ()
#6  0xf7f08ab4 in qpid::sys::Thread::runRunnable ()
#7  0xf7e99e06 in apr_threadkey_private_create () from /usr/lib/libapr-1.so.0
#8  0xf7e663db in start_thread () from /lib/libpthread.so.0
#9  0x43c9806e in clone () from /lib/libc.so.6
Thread 4 (Thread 4127189904 (LWP 19579)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xf7e6c98e in __lll_mutex_lock_wait () from /lib/libpthread.so.0
#2  0xf7e68820 in _L_mutex_lock_776 () from /lib/libpthread.so.0
#3  0xf7e686f1 in pthread_mutex_lock () from /lib/libpthread.so.0
#4  0xf7e8d2e0 in apr_thread_mutex_lock () from /usr/lib/libapr-1.so.0
#5  0xf7f0566b in qpid::sys::LFProcessor::run ()
#6  0xf7f08ab4 in qpid::sys::Thread::runRunnable ()
#7  0xf7e99e06 in apr_threadkey_private_create () from /usr/lib/libapr-1.so.0
#8  0xf7e663db in start_thread () from /lib/libpthread.so.0
#9  0x43c9806e in clone () from /lib/libc.so.6
Thread 3 (Thread 4116700048 (LWP 19580)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xf7e6c98e in __lll_mutex_lock_wait () from /lib/libpthread.so.0
#2  0xf7e68820 in _L_mutex_lock_776 () from /lib/libpthread.so.0
#3  0xf7e686f1 in pthread_mutex_lock () from /lib/libpthread.so.0
#4  0xf7e8d2e0 in apr_thread_mutex_lock () from /usr/lib/libapr-1.so.0
#5  0xf7f0566b in qpid::sys::LFProcessor::run ()
#6  0xf7f08ab4 in qpid::sys::Thread::runRunnable ()
#7  0xf7e99e06 in apr_threadkey_private_create () from /usr/lib/libapr-1.so.0
#8  0xf7e663db in start_thread () from /lib/libpthread.so.0
#9  0x43c9806e in clone () from /lib/libc.so.6
Thread 2 (Thread 4106210192 (LWP 19581)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xf7e6c98e in __lll_mutex_lock_wait () from /lib/libpthread.so.0
#2  0xf7e68820 in _L_mutex_lock_776 () from /lib/libpthread.so.0
#3  0xf7e686f1 in pthread_mutex_lock () from /lib/libpthread.so.0
#4  0xf7e8d2e0 in apr_thread_mutex_lock () from /usr/lib/libapr-1.so.0
#5  0xf7f0566b in qpid::sys::LFProcessor::run ()
#6  0xf7f08ab4 in qpid::sys::Thread::runRunnable ()
#7  0xf7e99e06 in apr_threadkey_private_create () from /usr/lib/libapr-1.so.0
#8  0xf7e663db in start_thread () from /lib/libpthread.so.0
#9  0x43c9806e in clone () from /lib/libc.so.6
Thread 1 (Thread 4158662352 (LWP 19575)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xf7e6cf88 in accept () from /lib/libpthread.so.0
#2  0xf7e9237d in apr_socket_accept () from /usr/lib/libapr-1.so.0
#3  0xf7f03264 in qpid::sys::APRAcceptor::run ()
#4  0xf7f981ab in qpid::broker::Broker::run ()
#5  0x080504f4 in std::runtime_error::what ()
#6  0x43be0f2c in __libc_start_main () from /lib/libc.so.6
#7  0x0804fec1 in std::runtime_error::what ()
#0  0xffffe410 in __kernel_vsyscall ()

Re: [C++] Build

Posted by Martin Ritchie <ri...@apache.org>.
Thanks Alan,
I'll check them out later today.

On 01/05/07, Alan Conway <ac...@redhat.com> wrote:
> I thought I had but clearly I goofed. They're there now:
> http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.i386.rpm
> http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.i386.rpm
>
> On Tue, 2007-05-01 at 17:12 +0100, Martin Ritchie wrote:
> > Just to be clear.
> >
> > Did you put the 32bit rpms up in the same location as the 64bit ones?
> >
> > Thanks
> >
> > On 01/05/07, Martin Ritchie <ri...@apache.org> wrote:
> > > Hi,
> > >
> > > http://rhm.et.redhat.com/download/
> > > Did you put just the src rpms up?
> > >
> > > On 01/05/07, Alan Conway <ac...@redhat.com> wrote:
> > > > On Tue, 2007-05-01 at 07:56 +0100, Martin Ritchie wrote:
> > > > > On 30/04/07, Alan Conway <ac...@redhat.com> wrote:
> > > > > > On Mon, 2007-04-30 at 13:02 -0400, Alan Conway wrote:
> > > > > > > I've been working on the M2 branch also and haven't seen the problem.
> > > > > > > Soon as I finish my current commit I'll make an RPM for you to try.
> > > > > >
> > > > > > Martin, if you're still looking for an M2 x86_64 build try these RPMs:
> > > > > > http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.x86_64.rpm
> > > > > > http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm
> > > > > >
> > > > > > Cheers,
> > > > > > Alan.
> > > > > >
> > > > >
> > > > > Thanks for the RPMs Alan. I wish I had better news, but the behaviour
> > > > > is the same. I must have some incompatible item installed. Do you have
> > > > > 32Bit rpm's to hand. Perhaps I can try and narrow down the problem.
> > > > >
> > > > > Cheers
> > > >
> > > > I just put x86 RPMs up in the same location.
> > > >
> > > > I'm a bit worried about what you're seeing, I'd like to pin it down. Let
> > > > me know if things work OK on 32 bit, and I'll think about how to get
> > > > some more info out of your stalled daemon. The ptrace you have looks
> > > > normal for a qpidd waiting for connections.
> > > >
> > > > Cheers,
> > > > Alan.
> > > >
> > > >
> > >
> > >
> > > --
> > > Martin Ritchie
> > >
> >
> >
>
>


-- 
Martin Ritchie

Re: [C++] Build

Posted by Alan Conway <ac...@redhat.com>.
I thought I had but clearly I goofed. They're there now:
http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.i386.rpm
http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.i386.rpm

On Tue, 2007-05-01 at 17:12 +0100, Martin Ritchie wrote:
> Just to be clear.
> 
> Did you put the 32bit rpms up in the same location as the 64bit ones?
> 
> Thanks
> 
> On 01/05/07, Martin Ritchie <ri...@apache.org> wrote:
> > Hi,
> >
> > http://rhm.et.redhat.com/download/
> > Did you put just the src rpms up?
> >
> > On 01/05/07, Alan Conway <ac...@redhat.com> wrote:
> > > On Tue, 2007-05-01 at 07:56 +0100, Martin Ritchie wrote:
> > > > On 30/04/07, Alan Conway <ac...@redhat.com> wrote:
> > > > > On Mon, 2007-04-30 at 13:02 -0400, Alan Conway wrote:
> > > > > > I've been working on the M2 branch also and haven't seen the problem.
> > > > > > Soon as I finish my current commit I'll make an RPM for you to try.
> > > > >
> > > > > Martin, if you're still looking for an M2 x86_64 build try these RPMs:
> > > > > http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.x86_64.rpm
> > > > > http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm
> > > > >
> > > > > Cheers,
> > > > > Alan.
> > > > >
> > > >
> > > > Thanks for the RPMs Alan. I wish I had better news, but the behaviour
> > > > is the same. I must have some incompatible item installed. Do you have
> > > > 32Bit rpm's to hand. Perhaps I can try and narrow down the problem.
> > > >
> > > > Cheers
> > >
> > > I just put x86 RPMs up in the same location.
> > >
> > > I'm a bit worried about what you're seeing, I'd like to pin it down. Let
> > > me know if things work OK on 32 bit, and I'll think about how to get
> > > some more info out of your stalled daemon. The ptrace you have looks
> > > normal for a qpidd waiting for connections.
> > >
> > > Cheers,
> > > Alan.
> > >
> > >
> >
> >
> > --
> > Martin Ritchie
> >
> 
> 


Re: [C++] Build

Posted by Martin Ritchie <ri...@apache.org>.
Just to be clear.

Did you put the 32bit rpms up in the same location as the 64bit ones?

Thanks

On 01/05/07, Martin Ritchie <ri...@apache.org> wrote:
> Hi,
>
> http://rhm.et.redhat.com/download/
> Did you put just the src rpms up?
>
> On 01/05/07, Alan Conway <ac...@redhat.com> wrote:
> > On Tue, 2007-05-01 at 07:56 +0100, Martin Ritchie wrote:
> > > On 30/04/07, Alan Conway <ac...@redhat.com> wrote:
> > > > On Mon, 2007-04-30 at 13:02 -0400, Alan Conway wrote:
> > > > > I've been working on the M2 branch also and haven't seen the problem.
> > > > > Soon as I finish my current commit I'll make an RPM for you to try.
> > > >
> > > > Martin, if you're still looking for an M2 x86_64 build try these RPMs:
> > > > http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.x86_64.rpm
> > > > http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm
> > > >
> > > > Cheers,
> > > > Alan.
> > > >
> > >
> > > Thanks for the RPMs Alan. I wish I had better news, but the behaviour
> > > is the same. I must have some incompatible item installed. Do you have
> > > 32Bit rpm's to hand. Perhaps I can try and narrow down the problem.
> > >
> > > Cheers
> >
> > I just put x86 RPMs up in the same location.
> >
> > I'm a bit worried about what you're seeing, I'd like to pin it down. Let
> > me know if things work OK on 32 bit, and I'll think about how to get
> > some more info out of your stalled daemon. The ptrace you have looks
> > normal for a qpidd waiting for connections.
> >
> > Cheers,
> > Alan.
> >
> >
>
>
> --
> Martin Ritchie
>


-- 
Martin Ritchie

Re: [C++] Build

Posted by Martin Ritchie <ri...@apache.org>.
Hi,

http://rhm.et.redhat.com/download/
Did you put just the src rpms up?

On 01/05/07, Alan Conway <ac...@redhat.com> wrote:
> On Tue, 2007-05-01 at 07:56 +0100, Martin Ritchie wrote:
> > On 30/04/07, Alan Conway <ac...@redhat.com> wrote:
> > > On Mon, 2007-04-30 at 13:02 -0400, Alan Conway wrote:
> > > > I've been working on the M2 branch also and haven't seen the problem.
> > > > Soon as I finish my current commit I'll make an RPM for you to try.
> > >
> > > Martin, if you're still looking for an M2 x86_64 build try these RPMs:
> > > http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.x86_64.rpm
> > > http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm
> > >
> > > Cheers,
> > > Alan.
> > >
> >
> > Thanks for the RPMs Alan. I wish I had better news, but the behaviour
> > is the same. I must have some incompatible item installed. Do you have
> > 32Bit rpm's to hand. Perhaps I can try and narrow down the problem.
> >
> > Cheers
>
> I just put x86 RPMs up in the same location.
>
> I'm a bit worried about what you're seeing, I'd like to pin it down. Let
> me know if things work OK on 32 bit, and I'll think about how to get
> some more info out of your stalled daemon. The ptrace you have looks
> normal for a qpidd waiting for connections.
>
> Cheers,
> Alan.
>
>


-- 
Martin Ritchie

Re: [C++] Build

Posted by Alan Conway <ac...@redhat.com>.
On Tue, 2007-05-01 at 07:56 +0100, Martin Ritchie wrote:
> On 30/04/07, Alan Conway <ac...@redhat.com> wrote:
> > On Mon, 2007-04-30 at 13:02 -0400, Alan Conway wrote:
> > > I've been working on the M2 branch also and haven't seen the problem.
> > > Soon as I finish my current commit I'll make an RPM for you to try.
> >
> > Martin, if you're still looking for an M2 x86_64 build try these RPMs:
> > http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.x86_64.rpm
> > http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm
> >
> > Cheers,
> > Alan.
> >
> 
> Thanks for the RPMs Alan. I wish I had better news, but the behaviour
> is the same. I must have some incompatible item installed. Do you have
> 32Bit rpm's to hand. Perhaps I can try and narrow down the problem.
> 
> Cheers

I just put x86 RPMs up in the same location.

I'm a bit worried about what you're seeing, I'd like to pin it down. Let
me know if things work OK on 32 bit, and I'll think about how to get
some more info out of your stalled daemon. The ptrace you have looks
normal for a qpidd waiting for connections.

Cheers,
Alan.


Re: [C++] Build

Posted by John O'Hara <jo...@gmail.com>.
Very cool.  Thanks.

On 01/05/07, Robert Godfrey <ro...@gmail.com> wrote:
>
> FYI I independently built the C++ broker from M2 on a similar 64-bit
> computer (Fedora Core 6 x86-64) last night.  I got it running, and
> connected using the java client and managed a fair degree of
> interaction.
>
> Eventually the broker seemed to hang, but it was too late at night to
> start trying to diagnose.  Hopefully I'll get another chance to look
> at it this evening (the computer is at home).
>
> I downloaded and built all the known AMQ brokers (qpid, RabbitMQ and
> OpenAMQ) last night and will have a play at getting some interop and
> performance stats out of them as I get a chance...
>
> Cheers,
> Rob
>
> On 01/05/07, Martin Ritchie <ri...@apache.org> wrote:
> > On 30/04/07, Alan Conway <ac...@redhat.com> wrote:
> > > On Mon, 2007-04-30 at 13:02 -0400, Alan Conway wrote:
> > > > I've been working on the M2 branch also and haven't seen the
> problem.
> > > > Soon as I finish my current commit I'll make an RPM for you to try.
> > >
> > > Martin, if you're still looking for an M2 x86_64 build try these RPMs:
> > > http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.x86_64.rpm
> > > http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm
> > >
> > > Cheers,
> > > Alan.
> > >
> >
> > Thanks for the RPMs Alan. I wish I had better news, but the behaviour
> > is the same. I must have some incompatible item installed. Do you have
> > 32Bit rpm's to hand. Perhaps I can try and narrow down the problem.
> >
> > Cheers
> > --
> > Martin Ritchie
> >
>

Re: [C++] Build

Posted by Alan Conway <ac...@redhat.com>.
On Tue, 2007-05-01 at 08:23 +0100, Robert Godfrey wrote:
> FYI I independently built the C++ broker from M2 on a similar 64-bit
> computer (Fedora Core 6 x86-64) last night.  I got it running, and
> connected using the java client and managed a fair degree of
> interaction.
> 
> Eventually the broker seemed to hang, but it was too late at night to
> start trying to diagnose.  Hopefully I'll get another chance to look
> at it this evening (the computer is at home).
> 
Keep me informed. This plus Martin's problems may point to a race
condition somewhere in qpidd. I'll set up some stress tests and see if I
can reproduce it locally.

Cheers,
Alan.



Re: [C++] Build

Posted by Robert Godfrey <ro...@gmail.com>.
FYI I independently built the C++ broker from M2 on a similar 64-bit
computer (Fedora Core 6 x86-64) last night.  I got it running, and
connected using the java client and managed a fair degree of
interaction.

Eventually the broker seemed to hang, but it was too late at night to
start trying to diagnose.  Hopefully I'll get another chance to look
at it this evening (the computer is at home).

I downloaded and built all the known AMQ brokers (qpid, RabbitMQ and
OpenAMQ) last night and will have a play at getting some interop and
performance stats out of them as I get a chance...

Cheers,
Rob

On 01/05/07, Martin Ritchie <ri...@apache.org> wrote:
> On 30/04/07, Alan Conway <ac...@redhat.com> wrote:
> > On Mon, 2007-04-30 at 13:02 -0400, Alan Conway wrote:
> > > I've been working on the M2 branch also and haven't seen the problem.
> > > Soon as I finish my current commit I'll make an RPM for you to try.
> >
> > Martin, if you're still looking for an M2 x86_64 build try these RPMs:
> > http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.x86_64.rpm
> > http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm
> >
> > Cheers,
> > Alan.
> >
>
> Thanks for the RPMs Alan. I wish I had better news, but the behaviour
> is the same. I must have some incompatible item installed. Do you have
> 32Bit rpm's to hand. Perhaps I can try and narrow down the problem.
>
> Cheers
> --
> Martin Ritchie
>

Re: [C++] Build

Posted by Martin Ritchie <ri...@apache.org>.
On 30/04/07, Alan Conway <ac...@redhat.com> wrote:
> On Mon, 2007-04-30 at 13:02 -0400, Alan Conway wrote:
> > I've been working on the M2 branch also and haven't seen the problem.
> > Soon as I finish my current commit I'll make an RPM for you to try.
>
> Martin, if you're still looking for an M2 x86_64 build try these RPMs:
> http://rhm.et.redhat.com/download/qpidd-0.1-5.M2.x86_64.rpm
> http://rhm.et.redhat.com/download/qpidc-0.1-5.M2.x86_64.rpm
>
> Cheers,
> Alan.
>

Thanks for the RPMs Alan. I wish I had better news, but the behaviour
is the same. I must have some incompatible item installed. Do you have
32Bit rpm's to hand. Perhaps I can try and narrow down the problem.

Cheers
-- 
Martin Ritchie