Menu Search

Qpid Proton 0.9 Release Notes

Proton is a high-performance, lightweight messaging library. More about Qpid Proton.

For more information about this release, including download links and documentation, see the release overview.

New features and improvements

  • PROTON-471 - Expose the Messenger work method in Perl bindings
  • PROTON-697 - SChannel SSL/TLS support for Proton-c on Windows
  • PROTON-747 - Use around wrapper on Messenger methods to raise errors
  • PROTON-750 - Have distinct API to indicate SSL layer is not really implemented
  • PROTON-753 - [proton-j] provide constants for descriptors required to configure source delivery outcomes
  • PROTON-769 - Simplify the trace flag logic by only keeping a single copy
  • PROTON-770 - Refactor Proton C to eliminate the pn_dispatcher_t class
  • PROTON-805 - Add dispatch request-response extension to utils.py
  • PROTON-812 - LinkException needs an attribute that indicates the reason for the exception.
  • PROTON-816 - Add access to dynamic-node-properties in termini
  • PROTON-819 - BlockingLink.__init__() raise LinkDetached instead of LinkException

Bugs fixed

  • PROTON-154 - proton-j: link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach
  • PROTON-548 - Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)
  • PROTON-563 - Generated Proton.sln doesn't compile
  • PROTON-578 - proton-c: windows/io.c prints "Unknown error" for all winsock errors
  • PROTON-667 - add support for transactional state and enable outgoing transfer frames to specify a txn-id
  • PROTON-723 - Proton-c does not support attaching to the transaction coordinator
  • PROTON-730 - Can't read transactional state set on incoming transfer
  • PROTON-736 - ruby: unable to send binary data?
  • PROTON-737 - [PATCH] ruby: StateError not included in exceptions
  • PROTON-739 - [PATCH] ruby: update messenger#subscribe to accept TTL
  • PROTON-742 - Proton Windows SChannel buffer copy error
  • PROTON-743 - [PATCH] ruby: user doesn't have access to clear messenger error object
  • PROTON-745 - DataImpl cant roundtrip a Symbol array it decoded.
  • PROTON-746 - Qpid::Proton::Messenger fails to encode a Ruby Symbol type.
  • PROTON-751 - [PATCH] proton-c: pn_connect failures aren't exposed via messenger->error
  • PROTON-752 - Ruby: Cproton calls don't unlock the GIL for blocking / long-running operations
  • PROTON-757 - [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards
  • PROTON-762 - Javascript tests run when emscripten is not installed (and fail)
  • PROTON-765 - 64-bit values are not being properly marshalled in Ruby on 32-bit systems
  • PROTON-771 - AMQP and SASL performatives are not validated against correct frame type
  • PROTON-775 - ruby: message annotations send from a ruby client are invalid
  • PROTON-779 - Building Proton documentation fails due to missing proton.py file
  • PROTON-784 - Settled Deliveries keep piling up, and do not seem to get freed from heap
  • PROTON-792 - [contrib/proton-jms] remove stale support of byte destination type annotation from message transformers
  • PROTON-794 - [Windows] Visual Studio 2008 compile error
  • PROTON-798 - Hang in Windows SSL negotiation
  • PROTON-800 - [Windows C] Reactor test times out
  • PROTON-804 - the transport doesn't always shutdown its output properly
  • PROTON-807 - Proton does not decode AMQP small long encoding correctly and does not use it.
  • PROTON-809 - Changes to build on AIX with IBM XL C
  • PROTON-811 - [PATCH] proton-j: no way to implement idle timeout of a connection
  • PROTON-814 - proton-c: pn_selector_select caches its return code from a previous error
  • PROTON-815 - LinkException on BlockingConnection.create_receiver() leaves things in bad state.
  • PROTON-817 - BlockingConnection doesn't pass options down in create_sender or create_receiver
  • PROTON-820 - Windows build error for perlPERL_wrap.c
  • PROTON-822 - Valgrind errors and problems with dispatch system tests.
  • PROTON-823 - Proton prints some log/trace information to stdout/stderr.
  • PROTON-825 - BlockingReceiver.receive() uses 100% CPU.
  • PROTON-828 - Python binding does not support MODIFIED delivery state
  • PROTON-831 - proton_tests.utils.SyncRequestResponseTest.test_request_response test fails on RHEL 5
  • PROTON-832 - messenger: next_drain is not reset for "manual" link credit mode in messenger
  • PROTON-833 - transport can emit frames with an invalid channel number after local session close
  • PROTON-835 - strncmp in pn_data_lookup doesn't work in some cases
  • PROTON-836 - Missing import SSLUnavailable in reactor.py
  • PROTON-839 - Proton 0.9 RC 2 blocker - proton_tests.utils.SyncRequestResponseTest.test_request_response ........ fail