You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Ted Ross <tr...@redhat.com> on 2015/09/04 16:30:23 UTC
Qpid Dispatch Router 0.5 RC2
Qpid Dispatch Router 0.5 RC2 can be found here:
http://people.apache.org/~tross/qpid-dispatch-0.5rc2
There are two changes since RC1:
- The missing sasl configuration file is now installed
- Listener configuration was simplified:
o The 'insecureOk' option for authenticatePeer was removed.
authenticatePeer is now a yes/no boolean. Insecure
authentication methods are allowed. This feature was proving to
be confusing and frustrating to testers. We will re-add it later
if there is a call to do so.
o saslMechanisms is now an optional attribute. If omitted, any
available mechanism can be used.
On 08/28/2015 09:50 AM, Ted Ross wrote:
> I've created a release candidate for Dispatch Router 0.5. The primary
> reason for this release is to conform to the incompatible changes in the
> Proton API. The tarball can be found here:
>
> http://people.apache.org/~tross/qpid-dispatch-0.5rc1
>
> The following improvements and bug fixes are included in this release:
>
> Improvements:
>
> DISPATCH-98 Refactor the handling of Message Annotations
> DISPATCH-99 Allow override of the forwarding logic on a per-address
> basis.
> DISPATCH-101 Create a field iterator that is specific to handling
> address fields
> DISPATCH-110 Provide access to recent log messages via management agent.
> DISPATCH-121 Allow pool allocation to be switched for plain allocation
> at build time.
> DISPATCH-123 Separate target to build documentation.
> DISPATCH-136 qdstat -n doesn't show the local router in the list
> DISPATCH-142 Move proton event handling from container down to server
> DISPATCH-145 Add identifying information to the properties map of the
> Open performative
> DISPATCH-149 Properly handle different detach/close scenarios for links
> DISPATCH-152 Expose SASL-related data via management
> DISPATCH-153 Expose full set of security capabilities via configuration
>
> Bug Fixes:
>
> DISPATCH-131 Valgrind errors during the system tests are not reported
> DISPATCH-132 Time values overflow on 32 bit systems
> DISPATCH-133 Router Link use-after-free
> DISPATCH-134 Driver runs at 100% CPU intermittently
> DISPATCH-137 Dispatch Code should be updated to support newer SASL
> calls in qpid-proton
> DISPATCH-143 Link-routing - Various robustness problems
> DISPATCH-146 management query sends non string values
> DISPATCH-154 dispatch-router coredumps when connector address is
> unresolvable
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid Dispatch Router 0.5 RC2
Posted by Ted Ross <tr...@redhat.com>.
On 09/08/2015 03:40 PM, Gordon Sim wrote:
> On 09/04/2015 03:30 PM, Ted Ross wrote:
>> Qpid Dispatch Router 0.5 RC2 can be found here:
>>
>> http://people.apache.org/~tross/qpid-dispatch-0.5rc2
>>
>> There are two changes since RC1:
>>
>> - The missing sasl configuration file is now installed
>> - Listener configuration was simplified:
>> o The 'insecureOk' option for authenticatePeer was removed.
>> authenticatePeer is now a yes/no boolean. Insecure
>> authentication methods are allowed. This feature was proving to
>> be confusing and frustrating to testers. We will re-add it later
>> if there is a call to do so.
>> o saslMechanisms is now an optional attribute. If omitted, any
>> available mechanism can be used.
>
> I see the following test failures, anything to be concerned about? Is it
> just some configuration/setup issue on my part?
Yes, this is an issue for which I will raise a Jira shortly. It is
caused by your sasl configuration not supporting EXTERNAL.
We need to update the tests to use a test-controlled SASL configuration.
My plan was to fix this for the next release.
>
>> 16/17 Test: system_tests_qdstat
>> Command: "/usr/bin/python"
>> "/home/gordon/qpid-releases/dispatch/0.5/build/tests/run.py" "-m"
>> "system_tests_qdstat" "-v"
>> Directory: /home/gordon/qpid-releases/dispatch/0.5/build/tests
>> "system_tests_qdstat" start time: Sep 08 20:35 BST
>> Output:
>> ----------------------------------------------------------
>> test_ssl_bad_trustfile_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_bad_trustfile_to_strict (system_tests_qdstat.QdstatSslTest)
>> ... ok
>> test_ssl_bad_trustfile_to_unsecured
>> (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_cert_to_auth (system_tests_qdstat.QdstatSslTest) ... FAIL
>> test_ssl_cert_to_none (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_cert_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_cert_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_none (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_none_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_none_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_none_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_schema_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_schema_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_schema_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_scheme_to_none (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_trustfile_cert_to_auth (system_tests_qdstat.QdstatSslTest)
>> ... FAIL
>> test_ssl_trustfile_cert_to_strict (system_tests_qdstat.QdstatSslTest)
>> ... ok
>> test_ssl_trustfile_cert_to_unsecured
>> (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_trustfile_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_trustfile_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
>> test_ssl_trustfile_to_unsecured (system_tests_qdstat.QdstatSslTest)
>> ... ok
>> test_address (system_tests_qdstat.QdstatTest) ... ok
>> test_connections (system_tests_qdstat.QdstatTest) ... ok
>> test_general (system_tests_qdstat.QdstatTest) ... ok
>> test_help (system_tests_qdstat.QdstatTest) ... ok
>> test_links (system_tests_qdstat.QdstatTest) ... ok
>> test_log (system_tests_qdstat.QdstatTest) ... ok
>> test_memory (system_tests_qdstat.QdstatTest) ... ok
>> test_nodes (system_tests_qdstat.QdstatTest) ... ok
>>
>> ======================================================================
>> FAIL: test_ssl_cert_to_auth (system_tests_qdstat.QdstatSslTest)
>> ----------------------------------------------------------------------
>> Traceback (most recent call last):
>> File
>> "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py",
>> line 177, in test_ssl_cert_to_auth
>> self.ssl_test('auth_s', ['client_cert_all'])
>> File
>> "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py",
>> line 131, in ssl_test
>> address=str(urls[url_name]))
>> File
>> "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py",
>> line 108, in run_qdstat
>> "qdstat exit status %s, output:\n%s" % (p.returncode, out)
>> AssertionError: qdstat exit status 1, output:
>> ConnectionException: Connection amqps://0.0.0.0:25009/$management
>> disconnected
>>
>>
>> ======================================================================
>> FAIL: test_ssl_trustfile_cert_to_auth (system_tests_qdstat.QdstatSslTest)
>> ----------------------------------------------------------------------
>> Traceback (most recent call last):
>> File
>> "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py",
>> line 180, in test_ssl_trustfile_cert_to_auth
>> self.ssl_test('auth_s', ['trustfile', 'client_cert_all'])
>> File
>> "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py",
>> line 131, in ssl_test
>> address=str(urls[url_name]))
>> File
>> "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py",
>> line 108, in run_qdstat
>> "qdstat exit status %s, output:\n%s" % (p.returncode, out)
>> AssertionError: qdstat exit status 1, output:
>> ConnectionException: Connection amqps://0.0.0.0:25009/$management
>> disconnected
>>
>>
>> ----------------------------------------------------------------------
>> Ran 29 tests in 8.372s
>>
>> FAILED (failures=2)
>> <end of output>
>> Test time = 8.55 sec
>> ----------------------------------------------------------
>> Test Failed.
>> "system_tests_qdstat" end time: Sep 08 20:35 BST
>> "system_tests_qdstat" time elapsed: 00:00:08
>> ----------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid Dispatch Router 0.5 RC2
Posted by Gordon Sim <gs...@redhat.com>.
On 09/04/2015 03:30 PM, Ted Ross wrote:
> Qpid Dispatch Router 0.5 RC2 can be found here:
>
> http://people.apache.org/~tross/qpid-dispatch-0.5rc2
>
> There are two changes since RC1:
>
> - The missing sasl configuration file is now installed
> - Listener configuration was simplified:
> o The 'insecureOk' option for authenticatePeer was removed.
> authenticatePeer is now a yes/no boolean. Insecure
> authentication methods are allowed. This feature was proving to
> be confusing and frustrating to testers. We will re-add it later
> if there is a call to do so.
> o saslMechanisms is now an optional attribute. If omitted, any
> available mechanism can be used.
I see the following test failures, anything to be concerned about? Is it
just some configuration/setup issue on my part?
> 16/17 Test: system_tests_qdstat
> Command: "/usr/bin/python" "/home/gordon/qpid-releases/dispatch/0.5/build/tests/run.py" "-m" "system_tests_qdstat" "-v"
> Directory: /home/gordon/qpid-releases/dispatch/0.5/build/tests
> "system_tests_qdstat" start time: Sep 08 20:35 BST
> Output:
> ----------------------------------------------------------
> test_ssl_bad_trustfile_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_bad_trustfile_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_bad_trustfile_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_cert_to_auth (system_tests_qdstat.QdstatSslTest) ... FAIL
> test_ssl_cert_to_none (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_cert_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_cert_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_none (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_none_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_none_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_none_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_schema_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_schema_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_schema_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_scheme_to_none (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_trustfile_cert_to_auth (system_tests_qdstat.QdstatSslTest) ... FAIL
> test_ssl_trustfile_cert_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_trustfile_cert_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_trustfile_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_trustfile_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
> test_ssl_trustfile_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
> test_address (system_tests_qdstat.QdstatTest) ... ok
> test_connections (system_tests_qdstat.QdstatTest) ... ok
> test_general (system_tests_qdstat.QdstatTest) ... ok
> test_help (system_tests_qdstat.QdstatTest) ... ok
> test_links (system_tests_qdstat.QdstatTest) ... ok
> test_log (system_tests_qdstat.QdstatTest) ... ok
> test_memory (system_tests_qdstat.QdstatTest) ... ok
> test_nodes (system_tests_qdstat.QdstatTest) ... ok
>
> ======================================================================
> FAIL: test_ssl_cert_to_auth (system_tests_qdstat.QdstatSslTest)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py", line 177, in test_ssl_cert_to_auth
> self.ssl_test('auth_s', ['client_cert_all'])
> File "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py", line 131, in ssl_test
> address=str(urls[url_name]))
> File "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py", line 108, in run_qdstat
> "qdstat exit status %s, output:\n%s" % (p.returncode, out)
> AssertionError: qdstat exit status 1, output:
> ConnectionException: Connection amqps://0.0.0.0:25009/$management disconnected
>
>
> ======================================================================
> FAIL: test_ssl_trustfile_cert_to_auth (system_tests_qdstat.QdstatSslTest)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py", line 180, in test_ssl_trustfile_cert_to_auth
> self.ssl_test('auth_s', ['trustfile', 'client_cert_all'])
> File "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py", line 131, in ssl_test
> address=str(urls[url_name]))
> File "/home/gordon/qpid-releases/dispatch/0.5/qpid-dispatch-0.5/tests/system_tests_qdstat.py", line 108, in run_qdstat
> "qdstat exit status %s, output:\n%s" % (p.returncode, out)
> AssertionError: qdstat exit status 1, output:
> ConnectionException: Connection amqps://0.0.0.0:25009/$management disconnected
>
>
> ----------------------------------------------------------------------
> Ran 29 tests in 8.372s
>
> FAILED (failures=2)
> <end of output>
> Test time = 8.55 sec
> ----------------------------------------------------------
> Test Failed.
> "system_tests_qdstat" end time: Sep 08 20:35 BST
> "system_tests_qdstat" time elapsed: 00:00:08
> ----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: [VOTE] Qpid Dispatch Router 0.5
Posted by Ted Ross <tr...@redhat.com>.
-1
Unfortunately, I need to vote down this release candidate. Due to
PROTON-989, this release crashes when run against some of the example
configurations in its own tests folder. (Hat tip to Mick Goulish for
finding this).
I will cancel this vote and release a new RC with a workaround for this bug.
-Ted
On 09/08/2015 09:23 AM, Ted Ross wrote:
> This is the vote thread for releasing Qpid Dispatch Router 0.5 RC2 as
> the final 0.5.
>
> Please record your vote for or against on this thread.
>
> Thanks,
> -Ted
>
>
> On 09/04/2015 10:30 AM, Ted Ross wrote:
>> Qpid Dispatch Router 0.5 RC2 can be found here:
>>
>> http://people.apache.org/~tross/qpid-dispatch-0.5rc2
>>
>> There are two changes since RC1:
>>
>> - The missing sasl configuration file is now installed
>> - Listener configuration was simplified:
>> o The 'insecureOk' option for authenticatePeer was removed.
>> authenticatePeer is now a yes/no boolean. Insecure
>> authentication methods are allowed. This feature was proving to
>> be confusing and frustrating to testers. We will re-add it later
>> if there is a call to do so.
>> o saslMechanisms is now an optional attribute. If omitted, any
>> available mechanism can be used.
>>
>> On 08/28/2015 09:50 AM, Ted Ross wrote:
>>> I've created a release candidate for Dispatch Router 0.5. The primary
>>> reason for this release is to conform to the incompatible changes in the
>>> Proton API. The tarball can be found here:
>>>
>>> http://people.apache.org/~tross/qpid-dispatch-0.5rc1
>>>
>>> The following improvements and bug fixes are included in this release:
>>>
>>> Improvements:
>>>
>>> DISPATCH-98 Refactor the handling of Message Annotations
>>> DISPATCH-99 Allow override of the forwarding logic on a per-address
>>> basis.
>>> DISPATCH-101 Create a field iterator that is specific to handling
>>> address fields
>>> DISPATCH-110 Provide access to recent log messages via management agent.
>>> DISPATCH-121 Allow pool allocation to be switched for plain allocation
>>> at build time.
>>> DISPATCH-123 Separate target to build documentation.
>>> DISPATCH-136 qdstat -n doesn't show the local router in the list
>>> DISPATCH-142 Move proton event handling from container down to server
>>> DISPATCH-145 Add identifying information to the properties map of the
>>> Open performative
>>> DISPATCH-149 Properly handle different detach/close scenarios for links
>>> DISPATCH-152 Expose SASL-related data via management
>>> DISPATCH-153 Expose full set of security capabilities via configuration
>>>
>>> Bug Fixes:
>>>
>>> DISPATCH-131 Valgrind errors during the system tests are not reported
>>> DISPATCH-132 Time values overflow on 32 bit systems
>>> DISPATCH-133 Router Link use-after-free
>>> DISPATCH-134 Driver runs at 100% CPU intermittently
>>> DISPATCH-137 Dispatch Code should be updated to support newer SASL
>>> calls in qpid-proton
>>> DISPATCH-143 Link-routing - Various robustness problems
>>> DISPATCH-146 management query sends non string values
>>> DISPATCH-154 dispatch-router coredumps when connector address is
>>> unresolvable
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
[VOTE-CANCELED] Qpid Dispatch Router 0.5
Posted by Ted Ross <tr...@redhat.com>.
I've canceled this vote due to a blocker problem found in RC2.
-Ted
On 09/08/2015 09:23 AM, Ted Ross wrote:
> This is the vote thread for releasing Qpid Dispatch Router 0.5 RC2 as
> the final 0.5.
>
> Please record your vote for or against on this thread.
>
> Thanks,
> -Ted
>
>
> On 09/04/2015 10:30 AM, Ted Ross wrote:
>> Qpid Dispatch Router 0.5 RC2 can be found here:
>>
>> http://people.apache.org/~tross/qpid-dispatch-0.5rc2
>>
>> There are two changes since RC1:
>>
>> - The missing sasl configuration file is now installed
>> - Listener configuration was simplified:
>> o The 'insecureOk' option for authenticatePeer was removed.
>> authenticatePeer is now a yes/no boolean. Insecure
>> authentication methods are allowed. This feature was proving to
>> be confusing and frustrating to testers. We will re-add it later
>> if there is a call to do so.
>> o saslMechanisms is now an optional attribute. If omitted, any
>> available mechanism can be used.
>>
>> On 08/28/2015 09:50 AM, Ted Ross wrote:
>>> I've created a release candidate for Dispatch Router 0.5. The primary
>>> reason for this release is to conform to the incompatible changes in the
>>> Proton API. The tarball can be found here:
>>>
>>> http://people.apache.org/~tross/qpid-dispatch-0.5rc1
>>>
>>> The following improvements and bug fixes are included in this release:
>>>
>>> Improvements:
>>>
>>> DISPATCH-98 Refactor the handling of Message Annotations
>>> DISPATCH-99 Allow override of the forwarding logic on a per-address
>>> basis.
>>> DISPATCH-101 Create a field iterator that is specific to handling
>>> address fields
>>> DISPATCH-110 Provide access to recent log messages via management agent.
>>> DISPATCH-121 Allow pool allocation to be switched for plain allocation
>>> at build time.
>>> DISPATCH-123 Separate target to build documentation.
>>> DISPATCH-136 qdstat -n doesn't show the local router in the list
>>> DISPATCH-142 Move proton event handling from container down to server
>>> DISPATCH-145 Add identifying information to the properties map of the
>>> Open performative
>>> DISPATCH-149 Properly handle different detach/close scenarios for links
>>> DISPATCH-152 Expose SASL-related data via management
>>> DISPATCH-153 Expose full set of security capabilities via configuration
>>>
>>> Bug Fixes:
>>>
>>> DISPATCH-131 Valgrind errors during the system tests are not reported
>>> DISPATCH-132 Time values overflow on 32 bit systems
>>> DISPATCH-133 Router Link use-after-free
>>> DISPATCH-134 Driver runs at 100% CPU intermittently
>>> DISPATCH-137 Dispatch Code should be updated to support newer SASL
>>> calls in qpid-proton
>>> DISPATCH-143 Link-routing - Various robustness problems
>>> DISPATCH-146 management query sends non string values
>>> DISPATCH-154 dispatch-router coredumps when connector address is
>>> unresolvable
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
[VOTE] Qpid Dispatch Router 0.5
Posted by Ted Ross <tr...@redhat.com>.
This is the vote thread for releasing Qpid Dispatch Router 0.5 RC2 as
the final 0.5.
Please record your vote for or against on this thread.
Thanks,
-Ted
On 09/04/2015 10:30 AM, Ted Ross wrote:
> Qpid Dispatch Router 0.5 RC2 can be found here:
>
> http://people.apache.org/~tross/qpid-dispatch-0.5rc2
>
> There are two changes since RC1:
>
> - The missing sasl configuration file is now installed
> - Listener configuration was simplified:
> o The 'insecureOk' option for authenticatePeer was removed.
> authenticatePeer is now a yes/no boolean. Insecure
> authentication methods are allowed. This feature was proving to
> be confusing and frustrating to testers. We will re-add it later
> if there is a call to do so.
> o saslMechanisms is now an optional attribute. If omitted, any
> available mechanism can be used.
>
> On 08/28/2015 09:50 AM, Ted Ross wrote:
>> I've created a release candidate for Dispatch Router 0.5. The primary
>> reason for this release is to conform to the incompatible changes in the
>> Proton API. The tarball can be found here:
>>
>> http://people.apache.org/~tross/qpid-dispatch-0.5rc1
>>
>> The following improvements and bug fixes are included in this release:
>>
>> Improvements:
>>
>> DISPATCH-98 Refactor the handling of Message Annotations
>> DISPATCH-99 Allow override of the forwarding logic on a per-address
>> basis.
>> DISPATCH-101 Create a field iterator that is specific to handling
>> address fields
>> DISPATCH-110 Provide access to recent log messages via management agent.
>> DISPATCH-121 Allow pool allocation to be switched for plain allocation
>> at build time.
>> DISPATCH-123 Separate target to build documentation.
>> DISPATCH-136 qdstat -n doesn't show the local router in the list
>> DISPATCH-142 Move proton event handling from container down to server
>> DISPATCH-145 Add identifying information to the properties map of the
>> Open performative
>> DISPATCH-149 Properly handle different detach/close scenarios for links
>> DISPATCH-152 Expose SASL-related data via management
>> DISPATCH-153 Expose full set of security capabilities via configuration
>>
>> Bug Fixes:
>>
>> DISPATCH-131 Valgrind errors during the system tests are not reported
>> DISPATCH-132 Time values overflow on 32 bit systems
>> DISPATCH-133 Router Link use-after-free
>> DISPATCH-134 Driver runs at 100% CPU intermittently
>> DISPATCH-137 Dispatch Code should be updated to support newer SASL
>> calls in qpid-proton
>> DISPATCH-143 Link-routing - Various robustness problems
>> DISPATCH-146 management query sends non string values
>> DISPATCH-154 dispatch-router coredumps when connector address is
>> unresolvable
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org