Re: Qpid Proton messenger on 32 bit linux
I use Proton with SwiftMQ broker which by default advertises max-frame-size=2147483647. Then realloc fails to allocate a memory region inside pn_buffer_ensure( disp-frame, disp-remote_max_frame) followed by a crash when disp-frame is used. Fortunately max-frame-size is configurable in SwiftMQ. I changed it to 65536 and Proton works now. -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Proton-messenger-on-32-bit-linux-tp7603445p7604255.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
[jira] [Created] (PROTON-515) Port to OpenVMS
Tomas Soltys created PROTON-515: --- Summary: Port to OpenVMS Key: PROTON-515 URL: https://issues.apache.org/jira/browse/PROTON-515 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.6 Environment: OpenVMS Reporter: Tomas Soltys Fix For: 0.7 There is a need for proton-c port to OpenVMS platform. To make proton-c functional on OpenVMS few changes in the source code are required. Here is list of files I have identified which require some attention: proton-c/src/platform_fmt.h proton-c/src/posix/driver.c proton-c/src/object/object.c proton-c/src/codec/codec.c proton-c/src/message/message.c -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (PROTON-515) Port to OpenVMS
[ https://issues.apache.org/jira/browse/PROTON-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Soltys updated PROTON-515: Attachment: platform_fmt.h.patch object.c.patch driver.c.patch codec.c.patch Attached are the patches which enable proton-c to be build and used on OpenVMS. Port to OpenVMS --- Key: PROTON-515 URL: https://issues.apache.org/jira/browse/PROTON-515 Project: Qpid Proton Issue Type: Improvement Components: proton-c Affects Versions: 0.6 Environment: OpenVMS Reporter: Tomas Soltys Labels: OpenVMS, patch Fix For: 0.7 Attachments: codec.c.patch, driver.c.patch, object.c.patch, platform_fmt.h.patch There is a need for proton-c port to OpenVMS platform. To make proton-c functional on OpenVMS few changes in the source code are required. Here is list of files I have identified which require some attention: proton-c/src/platform_fmt.h proton-c/src/posix/driver.c proton-c/src/object/object.c proton-c/src/codec/codec.c proton-c/src/message/message.c -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: Qpid Proton messenger on 32 bit linux
This behavior is a bug. I've opened a Jira: https://issues.apache.org/jira/browse/PROTON-516 - Original Message - From: serega sergejs.melde...@sap.com To: proton@qpid.apache.org Sent: Monday, February 10, 2014 4:29:25 AM Subject: Re: Qpid Proton messenger on 32 bit linux I use Proton with SwiftMQ broker which by default advertises max-frame-size=2147483647. Then realloc fails to allocate a memory region inside pn_buffer_ensure( disp-frame, disp-remote_max_frame) followed by a crash when disp-frame is used. Fortunately max-frame-size is configurable in SwiftMQ. I changed it to 65536 and Proton works now. -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Proton-messenger-on-32-bit-linux-tp7603445p7604255.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com. -- -K
[jira] [Created] (PROTON-516) [proton-c] Dispatcher frame buffer set to peer's max frame size.
Ken Giusti created PROTON-516: - Summary: [proton-c] Dispatcher frame buffer set to peer's max frame size. Key: PROTON-516 URL: https://issues.apache.org/jira/browse/PROTON-516 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.6 Reporter: Ken Giusti Fix For: 0.7 The size of the output frame buffer used by the Transport is set unconditionally to the max frame size advertised by the peer: In transport.c::int pn_do_open(pn_dispatcher_t *disp): pn_buffer_ensure( disp-frame, disp-remote_max_frame ); This can potentially exhaust memory on small memory systems (eg, embedded devices). Instead, the output frame buffer should grow as needed based on the size of the payloads generated, limited by the remote_max_frame value. And, of course, pn_buffer_ensure + caller should handle realloc failures instead of ignoring them. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: error when building proton
On Wed, Feb 05, 2014 at 12:08:48PM -0500, Justin Ross wrote: 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. On Debian the proper package is uuid-dev. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ pgpxfKciddcTw.pgp Description: PGP signature
[jira] [Created] (PROTON-517) ssl sniffing is broken
Rafael H. Schloming created PROTON-517: -- Summary: ssl sniffing is broken Key: PROTON-517 URL: https://issues.apache.org/jira/browse/PROTON-517 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Rafael H. Schloming Assignee: Rafael H. Schloming -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (PROTON-517) ssl sniffing is broken
[ https://issues.apache.org/jira/browse/PROTON-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved PROTON-517. Resolution: Fixed ssl sniffing is broken -- Key: PROTON-517 URL: https://issues.apache.org/jira/browse/PROTON-517 Project: Qpid Proton Issue Type: Bug Components: proton-j Reporter: Rafael H. Schloming Assignee: Rafael H. Schloming -- This message was sent by Atlassian JIRA (v6.1.5#6160)
