[jira] [Created] (PROTON-509) Proton build fails on OS X 10.9
Hiram Chirino created PROTON-509: Summary: Proton build fails on OS X 10.9 Key: PROTON-509 URL: https://issues.apache.org/jira/browse/PROTON-509 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Hiram Chirino Fix For: 0.7 Build failure posted at: https://gist.github.com/chirino/8823091 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: error when building proton
Hi Alan, I have uuid-dev installed but it still cannot find it. Is there a flag on the CMakeLists file? I can't see it when running ccmake. Thank you, Roberto On Wed, Feb 5, 2014 at 11:07 AM, Alan Conway acon...@redhat.com wrote: On Tue, 2014-02-04 at 17:50 -0500, Roberto Pagliari wrote: I'm getting this error when using ccmake to build proton (on Ubuntu 12) CMake Error at proton-c/CMakeLists.txt:126 (message): No Uuid API found does anyone know how to fix it? I can't find this flag in ccmake gui and uuid is available on my system. You may need uuid-devel or whatever is the equivalent package on your distribution. E.g. on fedora 20 the libuuid package contains the uuid library, but libuuid-devel contains the .h files that are also needed to build proton.
Re: error when building proton
Watch out. On Fedora at least, there are two uuid packages, uuid[-devel] and and libuuid[-devel]. Perhaps the same confusing situation exists on Ubuntu. Justin On Wed, Feb 5, 2014 at 12:02 PM, Roberto Pagliari robe...@canary.is wrote: Hi Alan, I have uuid-dev installed but it still cannot find it. Is there a flag on the CMakeLists file? I can't see it when running ccmake. Thank you, Roberto On Wed, Feb 5, 2014 at 11:07 AM, Alan Conway acon...@redhat.com wrote: On Tue, 2014-02-04 at 17:50 -0500, Roberto Pagliari wrote: I'm getting this error when using ccmake to build proton (on Ubuntu 12) CMake Error at proton-c/CMakeLists.txt:126 (message): No Uuid API found does anyone know how to fix it? I can't find this flag in ccmake gui and uuid is available on my system. You may need uuid-devel or whatever is the equivalent package on your distribution. E.g. on fedora 20 the libuuid package contains the uuid library, but libuuid-devel contains the .h files that are also needed to build proton.
Re: error when building proton
Actually, I seem to remember ubunutu providing uuid in the e2fsprogs package. Struck me as odd at the time... - Original Message - From: Justin Ross justin.r...@gmail.com To: proton@qpid.apache.org Sent: Wednesday, February 5, 2014 12:08:48 PM Subject: Re: error when building proton Watch out. On Fedora at least, there are two uuid packages, uuid[-devel] and and libuuid[-devel]. Perhaps the same confusing situation exists on Ubuntu. Justin On Wed, Feb 5, 2014 at 12:02 PM, Roberto Pagliari robe...@canary.is wrote: Hi Alan, I have uuid-dev installed but it still cannot find it. Is there a flag on the CMakeLists file? I can't see it when running ccmake. Thank you, Roberto On Wed, Feb 5, 2014 at 11:07 AM, Alan Conway acon...@redhat.com wrote: On Tue, 2014-02-04 at 17:50 -0500, Roberto Pagliari wrote: I'm getting this error when using ccmake to build proton (on Ubuntu 12) CMake Error at proton-c/CMakeLists.txt:126 (message): No Uuid API found does anyone know how to fix it? I can't find this flag in ccmake gui and uuid is available on my system. You may need uuid-devel or whatever is the equivalent package on your distribution. E.g. on fedora 20 the libuuid package contains the uuid library, but libuuid-devel contains the .h files that are also needed to build proton. -- -K
[jira] [Created] (PROTON-510) hostname field in the Open command is not set
Ted Ross created PROTON-510: --- Summary: hostname field in the Open command is not set Key: PROTON-510 URL: https://issues.apache.org/jira/browse/PROTON-510 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.6 Reporter: Ted Ross If an address of the form amqp://dns.domain.com/path is used in Proton/Messenger, when the connection is opened, the hostname field in the Open should contain dns.domain.com. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: error when building proton
There's one other thing to be careful of... Once CMake determines that it's not there, it will not reconsider after you've installed the dependency. Make sure you delete your whole build directory and re-configure. -Ted On 02/05/2014 12:02 PM, Roberto Pagliari wrote: Hi Alan, I have uuid-dev installed but it still cannot find it. Is there a flag on the CMakeLists file? I can't see it when running ccmake. Thank you, Roberto On Wed, Feb 5, 2014 at 11:07 AM, Alan Conway acon...@redhat.com wrote: On Tue, 2014-02-04 at 17:50 -0500, Roberto Pagliari wrote: I'm getting this error when using ccmake to build proton (on Ubuntu 12) CMake Error at proton-c/CMakeLists.txt:126 (message): No Uuid API found does anyone know how to fix it? I can't find this flag in ccmake gui and uuid is available on my system. You may need uuid-devel or whatever is the equivalent package on your distribution. E.g. on fedora 20 the libuuid package contains the uuid library, but libuuid-devel contains the .h files that are also needed to build proton.
Re: error when building proton
Starting from scratch is definitely the safest bet, but I *thought* that you could just delete the CMakeCache.txt Frase On 05/02/14 18:53, Ted Ross wrote: There's one other thing to be careful of... Once CMake determines that it's not there, it will not reconsider after you've installed the dependency. Make sure you delete your whole build directory and re-configure. -Ted On 02/05/2014 12:02 PM, Roberto Pagliari wrote: Hi Alan, I have uuid-dev installed but it still cannot find it. Is there a flag on the CMakeLists file? I can't see it when running ccmake. Thank you, Roberto On Wed, Feb 5, 2014 at 11:07 AM, Alan Conway acon...@redhat.com wrote: On Tue, 2014-02-04 at 17:50 -0500, Roberto Pagliari wrote: I'm getting this error when using ccmake to build proton (on Ubuntu 12) CMake Error at proton-c/CMakeLists.txt:126 (message): No Uuid API found does anyone know how to fix it? I can't find this flag in ccmake gui and uuid is available on my system. You may need uuid-devel or whatever is the equivalent package on your distribution. E.g. on fedora 20 the libuuid package contains the uuid library, but libuuid-devel contains the .h files that are also needed to build proton.
[jira] [Updated] (PROTON-508) Use of Sasl auth results in a large performance hit.
[ https://issues.apache.org/jira/browse/PROTON-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated PROTON-508: Attachment: (was: PROTON-508.txt) Use of Sasl auth results in a large performance hit. Key: PROTON-508 URL: https://issues.apache.org/jira/browse/PROTON-508 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.6 Reporter: Timothy Bish Fix For: 0.7 Attachments: PROTON-508.txt Using proton engine in ActiveMQ to implement AMQP 1.0 support we noticed that a send from broker to the QPid JMS client is terribly slow for large messages. After some debugging it appears that the SaslImpl class imposes a pretty big penalty due to the way it wraps the input and output processors of the TransportImpl class. When sasl() method of TransportImpl is called to get hold of the Sasl impl for authentication the transport init method is called and buffers are allocated. In the SaslImpl class the result is that the output buffer is allocated with the default value of the remote max frame size since there hasn't been any negotiation yet. After the SASL handshake completes and the TransportImpl has updated itself to reflect the QPid client's preferred 64k max frame size, the SaslImpl instance still continues on with it's internal output buffer of 512 bytes. The end result of this is that as we attempt to send out a larger message we end up in a situation where we are draining the underlying transport output buffer 512 bytes at a time. I attached a patch that takes a stab at making the SaslImpl become a passive entity after it completes the handshake. In testing on ActiveMQ we go from sending out a 10mb message in 35+ seconds to around 300ms. Unfortunately some of the tests in the proton tests suite are now failing with this so it's not quite right. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (PROTON-508) Use of Sasl auth results in a large performance hit.
[ https://issues.apache.org/jira/browse/PROTON-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated PROTON-508: Attachment: PROTON-508.txt New patch that resolves the issue and keeps tests passing. Problem found in ConnectionImpl prevented pending data from being written on blocked channel. Use of Sasl auth results in a large performance hit. Key: PROTON-508 URL: https://issues.apache.org/jira/browse/PROTON-508 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.6 Reporter: Timothy Bish Fix For: 0.7 Attachments: PROTON-508.txt Using proton engine in ActiveMQ to implement AMQP 1.0 support we noticed that a send from broker to the QPid JMS client is terribly slow for large messages. After some debugging it appears that the SaslImpl class imposes a pretty big penalty due to the way it wraps the input and output processors of the TransportImpl class. When sasl() method of TransportImpl is called to get hold of the Sasl impl for authentication the transport init method is called and buffers are allocated. In the SaslImpl class the result is that the output buffer is allocated with the default value of the remote max frame size since there hasn't been any negotiation yet. After the SASL handshake completes and the TransportImpl has updated itself to reflect the QPid client's preferred 64k max frame size, the SaslImpl instance still continues on with it's internal output buffer of 512 bytes. The end result of this is that as we attempt to send out a larger message we end up in a situation where we are draining the underlying transport output buffer 512 bytes at a time. I attached a patch that takes a stab at making the SaslImpl become a passive entity after it completes the handshake. In testing on ActiveMQ we go from sending out a 10mb message in 35+ seconds to around 300ms. Unfortunately some of the tests in the proton tests suite are now failing with this so it's not quite right. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
