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 2017/03/29 11:32:42 UTC

Qpid Dispatch Router 0.8.0 Release Candidate 1

The first release candidate for Qpid Dispatch Router 0.8.0 is ready for 
evaluation.

Build Artifacts:

     https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/

New Features:

     DISPATCH-103 - Websocket Listeners
     DISPATCH-195 - Add support for transactional messages in the Router
     DISPATCH-441 - Support password environment variable in qdrouter config
     DISPATCH-467 - Terminus renaming for autoLinks
     DISPATCH-529 - Address annotation for Multi-Tenancy
     DISPATCH-726 - Connection Property for Failover Servers

Improvements:

     DISPATCH-113 - expose NodeTracker::last_topology_change in management
     DISPATCH-542 - Popup text for clients should indicate if the client 
is a sender or receiver
     DISPATCH-543 - Initial load of topology page fetches too much 
information
     DISPATCH-544 - Add ability to hide the info panel on the left of 
the topology page
     DISPATCH-552 - Allow only one tree node to be expanded if there is 
a large number of routers
     DISPATCH-553 - Add statistic counter to the "log" entity to count 
log events per severity
     DISPATCH-559 - qdstat - Request only the columns that will be used 
in the display
     DISPATCH-561 - Create python program that returns fake management data
     DISPATCH-568 - Iterator module cleanup
     DISPATCH-570 - Add some counts to qdstat -g
     DISPATCH-572 - Adding log info with proton transport id and related 
remote IP/port
     DISPATCH-576 - Use new log entity statistic counter in console
     DISPATCH-578 - Dispatch trace logging forces all proton tracing on
     DISPATCH-579 - Expose software version via management
     DISPATCH-592 - Attempt to auto-login to the host:port that served 
the web page
     DISPATCH-597 - Log enhancements
     DISPATCH-600 - Support secure websockets
     DISPATCH-602 - Add a favicon to the stand-alone router site
     DISPATCH-606 - Default session window is too small, causing 
performance bottlenecks
     DISPATCH-627 - BatchedSettlement test fails with timeout on slower 
systems
     DISPATCH-629 - Add a protocol-version to the inter-router protocol 
to enable backward compatibility
     DISPATCH-641 - Make containerId attribute work with clients

Bugs Fixed:

     DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
     DISPATCH-216 - system_tests_protocol_family fails on systems with 
no IPv6
     DISPATCH-296 - segfault on router startup
     DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
     DISPATCH-314 - If a router has a normal listener, show it in a 
different color on the topology page
     DISPATCH-324 - Improve initial layout of topology node
     DISPATCH-344 - memory growth after repeated calls from qdstat -m
     DISPATCH-352 - Crash with empty configuration file
     DISPATCH-355 - query fails with what seems to be the error of a 
previous command
     DISPATCH-357 - Address field is empty for link routed links in the 
qdstat "links" output
     DISPATCH-433 - Navigating to console from bookmark displays empty 
page with just toolbars
     DISPATCH-451 - [AMQP] Hard coded session capacity should be 
configurable
     DISPATCH-503 - [display_name] successful test runs  have non-ascii 
characters in router log
     DISPATCH-504 - [display_name] successful test runs have invalid 
message errors  in router log
     DISPATCH-506 - Detach with no "error" sent by router on client TCP 
connection dropped
     DISPATCH-516 - Core dump when displayname IO adapter receives 
message with no reply-to
     DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch 
0.7.0
     DISPATCH-527 - The $displayname address is currently available. It 
should not be available to external users
     DISPATCH-530 - Cannot connect using Firefox 48+
     DISPATCH-534 - Node selection and location is lost when the 
topology changes
     DISPATCH-536 - Circular buffer overflow errors occur when there are 
a large number of routers
     DISPATCH-538 - Highlighted path between routers sometimes doesn't 
unhighlight
     DISPATCH-540 - Clients with both in and out links are rendered in 
yellow
     DISPATCH-541 - Highlighted path between routers contains black arrows
     DISPATCH-546 - Crosssection popup position is incorrect
     DISPATCH-547 - Stand-alone version can't download generated config 
file for new nodes
     DISPATCH-554 - Topology nodes and links are too far apart when 
there are a large number of routers
     DISPATCH-556 - qdstat fails at high scale
     DISPATCH-557 - High connection rates cause problems in the Python 
management agent
     DISPATCH-560 - [console] Only use the color red to indicate a 
failure/issue.
     DISPATCH-563 - Topology graph flashes and redraws a few seconds 
after it is 1st drawn
     DISPATCH-564 - Error when switching routers on Entities page
     DISPATCH-565 - Error fetching log on Entities page
     DISPATCH-566 - Message annotations are not propagated to brokers on 
a linkRoute
     DISPATCH-567 - Slight but persistent memory leak when running java 
messenger producer and consumer
     DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t 
enum values.
     DISPATCH-573 - Memory leaks on shutdown
     DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
     DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
     DISPATCH-581 - detach with closed=false propagated as closed=true 
on link route
     DISPATCH-582 - Memory Leak with reactor client
     DISPATCH-583 - Random segmentation fault
     DISPATCH-585 - Firefox dropdown and buttons on list page have 
incorrect padding
     DISPATCH-586 - Dispatch crash on running c sender and receiver
     DISPATCH-587 - Provide feedback when loading log entries
     DISPATCH-588 - Schema is not loaded if auto-login is enabled
     DISPATCH-589 - Missing links on topology page
     DISPATCH-594 - Log file over-written every time the router is restarted
     DISPATCH-595 - dispositions propagated after link detach on link route
     DISPATCH-596 - error is lost from rejected state in relayed disposition
     DISPATCH-598 - Router crash when calling sender and session close 
methods in onLinkFLow()
     DISPATCH-599 - Link routing : messages is not transferred if sender 
detach link immediately
     DISPATCH-601 - Valgrind errors in dispatch tests
     DISPATCH-603 - address resource leak
     DISPATCH-604 - Management - Link connection-id does not match 
identities of connections
     DISPATCH-605 - Memory Leak with multple sender/receivers in one session
     DISPATCH-607 - Handle empty response from GET-MGMT-NODES
     DISPATCH-608 - Links not cleaned up when a close is sent without 
being preceeded by a detach and end
     DISPATCH-609 - Name attribute is duplicated in QUERY response
     DISPATCH-610 - crash in qdr_link_cleanup_CT
     DISPATCH-611 - Router core dump with old config file
     DISPATCH-612 - Add support for GCC equivalent compiler options
     DISPATCH-613 - Remove semi-colon not needed after function definition
     DISPATCH-614 - strerror_r on Solaris does not return char*
     DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
     DISPATCH-616 - Arithmetic operations not allowed on void * pointer
     DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where 
_POSIX_HOST_NAME_MAX is defined instead
     DISPATCH-618 - Revert eventfd on Solaris
     DISPATCH-619 - Use memalign instead of posix_memalign which is not 
defined on Solaris
     DISPATCH-620 - no-strict-aliasing is only supported with GCC
     DISPATCH-621 - Add missing string.h include for Solaris compiler
     DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler 
error to avoid undefined symbol on Solaris
     DISPATCH-623 - Unreachable code (qd_field_iterator_free after a 
return statement) detected on Solaris
     DISPATCH-624 - Add Atomic operations support on Solaris
     DISPATCH-626 - Add hints for getaddrinfo on Solaris
     DISPATCH-628 - [PATCH] Multiple connections per autoLink and 
linkRoute overwrites connection handle
     DISPATCH-631 - Tests should be made conditional to skip tests for 
SASL features that are not available
     DISPATCH-633 - Creating connectors and addresses returns success 
codes of two different types.
     DISPATCH-634 - Dynamic Targets are unsupported
     DISPATCH-635 - The Ubuntu CI tests that involve two routers are failing
     DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is 
required; however, cmake complains with 0.14
     DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated 
fail when cyrus-sasl-plain is not installed
     DISPATCH-640 - containerId field conflics with the connector name
     DISPATCH-642 - Fix recognition of Artemis broker on topology page
     DISPATCH-643 - Duplicate log messages show up on normal AMQP close
     DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a 
pipe issue in Daemon mode
     DISPATCH-646 - Link route tests which test the drain feature fail 
intermittently
     DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch 
master
     DISPATCH-727 - qdmanage identity reporting and lookup are broken
     DISPATCH-728 - crash on shutdown with connector
     DISPATCH-729 - password-file option doesn't work correctly
     DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
     DISPATCH-732 - CONN_MGR log module is used in connection_manager.c 
but is missing from log schema
     DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails 
intermittently

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Posted by Ganesh Murthy <gm...@redhat.com>.
----- Original Message -----
> From: "Ted Ross" <tr...@redhat.com>
> To: users@qpid.apache.org
> Sent: Tuesday, April 4, 2017 1:15:48 PM
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> 
> Just for the record...  I'm waiting for the Adel/Ganesh issues to shake
> out before cutting an RC2 and starting a vote.
The test failure issues reported by Adel on RHEL 6.4 have been fixed on master branch. I am looking into the Solaris failures but that should not stop us from doing an RC2 after we address the licensing issues that Robbie pointed out.

Thanks.
> 
> -Ted
> 
> On 04/04/2017 12:55 PM, Adel Boutros wrote:
> > Hello Ganesh,
> >
> >
> > I have applied your patch and it works as expected.
> >
> >
> > Regarding Solaris, do you need extra information for analyzing?
> >
> >
> > Regards,
> >
> > Adel
> >
> > ________________________________
> > From: Ganesh Murthy <gm...@redhat.com>
> > Sent: Tuesday, April 4, 2017 1:48:07 PM
> > To: users@qpid.apache.org
> > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >
> > Hi Adel,
> >     I sent out an email to you before I saw our own Travis build indicated
> >     that it failed the same tests that you were seeing. I apologize. This
> >     pull request - https://github.com/apache/qpid-dispatch/pull/158/files
> >     - should work for you on RHEL 6.4. This PR passes on Travis as well as
> >     seen here -
> >
> > https://travis-ci.org/apache/qpid-dispatch/builds/218223226
> >
> > Thanks.
> >
> > ----- Original Message -----
> >> From: "Adel Boutros" <Ad...@live.com>
> >> To: users@qpid.apache.org
> >> Sent: Monday, April 3, 2017 12:57:37 PM
> >> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >>
> >> Hello Ganesh,
> >>
> >>
> >> Your pull request fixed one of the 3 failing tests
> >> (system_tests_protocol_family). The others still have the same errors:
> >>
> >>     12 - router_policy_test (Failed)
> >>     18 - system_tests_policy (Failed)
> >>
> >>
> >> Regards,
> >>
> >> Adel
> >>
> >> ________________________________
> >> From: Ganesh Murthy <gm...@redhat.com>
> >> Sent: Monday, April 3, 2017 6:02:31 PM
> >> To: users@qpid.apache.org
> >> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >>
> >> Hi Adel,
> >>     I believe this pull request -
> >>     https://github.com/apache/qpid-dispatch/pull/157 - must fix the test
> >>     failures you are seeing on RHEL 6.4. Can you please try applying it?
> >>
> >> As for the Solaris test failures, there seem to be a whole bunch of them.
> >> I
> >> have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738
> >>
> >> I am not sure we can get to them before the 0.8.0 release.
> >>
> >> Thanks.
> >>
> >> ----- Original Message -----
> >>> From: "Adel Boutros" <Ad...@live.com>
> >>> To: users@qpid.apache.org
> >>> Sent: Friday, March 31, 2017 3:55:32 AM
> >>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >>>
> >>>
> >>>
> >>> Hello Ganesh,
> >>>
> >>>
> >>>
> >>>
> >>> Please find attached the 3 build logs of the dispatch router 0.8.0 on
> >>> Linux
> >>> (Red Hat 6.4), Solaris x86 and Solaris Sparc.
> >>>
> >>> Please note we are using Proton 0.16.0 with only C++ bindings activated.
> >>>
> >>>
> >>>
> >>>
> >>> PS: The good news is the code compiles on all 3 OSes but it's the tests
> >>> which
> >>> are failing. We consider this as a big step forward compared to the
> >>> previous
> >>> versions where the code didn't even compile on Solaris.
> >>>
> >>>
> >>>
> >>>
> >>> Regards,
> >>>
> >>> Adel
> >>>
> >>> From: Ganesh Murthy <gm...@redhat.com>
> >>> Sent: Thursday, March 30, 2017 3:10:00 PM
> >>> To: users@qpid.apache.org
> >>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >>>
> >>>
> >>> ----- Original Message -----
> >>>> From: "Adel Boutros" <Ad...@live.com>
> >>>> To: users@qpid.apache.org
> >>>> Sent: Thursday, March 30, 2017 9:04:01 AM
> >>>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >>>>
> >>>> I rechecked quickly and I have different behaviors on different OSes.
> >>>>
> >>>>
> >>>> * Linux :
> >>>>
> >>> Can you please let us know what Linux flavor you are using so we can try
> >>> locally?
> >>>> router_policy_test and system_tests_protocol_family failing as stated
> >>>> previously
> >>>>
> >>> Please also send the complete output of the failing tests.
> >>>>
> >>>> *Solaris:
> >>>>
> >>>> Only router_policy_test is failing.
> >>>>
> >>>> For system_tests_protocol_family, I have the message "Skipping
> >>>> test..IPV6
> >>>> not
> >>>> enabled"
> >>>>
> >>>>
> >>>> We have some other test failures on Solaris and Linux but we will need
> >>>> to
> >>>> debug them and we won't have time at the moment for them. I can send you
> >>>> a
> >>>> report with the failures if you wish.
> >>>>
> >>> This is the commit that fixed DISPATCH-216 on master -
> >>> https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036
> >>> I verified that the above commit is present in the Qpid Dispatch Router
> >>> 0.8.0
> >>> Release Candidate 1 qpid-dispatch-0.8.0.tar.gz
> >>>>
> >>>> Regards,
> >>>>
> >>>> Adel
> >>>>
> >>>> ________________________________
> >>>> From: Ted Ross <tr...@redhat.com>
> >>>> Sent: Thursday, March 30, 2017 2:48:10 PM
> >>>> To: users@qpid.apache.org
> >>>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >>>>
> >>>> Adel,
> >>>>
> >>>> The commits associated with that Jira and PR #140 are included in this
> >>>> release candidate. We'll need to investigate whether it regressed again
> >>>> or if the commit didn't fix the problem.
> >>>>
> >>>> -Ted
> >>>>
> >>>> On 03/30/2017 11:30 AM, Adel Boutros wrote:
> >>>>> Hello Ted,
> >>>>>
> >>>>>
> >>>>> I thought the 0.8.0 release included the fixes to ignore IPv6 tests but
> >>>>> it
> >>>>> doens't seem to be the case. Ganesh was working on fixing those.
> >>>>>
> >>>>> Do you confirm they are not included?
> >>>>> (
> >>>>> http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571
> >>>>> )
> >>>>>
> >>>>>
> >>>>> I launched the CI on the release candidate and got the same IPv6
> >>>>> failures
> >>>>> as before
> >>>>>
> >>>>>
> >>>>> The following tests FAILED with ipv6 errors:
> >>>>> 12 - router_policy_test (Failed)
> >>>>> 19 - system_tests_protocol_family (Failed)
> >>>>>
> >>>>>
> >>>>>
> >>>>> 12: Test command: /python278/bin/python
> >>>>> "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m"
> >>>>> "unittest"
> >>>>> "-v" "router_policy_test"
> >>>>> 12: Test timeout computed to be: 1500
> >>>>> 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\'
> >>>>> is
> >>>>> invalid: Policy vhost \'photoserver\' user group \'superuser\' option
> >>>>> \'remoteHosts\' connectionOption \'::1\' failed to translate:
> >>>>> \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct:
> >>>>> \\\'::1\\\' did not resolve to one of the supported address
> >>>>> family"\\\'\'\'.'
> >>>>>
> >>>>>
> >>>>> 19: error: [Errno 97] Address family not supported by protocol
> >>>>>
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>> Adel
> >>>>>
> >>>>> ________________________________
> >>>>> From: Ted Ross <tr...@redhat.com>
> >>>>> Sent: Wednesday, March 29, 2017 1:32:42 PM
> >>>>> To: users@qpid.apache.org
> >>>>> Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >>>>>
> >>>>> The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> >>>>> evaluation.
> >>>>>
> >>>>> Build Artifacts:
> >>>>>
> >>>>> https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
> >>>>>
> >>>>> New Features:
> >>>>>
> >>>>> DISPATCH-103 - Websocket Listeners
> >>>>> DISPATCH-195 - Add support for transactional messages in the Router
> >>>>> DISPATCH-441 - Support password environment variable in qdrouter
> >>>>> config
> >>>>> DISPATCH-467 - Terminus renaming for autoLinks
> >>>>> DISPATCH-529 - Address annotation for Multi-Tenancy
> >>>>> DISPATCH-726 - Connection Property for Failover Servers
> >>>>>
> >>>>> Improvements:
> >>>>>
> >>>>> DISPATCH-113 - expose NodeTracker::last_topology_change in management
> >>>>> DISPATCH-542 - Popup text for clients should indicate if the client
> >>>>> is a sender or receiver
> >>>>> DISPATCH-543 - Initial load of topology page fetches too much
> >>>>> information
> >>>>> DISPATCH-544 - Add ability to hide the info panel on the left of
> >>>>> the topology page
> >>>>> DISPATCH-552 - Allow only one tree node to be expanded if there is
> >>>>> a large number of routers
> >>>>> DISPATCH-553 - Add statistic counter to the "log" entity to count
> >>>>> log events per severity
> >>>>> DISPATCH-559 - qdstat - Request only the columns that will be used
> >>>>> in the display
> >>>>> DISPATCH-561 - Create python program that returns fake management data
> >>>>> DISPATCH-568 - Iterator module cleanup
> >>>>> DISPATCH-570 - Add some counts to qdstat -g
> >>>>> DISPATCH-572 - Adding log info with proton transport id and related
> >>>>> remote IP/port
> >>>>> DISPATCH-576 - Use new log entity statistic counter in console
> >>>>> DISPATCH-578 - Dispatch trace logging forces all proton tracing on
> >>>>> DISPATCH-579 - Expose software version via management
> >>>>> DISPATCH-592 - Attempt to auto-login to the host:port that served
> >>>>> the web page
> >>>>> DISPATCH-597 - Log enhancements
> >>>>> DISPATCH-600 - Support secure websockets
> >>>>> DISPATCH-602 - Add a favicon to the stand-alone router site
> >>>>> DISPATCH-606 - Default session window is too small, causing
> >>>>> performance bottlenecks
> >>>>> DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> >>>>> systems
> >>>>> DISPATCH-629 - Add a protocol-version to the inter-router protocol
> >>>>> to enable backward compatibility
> >>>>> DISPATCH-641 - Make containerId attribute work with clients
> >>>>>
> >>>>> Bugs Fixed:
> >>>>>
> >>>>> DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
> >>>>> DISPATCH-216 - system_tests_protocol_family fails on systems with
> >>>>> no IPv6
> >>>>> DISPATCH-296 - segfault on router startup
> >>>>> DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
> >>>>> DISPATCH-314 - If a router has a normal listener, show it in a
> >>>>> different color on the topology page
> >>>>> DISPATCH-324 - Improve initial layout of topology node
> >>>>> DISPATCH-344 - memory growth after repeated calls from qdstat -m
> >>>>> DISPATCH-352 - Crash with empty configuration file
> >>>>> DISPATCH-355 - query fails with what seems to be the error of a
> >>>>> previous command
> >>>>> DISPATCH-357 - Address field is empty for link routed links in the
> >>>>> qdstat "links" output
> >>>>> DISPATCH-433 - Navigating to console from bookmark displays empty
> >>>>> page with just toolbars
> >>>>> DISPATCH-451 - [AMQP] Hard coded session capacity should be
> >>>>> configurable
> >>>>> DISPATCH-503 - [display_name] successful test runs have non-ascii
> >>>>> characters in router log
> >>>>> DISPATCH-504 - [display_name] successful test runs have invalid
> >>>>> message errors in router log
> >>>>> DISPATCH-506 - Detach with no "error" sent by router on client TCP
> >>>>> connection dropped
> >>>>> DISPATCH-516 - Core dump when displayname IO adapter receives
> >>>>> message with no reply-to
> >>>>> DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> >>>>> 0.7.0
> >>>>> DISPATCH-527 - The $displayname address is currently available. It
> >>>>> should not be available to external users
> >>>>> DISPATCH-530 - Cannot connect using Firefox 48+
> >>>>> DISPATCH-534 - Node selection and location is lost when the
> >>>>> topology changes
> >>>>> DISPATCH-536 - Circular buffer overflow errors occur when there are
> >>>>> a large number of routers
> >>>>> DISPATCH-538 - Highlighted path between routers sometimes doesn't
> >>>>> unhighlight
> >>>>> DISPATCH-540 - Clients with both in and out links are rendered in
> >>>>> yellow
> >>>>> DISPATCH-541 - Highlighted path between routers contains black arrows
> >>>>> DISPATCH-546 - Crosssection popup position is incorrect
> >>>>> DISPATCH-547 - Stand-alone version can't download generated config
> >>>>> file for new nodes
> >>>>> DISPATCH-554 - Topology nodes and links are too far apart when
> >>>>> there are a large number of routers
> >>>>> DISPATCH-556 - qdstat fails at high scale
> >>>>> DISPATCH-557 - High connection rates cause problems in the Python
> >>>>> management agent
> >>>>> DISPATCH-560 - [console] Only use the color red to indicate a
> >>>>> failure/issue.
> >>>>> DISPATCH-563 - Topology graph flashes and redraws a few seconds
> >>>>> after it is 1st drawn
> >>>>> DISPATCH-564 - Error when switching routers on Entities page
> >>>>> DISPATCH-565 - Error fetching log on Entities page
> >>>>> DISPATCH-566 - Message annotations are not propagated to brokers on
> >>>>> a linkRoute
> >>>>> DISPATCH-567 - Slight but persistent memory leak when running java
> >>>>> messenger producer and consumer
> >>>>> DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> >>>>> enum values.
> >>>>> DISPATCH-573 - Memory leaks on shutdown
> >>>>> DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
> >>>>> DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
> >>>>> DISPATCH-581 - detach with closed=false propagated as closed=true
> >>>>> on link route
> >>>>> DISPATCH-582 - Memory Leak with reactor client
> >>>>> DISPATCH-583 - Random segmentation fault
> >>>>> DISPATCH-585 - Firefox dropdown and buttons on list page have
> >>>>> incorrect padding
> >>>>> DISPATCH-586 - Dispatch crash on running c sender and receiver
> >>>>> DISPATCH-587 - Provide feedback when loading log entries
> >>>>> DISPATCH-588 - Schema is not loaded if auto-login is enabled
> >>>>> DISPATCH-589 - Missing links on topology page
> >>>>> DISPATCH-594 - Log file over-written every time the router is
> >>>>> restarted
> >>>>> DISPATCH-595 - dispositions propagated after link detach on link route
> >>>>> DISPATCH-596 - error is lost from rejected state in relayed
> >>>>> disposition
> >>>>> DISPATCH-598 - Router crash when calling sender and session close
> >>>>> methods in onLinkFLow()
> >>>>> DISPATCH-599 - Link routing : messages is not transferred if sender
> >>>>> detach link immediately
> >>>>> DISPATCH-601 - Valgrind errors in dispatch tests
> >>>>> DISPATCH-603 - address resource leak
> >>>>> DISPATCH-604 - Management - Link connection-id does not match
> >>>>> identities of connections
> >>>>> DISPATCH-605 - Memory Leak with multple sender/receivers in one
> >>>>> session
> >>>>> DISPATCH-607 - Handle empty response from GET-MGMT-NODES
> >>>>> DISPATCH-608 - Links not cleaned up when a close is sent without
> >>>>> being preceeded by a detach and end
> >>>>> DISPATCH-609 - Name attribute is duplicated in QUERY response
> >>>>> DISPATCH-610 - crash in qdr_link_cleanup_CT
> >>>>> DISPATCH-611 - Router core dump with old config file
> >>>>> DISPATCH-612 - Add support for GCC equivalent compiler options
> >>>>> DISPATCH-613 - Remove semi-colon not needed after function definition
> >>>>> DISPATCH-614 - strerror_r on Solaris does not return char*
> >>>>> DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
> >>>>> DISPATCH-616 - Arithmetic operations not allowed on void * pointer
> >>>>> DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> >>>>> _POSIX_HOST_NAME_MAX is defined instead
> >>>>> DISPATCH-618 - Revert eventfd on Solaris
> >>>>> DISPATCH-619 - Use memalign instead of posix_memalign which is not
> >>>>> defined on Solaris
> >>>>> DISPATCH-620 - no-strict-aliasing is only supported with GCC
> >>>>> DISPATCH-621 - Add missing string.h include for Solaris compiler
> >>>>> DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> >>>>> error to avoid undefined symbol on Solaris
> >>>>> DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> >>>>> return statement) detected on Solaris
> >>>>> DISPATCH-624 - Add Atomic operations support on Solaris
> >>>>> DISPATCH-626 - Add hints for getaddrinfo on Solaris
> >>>>> DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> >>>>> linkRoute overwrites connection handle
> >>>>> DISPATCH-631 - Tests should be made conditional to skip tests for
> >>>>> SASL features that are not available
> >>>>> DISPATCH-633 - Creating connectors and addresses returns success
> >>>>> codes of two different types.
> >>>>> DISPATCH-634 - Dynamic Targets are unsupported
> >>>>> DISPATCH-635 - The Ubuntu CI tests that involve two routers are
> >>>>> failing
> >>>>> DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> >>>>> required; however, cmake complains with 0.14
> >>>>> DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> >>>>> fail when cyrus-sasl-plain is not installed
> >>>>> DISPATCH-640 - containerId field conflics with the connector name
> >>>>> DISPATCH-642 - Fix recognition of Artemis broker on topology page
> >>>>> DISPATCH-643 - Duplicate log messages show up on normal AMQP close
> >>>>> DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> >>>>> pipe issue in Daemon mode
> >>>>> DISPATCH-646 - Link route tests which test the drain feature fail
> >>>>> intermittently
> >>>>> DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> >>>>> master
> >>>>> DISPATCH-727 - qdmanage identity reporting and lookup are broken
> >>>>> DISPATCH-728 - crash on shutdown with connector
> >>>>> DISPATCH-729 - password-file option doesn't work correctly
> >>>>> DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
> >>>>> DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> >>>>> but is missing from log schema
> >>>>> DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> >>>>> intermittently
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> 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
> >>
> >> ---------------------------------------------------------------------
> >> 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
> >
> >
> 
> --
> Ted Ross
> Senior Principal Software Engineer
> Red Hat
> 314 Littleton Road
> Westford, MA 01886
> tross@redhat.com     T: +1-978-392-3950     M: +1-978-399-4122
> 
> ---------------------------------------------------------------------
> 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.8.0 Release Candidate 1

Posted by Ted Ross <tr...@redhat.com>.
Just for the record...  I'm waiting for the Adel/Ganesh issues to shake 
out before cutting an RC2 and starting a vote.

-Ted

On 04/04/2017 12:55 PM, Adel Boutros wrote:
> Hello Ganesh,
>
>
> I have applied your patch and it works as expected.
>
>
> Regarding Solaris, do you need extra information for analyzing?
>
>
> Regards,
>
> Adel
>
> ________________________________
> From: Ganesh Murthy <gm...@redhat.com>
> Sent: Tuesday, April 4, 2017 1:48:07 PM
> To: users@qpid.apache.org
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
> Hi Adel,
>     I sent out an email to you before I saw our own Travis build indicated that it failed the same tests that you were seeing. I apologize. This pull request - https://github.com/apache/qpid-dispatch/pull/158/files - should work for you on RHEL 6.4. This PR passes on Travis as well as seen here -
>
> https://travis-ci.org/apache/qpid-dispatch/builds/218223226
>
> Thanks.
>
> ----- Original Message -----
>> From: "Adel Boutros" <Ad...@live.com>
>> To: users@qpid.apache.org
>> Sent: Monday, April 3, 2017 12:57:37 PM
>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>>
>> Hello Ganesh,
>>
>>
>> Your pull request fixed one of the 3 failing tests
>> (system_tests_protocol_family). The others still have the same errors:
>>
>>     12 - router_policy_test (Failed)
>>     18 - system_tests_policy (Failed)
>>
>>
>> Regards,
>>
>> Adel
>>
>> ________________________________
>> From: Ganesh Murthy <gm...@redhat.com>
>> Sent: Monday, April 3, 2017 6:02:31 PM
>> To: users@qpid.apache.org
>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>>
>> Hi Adel,
>>     I believe this pull request -
>>     https://github.com/apache/qpid-dispatch/pull/157 - must fix the test
>>     failures you are seeing on RHEL 6.4. Can you please try applying it?
>>
>> As for the Solaris test failures, there seem to be a whole bunch of them. I
>> have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738
>>
>> I am not sure we can get to them before the 0.8.0 release.
>>
>> Thanks.
>>
>> ----- Original Message -----
>>> From: "Adel Boutros" <Ad...@live.com>
>>> To: users@qpid.apache.org
>>> Sent: Friday, March 31, 2017 3:55:32 AM
>>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>>>
>>>
>>>
>>> Hello Ganesh,
>>>
>>>
>>>
>>>
>>> Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux
>>> (Red Hat 6.4), Solaris x86 and Solaris Sparc.
>>>
>>> Please note we are using Proton 0.16.0 with only C++ bindings activated.
>>>
>>>
>>>
>>>
>>> PS: The good news is the code compiles on all 3 OSes but it's the tests
>>> which
>>> are failing. We consider this as a big step forward compared to the
>>> previous
>>> versions where the code didn't even compile on Solaris.
>>>
>>>
>>>
>>>
>>> Regards,
>>>
>>> Adel
>>>
>>> From: Ganesh Murthy <gm...@redhat.com>
>>> Sent: Thursday, March 30, 2017 3:10:00 PM
>>> To: users@qpid.apache.org
>>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Adel Boutros" <Ad...@live.com>
>>>> To: users@qpid.apache.org
>>>> Sent: Thursday, March 30, 2017 9:04:01 AM
>>>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>>>>
>>>> I rechecked quickly and I have different behaviors on different OSes.
>>>>
>>>>
>>>> * Linux :
>>>>
>>> Can you please let us know what Linux flavor you are using so we can try
>>> locally?
>>>> router_policy_test and system_tests_protocol_family failing as stated
>>>> previously
>>>>
>>> Please also send the complete output of the failing tests.
>>>>
>>>> *Solaris:
>>>>
>>>> Only router_policy_test is failing.
>>>>
>>>> For system_tests_protocol_family, I have the message "Skipping test..IPV6
>>>> not
>>>> enabled"
>>>>
>>>>
>>>> We have some other test failures on Solaris and Linux but we will need to
>>>> debug them and we won't have time at the moment for them. I can send you
>>>> a
>>>> report with the failures if you wish.
>>>>
>>> This is the commit that fixed DISPATCH-216 on master -
>>> https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036
>>> I verified that the above commit is present in the Qpid Dispatch Router
>>> 0.8.0
>>> Release Candidate 1 qpid-dispatch-0.8.0.tar.gz
>>>>
>>>> Regards,
>>>>
>>>> Adel
>>>>
>>>> ________________________________
>>>> From: Ted Ross <tr...@redhat.com>
>>>> Sent: Thursday, March 30, 2017 2:48:10 PM
>>>> To: users@qpid.apache.org
>>>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>>>>
>>>> Adel,
>>>>
>>>> The commits associated with that Jira and PR #140 are included in this
>>>> release candidate. We'll need to investigate whether it regressed again
>>>> or if the commit didn't fix the problem.
>>>>
>>>> -Ted
>>>>
>>>> On 03/30/2017 11:30 AM, Adel Boutros wrote:
>>>>> Hello Ted,
>>>>>
>>>>>
>>>>> I thought the 0.8.0 release included the fixes to ignore IPv6 tests but
>>>>> it
>>>>> doens't seem to be the case. Ganesh was working on fixing those.
>>>>>
>>>>> Do you confirm they are not included?
>>>>> (
>>>>> http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571
>>>>> )
>>>>>
>>>>>
>>>>> I launched the CI on the release candidate and got the same IPv6
>>>>> failures
>>>>> as before
>>>>>
>>>>>
>>>>> The following tests FAILED with ipv6 errors:
>>>>> 12 - router_policy_test (Failed)
>>>>> 19 - system_tests_protocol_family (Failed)
>>>>>
>>>>>
>>>>>
>>>>> 12: Test command: /python278/bin/python
>>>>> "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m"
>>>>> "unittest"
>>>>> "-v" "router_policy_test"
>>>>> 12: Test timeout computed to be: 1500
>>>>> 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\'
>>>>> is
>>>>> invalid: Policy vhost \'photoserver\' user group \'superuser\' option
>>>>> \'remoteHosts\' connectionOption \'::1\' failed to translate:
>>>>> \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct:
>>>>> \\\'::1\\\' did not resolve to one of the supported address
>>>>> family"\\\'\'\'.'
>>>>>
>>>>>
>>>>> 19: error: [Errno 97] Address family not supported by protocol
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Adel
>>>>>
>>>>> ________________________________
>>>>> From: Ted Ross <tr...@redhat.com>
>>>>> Sent: Wednesday, March 29, 2017 1:32:42 PM
>>>>> To: users@qpid.apache.org
>>>>> Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
>>>>>
>>>>> The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
>>>>> evaluation.
>>>>>
>>>>> Build Artifacts:
>>>>>
>>>>> https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
>>>>>
>>>>> New Features:
>>>>>
>>>>> DISPATCH-103 - Websocket Listeners
>>>>> DISPATCH-195 - Add support for transactional messages in the Router
>>>>> DISPATCH-441 - Support password environment variable in qdrouter
>>>>> config
>>>>> DISPATCH-467 - Terminus renaming for autoLinks
>>>>> DISPATCH-529 - Address annotation for Multi-Tenancy
>>>>> DISPATCH-726 - Connection Property for Failover Servers
>>>>>
>>>>> Improvements:
>>>>>
>>>>> DISPATCH-113 - expose NodeTracker::last_topology_change in management
>>>>> DISPATCH-542 - Popup text for clients should indicate if the client
>>>>> is a sender or receiver
>>>>> DISPATCH-543 - Initial load of topology page fetches too much
>>>>> information
>>>>> DISPATCH-544 - Add ability to hide the info panel on the left of
>>>>> the topology page
>>>>> DISPATCH-552 - Allow only one tree node to be expanded if there is
>>>>> a large number of routers
>>>>> DISPATCH-553 - Add statistic counter to the "log" entity to count
>>>>> log events per severity
>>>>> DISPATCH-559 - qdstat - Request only the columns that will be used
>>>>> in the display
>>>>> DISPATCH-561 - Create python program that returns fake management data
>>>>> DISPATCH-568 - Iterator module cleanup
>>>>> DISPATCH-570 - Add some counts to qdstat -g
>>>>> DISPATCH-572 - Adding log info with proton transport id and related
>>>>> remote IP/port
>>>>> DISPATCH-576 - Use new log entity statistic counter in console
>>>>> DISPATCH-578 - Dispatch trace logging forces all proton tracing on
>>>>> DISPATCH-579 - Expose software version via management
>>>>> DISPATCH-592 - Attempt to auto-login to the host:port that served
>>>>> the web page
>>>>> DISPATCH-597 - Log enhancements
>>>>> DISPATCH-600 - Support secure websockets
>>>>> DISPATCH-602 - Add a favicon to the stand-alone router site
>>>>> DISPATCH-606 - Default session window is too small, causing
>>>>> performance bottlenecks
>>>>> DISPATCH-627 - BatchedSettlement test fails with timeout on slower
>>>>> systems
>>>>> DISPATCH-629 - Add a protocol-version to the inter-router protocol
>>>>> to enable backward compatibility
>>>>> DISPATCH-641 - Make containerId attribute work with clients
>>>>>
>>>>> Bugs Fixed:
>>>>>
>>>>> DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
>>>>> DISPATCH-216 - system_tests_protocol_family fails on systems with
>>>>> no IPv6
>>>>> DISPATCH-296 - segfault on router startup
>>>>> DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
>>>>> DISPATCH-314 - If a router has a normal listener, show it in a
>>>>> different color on the topology page
>>>>> DISPATCH-324 - Improve initial layout of topology node
>>>>> DISPATCH-344 - memory growth after repeated calls from qdstat -m
>>>>> DISPATCH-352 - Crash with empty configuration file
>>>>> DISPATCH-355 - query fails with what seems to be the error of a
>>>>> previous command
>>>>> DISPATCH-357 - Address field is empty for link routed links in the
>>>>> qdstat "links" output
>>>>> DISPATCH-433 - Navigating to console from bookmark displays empty
>>>>> page with just toolbars
>>>>> DISPATCH-451 - [AMQP] Hard coded session capacity should be
>>>>> configurable
>>>>> DISPATCH-503 - [display_name] successful test runs have non-ascii
>>>>> characters in router log
>>>>> DISPATCH-504 - [display_name] successful test runs have invalid
>>>>> message errors in router log
>>>>> DISPATCH-506 - Detach with no "error" sent by router on client TCP
>>>>> connection dropped
>>>>> DISPATCH-516 - Core dump when displayname IO adapter receives
>>>>> message with no reply-to
>>>>> DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
>>>>> 0.7.0
>>>>> DISPATCH-527 - The $displayname address is currently available. It
>>>>> should not be available to external users
>>>>> DISPATCH-530 - Cannot connect using Firefox 48+
>>>>> DISPATCH-534 - Node selection and location is lost when the
>>>>> topology changes
>>>>> DISPATCH-536 - Circular buffer overflow errors occur when there are
>>>>> a large number of routers
>>>>> DISPATCH-538 - Highlighted path between routers sometimes doesn't
>>>>> unhighlight
>>>>> DISPATCH-540 - Clients with both in and out links are rendered in
>>>>> yellow
>>>>> DISPATCH-541 - Highlighted path between routers contains black arrows
>>>>> DISPATCH-546 - Crosssection popup position is incorrect
>>>>> DISPATCH-547 - Stand-alone version can't download generated config
>>>>> file for new nodes
>>>>> DISPATCH-554 - Topology nodes and links are too far apart when
>>>>> there are a large number of routers
>>>>> DISPATCH-556 - qdstat fails at high scale
>>>>> DISPATCH-557 - High connection rates cause problems in the Python
>>>>> management agent
>>>>> DISPATCH-560 - [console] Only use the color red to indicate a
>>>>> failure/issue.
>>>>> DISPATCH-563 - Topology graph flashes and redraws a few seconds
>>>>> after it is 1st drawn
>>>>> DISPATCH-564 - Error when switching routers on Entities page
>>>>> DISPATCH-565 - Error fetching log on Entities page
>>>>> DISPATCH-566 - Message annotations are not propagated to brokers on
>>>>> a linkRoute
>>>>> DISPATCH-567 - Slight but persistent memory leak when running java
>>>>> messenger producer and consumer
>>>>> DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
>>>>> enum values.
>>>>> DISPATCH-573 - Memory leaks on shutdown
>>>>> DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
>>>>> DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
>>>>> DISPATCH-581 - detach with closed=false propagated as closed=true
>>>>> on link route
>>>>> DISPATCH-582 - Memory Leak with reactor client
>>>>> DISPATCH-583 - Random segmentation fault
>>>>> DISPATCH-585 - Firefox dropdown and buttons on list page have
>>>>> incorrect padding
>>>>> DISPATCH-586 - Dispatch crash on running c sender and receiver
>>>>> DISPATCH-587 - Provide feedback when loading log entries
>>>>> DISPATCH-588 - Schema is not loaded if auto-login is enabled
>>>>> DISPATCH-589 - Missing links on topology page
>>>>> DISPATCH-594 - Log file over-written every time the router is
>>>>> restarted
>>>>> DISPATCH-595 - dispositions propagated after link detach on link route
>>>>> DISPATCH-596 - error is lost from rejected state in relayed
>>>>> disposition
>>>>> DISPATCH-598 - Router crash when calling sender and session close
>>>>> methods in onLinkFLow()
>>>>> DISPATCH-599 - Link routing : messages is not transferred if sender
>>>>> detach link immediately
>>>>> DISPATCH-601 - Valgrind errors in dispatch tests
>>>>> DISPATCH-603 - address resource leak
>>>>> DISPATCH-604 - Management - Link connection-id does not match
>>>>> identities of connections
>>>>> DISPATCH-605 - Memory Leak with multple sender/receivers in one
>>>>> session
>>>>> DISPATCH-607 - Handle empty response from GET-MGMT-NODES
>>>>> DISPATCH-608 - Links not cleaned up when a close is sent without
>>>>> being preceeded by a detach and end
>>>>> DISPATCH-609 - Name attribute is duplicated in QUERY response
>>>>> DISPATCH-610 - crash in qdr_link_cleanup_CT
>>>>> DISPATCH-611 - Router core dump with old config file
>>>>> DISPATCH-612 - Add support for GCC equivalent compiler options
>>>>> DISPATCH-613 - Remove semi-colon not needed after function definition
>>>>> DISPATCH-614 - strerror_r on Solaris does not return char*
>>>>> DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
>>>>> DISPATCH-616 - Arithmetic operations not allowed on void * pointer
>>>>> DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
>>>>> _POSIX_HOST_NAME_MAX is defined instead
>>>>> DISPATCH-618 - Revert eventfd on Solaris
>>>>> DISPATCH-619 - Use memalign instead of posix_memalign which is not
>>>>> defined on Solaris
>>>>> DISPATCH-620 - no-strict-aliasing is only supported with GCC
>>>>> DISPATCH-621 - Add missing string.h include for Solaris compiler
>>>>> DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
>>>>> error to avoid undefined symbol on Solaris
>>>>> DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
>>>>> return statement) detected on Solaris
>>>>> DISPATCH-624 - Add Atomic operations support on Solaris
>>>>> DISPATCH-626 - Add hints for getaddrinfo on Solaris
>>>>> DISPATCH-628 - [PATCH] Multiple connections per autoLink and
>>>>> linkRoute overwrites connection handle
>>>>> DISPATCH-631 - Tests should be made conditional to skip tests for
>>>>> SASL features that are not available
>>>>> DISPATCH-633 - Creating connectors and addresses returns success
>>>>> codes of two different types.
>>>>> DISPATCH-634 - Dynamic Targets are unsupported
>>>>> DISPATCH-635 - The Ubuntu CI tests that involve two routers are
>>>>> failing
>>>>> DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
>>>>> required; however, cmake complains with 0.14
>>>>> DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
>>>>> fail when cyrus-sasl-plain is not installed
>>>>> DISPATCH-640 - containerId field conflics with the connector name
>>>>> DISPATCH-642 - Fix recognition of Artemis broker on topology page
>>>>> DISPATCH-643 - Duplicate log messages show up on normal AMQP close
>>>>> DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
>>>>> pipe issue in Daemon mode
>>>>> DISPATCH-646 - Link route tests which test the drain feature fail
>>>>> intermittently
>>>>> DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
>>>>> master
>>>>> DISPATCH-727 - qdmanage identity reporting and lookup are broken
>>>>> DISPATCH-728 - crash on shutdown with connector
>>>>> DISPATCH-729 - password-file option doesn't work correctly
>>>>> DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
>>>>> DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
>>>>> but is missing from log schema
>>>>> DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
>>>>> intermittently
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>
>> ---------------------------------------------------------------------
>> 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
>
>

-- 
Ted Ross
Senior Principal Software Engineer
Red Hat
314 Littleton Road
Westford, MA 01886
tross@redhat.com     T: +1-978-392-3950     M: +1-978-399-4122

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Posted by Adel Boutros <Ad...@live.com>.
Hello Ganesh,


I have applied your patch and it works as expected.


Regarding Solaris, do you need extra information for analyzing?


Regards,

Adel

________________________________
From: Ganesh Murthy <gm...@redhat.com>
Sent: Tuesday, April 4, 2017 1:48:07 PM
To: users@qpid.apache.org
Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Hi Adel,
    I sent out an email to you before I saw our own Travis build indicated that it failed the same tests that you were seeing. I apologize. This pull request - https://github.com/apache/qpid-dispatch/pull/158/files - should work for you on RHEL 6.4. This PR passes on Travis as well as seen here -

https://travis-ci.org/apache/qpid-dispatch/builds/218223226

Thanks.

----- Original Message -----
> From: "Adel Boutros" <Ad...@live.com>
> To: users@qpid.apache.org
> Sent: Monday, April 3, 2017 12:57:37 PM
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
> Hello Ganesh,
>
>
> Your pull request fixed one of the 3 failing tests
> (system_tests_protocol_family). The others still have the same errors:
>
>     12 - router_policy_test (Failed)
>     18 - system_tests_policy (Failed)
>
>
> Regards,
>
> Adel
>
> ________________________________
> From: Ganesh Murthy <gm...@redhat.com>
> Sent: Monday, April 3, 2017 6:02:31 PM
> To: users@qpid.apache.org
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
> Hi Adel,
>     I believe this pull request -
>     https://github.com/apache/qpid-dispatch/pull/157 - must fix the test
>     failures you are seeing on RHEL 6.4. Can you please try applying it?
>
> As for the Solaris test failures, there seem to be a whole bunch of them. I
> have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738
>
> I am not sure we can get to them before the 0.8.0 release.
>
> Thanks.
>
> ----- Original Message -----
> > From: "Adel Boutros" <Ad...@live.com>
> > To: users@qpid.apache.org
> > Sent: Friday, March 31, 2017 3:55:32 AM
> > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >
> >
> >
> > Hello Ganesh,
> >
> >
> >
> >
> > Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux
> > (Red Hat 6.4), Solaris x86 and Solaris Sparc.
> >
> > Please note we are using Proton 0.16.0 with only C++ bindings activated.
> >
> >
> >
> >
> > PS: The good news is the code compiles on all 3 OSes but it's the tests
> > which
> > are failing. We consider this as a big step forward compared to the
> > previous
> > versions where the code didn't even compile on Solaris.
> >
> >
> >
> >
> > Regards,
> >
> > Adel
> >
> > From: Ganesh Murthy <gm...@redhat.com>
> > Sent: Thursday, March 30, 2017 3:10:00 PM
> > To: users@qpid.apache.org
> > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >
> >
> > ----- Original Message -----
> > > From: "Adel Boutros" <Ad...@live.com>
> > > To: users@qpid.apache.org
> > > Sent: Thursday, March 30, 2017 9:04:01 AM
> > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> > >
> > > I rechecked quickly and I have different behaviors on different OSes.
> > >
> > >
> > > * Linux :
> > >
> > Can you please let us know what Linux flavor you are using so we can try
> > locally?
> > > router_policy_test and system_tests_protocol_family failing as stated
> > > previously
> > >
> > Please also send the complete output of the failing tests.
> > >
> > > *Solaris:
> > >
> > > Only router_policy_test is failing.
> > >
> > > For system_tests_protocol_family, I have the message "Skipping test..IPV6
> > > not
> > > enabled"
> > >
> > >
> > > We have some other test failures on Solaris and Linux but we will need to
> > > debug them and we won't have time at the moment for them. I can send you
> > > a
> > > report with the failures if you wish.
> > >
> > This is the commit that fixed DISPATCH-216 on master -
> > https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036
> > I verified that the above commit is present in the Qpid Dispatch Router
> > 0.8.0
> > Release Candidate 1 qpid-dispatch-0.8.0.tar.gz
> > >
> > > Regards,
> > >
> > > Adel
> > >
> > > ________________________________
> > > From: Ted Ross <tr...@redhat.com>
> > > Sent: Thursday, March 30, 2017 2:48:10 PM
> > > To: users@qpid.apache.org
> > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> > >
> > > Adel,
> > >
> > > The commits associated with that Jira and PR #140 are included in this
> > > release candidate. We'll need to investigate whether it regressed again
> > > or if the commit didn't fix the problem.
> > >
> > > -Ted
> > >
> > > On 03/30/2017 11:30 AM, Adel Boutros wrote:
> > > > Hello Ted,
> > > >
> > > >
> > > > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but
> > > > it
> > > > doens't seem to be the case. Ganesh was working on fixing those.
> > > >
> > > > Do you confirm they are not included?
> > > > (
> > > > http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571
> > > > )
> > > >
> > > >
> > > > I launched the CI on the release candidate and got the same IPv6
> > > > failures
> > > > as before
> > > >
> > > >
> > > > The following tests FAILED with ipv6 errors:
> > > > 12 - router_policy_test (Failed)
> > > > 19 - system_tests_protocol_family (Failed)
> > > >
> > > >
> > > >
> > > > 12: Test command: /python278/bin/python
> > > > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m"
> > > > "unittest"
> > > > "-v" "router_policy_test"
> > > > 12: Test timeout computed to be: 1500
> > > > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\'
> > > > is
> > > > invalid: Policy vhost \'photoserver\' user group \'superuser\' option
> > > > \'remoteHosts\' connectionOption \'::1\' failed to translate:
> > > > \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct:
> > > > \\\'::1\\\' did not resolve to one of the supported address
> > > > family"\\\'\'\'.'
> > > >
> > > >
> > > > 19: error: [Errno 97] Address family not supported by protocol
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Adel
> > > >
> > > > ________________________________
> > > > From: Ted Ross <tr...@redhat.com>
> > > > Sent: Wednesday, March 29, 2017 1:32:42 PM
> > > > To: users@qpid.apache.org
> > > > Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
> > > >
> > > > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> > > > evaluation.
> > > >
> > > > Build Artifacts:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
> > > >
> > > > New Features:
> > > >
> > > > DISPATCH-103 - Websocket Listeners
> > > > DISPATCH-195 - Add support for transactional messages in the Router
> > > > DISPATCH-441 - Support password environment variable in qdrouter
> > > > config
> > > > DISPATCH-467 - Terminus renaming for autoLinks
> > > > DISPATCH-529 - Address annotation for Multi-Tenancy
> > > > DISPATCH-726 - Connection Property for Failover Servers
> > > >
> > > > Improvements:
> > > >
> > > > DISPATCH-113 - expose NodeTracker::last_topology_change in management
> > > > DISPATCH-542 - Popup text for clients should indicate if the client
> > > > is a sender or receiver
> > > > DISPATCH-543 - Initial load of topology page fetches too much
> > > > information
> > > > DISPATCH-544 - Add ability to hide the info panel on the left of
> > > > the topology page
> > > > DISPATCH-552 - Allow only one tree node to be expanded if there is
> > > > a large number of routers
> > > > DISPATCH-553 - Add statistic counter to the "log" entity to count
> > > > log events per severity
> > > > DISPATCH-559 - qdstat - Request only the columns that will be used
> > > > in the display
> > > > DISPATCH-561 - Create python program that returns fake management data
> > > > DISPATCH-568 - Iterator module cleanup
> > > > DISPATCH-570 - Add some counts to qdstat -g
> > > > DISPATCH-572 - Adding log info with proton transport id and related
> > > > remote IP/port
> > > > DISPATCH-576 - Use new log entity statistic counter in console
> > > > DISPATCH-578 - Dispatch trace logging forces all proton tracing on
> > > > DISPATCH-579 - Expose software version via management
> > > > DISPATCH-592 - Attempt to auto-login to the host:port that served
> > > > the web page
> > > > DISPATCH-597 - Log enhancements
> > > > DISPATCH-600 - Support secure websockets
> > > > DISPATCH-602 - Add a favicon to the stand-alone router site
> > > > DISPATCH-606 - Default session window is too small, causing
> > > > performance bottlenecks
> > > > DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> > > > systems
> > > > DISPATCH-629 - Add a protocol-version to the inter-router protocol
> > > > to enable backward compatibility
> > > > DISPATCH-641 - Make containerId attribute work with clients
> > > >
> > > > Bugs Fixed:
> > > >
> > > > DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
> > > > DISPATCH-216 - system_tests_protocol_family fails on systems with
> > > > no IPv6
> > > > DISPATCH-296 - segfault on router startup
> > > > DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
> > > > DISPATCH-314 - If a router has a normal listener, show it in a
> > > > different color on the topology page
> > > > DISPATCH-324 - Improve initial layout of topology node
> > > > DISPATCH-344 - memory growth after repeated calls from qdstat -m
> > > > DISPATCH-352 - Crash with empty configuration file
> > > > DISPATCH-355 - query fails with what seems to be the error of a
> > > > previous command
> > > > DISPATCH-357 - Address field is empty for link routed links in the
> > > > qdstat "links" output
> > > > DISPATCH-433 - Navigating to console from bookmark displays empty
> > > > page with just toolbars
> > > > DISPATCH-451 - [AMQP] Hard coded session capacity should be
> > > > configurable
> > > > DISPATCH-503 - [display_name] successful test runs have non-ascii
> > > > characters in router log
> > > > DISPATCH-504 - [display_name] successful test runs have invalid
> > > > message errors in router log
> > > > DISPATCH-506 - Detach with no "error" sent by router on client TCP
> > > > connection dropped
> > > > DISPATCH-516 - Core dump when displayname IO adapter receives
> > > > message with no reply-to
> > > > DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> > > > 0.7.0
> > > > DISPATCH-527 - The $displayname address is currently available. It
> > > > should not be available to external users
> > > > DISPATCH-530 - Cannot connect using Firefox 48+
> > > > DISPATCH-534 - Node selection and location is lost when the
> > > > topology changes
> > > > DISPATCH-536 - Circular buffer overflow errors occur when there are
> > > > a large number of routers
> > > > DISPATCH-538 - Highlighted path between routers sometimes doesn't
> > > > unhighlight
> > > > DISPATCH-540 - Clients with both in and out links are rendered in
> > > > yellow
> > > > DISPATCH-541 - Highlighted path between routers contains black arrows
> > > > DISPATCH-546 - Crosssection popup position is incorrect
> > > > DISPATCH-547 - Stand-alone version can't download generated config
> > > > file for new nodes
> > > > DISPATCH-554 - Topology nodes and links are too far apart when
> > > > there are a large number of routers
> > > > DISPATCH-556 - qdstat fails at high scale
> > > > DISPATCH-557 - High connection rates cause problems in the Python
> > > > management agent
> > > > DISPATCH-560 - [console] Only use the color red to indicate a
> > > > failure/issue.
> > > > DISPATCH-563 - Topology graph flashes and redraws a few seconds
> > > > after it is 1st drawn
> > > > DISPATCH-564 - Error when switching routers on Entities page
> > > > DISPATCH-565 - Error fetching log on Entities page
> > > > DISPATCH-566 - Message annotations are not propagated to brokers on
> > > > a linkRoute
> > > > DISPATCH-567 - Slight but persistent memory leak when running java
> > > > messenger producer and consumer
> > > > DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> > > > enum values.
> > > > DISPATCH-573 - Memory leaks on shutdown
> > > > DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
> > > > DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
> > > > DISPATCH-581 - detach with closed=false propagated as closed=true
> > > > on link route
> > > > DISPATCH-582 - Memory Leak with reactor client
> > > > DISPATCH-583 - Random segmentation fault
> > > > DISPATCH-585 - Firefox dropdown and buttons on list page have
> > > > incorrect padding
> > > > DISPATCH-586 - Dispatch crash on running c sender and receiver
> > > > DISPATCH-587 - Provide feedback when loading log entries
> > > > DISPATCH-588 - Schema is not loaded if auto-login is enabled
> > > > DISPATCH-589 - Missing links on topology page
> > > > DISPATCH-594 - Log file over-written every time the router is
> > > > restarted
> > > > DISPATCH-595 - dispositions propagated after link detach on link route
> > > > DISPATCH-596 - error is lost from rejected state in relayed
> > > > disposition
> > > > DISPATCH-598 - Router crash when calling sender and session close
> > > > methods in onLinkFLow()
> > > > DISPATCH-599 - Link routing : messages is not transferred if sender
> > > > detach link immediately
> > > > DISPATCH-601 - Valgrind errors in dispatch tests
> > > > DISPATCH-603 - address resource leak
> > > > DISPATCH-604 - Management - Link connection-id does not match
> > > > identities of connections
> > > > DISPATCH-605 - Memory Leak with multple sender/receivers in one
> > > > session
> > > > DISPATCH-607 - Handle empty response from GET-MGMT-NODES
> > > > DISPATCH-608 - Links not cleaned up when a close is sent without
> > > > being preceeded by a detach and end
> > > > DISPATCH-609 - Name attribute is duplicated in QUERY response
> > > > DISPATCH-610 - crash in qdr_link_cleanup_CT
> > > > DISPATCH-611 - Router core dump with old config file
> > > > DISPATCH-612 - Add support for GCC equivalent compiler options
> > > > DISPATCH-613 - Remove semi-colon not needed after function definition
> > > > DISPATCH-614 - strerror_r on Solaris does not return char*
> > > > DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
> > > > DISPATCH-616 - Arithmetic operations not allowed on void * pointer
> > > > DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> > > > _POSIX_HOST_NAME_MAX is defined instead
> > > > DISPATCH-618 - Revert eventfd on Solaris
> > > > DISPATCH-619 - Use memalign instead of posix_memalign which is not
> > > > defined on Solaris
> > > > DISPATCH-620 - no-strict-aliasing is only supported with GCC
> > > > DISPATCH-621 - Add missing string.h include for Solaris compiler
> > > > DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> > > > error to avoid undefined symbol on Solaris
> > > > DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> > > > return statement) detected on Solaris
> > > > DISPATCH-624 - Add Atomic operations support on Solaris
> > > > DISPATCH-626 - Add hints for getaddrinfo on Solaris
> > > > DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> > > > linkRoute overwrites connection handle
> > > > DISPATCH-631 - Tests should be made conditional to skip tests for
> > > > SASL features that are not available
> > > > DISPATCH-633 - Creating connectors and addresses returns success
> > > > codes of two different types.
> > > > DISPATCH-634 - Dynamic Targets are unsupported
> > > > DISPATCH-635 - The Ubuntu CI tests that involve two routers are
> > > > failing
> > > > DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> > > > required; however, cmake complains with 0.14
> > > > DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> > > > fail when cyrus-sasl-plain is not installed
> > > > DISPATCH-640 - containerId field conflics with the connector name
> > > > DISPATCH-642 - Fix recognition of Artemis broker on topology page
> > > > DISPATCH-643 - Duplicate log messages show up on normal AMQP close
> > > > DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> > > > pipe issue in Daemon mode
> > > > DISPATCH-646 - Link route tests which test the drain feature fail
> > > > intermittently
> > > > DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> > > > master
> > > > DISPATCH-727 - qdmanage identity reporting and lookup are broken
> > > > DISPATCH-728 - crash on shutdown with connector
> > > > DISPATCH-729 - password-file option doesn't work correctly
> > > > DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
> > > > DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> > > > but is missing from log schema
> > > > DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> > > > intermittently
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
>
> ---------------------------------------------------------------------
> 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.8.0 Release Candidate 1

Posted by Ganesh Murthy <gm...@redhat.com>.
Hi Adel,
    I sent out an email to you before I saw our own Travis build indicated that it failed the same tests that you were seeing. I apologize. This pull request - https://github.com/apache/qpid-dispatch/pull/158/files - should work for you on RHEL 6.4. This PR passes on Travis as well as seen here - 

https://travis-ci.org/apache/qpid-dispatch/builds/218223226

Thanks.

----- Original Message -----
> From: "Adel Boutros" <Ad...@live.com>
> To: users@qpid.apache.org
> Sent: Monday, April 3, 2017 12:57:37 PM
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> 
> Hello Ganesh,
> 
> 
> Your pull request fixed one of the 3 failing tests
> (system_tests_protocol_family). The others still have the same errors:
> 
>     12 - router_policy_test (Failed)
>     18 - system_tests_policy (Failed)
> 
> 
> Regards,
> 
> Adel
> 
> ________________________________
> From: Ganesh Murthy <gm...@redhat.com>
> Sent: Monday, April 3, 2017 6:02:31 PM
> To: users@qpid.apache.org
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> 
> Hi Adel,
>     I believe this pull request -
>     https://github.com/apache/qpid-dispatch/pull/157 - must fix the test
>     failures you are seeing on RHEL 6.4. Can you please try applying it?
> 
> As for the Solaris test failures, there seem to be a whole bunch of them. I
> have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738
> 
> I am not sure we can get to them before the 0.8.0 release.
> 
> Thanks.
> 
> ----- Original Message -----
> > From: "Adel Boutros" <Ad...@live.com>
> > To: users@qpid.apache.org
> > Sent: Friday, March 31, 2017 3:55:32 AM
> > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >
> >
> >
> > Hello Ganesh,
> >
> >
> >
> >
> > Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux
> > (Red Hat 6.4), Solaris x86 and Solaris Sparc.
> >
> > Please note we are using Proton 0.16.0 with only C++ bindings activated.
> >
> >
> >
> >
> > PS: The good news is the code compiles on all 3 OSes but it's the tests
> > which
> > are failing. We consider this as a big step forward compared to the
> > previous
> > versions where the code didn't even compile on Solaris.
> >
> >
> >
> >
> > Regards,
> >
> > Adel
> >
> > From: Ganesh Murthy <gm...@redhat.com>
> > Sent: Thursday, March 30, 2017 3:10:00 PM
> > To: users@qpid.apache.org
> > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >
> >
> > ----- Original Message -----
> > > From: "Adel Boutros" <Ad...@live.com>
> > > To: users@qpid.apache.org
> > > Sent: Thursday, March 30, 2017 9:04:01 AM
> > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> > >
> > > I rechecked quickly and I have different behaviors on different OSes.
> > >
> > >
> > > * Linux :
> > >
> > Can you please let us know what Linux flavor you are using so we can try
> > locally?
> > > router_policy_test and system_tests_protocol_family failing as stated
> > > previously
> > >
> > Please also send the complete output of the failing tests.
> > >
> > > *Solaris:
> > >
> > > Only router_policy_test is failing.
> > >
> > > For system_tests_protocol_family, I have the message "Skipping test..IPV6
> > > not
> > > enabled"
> > >
> > >
> > > We have some other test failures on Solaris and Linux but we will need to
> > > debug them and we won't have time at the moment for them. I can send you
> > > a
> > > report with the failures if you wish.
> > >
> > This is the commit that fixed DISPATCH-216 on master -
> > https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036
> > I verified that the above commit is present in the Qpid Dispatch Router
> > 0.8.0
> > Release Candidate 1 qpid-dispatch-0.8.0.tar.gz
> > >
> > > Regards,
> > >
> > > Adel
> > >
> > > ________________________________
> > > From: Ted Ross <tr...@redhat.com>
> > > Sent: Thursday, March 30, 2017 2:48:10 PM
> > > To: users@qpid.apache.org
> > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> > >
> > > Adel,
> > >
> > > The commits associated with that Jira and PR #140 are included in this
> > > release candidate. We'll need to investigate whether it regressed again
> > > or if the commit didn't fix the problem.
> > >
> > > -Ted
> > >
> > > On 03/30/2017 11:30 AM, Adel Boutros wrote:
> > > > Hello Ted,
> > > >
> > > >
> > > > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but
> > > > it
> > > > doens't seem to be the case. Ganesh was working on fixing those.
> > > >
> > > > Do you confirm they are not included?
> > > > (
> > > > http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571
> > > > )
> > > >
> > > >
> > > > I launched the CI on the release candidate and got the same IPv6
> > > > failures
> > > > as before
> > > >
> > > >
> > > > The following tests FAILED with ipv6 errors:
> > > > 12 - router_policy_test (Failed)
> > > > 19 - system_tests_protocol_family (Failed)
> > > >
> > > >
> > > >
> > > > 12: Test command: /python278/bin/python
> > > > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m"
> > > > "unittest"
> > > > "-v" "router_policy_test"
> > > > 12: Test timeout computed to be: 1500
> > > > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\'
> > > > is
> > > > invalid: Policy vhost \'photoserver\' user group \'superuser\' option
> > > > \'remoteHosts\' connectionOption \'::1\' failed to translate:
> > > > \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct:
> > > > \\\'::1\\\' did not resolve to one of the supported address
> > > > family"\\\'\'\'.'
> > > >
> > > >
> > > > 19: error: [Errno 97] Address family not supported by protocol
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Adel
> > > >
> > > > ________________________________
> > > > From: Ted Ross <tr...@redhat.com>
> > > > Sent: Wednesday, March 29, 2017 1:32:42 PM
> > > > To: users@qpid.apache.org
> > > > Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
> > > >
> > > > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> > > > evaluation.
> > > >
> > > > Build Artifacts:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
> > > >
> > > > New Features:
> > > >
> > > > DISPATCH-103 - Websocket Listeners
> > > > DISPATCH-195 - Add support for transactional messages in the Router
> > > > DISPATCH-441 - Support password environment variable in qdrouter
> > > > config
> > > > DISPATCH-467 - Terminus renaming for autoLinks
> > > > DISPATCH-529 - Address annotation for Multi-Tenancy
> > > > DISPATCH-726 - Connection Property for Failover Servers
> > > >
> > > > Improvements:
> > > >
> > > > DISPATCH-113 - expose NodeTracker::last_topology_change in management
> > > > DISPATCH-542 - Popup text for clients should indicate if the client
> > > > is a sender or receiver
> > > > DISPATCH-543 - Initial load of topology page fetches too much
> > > > information
> > > > DISPATCH-544 - Add ability to hide the info panel on the left of
> > > > the topology page
> > > > DISPATCH-552 - Allow only one tree node to be expanded if there is
> > > > a large number of routers
> > > > DISPATCH-553 - Add statistic counter to the "log" entity to count
> > > > log events per severity
> > > > DISPATCH-559 - qdstat - Request only the columns that will be used
> > > > in the display
> > > > DISPATCH-561 - Create python program that returns fake management data
> > > > DISPATCH-568 - Iterator module cleanup
> > > > DISPATCH-570 - Add some counts to qdstat -g
> > > > DISPATCH-572 - Adding log info with proton transport id and related
> > > > remote IP/port
> > > > DISPATCH-576 - Use new log entity statistic counter in console
> > > > DISPATCH-578 - Dispatch trace logging forces all proton tracing on
> > > > DISPATCH-579 - Expose software version via management
> > > > DISPATCH-592 - Attempt to auto-login to the host:port that served
> > > > the web page
> > > > DISPATCH-597 - Log enhancements
> > > > DISPATCH-600 - Support secure websockets
> > > > DISPATCH-602 - Add a favicon to the stand-alone router site
> > > > DISPATCH-606 - Default session window is too small, causing
> > > > performance bottlenecks
> > > > DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> > > > systems
> > > > DISPATCH-629 - Add a protocol-version to the inter-router protocol
> > > > to enable backward compatibility
> > > > DISPATCH-641 - Make containerId attribute work with clients
> > > >
> > > > Bugs Fixed:
> > > >
> > > > DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
> > > > DISPATCH-216 - system_tests_protocol_family fails on systems with
> > > > no IPv6
> > > > DISPATCH-296 - segfault on router startup
> > > > DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
> > > > DISPATCH-314 - If a router has a normal listener, show it in a
> > > > different color on the topology page
> > > > DISPATCH-324 - Improve initial layout of topology node
> > > > DISPATCH-344 - memory growth after repeated calls from qdstat -m
> > > > DISPATCH-352 - Crash with empty configuration file
> > > > DISPATCH-355 - query fails with what seems to be the error of a
> > > > previous command
> > > > DISPATCH-357 - Address field is empty for link routed links in the
> > > > qdstat "links" output
> > > > DISPATCH-433 - Navigating to console from bookmark displays empty
> > > > page with just toolbars
> > > > DISPATCH-451 - [AMQP] Hard coded session capacity should be
> > > > configurable
> > > > DISPATCH-503 - [display_name] successful test runs have non-ascii
> > > > characters in router log
> > > > DISPATCH-504 - [display_name] successful test runs have invalid
> > > > message errors in router log
> > > > DISPATCH-506 - Detach with no "error" sent by router on client TCP
> > > > connection dropped
> > > > DISPATCH-516 - Core dump when displayname IO adapter receives
> > > > message with no reply-to
> > > > DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> > > > 0.7.0
> > > > DISPATCH-527 - The $displayname address is currently available. It
> > > > should not be available to external users
> > > > DISPATCH-530 - Cannot connect using Firefox 48+
> > > > DISPATCH-534 - Node selection and location is lost when the
> > > > topology changes
> > > > DISPATCH-536 - Circular buffer overflow errors occur when there are
> > > > a large number of routers
> > > > DISPATCH-538 - Highlighted path between routers sometimes doesn't
> > > > unhighlight
> > > > DISPATCH-540 - Clients with both in and out links are rendered in
> > > > yellow
> > > > DISPATCH-541 - Highlighted path between routers contains black arrows
> > > > DISPATCH-546 - Crosssection popup position is incorrect
> > > > DISPATCH-547 - Stand-alone version can't download generated config
> > > > file for new nodes
> > > > DISPATCH-554 - Topology nodes and links are too far apart when
> > > > there are a large number of routers
> > > > DISPATCH-556 - qdstat fails at high scale
> > > > DISPATCH-557 - High connection rates cause problems in the Python
> > > > management agent
> > > > DISPATCH-560 - [console] Only use the color red to indicate a
> > > > failure/issue.
> > > > DISPATCH-563 - Topology graph flashes and redraws a few seconds
> > > > after it is 1st drawn
> > > > DISPATCH-564 - Error when switching routers on Entities page
> > > > DISPATCH-565 - Error fetching log on Entities page
> > > > DISPATCH-566 - Message annotations are not propagated to brokers on
> > > > a linkRoute
> > > > DISPATCH-567 - Slight but persistent memory leak when running java
> > > > messenger producer and consumer
> > > > DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> > > > enum values.
> > > > DISPATCH-573 - Memory leaks on shutdown
> > > > DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
> > > > DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
> > > > DISPATCH-581 - detach with closed=false propagated as closed=true
> > > > on link route
> > > > DISPATCH-582 - Memory Leak with reactor client
> > > > DISPATCH-583 - Random segmentation fault
> > > > DISPATCH-585 - Firefox dropdown and buttons on list page have
> > > > incorrect padding
> > > > DISPATCH-586 - Dispatch crash on running c sender and receiver
> > > > DISPATCH-587 - Provide feedback when loading log entries
> > > > DISPATCH-588 - Schema is not loaded if auto-login is enabled
> > > > DISPATCH-589 - Missing links on topology page
> > > > DISPATCH-594 - Log file over-written every time the router is
> > > > restarted
> > > > DISPATCH-595 - dispositions propagated after link detach on link route
> > > > DISPATCH-596 - error is lost from rejected state in relayed
> > > > disposition
> > > > DISPATCH-598 - Router crash when calling sender and session close
> > > > methods in onLinkFLow()
> > > > DISPATCH-599 - Link routing : messages is not transferred if sender
> > > > detach link immediately
> > > > DISPATCH-601 - Valgrind errors in dispatch tests
> > > > DISPATCH-603 - address resource leak
> > > > DISPATCH-604 - Management - Link connection-id does not match
> > > > identities of connections
> > > > DISPATCH-605 - Memory Leak with multple sender/receivers in one
> > > > session
> > > > DISPATCH-607 - Handle empty response from GET-MGMT-NODES
> > > > DISPATCH-608 - Links not cleaned up when a close is sent without
> > > > being preceeded by a detach and end
> > > > DISPATCH-609 - Name attribute is duplicated in QUERY response
> > > > DISPATCH-610 - crash in qdr_link_cleanup_CT
> > > > DISPATCH-611 - Router core dump with old config file
> > > > DISPATCH-612 - Add support for GCC equivalent compiler options
> > > > DISPATCH-613 - Remove semi-colon not needed after function definition
> > > > DISPATCH-614 - strerror_r on Solaris does not return char*
> > > > DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
> > > > DISPATCH-616 - Arithmetic operations not allowed on void * pointer
> > > > DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> > > > _POSIX_HOST_NAME_MAX is defined instead
> > > > DISPATCH-618 - Revert eventfd on Solaris
> > > > DISPATCH-619 - Use memalign instead of posix_memalign which is not
> > > > defined on Solaris
> > > > DISPATCH-620 - no-strict-aliasing is only supported with GCC
> > > > DISPATCH-621 - Add missing string.h include for Solaris compiler
> > > > DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> > > > error to avoid undefined symbol on Solaris
> > > > DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> > > > return statement) detected on Solaris
> > > > DISPATCH-624 - Add Atomic operations support on Solaris
> > > > DISPATCH-626 - Add hints for getaddrinfo on Solaris
> > > > DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> > > > linkRoute overwrites connection handle
> > > > DISPATCH-631 - Tests should be made conditional to skip tests for
> > > > SASL features that are not available
> > > > DISPATCH-633 - Creating connectors and addresses returns success
> > > > codes of two different types.
> > > > DISPATCH-634 - Dynamic Targets are unsupported
> > > > DISPATCH-635 - The Ubuntu CI tests that involve two routers are
> > > > failing
> > > > DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> > > > required; however, cmake complains with 0.14
> > > > DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> > > > fail when cyrus-sasl-plain is not installed
> > > > DISPATCH-640 - containerId field conflics with the connector name
> > > > DISPATCH-642 - Fix recognition of Artemis broker on topology page
> > > > DISPATCH-643 - Duplicate log messages show up on normal AMQP close
> > > > DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> > > > pipe issue in Daemon mode
> > > > DISPATCH-646 - Link route tests which test the drain feature fail
> > > > intermittently
> > > > DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> > > > master
> > > > DISPATCH-727 - qdmanage identity reporting and lookup are broken
> > > > DISPATCH-728 - crash on shutdown with connector
> > > > DISPATCH-729 - password-file option doesn't work correctly
> > > > DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
> > > > DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> > > > but is missing from log schema
> > > > DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> > > > intermittently
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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
> 
> ---------------------------------------------------------------------
> 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.8.0 Release Candidate 1

Posted by Adel Boutros <Ad...@live.com>.
Hello Ganesh,


Your pull request fixed one of the 3 failing tests (system_tests_protocol_family). The others still have the same errors:

    12 - router_policy_test (Failed)
    18 - system_tests_policy (Failed)


Regards,

Adel

________________________________
From: Ganesh Murthy <gm...@redhat.com>
Sent: Monday, April 3, 2017 6:02:31 PM
To: users@qpid.apache.org
Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Hi Adel,
    I believe this pull request - https://github.com/apache/qpid-dispatch/pull/157 - must fix the test failures you are seeing on RHEL 6.4. Can you please try applying it?

As for the Solaris test failures, there seem to be a whole bunch of them. I have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738

I am not sure we can get to them before the 0.8.0 release.

Thanks.

----- Original Message -----
> From: "Adel Boutros" <Ad...@live.com>
> To: users@qpid.apache.org
> Sent: Friday, March 31, 2017 3:55:32 AM
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
>
>
> Hello Ganesh,
>
>
>
>
> Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux
> (Red Hat 6.4), Solaris x86 and Solaris Sparc.
>
> Please note we are using Proton 0.16.0 with only C++ bindings activated.
>
>
>
>
> PS: The good news is the code compiles on all 3 OSes but it's the tests which
> are failing. We consider this as a big step forward compared to the previous
> versions where the code didn't even compile on Solaris.
>
>
>
>
> Regards,
>
> Adel
>
> From: Ganesh Murthy <gm...@redhat.com>
> Sent: Thursday, March 30, 2017 3:10:00 PM
> To: users@qpid.apache.org
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
>
> ----- Original Message -----
> > From: "Adel Boutros" <Ad...@live.com>
> > To: users@qpid.apache.org
> > Sent: Thursday, March 30, 2017 9:04:01 AM
> > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >
> > I rechecked quickly and I have different behaviors on different OSes.
> >
> >
> > * Linux :
> >
> Can you please let us know what Linux flavor you are using so we can try
> locally?
> > router_policy_test and system_tests_protocol_family failing as stated
> > previously
> >
> Please also send the complete output of the failing tests.
> >
> > *Solaris:
> >
> > Only router_policy_test is failing.
> >
> > For system_tests_protocol_family, I have the message "Skipping test..IPV6
> > not
> > enabled"
> >
> >
> > We have some other test failures on Solaris and Linux but we will need to
> > debug them and we won't have time at the moment for them. I can send you a
> > report with the failures if you wish.
> >
> This is the commit that fixed DISPATCH-216 on master -
> https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036
> I verified that the above commit is present in the Qpid Dispatch Router 0.8.0
> Release Candidate 1 qpid-dispatch-0.8.0.tar.gz
> >
> > Regards,
> >
> > Adel
> >
> > ________________________________
> > From: Ted Ross <tr...@redhat.com>
> > Sent: Thursday, March 30, 2017 2:48:10 PM
> > To: users@qpid.apache.org
> > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >
> > Adel,
> >
> > The commits associated with that Jira and PR #140 are included in this
> > release candidate. We'll need to investigate whether it regressed again
> > or if the commit didn't fix the problem.
> >
> > -Ted
> >
> > On 03/30/2017 11:30 AM, Adel Boutros wrote:
> > > Hello Ted,
> > >
> > >
> > > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but
> > > it
> > > doens't seem to be the case. Ganesh was working on fixing those.
> > >
> > > Do you confirm they are not included?
> > > (
> > > http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571
> > > )
> > >
> > >
> > > I launched the CI on the release candidate and got the same IPv6 failures
> > > as before
> > >
> > >
> > > The following tests FAILED with ipv6 errors:
> > > 12 - router_policy_test (Failed)
> > > 19 - system_tests_protocol_family (Failed)
> > >
> > >
> > >
> > > 12: Test command: /python278/bin/python
> > > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m"
> > > "unittest"
> > > "-v" "router_policy_test"
> > > 12: Test timeout computed to be: 1500
> > > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\'
> > > is
> > > invalid: Policy vhost \'photoserver\' user group \'superuser\' option
> > > \'remoteHosts\' connectionOption \'::1\' failed to translate:
> > > \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct:
> > > \\\'::1\\\' did not resolve to one of the supported address
> > > family"\\\'\'\'.'
> > >
> > >
> > > 19: error: [Errno 97] Address family not supported by protocol
> > >
> > >
> > > Regards,
> > >
> > > Adel
> > >
> > > ________________________________
> > > From: Ted Ross <tr...@redhat.com>
> > > Sent: Wednesday, March 29, 2017 1:32:42 PM
> > > To: users@qpid.apache.org
> > > Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
> > >
> > > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> > > evaluation.
> > >
> > > Build Artifacts:
> > >
> > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
> > >
> > > New Features:
> > >
> > > DISPATCH-103 - Websocket Listeners
> > > DISPATCH-195 - Add support for transactional messages in the Router
> > > DISPATCH-441 - Support password environment variable in qdrouter
> > > config
> > > DISPATCH-467 - Terminus renaming for autoLinks
> > > DISPATCH-529 - Address annotation for Multi-Tenancy
> > > DISPATCH-726 - Connection Property for Failover Servers
> > >
> > > Improvements:
> > >
> > > DISPATCH-113 - expose NodeTracker::last_topology_change in management
> > > DISPATCH-542 - Popup text for clients should indicate if the client
> > > is a sender or receiver
> > > DISPATCH-543 - Initial load of topology page fetches too much
> > > information
> > > DISPATCH-544 - Add ability to hide the info panel on the left of
> > > the topology page
> > > DISPATCH-552 - Allow only one tree node to be expanded if there is
> > > a large number of routers
> > > DISPATCH-553 - Add statistic counter to the "log" entity to count
> > > log events per severity
> > > DISPATCH-559 - qdstat - Request only the columns that will be used
> > > in the display
> > > DISPATCH-561 - Create python program that returns fake management data
> > > DISPATCH-568 - Iterator module cleanup
> > > DISPATCH-570 - Add some counts to qdstat -g
> > > DISPATCH-572 - Adding log info with proton transport id and related
> > > remote IP/port
> > > DISPATCH-576 - Use new log entity statistic counter in console
> > > DISPATCH-578 - Dispatch trace logging forces all proton tracing on
> > > DISPATCH-579 - Expose software version via management
> > > DISPATCH-592 - Attempt to auto-login to the host:port that served
> > > the web page
> > > DISPATCH-597 - Log enhancements
> > > DISPATCH-600 - Support secure websockets
> > > DISPATCH-602 - Add a favicon to the stand-alone router site
> > > DISPATCH-606 - Default session window is too small, causing
> > > performance bottlenecks
> > > DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> > > systems
> > > DISPATCH-629 - Add a protocol-version to the inter-router protocol
> > > to enable backward compatibility
> > > DISPATCH-641 - Make containerId attribute work with clients
> > >
> > > Bugs Fixed:
> > >
> > > DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
> > > DISPATCH-216 - system_tests_protocol_family fails on systems with
> > > no IPv6
> > > DISPATCH-296 - segfault on router startup
> > > DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
> > > DISPATCH-314 - If a router has a normal listener, show it in a
> > > different color on the topology page
> > > DISPATCH-324 - Improve initial layout of topology node
> > > DISPATCH-344 - memory growth after repeated calls from qdstat -m
> > > DISPATCH-352 - Crash with empty configuration file
> > > DISPATCH-355 - query fails with what seems to be the error of a
> > > previous command
> > > DISPATCH-357 - Address field is empty for link routed links in the
> > > qdstat "links" output
> > > DISPATCH-433 - Navigating to console from bookmark displays empty
> > > page with just toolbars
> > > DISPATCH-451 - [AMQP] Hard coded session capacity should be
> > > configurable
> > > DISPATCH-503 - [display_name] successful test runs have non-ascii
> > > characters in router log
> > > DISPATCH-504 - [display_name] successful test runs have invalid
> > > message errors in router log
> > > DISPATCH-506 - Detach with no "error" sent by router on client TCP
> > > connection dropped
> > > DISPATCH-516 - Core dump when displayname IO adapter receives
> > > message with no reply-to
> > > DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> > > 0.7.0
> > > DISPATCH-527 - The $displayname address is currently available. It
> > > should not be available to external users
> > > DISPATCH-530 - Cannot connect using Firefox 48+
> > > DISPATCH-534 - Node selection and location is lost when the
> > > topology changes
> > > DISPATCH-536 - Circular buffer overflow errors occur when there are
> > > a large number of routers
> > > DISPATCH-538 - Highlighted path between routers sometimes doesn't
> > > unhighlight
> > > DISPATCH-540 - Clients with both in and out links are rendered in
> > > yellow
> > > DISPATCH-541 - Highlighted path between routers contains black arrows
> > > DISPATCH-546 - Crosssection popup position is incorrect
> > > DISPATCH-547 - Stand-alone version can't download generated config
> > > file for new nodes
> > > DISPATCH-554 - Topology nodes and links are too far apart when
> > > there are a large number of routers
> > > DISPATCH-556 - qdstat fails at high scale
> > > DISPATCH-557 - High connection rates cause problems in the Python
> > > management agent
> > > DISPATCH-560 - [console] Only use the color red to indicate a
> > > failure/issue.
> > > DISPATCH-563 - Topology graph flashes and redraws a few seconds
> > > after it is 1st drawn
> > > DISPATCH-564 - Error when switching routers on Entities page
> > > DISPATCH-565 - Error fetching log on Entities page
> > > DISPATCH-566 - Message annotations are not propagated to brokers on
> > > a linkRoute
> > > DISPATCH-567 - Slight but persistent memory leak when running java
> > > messenger producer and consumer
> > > DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> > > enum values.
> > > DISPATCH-573 - Memory leaks on shutdown
> > > DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
> > > DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
> > > DISPATCH-581 - detach with closed=false propagated as closed=true
> > > on link route
> > > DISPATCH-582 - Memory Leak with reactor client
> > > DISPATCH-583 - Random segmentation fault
> > > DISPATCH-585 - Firefox dropdown and buttons on list page have
> > > incorrect padding
> > > DISPATCH-586 - Dispatch crash on running c sender and receiver
> > > DISPATCH-587 - Provide feedback when loading log entries
> > > DISPATCH-588 - Schema is not loaded if auto-login is enabled
> > > DISPATCH-589 - Missing links on topology page
> > > DISPATCH-594 - Log file over-written every time the router is
> > > restarted
> > > DISPATCH-595 - dispositions propagated after link detach on link route
> > > DISPATCH-596 - error is lost from rejected state in relayed
> > > disposition
> > > DISPATCH-598 - Router crash when calling sender and session close
> > > methods in onLinkFLow()
> > > DISPATCH-599 - Link routing : messages is not transferred if sender
> > > detach link immediately
> > > DISPATCH-601 - Valgrind errors in dispatch tests
> > > DISPATCH-603 - address resource leak
> > > DISPATCH-604 - Management - Link connection-id does not match
> > > identities of connections
> > > DISPATCH-605 - Memory Leak with multple sender/receivers in one
> > > session
> > > DISPATCH-607 - Handle empty response from GET-MGMT-NODES
> > > DISPATCH-608 - Links not cleaned up when a close is sent without
> > > being preceeded by a detach and end
> > > DISPATCH-609 - Name attribute is duplicated in QUERY response
> > > DISPATCH-610 - crash in qdr_link_cleanup_CT
> > > DISPATCH-611 - Router core dump with old config file
> > > DISPATCH-612 - Add support for GCC equivalent compiler options
> > > DISPATCH-613 - Remove semi-colon not needed after function definition
> > > DISPATCH-614 - strerror_r on Solaris does not return char*
> > > DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
> > > DISPATCH-616 - Arithmetic operations not allowed on void * pointer
> > > DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> > > _POSIX_HOST_NAME_MAX is defined instead
> > > DISPATCH-618 - Revert eventfd on Solaris
> > > DISPATCH-619 - Use memalign instead of posix_memalign which is not
> > > defined on Solaris
> > > DISPATCH-620 - no-strict-aliasing is only supported with GCC
> > > DISPATCH-621 - Add missing string.h include for Solaris compiler
> > > DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> > > error to avoid undefined symbol on Solaris
> > > DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> > > return statement) detected on Solaris
> > > DISPATCH-624 - Add Atomic operations support on Solaris
> > > DISPATCH-626 - Add hints for getaddrinfo on Solaris
> > > DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> > > linkRoute overwrites connection handle
> > > DISPATCH-631 - Tests should be made conditional to skip tests for
> > > SASL features that are not available
> > > DISPATCH-633 - Creating connectors and addresses returns success
> > > codes of two different types.
> > > DISPATCH-634 - Dynamic Targets are unsupported
> > > DISPATCH-635 - The Ubuntu CI tests that involve two routers are
> > > failing
> > > DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> > > required; however, cmake complains with 0.14
> > > DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> > > fail when cyrus-sasl-plain is not installed
> > > DISPATCH-640 - containerId field conflics with the connector name
> > > DISPATCH-642 - Fix recognition of Artemis broker on topology page
> > > DISPATCH-643 - Duplicate log messages show up on normal AMQP close
> > > DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> > > pipe issue in Daemon mode
> > > DISPATCH-646 - Link route tests which test the drain feature fail
> > > intermittently
> > > DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> > > master
> > > DISPATCH-727 - qdmanage identity reporting and lookup are broken
> > > DISPATCH-728 - crash on shutdown with connector
> > > DISPATCH-729 - password-file option doesn't work correctly
> > > DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
> > > DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> > > but is missing from log schema
> > > DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> > > intermittently
> > >
> > > ---------------------------------------------------------------------
> > > 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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Posted by Ganesh Murthy <gm...@redhat.com>.
Hi Adel,
    I believe this pull request - https://github.com/apache/qpid-dispatch/pull/157 - must fix the test failures you are seeing on RHEL 6.4. Can you please try applying it?

As for the Solaris test failures, there seem to be a whole bunch of them. I have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738

I am not sure we can get to them before the 0.8.0 release.

Thanks.

----- Original Message -----
> From: "Adel Boutros" <Ad...@live.com>
> To: users@qpid.apache.org
> Sent: Friday, March 31, 2017 3:55:32 AM
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> 
> 
> 
> Hello Ganesh,
> 
> 
> 
> 
> Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux
> (Red Hat 6.4), Solaris x86 and Solaris Sparc.
> 
> Please note we are using Proton 0.16.0 with only C++ bindings activated.
> 
> 
> 
> 
> PS: The good news is the code compiles on all 3 OSes but it's the tests which
> are failing. We consider this as a big step forward compared to the previous
> versions where the code didn't even compile on Solaris.
> 
> 
> 
> 
> Regards,
> 
> Adel
> 
> From: Ganesh Murthy <gm...@redhat.com>
> Sent: Thursday, March 30, 2017 3:10:00 PM
> To: users@qpid.apache.org
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> 
> 
> ----- Original Message -----
> > From: "Adel Boutros" <Ad...@live.com>
> > To: users@qpid.apache.org
> > Sent: Thursday, March 30, 2017 9:04:01 AM
> > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> > 
> > I rechecked quickly and I have different behaviors on different OSes.
> > 
> > 
> > * Linux :
> > 
> Can you please let us know what Linux flavor you are using so we can try
> locally?
> > router_policy_test and system_tests_protocol_family failing as stated
> > previously
> > 
> Please also send the complete output of the failing tests.
> > 
> > *Solaris:
> > 
> > Only router_policy_test is failing.
> > 
> > For system_tests_protocol_family, I have the message "Skipping test..IPV6
> > not
> > enabled"
> > 
> > 
> > We have some other test failures on Solaris and Linux but we will need to
> > debug them and we won't have time at the moment for them. I can send you a
> > report with the failures if you wish.
> > 
> This is the commit that fixed DISPATCH-216 on master -
> https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036
> I verified that the above commit is present in the Qpid Dispatch Router 0.8.0
> Release Candidate 1 qpid-dispatch-0.8.0.tar.gz
> > 
> > Regards,
> > 
> > Adel
> > 
> > ________________________________
> > From: Ted Ross <tr...@redhat.com>
> > Sent: Thursday, March 30, 2017 2:48:10 PM
> > To: users@qpid.apache.org
> > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> > 
> > Adel,
> > 
> > The commits associated with that Jira and PR #140 are included in this
> > release candidate. We'll need to investigate whether it regressed again
> > or if the commit didn't fix the problem.
> > 
> > -Ted
> > 
> > On 03/30/2017 11:30 AM, Adel Boutros wrote:
> > > Hello Ted,
> > > 
> > > 
> > > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but
> > > it
> > > doens't seem to be the case. Ganesh was working on fixing those.
> > > 
> > > Do you confirm they are not included?
> > > (
> > > http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571
> > > )
> > > 
> > > 
> > > I launched the CI on the release candidate and got the same IPv6 failures
> > > as before
> > > 
> > > 
> > > The following tests FAILED with ipv6 errors:
> > > 12 - router_policy_test (Failed)
> > > 19 - system_tests_protocol_family (Failed)
> > > 
> > > 
> > > 
> > > 12: Test command: /python278/bin/python
> > > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m"
> > > "unittest"
> > > "-v" "router_policy_test"
> > > 12: Test timeout computed to be: 1500
> > > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\'
> > > is
> > > invalid: Policy vhost \'photoserver\' user group \'superuser\' option
> > > \'remoteHosts\' connectionOption \'::1\' failed to translate:
> > > \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct:
> > > \\\'::1\\\' did not resolve to one of the supported address
> > > family"\\\'\'\'.'
> > > 
> > > 
> > > 19: error: [Errno 97] Address family not supported by protocol
> > > 
> > > 
> > > Regards,
> > > 
> > > Adel
> > > 
> > > ________________________________
> > > From: Ted Ross <tr...@redhat.com>
> > > Sent: Wednesday, March 29, 2017 1:32:42 PM
> > > To: users@qpid.apache.org
> > > Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
> > > 
> > > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> > > evaluation.
> > > 
> > > Build Artifacts:
> > > 
> > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
> > > 
> > > New Features:
> > > 
> > > DISPATCH-103 - Websocket Listeners
> > > DISPATCH-195 - Add support for transactional messages in the Router
> > > DISPATCH-441 - Support password environment variable in qdrouter
> > > config
> > > DISPATCH-467 - Terminus renaming for autoLinks
> > > DISPATCH-529 - Address annotation for Multi-Tenancy
> > > DISPATCH-726 - Connection Property for Failover Servers
> > > 
> > > Improvements:
> > > 
> > > DISPATCH-113 - expose NodeTracker::last_topology_change in management
> > > DISPATCH-542 - Popup text for clients should indicate if the client
> > > is a sender or receiver
> > > DISPATCH-543 - Initial load of topology page fetches too much
> > > information
> > > DISPATCH-544 - Add ability to hide the info panel on the left of
> > > the topology page
> > > DISPATCH-552 - Allow only one tree node to be expanded if there is
> > > a large number of routers
> > > DISPATCH-553 - Add statistic counter to the "log" entity to count
> > > log events per severity
> > > DISPATCH-559 - qdstat - Request only the columns that will be used
> > > in the display
> > > DISPATCH-561 - Create python program that returns fake management data
> > > DISPATCH-568 - Iterator module cleanup
> > > DISPATCH-570 - Add some counts to qdstat -g
> > > DISPATCH-572 - Adding log info with proton transport id and related
> > > remote IP/port
> > > DISPATCH-576 - Use new log entity statistic counter in console
> > > DISPATCH-578 - Dispatch trace logging forces all proton tracing on
> > > DISPATCH-579 - Expose software version via management
> > > DISPATCH-592 - Attempt to auto-login to the host:port that served
> > > the web page
> > > DISPATCH-597 - Log enhancements
> > > DISPATCH-600 - Support secure websockets
> > > DISPATCH-602 - Add a favicon to the stand-alone router site
> > > DISPATCH-606 - Default session window is too small, causing
> > > performance bottlenecks
> > > DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> > > systems
> > > DISPATCH-629 - Add a protocol-version to the inter-router protocol
> > > to enable backward compatibility
> > > DISPATCH-641 - Make containerId attribute work with clients
> > > 
> > > Bugs Fixed:
> > > 
> > > DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
> > > DISPATCH-216 - system_tests_protocol_family fails on systems with
> > > no IPv6
> > > DISPATCH-296 - segfault on router startup
> > > DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
> > > DISPATCH-314 - If a router has a normal listener, show it in a
> > > different color on the topology page
> > > DISPATCH-324 - Improve initial layout of topology node
> > > DISPATCH-344 - memory growth after repeated calls from qdstat -m
> > > DISPATCH-352 - Crash with empty configuration file
> > > DISPATCH-355 - query fails with what seems to be the error of a
> > > previous command
> > > DISPATCH-357 - Address field is empty for link routed links in the
> > > qdstat "links" output
> > > DISPATCH-433 - Navigating to console from bookmark displays empty
> > > page with just toolbars
> > > DISPATCH-451 - [AMQP] Hard coded session capacity should be
> > > configurable
> > > DISPATCH-503 - [display_name] successful test runs have non-ascii
> > > characters in router log
> > > DISPATCH-504 - [display_name] successful test runs have invalid
> > > message errors in router log
> > > DISPATCH-506 - Detach with no "error" sent by router on client TCP
> > > connection dropped
> > > DISPATCH-516 - Core dump when displayname IO adapter receives
> > > message with no reply-to
> > > DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> > > 0.7.0
> > > DISPATCH-527 - The $displayname address is currently available. It
> > > should not be available to external users
> > > DISPATCH-530 - Cannot connect using Firefox 48+
> > > DISPATCH-534 - Node selection and location is lost when the
> > > topology changes
> > > DISPATCH-536 - Circular buffer overflow errors occur when there are
> > > a large number of routers
> > > DISPATCH-538 - Highlighted path between routers sometimes doesn't
> > > unhighlight
> > > DISPATCH-540 - Clients with both in and out links are rendered in
> > > yellow
> > > DISPATCH-541 - Highlighted path between routers contains black arrows
> > > DISPATCH-546 - Crosssection popup position is incorrect
> > > DISPATCH-547 - Stand-alone version can't download generated config
> > > file for new nodes
> > > DISPATCH-554 - Topology nodes and links are too far apart when
> > > there are a large number of routers
> > > DISPATCH-556 - qdstat fails at high scale
> > > DISPATCH-557 - High connection rates cause problems in the Python
> > > management agent
> > > DISPATCH-560 - [console] Only use the color red to indicate a
> > > failure/issue.
> > > DISPATCH-563 - Topology graph flashes and redraws a few seconds
> > > after it is 1st drawn
> > > DISPATCH-564 - Error when switching routers on Entities page
> > > DISPATCH-565 - Error fetching log on Entities page
> > > DISPATCH-566 - Message annotations are not propagated to brokers on
> > > a linkRoute
> > > DISPATCH-567 - Slight but persistent memory leak when running java
> > > messenger producer and consumer
> > > DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> > > enum values.
> > > DISPATCH-573 - Memory leaks on shutdown
> > > DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
> > > DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
> > > DISPATCH-581 - detach with closed=false propagated as closed=true
> > > on link route
> > > DISPATCH-582 - Memory Leak with reactor client
> > > DISPATCH-583 - Random segmentation fault
> > > DISPATCH-585 - Firefox dropdown and buttons on list page have
> > > incorrect padding
> > > DISPATCH-586 - Dispatch crash on running c sender and receiver
> > > DISPATCH-587 - Provide feedback when loading log entries
> > > DISPATCH-588 - Schema is not loaded if auto-login is enabled
> > > DISPATCH-589 - Missing links on topology page
> > > DISPATCH-594 - Log file over-written every time the router is
> > > restarted
> > > DISPATCH-595 - dispositions propagated after link detach on link route
> > > DISPATCH-596 - error is lost from rejected state in relayed
> > > disposition
> > > DISPATCH-598 - Router crash when calling sender and session close
> > > methods in onLinkFLow()
> > > DISPATCH-599 - Link routing : messages is not transferred if sender
> > > detach link immediately
> > > DISPATCH-601 - Valgrind errors in dispatch tests
> > > DISPATCH-603 - address resource leak
> > > DISPATCH-604 - Management - Link connection-id does not match
> > > identities of connections
> > > DISPATCH-605 - Memory Leak with multple sender/receivers in one
> > > session
> > > DISPATCH-607 - Handle empty response from GET-MGMT-NODES
> > > DISPATCH-608 - Links not cleaned up when a close is sent without
> > > being preceeded by a detach and end
> > > DISPATCH-609 - Name attribute is duplicated in QUERY response
> > > DISPATCH-610 - crash in qdr_link_cleanup_CT
> > > DISPATCH-611 - Router core dump with old config file
> > > DISPATCH-612 - Add support for GCC equivalent compiler options
> > > DISPATCH-613 - Remove semi-colon not needed after function definition
> > > DISPATCH-614 - strerror_r on Solaris does not return char*
> > > DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
> > > DISPATCH-616 - Arithmetic operations not allowed on void * pointer
> > > DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> > > _POSIX_HOST_NAME_MAX is defined instead
> > > DISPATCH-618 - Revert eventfd on Solaris
> > > DISPATCH-619 - Use memalign instead of posix_memalign which is not
> > > defined on Solaris
> > > DISPATCH-620 - no-strict-aliasing is only supported with GCC
> > > DISPATCH-621 - Add missing string.h include for Solaris compiler
> > > DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> > > error to avoid undefined symbol on Solaris
> > > DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> > > return statement) detected on Solaris
> > > DISPATCH-624 - Add Atomic operations support on Solaris
> > > DISPATCH-626 - Add hints for getaddrinfo on Solaris
> > > DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> > > linkRoute overwrites connection handle
> > > DISPATCH-631 - Tests should be made conditional to skip tests for
> > > SASL features that are not available
> > > DISPATCH-633 - Creating connectors and addresses returns success
> > > codes of two different types.
> > > DISPATCH-634 - Dynamic Targets are unsupported
> > > DISPATCH-635 - The Ubuntu CI tests that involve two routers are
> > > failing
> > > DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> > > required; however, cmake complains with 0.14
> > > DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> > > fail when cyrus-sasl-plain is not installed
> > > DISPATCH-640 - containerId field conflics with the connector name
> > > DISPATCH-642 - Fix recognition of Artemis broker on topology page
> > > DISPATCH-643 - Duplicate log messages show up on normal AMQP close
> > > DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> > > pipe issue in Daemon mode
> > > DISPATCH-646 - Link route tests which test the drain feature fail
> > > intermittently
> > > DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> > > master
> > > DISPATCH-727 - qdmanage identity reporting and lookup are broken
> > > DISPATCH-728 - crash on shutdown with connector
> > > DISPATCH-729 - password-file option doesn't work correctly
> > > DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
> > > DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> > > but is missing from log schema
> > > DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> > > intermittently
> > > 
> > > ---------------------------------------------------------------------
> > > 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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Posted by Adel Boutros <Ad...@live.com>.
Small correction:


We are using Proton 0.16.0 with only C++ and Python bindings activated.

________________________________
From: Adel Boutros
Sent: Friday, March 31, 2017 9:55:32 AM
To: users@qpid.apache.org
Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1


Hello Ganesh,


Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux (Red Hat 6.4), Solaris x86 and Solaris Sparc.

Please note we are using Proton 0.16.0 with only C++ bindings activated.


PS: The good news is the code compiles on all 3 OSes but it's the tests which are failing. We consider this as a big step forward compared to the previous versions where the code didn't even compile on Solaris.


Regards,

Adel

________________________________
From: Ganesh Murthy <gm...@redhat.com>
Sent: Thursday, March 30, 2017 3:10:00 PM
To: users@qpid.apache.org
Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1



----- Original Message -----
> From: "Adel Boutros" <Ad...@live.com>
> To: users@qpid.apache.org
> Sent: Thursday, March 30, 2017 9:04:01 AM
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
> I rechecked quickly and I have different behaviors on different OSes.
>
>
> * Linux :
>
Can you please let us know what Linux flavor you are using so we can try locally?
> router_policy_test and system_tests_protocol_family failing as stated
> previously
>
Please also send the complete output of the failing tests.
>
> *Solaris:
>
> Only router_policy_test  is failing.
>
> For system_tests_protocol_family, I have the message "Skipping test..IPV6 not
> enabled"
>
>
> We have some other test failures on Solaris and Linux but we will need to
> debug them and we won't have time at the moment for them. I can send you a
> report with the failures if you wish.
>
This is the commit that fixed DISPATCH-216 on master - https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036
I verified that the above commit is present in the Qpid Dispatch Router 0.8.0 Release Candidate 1 qpid-dispatch-0.8.0.tar.gz
>
> Regards,
>
> Adel
>
> ________________________________
> From: Ted Ross <tr...@redhat.com>
> Sent: Thursday, March 30, 2017 2:48:10 PM
> To: users@qpid.apache.org
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
> Adel,
>
> The commits associated with that Jira and PR #140 are included in this
> release candidate.  We'll need to investigate whether it regressed again
> or if the commit didn't fix the problem.
>
> -Ted
>
> On 03/30/2017 11:30 AM, Adel Boutros wrote:
> > Hello Ted,
> >
> >
> > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it
> > doens't seem to be the case. Ganesh was working on fixing those.
> >
> > Do you confirm they are not included?
> > (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571)
> >
> >
> > I launched the CI on the release candidate and got the same IPv6 failures
> > as before
> >
> >
> > The following tests FAILED with ipv6 errors:
> > 12 - router_policy_test (Failed)
> > 19 - system_tests_protocol_family (Failed)
> >
> >
> >
> > 12: Test command: /python278/bin/python
> > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest"
> > "-v" "router_policy_test"
> > 12: Test timeout computed to be: 1500
> > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is
> > invalid: Policy vhost \'photoserver\' user group \'superuser\' option
> > \'remoteHosts\' connectionOption \'::1\' failed to translate:
> > \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct:
> > \\\'::1\\\' did not resolve to one of the supported address
> > family"\\\'\'\'.'
> >
> >
> > 19: error: [Errno 97] Address family not supported by protocol
> >
> >
> > Regards,
> >
> > Adel
> >
> > ________________________________
> > From: Ted Ross <tr...@redhat.com>
> > Sent: Wednesday, March 29, 2017 1:32:42 PM
> > To: users@qpid.apache.org
> > Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >
> > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> > evaluation.
> >
> > Build Artifacts:
> >
> >      https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
> >
> > New Features:
> >
> >      DISPATCH-103 - Websocket Listeners
> >      DISPATCH-195 - Add support for transactional messages in the Router
> >      DISPATCH-441 - Support password environment variable in qdrouter
> >      config
> >      DISPATCH-467 - Terminus renaming for autoLinks
> >      DISPATCH-529 - Address annotation for Multi-Tenancy
> >      DISPATCH-726 - Connection Property for Failover Servers
> >
> > Improvements:
> >
> >      DISPATCH-113 - expose NodeTracker::last_topology_change in management
> >      DISPATCH-542 - Popup text for clients should indicate if the client
> > is a sender or receiver
> >      DISPATCH-543 - Initial load of topology page fetches too much
> > information
> >      DISPATCH-544 - Add ability to hide the info panel on the left of
> > the topology page
> >      DISPATCH-552 - Allow only one tree node to be expanded if there is
> > a large number of routers
> >      DISPATCH-553 - Add statistic counter to the "log" entity to count
> > log events per severity
> >      DISPATCH-559 - qdstat - Request only the columns that will be used
> > in the display
> >      DISPATCH-561 - Create python program that returns fake management data
> >      DISPATCH-568 - Iterator module cleanup
> >      DISPATCH-570 - Add some counts to qdstat -g
> >      DISPATCH-572 - Adding log info with proton transport id and related
> > remote IP/port
> >      DISPATCH-576 - Use new log entity statistic counter in console
> >      DISPATCH-578 - Dispatch trace logging forces all proton tracing on
> >      DISPATCH-579 - Expose software version via management
> >      DISPATCH-592 - Attempt to auto-login to the host:port that served
> > the web page
> >      DISPATCH-597 - Log enhancements
> >      DISPATCH-600 - Support secure websockets
> >      DISPATCH-602 - Add a favicon to the stand-alone router site
> >      DISPATCH-606 - Default session window is too small, causing
> > performance bottlenecks
> >      DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> > systems
> >      DISPATCH-629 - Add a protocol-version to the inter-router protocol
> > to enable backward compatibility
> >      DISPATCH-641 - Make containerId attribute work with clients
> >
> > Bugs Fixed:
> >
> >      DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
> >      DISPATCH-216 - system_tests_protocol_family fails on systems with
> > no IPv6
> >      DISPATCH-296 - segfault on router startup
> >      DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
> >      DISPATCH-314 - If a router has a normal listener, show it in a
> > different color on the topology page
> >      DISPATCH-324 - Improve initial layout of topology node
> >      DISPATCH-344 - memory growth after repeated calls from qdstat -m
> >      DISPATCH-352 - Crash with empty configuration file
> >      DISPATCH-355 - query fails with what seems to be the error of a
> > previous command
> >      DISPATCH-357 - Address field is empty for link routed links in the
> > qdstat "links" output
> >      DISPATCH-433 - Navigating to console from bookmark displays empty
> > page with just toolbars
> >      DISPATCH-451 - [AMQP] Hard coded session capacity should be
> > configurable
> >      DISPATCH-503 - [display_name] successful test runs  have non-ascii
> > characters in router log
> >      DISPATCH-504 - [display_name] successful test runs have invalid
> > message errors  in router log
> >      DISPATCH-506 - Detach with no "error" sent by router on client TCP
> > connection dropped
> >      DISPATCH-516 - Core dump when displayname IO adapter receives
> > message with no reply-to
> >      DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> > 0.7.0
> >      DISPATCH-527 - The $displayname address is currently available. It
> > should not be available to external users
> >      DISPATCH-530 - Cannot connect using Firefox 48+
> >      DISPATCH-534 - Node selection and location is lost when the
> > topology changes
> >      DISPATCH-536 - Circular buffer overflow errors occur when there are
> > a large number of routers
> >      DISPATCH-538 - Highlighted path between routers sometimes doesn't
> > unhighlight
> >      DISPATCH-540 - Clients with both in and out links are rendered in
> > yellow
> >      DISPATCH-541 - Highlighted path between routers contains black arrows
> >      DISPATCH-546 - Crosssection popup position is incorrect
> >      DISPATCH-547 - Stand-alone version can't download generated config
> > file for new nodes
> >      DISPATCH-554 - Topology nodes and links are too far apart when
> > there are a large number of routers
> >      DISPATCH-556 - qdstat fails at high scale
> >      DISPATCH-557 - High connection rates cause problems in the Python
> > management agent
> >      DISPATCH-560 - [console] Only use the color red to indicate a
> > failure/issue.
> >      DISPATCH-563 - Topology graph flashes and redraws a few seconds
> > after it is 1st drawn
> >      DISPATCH-564 - Error when switching routers on Entities page
> >      DISPATCH-565 - Error fetching log on Entities page
> >      DISPATCH-566 - Message annotations are not propagated to brokers on
> > a linkRoute
> >      DISPATCH-567 - Slight but persistent memory leak when running java
> > messenger producer and consumer
> >      DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> > enum values.
> >      DISPATCH-573 - Memory leaks on shutdown
> >      DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
> >      DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
> >      DISPATCH-581 - detach with closed=false propagated as closed=true
> > on link route
> >      DISPATCH-582 - Memory Leak with reactor client
> >      DISPATCH-583 - Random segmentation fault
> >      DISPATCH-585 - Firefox dropdown and buttons on list page have
> > incorrect padding
> >      DISPATCH-586 - Dispatch crash on running c sender and receiver
> >      DISPATCH-587 - Provide feedback when loading log entries
> >      DISPATCH-588 - Schema is not loaded if auto-login is enabled
> >      DISPATCH-589 - Missing links on topology page
> >      DISPATCH-594 - Log file over-written every time the router is
> >      restarted
> >      DISPATCH-595 - dispositions propagated after link detach on link route
> >      DISPATCH-596 - error is lost from rejected state in relayed
> >      disposition
> >      DISPATCH-598 - Router crash when calling sender and session close
> > methods in onLinkFLow()
> >      DISPATCH-599 - Link routing : messages is not transferred if sender
> > detach link immediately
> >      DISPATCH-601 - Valgrind errors in dispatch tests
> >      DISPATCH-603 - address resource leak
> >      DISPATCH-604 - Management - Link connection-id does not match
> > identities of connections
> >      DISPATCH-605 - Memory Leak with multple sender/receivers in one
> >      session
> >      DISPATCH-607 - Handle empty response from GET-MGMT-NODES
> >      DISPATCH-608 - Links not cleaned up when a close is sent without
> > being preceeded by a detach and end
> >      DISPATCH-609 - Name attribute is duplicated in QUERY response
> >      DISPATCH-610 - crash in qdr_link_cleanup_CT
> >      DISPATCH-611 - Router core dump with old config file
> >      DISPATCH-612 - Add support for GCC equivalent compiler options
> >      DISPATCH-613 - Remove semi-colon not needed after function definition
> >      DISPATCH-614 - strerror_r on Solaris does not return char*
> >      DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
> >      DISPATCH-616 - Arithmetic operations not allowed on void * pointer
> >      DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> > _POSIX_HOST_NAME_MAX is defined instead
> >      DISPATCH-618 - Revert eventfd on Solaris
> >      DISPATCH-619 - Use memalign instead of posix_memalign which is not
> > defined on Solaris
> >      DISPATCH-620 - no-strict-aliasing is only supported with GCC
> >      DISPATCH-621 - Add missing string.h include for Solaris compiler
> >      DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> > error to avoid undefined symbol on Solaris
> >      DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> > return statement) detected on Solaris
> >      DISPATCH-624 - Add Atomic operations support on Solaris
> >      DISPATCH-626 - Add hints for getaddrinfo on Solaris
> >      DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> > linkRoute overwrites connection handle
> >      DISPATCH-631 - Tests should be made conditional to skip tests for
> > SASL features that are not available
> >      DISPATCH-633 - Creating connectors and addresses returns success
> > codes of two different types.
> >      DISPATCH-634 - Dynamic Targets are unsupported
> >      DISPATCH-635 - The Ubuntu CI tests that involve two routers are
> >      failing
> >      DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> > required; however, cmake complains with 0.14
> >      DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> > fail when cyrus-sasl-plain is not installed
> >      DISPATCH-640 - containerId field conflics with the connector name
> >      DISPATCH-642 - Fix recognition of Artemis broker on topology page
> >      DISPATCH-643 - Duplicate log messages show up on normal AMQP close
> >      DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> > pipe issue in Daemon mode
> >      DISPATCH-646 - Link route tests which test the drain feature fail
> > intermittently
> >      DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> > master
> >      DISPATCH-727 - qdmanage identity reporting and lookup are broken
> >      DISPATCH-728 - crash on shutdown with connector
> >      DISPATCH-729 - password-file option doesn't work correctly
> >      DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
> >      DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> > but is missing from log schema
> >      DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> > intermittently
> >
> > ---------------------------------------------------------------------
> > 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


Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Posted by Adel Boutros <Ad...@live.com>.
Hello Ganesh,


Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux (Red Hat 6.4), Solaris x86 and Solaris Sparc.

Please note we are using Proton 0.16.0 with only C++ bindings activated.


PS: The good news is the code compiles on all 3 OSes but it's the tests which are failing. We consider this as a big step forward compared to the previous versions where the code didn't even compile on Solaris.


Regards,

Adel

________________________________
From: Ganesh Murthy <gm...@redhat.com>
Sent: Thursday, March 30, 2017 3:10:00 PM
To: users@qpid.apache.org
Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1



----- Original Message -----
> From: "Adel Boutros" <Ad...@live.com>
> To: users@qpid.apache.org
> Sent: Thursday, March 30, 2017 9:04:01 AM
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
> I rechecked quickly and I have different behaviors on different OSes.
>
>
> * Linux :
>
Can you please let us know what Linux flavor you are using so we can try locally?
> router_policy_test and system_tests_protocol_family failing as stated
> previously
>
Please also send the complete output of the failing tests.
>
> *Solaris:
>
> Only router_policy_test  is failing.
>
> For system_tests_protocol_family, I have the message "Skipping test..IPV6 not
> enabled"
>
>
> We have some other test failures on Solaris and Linux but we will need to
> debug them and we won't have time at the moment for them. I can send you a
> report with the failures if you wish.
>
This is the commit that fixed DISPATCH-216 on master - https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036
I verified that the above commit is present in the Qpid Dispatch Router 0.8.0 Release Candidate 1 qpid-dispatch-0.8.0.tar.gz
>
> Regards,
>
> Adel
>
> ________________________________
> From: Ted Ross <tr...@redhat.com>
> Sent: Thursday, March 30, 2017 2:48:10 PM
> To: users@qpid.apache.org
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
> Adel,
>
> The commits associated with that Jira and PR #140 are included in this
> release candidate.  We'll need to investigate whether it regressed again
> or if the commit didn't fix the problem.
>
> -Ted
>
> On 03/30/2017 11:30 AM, Adel Boutros wrote:
> > Hello Ted,
> >
> >
> > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it
> > doens't seem to be the case. Ganesh was working on fixing those.
> >
> > Do you confirm they are not included?
> > (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571)
> >
> >
> > I launched the CI on the release candidate and got the same IPv6 failures
> > as before
> >
> >
> > The following tests FAILED with ipv6 errors:
> > 12 - router_policy_test (Failed)
> > 19 - system_tests_protocol_family (Failed)
> >
> >
> >
> > 12: Test command: /python278/bin/python
> > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest"
> > "-v" "router_policy_test"
> > 12: Test timeout computed to be: 1500
> > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is
> > invalid: Policy vhost \'photoserver\' user group \'superuser\' option
> > \'remoteHosts\' connectionOption \'::1\' failed to translate:
> > \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct:
> > \\\'::1\\\' did not resolve to one of the supported address
> > family"\\\'\'\'.'
> >
> >
> > 19: error: [Errno 97] Address family not supported by protocol
> >
> >
> > Regards,
> >
> > Adel
> >
> > ________________________________
> > From: Ted Ross <tr...@redhat.com>
> > Sent: Wednesday, March 29, 2017 1:32:42 PM
> > To: users@qpid.apache.org
> > Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >
> > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> > evaluation.
> >
> > Build Artifacts:
> >
> >      https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
> >
> > New Features:
> >
> >      DISPATCH-103 - Websocket Listeners
> >      DISPATCH-195 - Add support for transactional messages in the Router
> >      DISPATCH-441 - Support password environment variable in qdrouter
> >      config
> >      DISPATCH-467 - Terminus renaming for autoLinks
> >      DISPATCH-529 - Address annotation for Multi-Tenancy
> >      DISPATCH-726 - Connection Property for Failover Servers
> >
> > Improvements:
> >
> >      DISPATCH-113 - expose NodeTracker::last_topology_change in management
> >      DISPATCH-542 - Popup text for clients should indicate if the client
> > is a sender or receiver
> >      DISPATCH-543 - Initial load of topology page fetches too much
> > information
> >      DISPATCH-544 - Add ability to hide the info panel on the left of
> > the topology page
> >      DISPATCH-552 - Allow only one tree node to be expanded if there is
> > a large number of routers
> >      DISPATCH-553 - Add statistic counter to the "log" entity to count
> > log events per severity
> >      DISPATCH-559 - qdstat - Request only the columns that will be used
> > in the display
> >      DISPATCH-561 - Create python program that returns fake management data
> >      DISPATCH-568 - Iterator module cleanup
> >      DISPATCH-570 - Add some counts to qdstat -g
> >      DISPATCH-572 - Adding log info with proton transport id and related
> > remote IP/port
> >      DISPATCH-576 - Use new log entity statistic counter in console
> >      DISPATCH-578 - Dispatch trace logging forces all proton tracing on
> >      DISPATCH-579 - Expose software version via management
> >      DISPATCH-592 - Attempt to auto-login to the host:port that served
> > the web page
> >      DISPATCH-597 - Log enhancements
> >      DISPATCH-600 - Support secure websockets
> >      DISPATCH-602 - Add a favicon to the stand-alone router site
> >      DISPATCH-606 - Default session window is too small, causing
> > performance bottlenecks
> >      DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> > systems
> >      DISPATCH-629 - Add a protocol-version to the inter-router protocol
> > to enable backward compatibility
> >      DISPATCH-641 - Make containerId attribute work with clients
> >
> > Bugs Fixed:
> >
> >      DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
> >      DISPATCH-216 - system_tests_protocol_family fails on systems with
> > no IPv6
> >      DISPATCH-296 - segfault on router startup
> >      DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
> >      DISPATCH-314 - If a router has a normal listener, show it in a
> > different color on the topology page
> >      DISPATCH-324 - Improve initial layout of topology node
> >      DISPATCH-344 - memory growth after repeated calls from qdstat -m
> >      DISPATCH-352 - Crash with empty configuration file
> >      DISPATCH-355 - query fails with what seems to be the error of a
> > previous command
> >      DISPATCH-357 - Address field is empty for link routed links in the
> > qdstat "links" output
> >      DISPATCH-433 - Navigating to console from bookmark displays empty
> > page with just toolbars
> >      DISPATCH-451 - [AMQP] Hard coded session capacity should be
> > configurable
> >      DISPATCH-503 - [display_name] successful test runs  have non-ascii
> > characters in router log
> >      DISPATCH-504 - [display_name] successful test runs have invalid
> > message errors  in router log
> >      DISPATCH-506 - Detach with no "error" sent by router on client TCP
> > connection dropped
> >      DISPATCH-516 - Core dump when displayname IO adapter receives
> > message with no reply-to
> >      DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> > 0.7.0
> >      DISPATCH-527 - The $displayname address is currently available. It
> > should not be available to external users
> >      DISPATCH-530 - Cannot connect using Firefox 48+
> >      DISPATCH-534 - Node selection and location is lost when the
> > topology changes
> >      DISPATCH-536 - Circular buffer overflow errors occur when there are
> > a large number of routers
> >      DISPATCH-538 - Highlighted path between routers sometimes doesn't
> > unhighlight
> >      DISPATCH-540 - Clients with both in and out links are rendered in
> > yellow
> >      DISPATCH-541 - Highlighted path between routers contains black arrows
> >      DISPATCH-546 - Crosssection popup position is incorrect
> >      DISPATCH-547 - Stand-alone version can't download generated config
> > file for new nodes
> >      DISPATCH-554 - Topology nodes and links are too far apart when
> > there are a large number of routers
> >      DISPATCH-556 - qdstat fails at high scale
> >      DISPATCH-557 - High connection rates cause problems in the Python
> > management agent
> >      DISPATCH-560 - [console] Only use the color red to indicate a
> > failure/issue.
> >      DISPATCH-563 - Topology graph flashes and redraws a few seconds
> > after it is 1st drawn
> >      DISPATCH-564 - Error when switching routers on Entities page
> >      DISPATCH-565 - Error fetching log on Entities page
> >      DISPATCH-566 - Message annotations are not propagated to brokers on
> > a linkRoute
> >      DISPATCH-567 - Slight but persistent memory leak when running java
> > messenger producer and consumer
> >      DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> > enum values.
> >      DISPATCH-573 - Memory leaks on shutdown
> >      DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
> >      DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
> >      DISPATCH-581 - detach with closed=false propagated as closed=true
> > on link route
> >      DISPATCH-582 - Memory Leak with reactor client
> >      DISPATCH-583 - Random segmentation fault
> >      DISPATCH-585 - Firefox dropdown and buttons on list page have
> > incorrect padding
> >      DISPATCH-586 - Dispatch crash on running c sender and receiver
> >      DISPATCH-587 - Provide feedback when loading log entries
> >      DISPATCH-588 - Schema is not loaded if auto-login is enabled
> >      DISPATCH-589 - Missing links on topology page
> >      DISPATCH-594 - Log file over-written every time the router is
> >      restarted
> >      DISPATCH-595 - dispositions propagated after link detach on link route
> >      DISPATCH-596 - error is lost from rejected state in relayed
> >      disposition
> >      DISPATCH-598 - Router crash when calling sender and session close
> > methods in onLinkFLow()
> >      DISPATCH-599 - Link routing : messages is not transferred if sender
> > detach link immediately
> >      DISPATCH-601 - Valgrind errors in dispatch tests
> >      DISPATCH-603 - address resource leak
> >      DISPATCH-604 - Management - Link connection-id does not match
> > identities of connections
> >      DISPATCH-605 - Memory Leak with multple sender/receivers in one
> >      session
> >      DISPATCH-607 - Handle empty response from GET-MGMT-NODES
> >      DISPATCH-608 - Links not cleaned up when a close is sent without
> > being preceeded by a detach and end
> >      DISPATCH-609 - Name attribute is duplicated in QUERY response
> >      DISPATCH-610 - crash in qdr_link_cleanup_CT
> >      DISPATCH-611 - Router core dump with old config file
> >      DISPATCH-612 - Add support for GCC equivalent compiler options
> >      DISPATCH-613 - Remove semi-colon not needed after function definition
> >      DISPATCH-614 - strerror_r on Solaris does not return char*
> >      DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
> >      DISPATCH-616 - Arithmetic operations not allowed on void * pointer
> >      DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> > _POSIX_HOST_NAME_MAX is defined instead
> >      DISPATCH-618 - Revert eventfd on Solaris
> >      DISPATCH-619 - Use memalign instead of posix_memalign which is not
> > defined on Solaris
> >      DISPATCH-620 - no-strict-aliasing is only supported with GCC
> >      DISPATCH-621 - Add missing string.h include for Solaris compiler
> >      DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> > error to avoid undefined symbol on Solaris
> >      DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> > return statement) detected on Solaris
> >      DISPATCH-624 - Add Atomic operations support on Solaris
> >      DISPATCH-626 - Add hints for getaddrinfo on Solaris
> >      DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> > linkRoute overwrites connection handle
> >      DISPATCH-631 - Tests should be made conditional to skip tests for
> > SASL features that are not available
> >      DISPATCH-633 - Creating connectors and addresses returns success
> > codes of two different types.
> >      DISPATCH-634 - Dynamic Targets are unsupported
> >      DISPATCH-635 - The Ubuntu CI tests that involve two routers are
> >      failing
> >      DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> > required; however, cmake complains with 0.14
> >      DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> > fail when cyrus-sasl-plain is not installed
> >      DISPATCH-640 - containerId field conflics with the connector name
> >      DISPATCH-642 - Fix recognition of Artemis broker on topology page
> >      DISPATCH-643 - Duplicate log messages show up on normal AMQP close
> >      DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> > pipe issue in Daemon mode
> >      DISPATCH-646 - Link route tests which test the drain feature fail
> > intermittently
> >      DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> > master
> >      DISPATCH-727 - qdmanage identity reporting and lookup are broken
> >      DISPATCH-728 - crash on shutdown with connector
> >      DISPATCH-729 - password-file option doesn't work correctly
> >      DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
> >      DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> > but is missing from log schema
> >      DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> > intermittently
> >
> > ---------------------------------------------------------------------
> > 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


Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Posted by Ganesh Murthy <gm...@redhat.com>.

----- Original Message -----
> From: "Adel Boutros" <Ad...@live.com>
> To: users@qpid.apache.org
> Sent: Thursday, March 30, 2017 9:04:01 AM
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> 
> I rechecked quickly and I have different behaviors on different OSes.
> 
> 
> * Linux :
> 
Can you please let us know what Linux flavor you are using so we can try locally?
> router_policy_test and system_tests_protocol_family failing as stated
> previously
> 
Please also send the complete output of the failing tests.
> 
> *Solaris:
> 
> Only router_policy_test  is failing.
> 
> For system_tests_protocol_family, I have the message "Skipping test..IPV6 not
> enabled"
> 
> 
> We have some other test failures on Solaris and Linux but we will need to
> debug them and we won't have time at the moment for them. I can send you a
> report with the failures if you wish.
> 
This is the commit that fixed DISPATCH-216 on master - https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036
I verified that the above commit is present in the Qpid Dispatch Router 0.8.0 Release Candidate 1 qpid-dispatch-0.8.0.tar.gz
> 
> Regards,
> 
> Adel
> 
> ________________________________
> From: Ted Ross <tr...@redhat.com>
> Sent: Thursday, March 30, 2017 2:48:10 PM
> To: users@qpid.apache.org
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> 
> Adel,
> 
> The commits associated with that Jira and PR #140 are included in this
> release candidate.  We'll need to investigate whether it regressed again
> or if the commit didn't fix the problem.
> 
> -Ted
> 
> On 03/30/2017 11:30 AM, Adel Boutros wrote:
> > Hello Ted,
> >
> >
> > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it
> > doens't seem to be the case. Ganesh was working on fixing those.
> >
> > Do you confirm they are not included?
> > (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571)
> >
> >
> > I launched the CI on the release candidate and got the same IPv6 failures
> > as before
> >
> >
> > The following tests FAILED with ipv6 errors:
> > 12 - router_policy_test (Failed)
> > 19 - system_tests_protocol_family (Failed)
> >
> >
> >
> > 12: Test command: /python278/bin/python
> > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest"
> > "-v" "router_policy_test"
> > 12: Test timeout computed to be: 1500
> > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is
> > invalid: Policy vhost \'photoserver\' user group \'superuser\' option
> > \'remoteHosts\' connectionOption \'::1\' failed to translate:
> > \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct:
> > \\\'::1\\\' did not resolve to one of the supported address
> > family"\\\'\'\'.'
> >
> >
> > 19: error: [Errno 97] Address family not supported by protocol
> >
> >
> > Regards,
> >
> > Adel
> >
> > ________________________________
> > From: Ted Ross <tr...@redhat.com>
> > Sent: Wednesday, March 29, 2017 1:32:42 PM
> > To: users@qpid.apache.org
> > Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
> >
> > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> > evaluation.
> >
> > Build Artifacts:
> >
> >      https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
> >
> > New Features:
> >
> >      DISPATCH-103 - Websocket Listeners
> >      DISPATCH-195 - Add support for transactional messages in the Router
> >      DISPATCH-441 - Support password environment variable in qdrouter
> >      config
> >      DISPATCH-467 - Terminus renaming for autoLinks
> >      DISPATCH-529 - Address annotation for Multi-Tenancy
> >      DISPATCH-726 - Connection Property for Failover Servers
> >
> > Improvements:
> >
> >      DISPATCH-113 - expose NodeTracker::last_topology_change in management
> >      DISPATCH-542 - Popup text for clients should indicate if the client
> > is a sender or receiver
> >      DISPATCH-543 - Initial load of topology page fetches too much
> > information
> >      DISPATCH-544 - Add ability to hide the info panel on the left of
> > the topology page
> >      DISPATCH-552 - Allow only one tree node to be expanded if there is
> > a large number of routers
> >      DISPATCH-553 - Add statistic counter to the "log" entity to count
> > log events per severity
> >      DISPATCH-559 - qdstat - Request only the columns that will be used
> > in the display
> >      DISPATCH-561 - Create python program that returns fake management data
> >      DISPATCH-568 - Iterator module cleanup
> >      DISPATCH-570 - Add some counts to qdstat -g
> >      DISPATCH-572 - Adding log info with proton transport id and related
> > remote IP/port
> >      DISPATCH-576 - Use new log entity statistic counter in console
> >      DISPATCH-578 - Dispatch trace logging forces all proton tracing on
> >      DISPATCH-579 - Expose software version via management
> >      DISPATCH-592 - Attempt to auto-login to the host:port that served
> > the web page
> >      DISPATCH-597 - Log enhancements
> >      DISPATCH-600 - Support secure websockets
> >      DISPATCH-602 - Add a favicon to the stand-alone router site
> >      DISPATCH-606 - Default session window is too small, causing
> > performance bottlenecks
> >      DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> > systems
> >      DISPATCH-629 - Add a protocol-version to the inter-router protocol
> > to enable backward compatibility
> >      DISPATCH-641 - Make containerId attribute work with clients
> >
> > Bugs Fixed:
> >
> >      DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
> >      DISPATCH-216 - system_tests_protocol_family fails on systems with
> > no IPv6
> >      DISPATCH-296 - segfault on router startup
> >      DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
> >      DISPATCH-314 - If a router has a normal listener, show it in a
> > different color on the topology page
> >      DISPATCH-324 - Improve initial layout of topology node
> >      DISPATCH-344 - memory growth after repeated calls from qdstat -m
> >      DISPATCH-352 - Crash with empty configuration file
> >      DISPATCH-355 - query fails with what seems to be the error of a
> > previous command
> >      DISPATCH-357 - Address field is empty for link routed links in the
> > qdstat "links" output
> >      DISPATCH-433 - Navigating to console from bookmark displays empty
> > page with just toolbars
> >      DISPATCH-451 - [AMQP] Hard coded session capacity should be
> > configurable
> >      DISPATCH-503 - [display_name] successful test runs  have non-ascii
> > characters in router log
> >      DISPATCH-504 - [display_name] successful test runs have invalid
> > message errors  in router log
> >      DISPATCH-506 - Detach with no "error" sent by router on client TCP
> > connection dropped
> >      DISPATCH-516 - Core dump when displayname IO adapter receives
> > message with no reply-to
> >      DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> > 0.7.0
> >      DISPATCH-527 - The $displayname address is currently available. It
> > should not be available to external users
> >      DISPATCH-530 - Cannot connect using Firefox 48+
> >      DISPATCH-534 - Node selection and location is lost when the
> > topology changes
> >      DISPATCH-536 - Circular buffer overflow errors occur when there are
> > a large number of routers
> >      DISPATCH-538 - Highlighted path between routers sometimes doesn't
> > unhighlight
> >      DISPATCH-540 - Clients with both in and out links are rendered in
> > yellow
> >      DISPATCH-541 - Highlighted path between routers contains black arrows
> >      DISPATCH-546 - Crosssection popup position is incorrect
> >      DISPATCH-547 - Stand-alone version can't download generated config
> > file for new nodes
> >      DISPATCH-554 - Topology nodes and links are too far apart when
> > there are a large number of routers
> >      DISPATCH-556 - qdstat fails at high scale
> >      DISPATCH-557 - High connection rates cause problems in the Python
> > management agent
> >      DISPATCH-560 - [console] Only use the color red to indicate a
> > failure/issue.
> >      DISPATCH-563 - Topology graph flashes and redraws a few seconds
> > after it is 1st drawn
> >      DISPATCH-564 - Error when switching routers on Entities page
> >      DISPATCH-565 - Error fetching log on Entities page
> >      DISPATCH-566 - Message annotations are not propagated to brokers on
> > a linkRoute
> >      DISPATCH-567 - Slight but persistent memory leak when running java
> > messenger producer and consumer
> >      DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> > enum values.
> >      DISPATCH-573 - Memory leaks on shutdown
> >      DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
> >      DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
> >      DISPATCH-581 - detach with closed=false propagated as closed=true
> > on link route
> >      DISPATCH-582 - Memory Leak with reactor client
> >      DISPATCH-583 - Random segmentation fault
> >      DISPATCH-585 - Firefox dropdown and buttons on list page have
> > incorrect padding
> >      DISPATCH-586 - Dispatch crash on running c sender and receiver
> >      DISPATCH-587 - Provide feedback when loading log entries
> >      DISPATCH-588 - Schema is not loaded if auto-login is enabled
> >      DISPATCH-589 - Missing links on topology page
> >      DISPATCH-594 - Log file over-written every time the router is
> >      restarted
> >      DISPATCH-595 - dispositions propagated after link detach on link route
> >      DISPATCH-596 - error is lost from rejected state in relayed
> >      disposition
> >      DISPATCH-598 - Router crash when calling sender and session close
> > methods in onLinkFLow()
> >      DISPATCH-599 - Link routing : messages is not transferred if sender
> > detach link immediately
> >      DISPATCH-601 - Valgrind errors in dispatch tests
> >      DISPATCH-603 - address resource leak
> >      DISPATCH-604 - Management - Link connection-id does not match
> > identities of connections
> >      DISPATCH-605 - Memory Leak with multple sender/receivers in one
> >      session
> >      DISPATCH-607 - Handle empty response from GET-MGMT-NODES
> >      DISPATCH-608 - Links not cleaned up when a close is sent without
> > being preceeded by a detach and end
> >      DISPATCH-609 - Name attribute is duplicated in QUERY response
> >      DISPATCH-610 - crash in qdr_link_cleanup_CT
> >      DISPATCH-611 - Router core dump with old config file
> >      DISPATCH-612 - Add support for GCC equivalent compiler options
> >      DISPATCH-613 - Remove semi-colon not needed after function definition
> >      DISPATCH-614 - strerror_r on Solaris does not return char*
> >      DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
> >      DISPATCH-616 - Arithmetic operations not allowed on void * pointer
> >      DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> > _POSIX_HOST_NAME_MAX is defined instead
> >      DISPATCH-618 - Revert eventfd on Solaris
> >      DISPATCH-619 - Use memalign instead of posix_memalign which is not
> > defined on Solaris
> >      DISPATCH-620 - no-strict-aliasing is only supported with GCC
> >      DISPATCH-621 - Add missing string.h include for Solaris compiler
> >      DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> > error to avoid undefined symbol on Solaris
> >      DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> > return statement) detected on Solaris
> >      DISPATCH-624 - Add Atomic operations support on Solaris
> >      DISPATCH-626 - Add hints for getaddrinfo on Solaris
> >      DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> > linkRoute overwrites connection handle
> >      DISPATCH-631 - Tests should be made conditional to skip tests for
> > SASL features that are not available
> >      DISPATCH-633 - Creating connectors and addresses returns success
> > codes of two different types.
> >      DISPATCH-634 - Dynamic Targets are unsupported
> >      DISPATCH-635 - The Ubuntu CI tests that involve two routers are
> >      failing
> >      DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> > required; however, cmake complains with 0.14
> >      DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> > fail when cyrus-sasl-plain is not installed
> >      DISPATCH-640 - containerId field conflics with the connector name
> >      DISPATCH-642 - Fix recognition of Artemis broker on topology page
> >      DISPATCH-643 - Duplicate log messages show up on normal AMQP close
> >      DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> > pipe issue in Daemon mode
> >      DISPATCH-646 - Link route tests which test the drain feature fail
> > intermittently
> >      DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> > master
> >      DISPATCH-727 - qdmanage identity reporting and lookup are broken
> >      DISPATCH-728 - crash on shutdown with connector
> >      DISPATCH-729 - password-file option doesn't work correctly
> >      DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
> >      DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> > but is missing from log schema
> >      DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> > intermittently
> >
> > ---------------------------------------------------------------------
> > 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


Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Posted by Adel Boutros <Ad...@live.com>.
I rechecked quickly and I have different behaviors on different OSes.


* Linux :

router_policy_test and system_tests_protocol_family failing as stated previously


*Solaris:

Only router_policy_test  is failing.

For system_tests_protocol_family, I have the message "Skipping test..IPV6 not enabled"


We have some other test failures on Solaris and Linux but we will need to debug them and we won't have time at the moment for them. I can send you a report with the failures if you wish.


Regards,

Adel

________________________________
From: Ted Ross <tr...@redhat.com>
Sent: Thursday, March 30, 2017 2:48:10 PM
To: users@qpid.apache.org
Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Adel,

The commits associated with that Jira and PR #140 are included in this
release candidate.  We'll need to investigate whether it regressed again
or if the commit didn't fix the problem.

-Ted

On 03/30/2017 11:30 AM, Adel Boutros wrote:
> Hello Ted,
>
>
> I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it doens't seem to be the case. Ganesh was working on fixing those.
>
> Do you confirm they are not included? (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571)
>
>
> I launched the CI on the release candidate and got the same IPv6 failures as before
>
>
> The following tests FAILED with ipv6 errors:
> 12 - router_policy_test (Failed)
> 19 - system_tests_protocol_family (Failed)
>
>
>
> 12: Test command: /python278/bin/python "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest" "-v" "router_policy_test"
> 12: Test timeout computed to be: 1500
> 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is invalid: Policy vhost \'photoserver\' user group \'superuser\' option \'remoteHosts\' connectionOption \'::1\' failed to translate: \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct: \\\'::1\\\' did not resolve to one of the supported address family"\\\'\'\'.'
>
>
> 19: error: [Errno 97] Address family not supported by protocol
>
>
> Regards,
>
> Adel
>
> ________________________________
> From: Ted Ross <tr...@redhat.com>
> Sent: Wednesday, March 29, 2017 1:32:42 PM
> To: users@qpid.apache.org
> Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
> The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> evaluation.
>
> Build Artifacts:
>
>      https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
>
> New Features:
>
>      DISPATCH-103 - Websocket Listeners
>      DISPATCH-195 - Add support for transactional messages in the Router
>      DISPATCH-441 - Support password environment variable in qdrouter config
>      DISPATCH-467 - Terminus renaming for autoLinks
>      DISPATCH-529 - Address annotation for Multi-Tenancy
>      DISPATCH-726 - Connection Property for Failover Servers
>
> Improvements:
>
>      DISPATCH-113 - expose NodeTracker::last_topology_change in management
>      DISPATCH-542 - Popup text for clients should indicate if the client
> is a sender or receiver
>      DISPATCH-543 - Initial load of topology page fetches too much
> information
>      DISPATCH-544 - Add ability to hide the info panel on the left of
> the topology page
>      DISPATCH-552 - Allow only one tree node to be expanded if there is
> a large number of routers
>      DISPATCH-553 - Add statistic counter to the "log" entity to count
> log events per severity
>      DISPATCH-559 - qdstat - Request only the columns that will be used
> in the display
>      DISPATCH-561 - Create python program that returns fake management data
>      DISPATCH-568 - Iterator module cleanup
>      DISPATCH-570 - Add some counts to qdstat -g
>      DISPATCH-572 - Adding log info with proton transport id and related
> remote IP/port
>      DISPATCH-576 - Use new log entity statistic counter in console
>      DISPATCH-578 - Dispatch trace logging forces all proton tracing on
>      DISPATCH-579 - Expose software version via management
>      DISPATCH-592 - Attempt to auto-login to the host:port that served
> the web page
>      DISPATCH-597 - Log enhancements
>      DISPATCH-600 - Support secure websockets
>      DISPATCH-602 - Add a favicon to the stand-alone router site
>      DISPATCH-606 - Default session window is too small, causing
> performance bottlenecks
>      DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> systems
>      DISPATCH-629 - Add a protocol-version to the inter-router protocol
> to enable backward compatibility
>      DISPATCH-641 - Make containerId attribute work with clients
>
> Bugs Fixed:
>
>      DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
>      DISPATCH-216 - system_tests_protocol_family fails on systems with
> no IPv6
>      DISPATCH-296 - segfault on router startup
>      DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
>      DISPATCH-314 - If a router has a normal listener, show it in a
> different color on the topology page
>      DISPATCH-324 - Improve initial layout of topology node
>      DISPATCH-344 - memory growth after repeated calls from qdstat -m
>      DISPATCH-352 - Crash with empty configuration file
>      DISPATCH-355 - query fails with what seems to be the error of a
> previous command
>      DISPATCH-357 - Address field is empty for link routed links in the
> qdstat "links" output
>      DISPATCH-433 - Navigating to console from bookmark displays empty
> page with just toolbars
>      DISPATCH-451 - [AMQP] Hard coded session capacity should be
> configurable
>      DISPATCH-503 - [display_name] successful test runs  have non-ascii
> characters in router log
>      DISPATCH-504 - [display_name] successful test runs have invalid
> message errors  in router log
>      DISPATCH-506 - Detach with no "error" sent by router on client TCP
> connection dropped
>      DISPATCH-516 - Core dump when displayname IO adapter receives
> message with no reply-to
>      DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> 0.7.0
>      DISPATCH-527 - The $displayname address is currently available. It
> should not be available to external users
>      DISPATCH-530 - Cannot connect using Firefox 48+
>      DISPATCH-534 - Node selection and location is lost when the
> topology changes
>      DISPATCH-536 - Circular buffer overflow errors occur when there are
> a large number of routers
>      DISPATCH-538 - Highlighted path between routers sometimes doesn't
> unhighlight
>      DISPATCH-540 - Clients with both in and out links are rendered in
> yellow
>      DISPATCH-541 - Highlighted path between routers contains black arrows
>      DISPATCH-546 - Crosssection popup position is incorrect
>      DISPATCH-547 - Stand-alone version can't download generated config
> file for new nodes
>      DISPATCH-554 - Topology nodes and links are too far apart when
> there are a large number of routers
>      DISPATCH-556 - qdstat fails at high scale
>      DISPATCH-557 - High connection rates cause problems in the Python
> management agent
>      DISPATCH-560 - [console] Only use the color red to indicate a
> failure/issue.
>      DISPATCH-563 - Topology graph flashes and redraws a few seconds
> after it is 1st drawn
>      DISPATCH-564 - Error when switching routers on Entities page
>      DISPATCH-565 - Error fetching log on Entities page
>      DISPATCH-566 - Message annotations are not propagated to brokers on
> a linkRoute
>      DISPATCH-567 - Slight but persistent memory leak when running java
> messenger producer and consumer
>      DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> enum values.
>      DISPATCH-573 - Memory leaks on shutdown
>      DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
>      DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
>      DISPATCH-581 - detach with closed=false propagated as closed=true
> on link route
>      DISPATCH-582 - Memory Leak with reactor client
>      DISPATCH-583 - Random segmentation fault
>      DISPATCH-585 - Firefox dropdown and buttons on list page have
> incorrect padding
>      DISPATCH-586 - Dispatch crash on running c sender and receiver
>      DISPATCH-587 - Provide feedback when loading log entries
>      DISPATCH-588 - Schema is not loaded if auto-login is enabled
>      DISPATCH-589 - Missing links on topology page
>      DISPATCH-594 - Log file over-written every time the router is restarted
>      DISPATCH-595 - dispositions propagated after link detach on link route
>      DISPATCH-596 - error is lost from rejected state in relayed disposition
>      DISPATCH-598 - Router crash when calling sender and session close
> methods in onLinkFLow()
>      DISPATCH-599 - Link routing : messages is not transferred if sender
> detach link immediately
>      DISPATCH-601 - Valgrind errors in dispatch tests
>      DISPATCH-603 - address resource leak
>      DISPATCH-604 - Management - Link connection-id does not match
> identities of connections
>      DISPATCH-605 - Memory Leak with multple sender/receivers in one session
>      DISPATCH-607 - Handle empty response from GET-MGMT-NODES
>      DISPATCH-608 - Links not cleaned up when a close is sent without
> being preceeded by a detach and end
>      DISPATCH-609 - Name attribute is duplicated in QUERY response
>      DISPATCH-610 - crash in qdr_link_cleanup_CT
>      DISPATCH-611 - Router core dump with old config file
>      DISPATCH-612 - Add support for GCC equivalent compiler options
>      DISPATCH-613 - Remove semi-colon not needed after function definition
>      DISPATCH-614 - strerror_r on Solaris does not return char*
>      DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
>      DISPATCH-616 - Arithmetic operations not allowed on void * pointer
>      DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> _POSIX_HOST_NAME_MAX is defined instead
>      DISPATCH-618 - Revert eventfd on Solaris
>      DISPATCH-619 - Use memalign instead of posix_memalign which is not
> defined on Solaris
>      DISPATCH-620 - no-strict-aliasing is only supported with GCC
>      DISPATCH-621 - Add missing string.h include for Solaris compiler
>      DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> error to avoid undefined symbol on Solaris
>      DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> return statement) detected on Solaris
>      DISPATCH-624 - Add Atomic operations support on Solaris
>      DISPATCH-626 - Add hints for getaddrinfo on Solaris
>      DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> linkRoute overwrites connection handle
>      DISPATCH-631 - Tests should be made conditional to skip tests for
> SASL features that are not available
>      DISPATCH-633 - Creating connectors and addresses returns success
> codes of two different types.
>      DISPATCH-634 - Dynamic Targets are unsupported
>      DISPATCH-635 - The Ubuntu CI tests that involve two routers are failing
>      DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> required; however, cmake complains with 0.14
>      DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> fail when cyrus-sasl-plain is not installed
>      DISPATCH-640 - containerId field conflics with the connector name
>      DISPATCH-642 - Fix recognition of Artemis broker on topology page
>      DISPATCH-643 - Duplicate log messages show up on normal AMQP close
>      DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> pipe issue in Daemon mode
>      DISPATCH-646 - Link route tests which test the drain feature fail
> intermittently
>      DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> master
>      DISPATCH-727 - qdmanage identity reporting and lookup are broken
>      DISPATCH-728 - crash on shutdown with connector
>      DISPATCH-729 - password-file option doesn't work correctly
>      DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
>      DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> but is missing from log schema
>      DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> intermittently
>
> ---------------------------------------------------------------------
> 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.8.0 Release Candidate 1

Posted by Ted Ross <tr...@redhat.com>.
Adel,

The commits associated with that Jira and PR #140 are included in this 
release candidate.  We'll need to investigate whether it regressed again 
or if the commit didn't fix the problem.

-Ted

On 03/30/2017 11:30 AM, Adel Boutros wrote:
> Hello Ted,
>
>
> I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it doens't seem to be the case. Ganesh was working on fixing those.
>
> Do you confirm they are not included? (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571)
>
>
> I launched the CI on the release candidate and got the same IPv6 failures as before
>
>
> The following tests FAILED with ipv6 errors:
> 12 - router_policy_test (Failed)
> 19 - system_tests_protocol_family (Failed)
>
>
>
> 12: Test command: /python278/bin/python "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest" "-v" "router_policy_test"
> 12: Test timeout computed to be: 1500
> 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is invalid: Policy vhost \'photoserver\' user group \'superuser\' option \'remoteHosts\' connectionOption \'::1\' failed to translate: \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct: \\\'::1\\\' did not resolve to one of the supported address family"\\\'\'\'.'
>
>
> 19: error: [Errno 97] Address family not supported by protocol
>
>
> Regards,
>
> Adel
>
> ________________________________
> From: Ted Ross <tr...@redhat.com>
> Sent: Wednesday, March 29, 2017 1:32:42 PM
> To: users@qpid.apache.org
> Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1
>
> The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> evaluation.
>
> Build Artifacts:
>
>      https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
>
> New Features:
>
>      DISPATCH-103 - Websocket Listeners
>      DISPATCH-195 - Add support for transactional messages in the Router
>      DISPATCH-441 - Support password environment variable in qdrouter config
>      DISPATCH-467 - Terminus renaming for autoLinks
>      DISPATCH-529 - Address annotation for Multi-Tenancy
>      DISPATCH-726 - Connection Property for Failover Servers
>
> Improvements:
>
>      DISPATCH-113 - expose NodeTracker::last_topology_change in management
>      DISPATCH-542 - Popup text for clients should indicate if the client
> is a sender or receiver
>      DISPATCH-543 - Initial load of topology page fetches too much
> information
>      DISPATCH-544 - Add ability to hide the info panel on the left of
> the topology page
>      DISPATCH-552 - Allow only one tree node to be expanded if there is
> a large number of routers
>      DISPATCH-553 - Add statistic counter to the "log" entity to count
> log events per severity
>      DISPATCH-559 - qdstat - Request only the columns that will be used
> in the display
>      DISPATCH-561 - Create python program that returns fake management data
>      DISPATCH-568 - Iterator module cleanup
>      DISPATCH-570 - Add some counts to qdstat -g
>      DISPATCH-572 - Adding log info with proton transport id and related
> remote IP/port
>      DISPATCH-576 - Use new log entity statistic counter in console
>      DISPATCH-578 - Dispatch trace logging forces all proton tracing on
>      DISPATCH-579 - Expose software version via management
>      DISPATCH-592 - Attempt to auto-login to the host:port that served
> the web page
>      DISPATCH-597 - Log enhancements
>      DISPATCH-600 - Support secure websockets
>      DISPATCH-602 - Add a favicon to the stand-alone router site
>      DISPATCH-606 - Default session window is too small, causing
> performance bottlenecks
>      DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> systems
>      DISPATCH-629 - Add a protocol-version to the inter-router protocol
> to enable backward compatibility
>      DISPATCH-641 - Make containerId attribute work with clients
>
> Bugs Fixed:
>
>      DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
>      DISPATCH-216 - system_tests_protocol_family fails on systems with
> no IPv6
>      DISPATCH-296 - segfault on router startup
>      DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
>      DISPATCH-314 - If a router has a normal listener, show it in a
> different color on the topology page
>      DISPATCH-324 - Improve initial layout of topology node
>      DISPATCH-344 - memory growth after repeated calls from qdstat -m
>      DISPATCH-352 - Crash with empty configuration file
>      DISPATCH-355 - query fails with what seems to be the error of a
> previous command
>      DISPATCH-357 - Address field is empty for link routed links in the
> qdstat "links" output
>      DISPATCH-433 - Navigating to console from bookmark displays empty
> page with just toolbars
>      DISPATCH-451 - [AMQP] Hard coded session capacity should be
> configurable
>      DISPATCH-503 - [display_name] successful test runs  have non-ascii
> characters in router log
>      DISPATCH-504 - [display_name] successful test runs have invalid
> message errors  in router log
>      DISPATCH-506 - Detach with no "error" sent by router on client TCP
> connection dropped
>      DISPATCH-516 - Core dump when displayname IO adapter receives
> message with no reply-to
>      DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> 0.7.0
>      DISPATCH-527 - The $displayname address is currently available. It
> should not be available to external users
>      DISPATCH-530 - Cannot connect using Firefox 48+
>      DISPATCH-534 - Node selection and location is lost when the
> topology changes
>      DISPATCH-536 - Circular buffer overflow errors occur when there are
> a large number of routers
>      DISPATCH-538 - Highlighted path between routers sometimes doesn't
> unhighlight
>      DISPATCH-540 - Clients with both in and out links are rendered in
> yellow
>      DISPATCH-541 - Highlighted path between routers contains black arrows
>      DISPATCH-546 - Crosssection popup position is incorrect
>      DISPATCH-547 - Stand-alone version can't download generated config
> file for new nodes
>      DISPATCH-554 - Topology nodes and links are too far apart when
> there are a large number of routers
>      DISPATCH-556 - qdstat fails at high scale
>      DISPATCH-557 - High connection rates cause problems in the Python
> management agent
>      DISPATCH-560 - [console] Only use the color red to indicate a
> failure/issue.
>      DISPATCH-563 - Topology graph flashes and redraws a few seconds
> after it is 1st drawn
>      DISPATCH-564 - Error when switching routers on Entities page
>      DISPATCH-565 - Error fetching log on Entities page
>      DISPATCH-566 - Message annotations are not propagated to brokers on
> a linkRoute
>      DISPATCH-567 - Slight but persistent memory leak when running java
> messenger producer and consumer
>      DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> enum values.
>      DISPATCH-573 - Memory leaks on shutdown
>      DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
>      DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
>      DISPATCH-581 - detach with closed=false propagated as closed=true
> on link route
>      DISPATCH-582 - Memory Leak with reactor client
>      DISPATCH-583 - Random segmentation fault
>      DISPATCH-585 - Firefox dropdown and buttons on list page have
> incorrect padding
>      DISPATCH-586 - Dispatch crash on running c sender and receiver
>      DISPATCH-587 - Provide feedback when loading log entries
>      DISPATCH-588 - Schema is not loaded if auto-login is enabled
>      DISPATCH-589 - Missing links on topology page
>      DISPATCH-594 - Log file over-written every time the router is restarted
>      DISPATCH-595 - dispositions propagated after link detach on link route
>      DISPATCH-596 - error is lost from rejected state in relayed disposition
>      DISPATCH-598 - Router crash when calling sender and session close
> methods in onLinkFLow()
>      DISPATCH-599 - Link routing : messages is not transferred if sender
> detach link immediately
>      DISPATCH-601 - Valgrind errors in dispatch tests
>      DISPATCH-603 - address resource leak
>      DISPATCH-604 - Management - Link connection-id does not match
> identities of connections
>      DISPATCH-605 - Memory Leak with multple sender/receivers in one session
>      DISPATCH-607 - Handle empty response from GET-MGMT-NODES
>      DISPATCH-608 - Links not cleaned up when a close is sent without
> being preceeded by a detach and end
>      DISPATCH-609 - Name attribute is duplicated in QUERY response
>      DISPATCH-610 - crash in qdr_link_cleanup_CT
>      DISPATCH-611 - Router core dump with old config file
>      DISPATCH-612 - Add support for GCC equivalent compiler options
>      DISPATCH-613 - Remove semi-colon not needed after function definition
>      DISPATCH-614 - strerror_r on Solaris does not return char*
>      DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
>      DISPATCH-616 - Arithmetic operations not allowed on void * pointer
>      DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> _POSIX_HOST_NAME_MAX is defined instead
>      DISPATCH-618 - Revert eventfd on Solaris
>      DISPATCH-619 - Use memalign instead of posix_memalign which is not
> defined on Solaris
>      DISPATCH-620 - no-strict-aliasing is only supported with GCC
>      DISPATCH-621 - Add missing string.h include for Solaris compiler
>      DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> error to avoid undefined symbol on Solaris
>      DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> return statement) detected on Solaris
>      DISPATCH-624 - Add Atomic operations support on Solaris
>      DISPATCH-626 - Add hints for getaddrinfo on Solaris
>      DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> linkRoute overwrites connection handle
>      DISPATCH-631 - Tests should be made conditional to skip tests for
> SASL features that are not available
>      DISPATCH-633 - Creating connectors and addresses returns success
> codes of two different types.
>      DISPATCH-634 - Dynamic Targets are unsupported
>      DISPATCH-635 - The Ubuntu CI tests that involve two routers are failing
>      DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> required; however, cmake complains with 0.14
>      DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> fail when cyrus-sasl-plain is not installed
>      DISPATCH-640 - containerId field conflics with the connector name
>      DISPATCH-642 - Fix recognition of Artemis broker on topology page
>      DISPATCH-643 - Duplicate log messages show up on normal AMQP close
>      DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> pipe issue in Daemon mode
>      DISPATCH-646 - Link route tests which test the drain feature fail
> intermittently
>      DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> master
>      DISPATCH-727 - qdmanage identity reporting and lookup are broken
>      DISPATCH-728 - crash on shutdown with connector
>      DISPATCH-729 - password-file option doesn't work correctly
>      DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
>      DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> but is missing from log schema
>      DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> intermittently
>
> ---------------------------------------------------------------------
> 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.8.0 Release Candidate 1

Posted by Adel Boutros <Ad...@live.com>.
Hello Ted,


I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it doens't seem to be the case. Ganesh was working on fixing those.

Do you confirm they are not included? (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571)


I launched the CI on the release candidate and got the same IPv6 failures as before


The following tests FAILED with ipv6 errors:
12 - router_policy_test (Failed)
19 - system_tests_protocol_family (Failed)



12: Test command: /python278/bin/python "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest" "-v" "router_policy_test"
12: Test timeout computed to be: 1500
12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is invalid: Policy vhost \'photoserver\' user group \'superuser\' option \'remoteHosts\' connectionOption \'::1\' failed to translate: \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct: \\\'::1\\\' did not resolve to one of the supported address family"\\\'\'\'.'


19: error: [Errno 97] Address family not supported by protocol


Regards,

Adel

________________________________
From: Ted Ross <tr...@redhat.com>
Sent: Wednesday, March 29, 2017 1:32:42 PM
To: users@qpid.apache.org
Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1

The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
evaluation.

Build Artifacts:

     https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/

New Features:

     DISPATCH-103 - Websocket Listeners
     DISPATCH-195 - Add support for transactional messages in the Router
     DISPATCH-441 - Support password environment variable in qdrouter config
     DISPATCH-467 - Terminus renaming for autoLinks
     DISPATCH-529 - Address annotation for Multi-Tenancy
     DISPATCH-726 - Connection Property for Failover Servers

Improvements:

     DISPATCH-113 - expose NodeTracker::last_topology_change in management
     DISPATCH-542 - Popup text for clients should indicate if the client
is a sender or receiver
     DISPATCH-543 - Initial load of topology page fetches too much
information
     DISPATCH-544 - Add ability to hide the info panel on the left of
the topology page
     DISPATCH-552 - Allow only one tree node to be expanded if there is
a large number of routers
     DISPATCH-553 - Add statistic counter to the "log" entity to count
log events per severity
     DISPATCH-559 - qdstat - Request only the columns that will be used
in the display
     DISPATCH-561 - Create python program that returns fake management data
     DISPATCH-568 - Iterator module cleanup
     DISPATCH-570 - Add some counts to qdstat -g
     DISPATCH-572 - Adding log info with proton transport id and related
remote IP/port
     DISPATCH-576 - Use new log entity statistic counter in console
     DISPATCH-578 - Dispatch trace logging forces all proton tracing on
     DISPATCH-579 - Expose software version via management
     DISPATCH-592 - Attempt to auto-login to the host:port that served
the web page
     DISPATCH-597 - Log enhancements
     DISPATCH-600 - Support secure websockets
     DISPATCH-602 - Add a favicon to the stand-alone router site
     DISPATCH-606 - Default session window is too small, causing
performance bottlenecks
     DISPATCH-627 - BatchedSettlement test fails with timeout on slower
systems
     DISPATCH-629 - Add a protocol-version to the inter-router protocol
to enable backward compatibility
     DISPATCH-641 - Make containerId attribute work with clients

Bugs Fixed:

     DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
     DISPATCH-216 - system_tests_protocol_family fails on systems with
no IPv6
     DISPATCH-296 - segfault on router startup
     DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
     DISPATCH-314 - If a router has a normal listener, show it in a
different color on the topology page
     DISPATCH-324 - Improve initial layout of topology node
     DISPATCH-344 - memory growth after repeated calls from qdstat -m
     DISPATCH-352 - Crash with empty configuration file
     DISPATCH-355 - query fails with what seems to be the error of a
previous command
     DISPATCH-357 - Address field is empty for link routed links in the
qdstat "links" output
     DISPATCH-433 - Navigating to console from bookmark displays empty
page with just toolbars
     DISPATCH-451 - [AMQP] Hard coded session capacity should be
configurable
     DISPATCH-503 - [display_name] successful test runs  have non-ascii
characters in router log
     DISPATCH-504 - [display_name] successful test runs have invalid
message errors  in router log
     DISPATCH-506 - Detach with no "error" sent by router on client TCP
connection dropped
     DISPATCH-516 - Core dump when displayname IO adapter receives
message with no reply-to
     DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
0.7.0
     DISPATCH-527 - The $displayname address is currently available. It
should not be available to external users
     DISPATCH-530 - Cannot connect using Firefox 48+
     DISPATCH-534 - Node selection and location is lost when the
topology changes
     DISPATCH-536 - Circular buffer overflow errors occur when there are
a large number of routers
     DISPATCH-538 - Highlighted path between routers sometimes doesn't
unhighlight
     DISPATCH-540 - Clients with both in and out links are rendered in
yellow
     DISPATCH-541 - Highlighted path between routers contains black arrows
     DISPATCH-546 - Crosssection popup position is incorrect
     DISPATCH-547 - Stand-alone version can't download generated config
file for new nodes
     DISPATCH-554 - Topology nodes and links are too far apart when
there are a large number of routers
     DISPATCH-556 - qdstat fails at high scale
     DISPATCH-557 - High connection rates cause problems in the Python
management agent
     DISPATCH-560 - [console] Only use the color red to indicate a
failure/issue.
     DISPATCH-563 - Topology graph flashes and redraws a few seconds
after it is 1st drawn
     DISPATCH-564 - Error when switching routers on Entities page
     DISPATCH-565 - Error fetching log on Entities page
     DISPATCH-566 - Message annotations are not propagated to brokers on
a linkRoute
     DISPATCH-567 - Slight but persistent memory leak when running java
messenger producer and consumer
     DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
enum values.
     DISPATCH-573 - Memory leaks on shutdown
     DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
     DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
     DISPATCH-581 - detach with closed=false propagated as closed=true
on link route
     DISPATCH-582 - Memory Leak with reactor client
     DISPATCH-583 - Random segmentation fault
     DISPATCH-585 - Firefox dropdown and buttons on list page have
incorrect padding
     DISPATCH-586 - Dispatch crash on running c sender and receiver
     DISPATCH-587 - Provide feedback when loading log entries
     DISPATCH-588 - Schema is not loaded if auto-login is enabled
     DISPATCH-589 - Missing links on topology page
     DISPATCH-594 - Log file over-written every time the router is restarted
     DISPATCH-595 - dispositions propagated after link detach on link route
     DISPATCH-596 - error is lost from rejected state in relayed disposition
     DISPATCH-598 - Router crash when calling sender and session close
methods in onLinkFLow()
     DISPATCH-599 - Link routing : messages is not transferred if sender
detach link immediately
     DISPATCH-601 - Valgrind errors in dispatch tests
     DISPATCH-603 - address resource leak
     DISPATCH-604 - Management - Link connection-id does not match
identities of connections
     DISPATCH-605 - Memory Leak with multple sender/receivers in one session
     DISPATCH-607 - Handle empty response from GET-MGMT-NODES
     DISPATCH-608 - Links not cleaned up when a close is sent without
being preceeded by a detach and end
     DISPATCH-609 - Name attribute is duplicated in QUERY response
     DISPATCH-610 - crash in qdr_link_cleanup_CT
     DISPATCH-611 - Router core dump with old config file
     DISPATCH-612 - Add support for GCC equivalent compiler options
     DISPATCH-613 - Remove semi-colon not needed after function definition
     DISPATCH-614 - strerror_r on Solaris does not return char*
     DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
     DISPATCH-616 - Arithmetic operations not allowed on void * pointer
     DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
_POSIX_HOST_NAME_MAX is defined instead
     DISPATCH-618 - Revert eventfd on Solaris
     DISPATCH-619 - Use memalign instead of posix_memalign which is not
defined on Solaris
     DISPATCH-620 - no-strict-aliasing is only supported with GCC
     DISPATCH-621 - Add missing string.h include for Solaris compiler
     DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
error to avoid undefined symbol on Solaris
     DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
return statement) detected on Solaris
     DISPATCH-624 - Add Atomic operations support on Solaris
     DISPATCH-626 - Add hints for getaddrinfo on Solaris
     DISPATCH-628 - [PATCH] Multiple connections per autoLink and
linkRoute overwrites connection handle
     DISPATCH-631 - Tests should be made conditional to skip tests for
SASL features that are not available
     DISPATCH-633 - Creating connectors and addresses returns success
codes of two different types.
     DISPATCH-634 - Dynamic Targets are unsupported
     DISPATCH-635 - The Ubuntu CI tests that involve two routers are failing
     DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
required; however, cmake complains with 0.14
     DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
fail when cyrus-sasl-plain is not installed
     DISPATCH-640 - containerId field conflics with the connector name
     DISPATCH-642 - Fix recognition of Artemis broker on topology page
     DISPATCH-643 - Duplicate log messages show up on normal AMQP close
     DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
pipe issue in Daemon mode
     DISPATCH-646 - Link route tests which test the drain feature fail
intermittently
     DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
master
     DISPATCH-727 - qdmanage identity reporting and lookup are broken
     DISPATCH-728 - crash on shutdown with connector
     DISPATCH-729 - password-file option doesn't work correctly
     DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
     DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
but is missing from log schema
     DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
intermittently

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Posted by Ganesh Murthy <gm...@redhat.com>.
I think I have fixed all the license problems that Robbie pointed out. The code is now checked into master

I added a file, .rat-excludes, to the base folder and it includes the js files whose licenses I have explicitly copied into the main LICENSE file. 

----- Original Message -----
> From: "Robbie Gemmell" <ro...@gmail.com>
> To: users@qpid.apache.org
> Sent: Tuesday, April 4, 2017 6:42:44 AM
> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
> 
> I gave the router a try out, building against Proton 0.17.0. The build
> completed fine, all tests passed, and I ran the Qpid JMS HelloWorld
> against the built router.
> 
> The signature and checksums verified fine, though the .sha512 checksum
> file should be renamed with .sha extension for consistency with the
> release policy and the other components that moved to SHA512
> checksums.
> 
> Giving the release archive a look over, I noticed various license
> related issues with the content:
> - One file, tooltipsy.min.js, indicates it is GPLv2, which is
> considered Category X
> (https://www.apache.org/legal/resolved.html#category-x) meaning it
> can't be included and needs removed prior to release.

tooltipsy.min.js has been removed and is no longer in the source tree (thanks Ernie)

> - Several other files need called out in the LICENCE file with detail
> of their licence terms since they aren't ALv2.
> - There are a number of files that lack a licence header that should
> have one. See the RAT output summary below, though note this includes

I have added license header to several files and checked them into master branch.

> all the non-ALv2 files since we dont have an excludes list to reduce
> the noise where actually appropriate. For the mass of JSON files, I
> guess it depends how they are used given JSON doesn't strictly support
> comments (though many impls do), though 'test data that would cause
> failure with a header' is an allowed exception:
> https://www.apache.org/legal/src-headers.html#faq-exceptions. If it

The JSON files cannot have the license header and they confirm to https://www.apache.org/legal/src-headers.html#faq-exceptions
I have added a file to the base folder called .rat-excludes and I have added the json files to it. The RAT tool when run in the future
must use this .rat-excludes file. This file also includes several third party javascript files whose licenses I have now copied into the main
LICENSE file. Robbie, please take a look at the .rat-excludes and the LICENSE file and let me know if there is something I added that 
should not be there.

When I ran the RAT tool on the latest master using the .rat-excludes, it passed.

> works, we should probably add it if only because it greatly cuts down
> the noise. There is a short version of the source header for use in
> very select cases where the full header might not be suited:
> https://www.apache.org/legal/src-headers.html#is-a-short-form-of-the-source-header-available
> 
> We run nightly RAT checks in CI for the java components since RAT is
> available to their maven builds simply from inheriting the apache
> parent pom, so all we need to do is configure an excludes list entries
> as appropriate and run the goal. It would be worth setting up similar
> jobs for the other components as well to help avoid getting into this
> situation in future. This could either be done just using the RAT jar,
> or generating a simple pom within the CI job, or various other ways (I
> believe there are perhaps even tailored Buildbot jobs available for
> this).
I am looking into how we can add RAT to our CI jobs since we don't use Maven.
Thanks.
> 
> Robbie
> 
> *****************************************************
> Summary
> -------
> Generated at: 2017-04-04T10:14:23+01:00
> Notes: 9
> Binaries: 37
> Archives: 0
> Standards: 682
> 
> Apache Licensed: 352
> Generated Documents: 0
> 
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 
> 330 Unknown Licenses
> 
> *******************************
> 
> Unapproved licenses:
> 
>   qpid-dispatch-0.8.0/.reviewboardrc
>   qpid-dispatch-0.8.0/.travis.yml
>   qpid-dispatch-0.8.0/VERSION.txt
>   qpid-dispatch-0.8.0/reconfigure.in
>   qpid-dispatch-0.8.0/bin/find_ports.sh
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/MANIFEST.in
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/README.rst
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/__init__.py
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/overv/__init__.py
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/overv/templates/overv/index.html
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/connect.json
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/jquery.dynatree.min.js
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/d3.v3.min.js
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/rhea-min.js
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/slider.js
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/tooltipsy.min.js
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/ui-grid.js
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/topology/download-dialog-template.html
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/topology/node-config-template.html
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/templates/dispatch/base.html
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/topology/__init__.py
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/topology/templates/topology/index.html
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/enabled/_4030_dispatch_overv_panel.py
>   qpid-dispatch-0.8.0/console/dispatch-dashboard/enabled/_4050_dispatch_topology_panel.py
>   qpid-dispatch-0.8.0/console/hawtio/README.md
>   qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/index.html
>   qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/html/tmplListChart.html
>   qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/html/tmplListTree.html
>   qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/html/tmplOverviewTree.html
>   qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/lib/rhea-min.js
>   qpid-dispatch-0.8.0/console/stand-alone/bower_components/angular-patternfly/dist/angular-patternfly.min.js
>   qpid-dispatch-0.8.0/console/stand-alone/bower_components/angular-patternfly/dist/styles/angular-patternfly.min.css
>   qpid-dispatch-0.8.0/console/stand-alone/plugin/css/dispatchpf.css
>   qpid-dispatch-0.8.0/console/stand-alone/plugin/data/places1.json
>   qpid-dispatch-0.8.0/console/stand-alone/plugin/data/world-110m.json
>   qpid-dispatch-0.8.0/console/stand-alone/plugin/html/tmplChartConfig.html
>   qpid-dispatch-0.8.0/console/stand-alone/plugin/html/tmplListChart.html
>   qpid-dispatch-0.8.0/console/stand-alone/plugin/html/tmplListTree.html
>   qpid-dispatch-0.8.0/console/stand-alone/plugin/html/tmplOverviewTree.html
>   qpid-dispatch-0.8.0/console/stand-alone/plugin/lib/rhea-min.js
>   qpid-dispatch-0.8.0/console/test/css/mock.css
>   qpid-dispatch-0.8.0/console/test/lib/rhea-min.js
>   qpid-dispatch-0.8.0/console/test/mock/__init__.py
>   qpid-dispatch-0.8.0/console/test/topologies/schema.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-1/R.0.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.0.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.1.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.10.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.100.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.101.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.102.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.103.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.104.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.105.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.106.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.107.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.108.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.11.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.111.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.113.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.114.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.115.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.116.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.118.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.119.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.12.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.120.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.121.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.123.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.124.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.125.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.126.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.127.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.128.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.129.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.13.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.130.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.131.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.132.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.134.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.135.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.136.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.137.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.138.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.139.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.14.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.140.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.141.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.142.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.145.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.146.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.147.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.148.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.149.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.15.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.150.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.151.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.152.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.153.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.154.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.155.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.157.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.159.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.16.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.17.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.18.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.19.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.2.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.20.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.21.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.22.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.23.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.24.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.25.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.26.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.27.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.28.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.29.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.3.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.30.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.31.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.32.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.33.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.34.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.35.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.36.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.37.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.38.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.39.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.4.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.40.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.41.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.42.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.43.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.44.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.45.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.46.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.47.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.48.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.49.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.5.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.50.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.51.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.52.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.53.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.54.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.55.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.56.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.57.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.58.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.59.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.6.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.60.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.61.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.62.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.63.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.64.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.65.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.66.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.67.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.69.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.7.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.70.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.71.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.74.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.75.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.78.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.8.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.82.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.83.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.85.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.87.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.88.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.9.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.91.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.92.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.93.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.95.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.96.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.97.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-160/R.99.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-4/R.0.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-4/R.1.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-4/R.2.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-4/R.3.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.0.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.1.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.10.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.11.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.12.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.13.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.14.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.15.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.16.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.17.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.18.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.19.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.2.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.20.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.21.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.22.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.23.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.24.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.25.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.26.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.27.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.28.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.29.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.3.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.30.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.31.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.32.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.33.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.34.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.35.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.36.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.37.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.38.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.39.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.4.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.5.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.6.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.7.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.8.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-40/R.9.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.0.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.1.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.2.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.3.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.4.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.5.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.0.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.1.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.10.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.11.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.12.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.13.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.14.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.15.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.16.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.17.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.18.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.19.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.2.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.20.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.21.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.22.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.23.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.24.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.25.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.26.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.27.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.28.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.29.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.3.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.30.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.31.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.32.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.33.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.34.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.35.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.36.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.37.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.38.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.39.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.4.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.40.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.41.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.42.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.43.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.44.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.45.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.46.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.47.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.48.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.49.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.5.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.50.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.51.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.52.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.53.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.54.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.55.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.56.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.57.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.58.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.59.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.6.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.60.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.61.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.62.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.63.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.64.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.65.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.66.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.67.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.68.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.69.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.7.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.70.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.71.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.72.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.73.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.74.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.75.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.76.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.77.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.78.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.79.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.8.json
>   qpid-dispatch-0.8.0/console/test/topologies/config-80/R.9.json
>   qpid-dispatch-0.8.0/doc/asciidoc.conf.in
>   qpid-dispatch-0.8.0/doc/notes/code-conventions.txt
>   qpid-dispatch-0.8.0/dockerfiles/README.md
>   qpid-dispatch-0.8.0/python/qpid_dispatch/management/qdrouter.json
>   qpid-dispatch-0.8.0/tests/system_tests_http.txt
>   qpid-dispatch-0.8.0/tests/valgrind.supp
>   qpid-dispatch-0.8.0/tests/config-0-empty/qdrouterd-empty.conf
>   qpid-dispatch-0.8.0/tests/config-2/gencerts.sh
>   qpid-dispatch-0.8.0/tests/displayname_files/profile_names1.json
>   qpid-dispatch-0.8.0/tests/displayname_files/profile_names2.json
>   qpid-dispatch-0.8.0/tests/policy-2/policy-photoserver-sasl.conf.in
>   qpid-dispatch-0.8.0/tests/policy-2/test-router-with-policy.json.in
>   qpid-dispatch-0.8.0/tests/policy-3/test-sender-receiver-limits.json
>   qpid-dispatch-0.8.0/tests/ssl_certs/client-password-file.txt
>   qpid-dispatch-0.8.0/tests/ssl_certs/gencerts.sh
>   qpid-dispatch-0.8.0/tests/ssl_certs/gencerts_openssl.sh
>   qpid-dispatch-0.8.0/tests/ssl_certs/server-password-file-bad.txt
>   qpid-dispatch-0.8.0/tests/ssl_certs/server-password-file.txt
>   qpid-dispatch-0.8.0/tests/ssl_certs/v3_ca.ext
> 
> *******************************
> 
> 
> 
> On 29 March 2017 at 12:32, Ted Ross <tr...@redhat.com> wrote:
> > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> > evaluation.
> >
> > Build Artifacts:
> >
> >     https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
> >
> > New Features:
> >
> >     DISPATCH-103 - Websocket Listeners
> >     DISPATCH-195 - Add support for transactional messages in the Router
> >     DISPATCH-441 - Support password environment variable in qdrouter config
> >     DISPATCH-467 - Terminus renaming for autoLinks
> >     DISPATCH-529 - Address annotation for Multi-Tenancy
> >     DISPATCH-726 - Connection Property for Failover Servers
> >
> > Improvements:
> >
> >     DISPATCH-113 - expose NodeTracker::last_topology_change in management
> >     DISPATCH-542 - Popup text for clients should indicate if the client is
> >     a
> > sender or receiver
> >     DISPATCH-543 - Initial load of topology page fetches too much
> > information
> >     DISPATCH-544 - Add ability to hide the info panel on the left of the
> > topology page
> >     DISPATCH-552 - Allow only one tree node to be expanded if there is a
> > large number of routers
> >     DISPATCH-553 - Add statistic counter to the "log" entity to count log
> > events per severity
> >     DISPATCH-559 - qdstat - Request only the columns that will be used in
> > the display
> >     DISPATCH-561 - Create python program that returns fake management data
> >     DISPATCH-568 - Iterator module cleanup
> >     DISPATCH-570 - Add some counts to qdstat -g
> >     DISPATCH-572 - Adding log info with proton transport id and related
> > remote IP/port
> >     DISPATCH-576 - Use new log entity statistic counter in console
> >     DISPATCH-578 - Dispatch trace logging forces all proton tracing on
> >     DISPATCH-579 - Expose software version via management
> >     DISPATCH-592 - Attempt to auto-login to the host:port that served the
> > web page
> >     DISPATCH-597 - Log enhancements
> >     DISPATCH-600 - Support secure websockets
> >     DISPATCH-602 - Add a favicon to the stand-alone router site
> >     DISPATCH-606 - Default session window is too small, causing performance
> > bottlenecks
> >     DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> > systems
> >     DISPATCH-629 - Add a protocol-version to the inter-router protocol to
> > enable backward compatibility
> >     DISPATCH-641 - Make containerId attribute work with clients
> >
> > Bugs Fixed:
> >
> >     DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
> >     DISPATCH-216 - system_tests_protocol_family fails on systems with no
> > IPv6
> >     DISPATCH-296 - segfault on router startup
> >     DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
> >     DISPATCH-314 - If a router has a normal listener, show it in a
> >     different
> > color on the topology page
> >     DISPATCH-324 - Improve initial layout of topology node
> >     DISPATCH-344 - memory growth after repeated calls from qdstat -m
> >     DISPATCH-352 - Crash with empty configuration file
> >     DISPATCH-355 - query fails with what seems to be the error of a
> >     previous
> > command
> >     DISPATCH-357 - Address field is empty for link routed links in the
> > qdstat "links" output
> >     DISPATCH-433 - Navigating to console from bookmark displays empty page
> > with just toolbars
> >     DISPATCH-451 - [AMQP] Hard coded session capacity should be
> >     configurable
> >     DISPATCH-503 - [display_name] successful test runs  have non-ascii
> > characters in router log
> >     DISPATCH-504 - [display_name] successful test runs have invalid message
> > errors  in router log
> >     DISPATCH-506 - Detach with no "error" sent by router on client TCP
> > connection dropped
> >     DISPATCH-516 - Core dump when displayname IO adapter receives message
> > with no reply-to
> >     DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> > 0.7.0
> >     DISPATCH-527 - The $displayname address is currently available. It
> > should not be available to external users
> >     DISPATCH-530 - Cannot connect using Firefox 48+
> >     DISPATCH-534 - Node selection and location is lost when the topology
> > changes
> >     DISPATCH-536 - Circular buffer overflow errors occur when there are a
> > large number of routers
> >     DISPATCH-538 - Highlighted path between routers sometimes doesn't
> > unhighlight
> >     DISPATCH-540 - Clients with both in and out links are rendered in
> >     yellow
> >     DISPATCH-541 - Highlighted path between routers contains black arrows
> >     DISPATCH-546 - Crosssection popup position is incorrect
> >     DISPATCH-547 - Stand-alone version can't download generated config file
> > for new nodes
> >     DISPATCH-554 - Topology nodes and links are too far apart when there
> >     are
> > a large number of routers
> >     DISPATCH-556 - qdstat fails at high scale
> >     DISPATCH-557 - High connection rates cause problems in the Python
> > management agent
> >     DISPATCH-560 - [console] Only use the color red to indicate a
> > failure/issue.
> >     DISPATCH-563 - Topology graph flashes and redraws a few seconds after
> >     it
> > is 1st drawn
> >     DISPATCH-564 - Error when switching routers on Entities page
> >     DISPATCH-565 - Error fetching log on Entities page
> >     DISPATCH-566 - Message annotations are not propagated to brokers on a
> > linkRoute
> >     DISPATCH-567 - Slight but persistent memory leak when running java
> > messenger producer and consumer
> >     DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> >     enum
> > values.
> >     DISPATCH-573 - Memory leaks on shutdown
> >     DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
> >     DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
> >     DISPATCH-581 - detach with closed=false propagated as closed=true on
> > link route
> >     DISPATCH-582 - Memory Leak with reactor client
> >     DISPATCH-583 - Random segmentation fault
> >     DISPATCH-585 - Firefox dropdown and buttons on list page have incorrect
> > padding
> >     DISPATCH-586 - Dispatch crash on running c sender and receiver
> >     DISPATCH-587 - Provide feedback when loading log entries
> >     DISPATCH-588 - Schema is not loaded if auto-login is enabled
> >     DISPATCH-589 - Missing links on topology page
> >     DISPATCH-594 - Log file over-written every time the router is restarted
> >     DISPATCH-595 - dispositions propagated after link detach on link route
> >     DISPATCH-596 - error is lost from rejected state in relayed disposition
> >     DISPATCH-598 - Router crash when calling sender and session close
> > methods in onLinkFLow()
> >     DISPATCH-599 - Link routing : messages is not transferred if sender
> > detach link immediately
> >     DISPATCH-601 - Valgrind errors in dispatch tests
> >     DISPATCH-603 - address resource leak
> >     DISPATCH-604 - Management - Link connection-id does not match
> >     identities
> > of connections
> >     DISPATCH-605 - Memory Leak with multple sender/receivers in one session
> >     DISPATCH-607 - Handle empty response from GET-MGMT-NODES
> >     DISPATCH-608 - Links not cleaned up when a close is sent without being
> > preceeded by a detach and end
> >     DISPATCH-609 - Name attribute is duplicated in QUERY response
> >     DISPATCH-610 - crash in qdr_link_cleanup_CT
> >     DISPATCH-611 - Router core dump with old config file
> >     DISPATCH-612 - Add support for GCC equivalent compiler options
> >     DISPATCH-613 - Remove semi-colon not needed after function definition
> >     DISPATCH-614 - strerror_r on Solaris does not return char*
> >     DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
> >     DISPATCH-616 - Arithmetic operations not allowed on void * pointer
> >     DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> > _POSIX_HOST_NAME_MAX is defined instead
> >     DISPATCH-618 - Revert eventfd on Solaris
> >     DISPATCH-619 - Use memalign instead of posix_memalign which is not
> > defined on Solaris
> >     DISPATCH-620 - no-strict-aliasing is only supported with GCC
> >     DISPATCH-621 - Add missing string.h include for Solaris compiler
> >     DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler error
> > to avoid undefined symbol on Solaris
> >     DISPATCH-623 - Unreachable code (qd_field_iterator_free after a return
> > statement) detected on Solaris
> >     DISPATCH-624 - Add Atomic operations support on Solaris
> >     DISPATCH-626 - Add hints for getaddrinfo on Solaris
> >     DISPATCH-628 - [PATCH] Multiple connections per autoLink and linkRoute
> > overwrites connection handle
> >     DISPATCH-631 - Tests should be made conditional to skip tests for SASL
> > features that are not available
> >     DISPATCH-633 - Creating connectors and addresses returns success codes
> > of two different types.
> >     DISPATCH-634 - Dynamic Targets are unsupported
> >     DISPATCH-635 - The Ubuntu CI tests that involve two routers are failing
> >     DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is required;
> > however, cmake complains with 0.14
> >     DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated fail
> > when cyrus-sasl-plain is not installed
> >     DISPATCH-640 - containerId field conflics with the connector name
> >     DISPATCH-642 - Fix recognition of Artemis broker on topology page
> >     DISPATCH-643 - Duplicate log messages show up on normal AMQP close
> >     DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a pipe
> > issue in Daemon mode
> >     DISPATCH-646 - Link route tests which test the drain feature fail
> > intermittently
> >     DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> > master
> >     DISPATCH-727 - qdmanage identity reporting and lookup are broken
> >     DISPATCH-728 - crash on shutdown with connector
> >     DISPATCH-729 - password-file option doesn't work correctly
> >     DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
> >     DISPATCH-732 - CONN_MGR log module is used in connection_manager.c but
> > is missing from log schema
> >     DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> > intermittently
> >
> > ---------------------------------------------------------------------
> > 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


Re: Qpid Dispatch Router 0.8.0 Release Candidate 1

Posted by Robbie Gemmell <ro...@gmail.com>.
I gave the router a try out, building against Proton 0.17.0. The build
completed fine, all tests passed, and I ran the Qpid JMS HelloWorld
against the built router.

The signature and checksums verified fine, though the .sha512 checksum
file should be renamed with .sha extension for consistency with the
release policy and the other components that moved to SHA512
checksums.

Giving the release archive a look over, I noticed various license
related issues with the content:
- One file, tooltipsy.min.js, indicates it is GPLv2, which is
considered Category X
(https://www.apache.org/legal/resolved.html#category-x) meaning it
can't be included and needs removed prior to release.
- Several other files need called out in the LICENCE file with detail
of their licence terms since they aren't ALv2.
- There are a number of files that lack a licence header that should
have one. See the RAT output summary below, though note this includes
all the non-ALv2 files since we dont have an excludes list to reduce
the noise where actually appropriate. For the mass of JSON files, I
guess it depends how they are used given JSON doesn't strictly support
comments (though many impls do), though 'test data that would cause
failure with a header' is an allowed exception:
https://www.apache.org/legal/src-headers.html#faq-exceptions. If it
works, we should probably add it if only because it greatly cuts down
the noise. There is a short version of the source header for use in
very select cases where the full header might not be suited:
https://www.apache.org/legal/src-headers.html#is-a-short-form-of-the-source-header-available

We run nightly RAT checks in CI for the java components since RAT is
available to their maven builds simply from inheriting the apache
parent pom, so all we need to do is configure an excludes list entries
as appropriate and run the goal. It would be worth setting up similar
jobs for the other components as well to help avoid getting into this
situation in future. This could either be done just using the RAT jar,
or generating a simple pom within the CI job, or various other ways (I
believe there are perhaps even tailored Buildbot jobs available for
this).

Robbie

*****************************************************
Summary
-------
Generated at: 2017-04-04T10:14:23+01:00
Notes: 9
Binaries: 37
Archives: 0
Standards: 682

Apache Licensed: 352
Generated Documents: 0

JavaDocs are generated and so license header is optional
Generated files do not required license headers

330 Unknown Licenses

*******************************

Unapproved licenses:

  qpid-dispatch-0.8.0/.reviewboardrc
  qpid-dispatch-0.8.0/.travis.yml
  qpid-dispatch-0.8.0/VERSION.txt
  qpid-dispatch-0.8.0/reconfigure.in
  qpid-dispatch-0.8.0/bin/find_ports.sh
  qpid-dispatch-0.8.0/console/dispatch-dashboard/MANIFEST.in
  qpid-dispatch-0.8.0/console/dispatch-dashboard/README.rst
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/__init__.py
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/overv/__init__.py
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/overv/templates/overv/index.html
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/connect.json
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/jquery.dynatree.min.js
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/d3.v3.min.js
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/rhea-min.js
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/slider.js
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/tooltipsy.min.js
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/ui-grid.js
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/topology/download-dialog-template.html
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/topology/node-config-template.html
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/templates/dispatch/base.html
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/topology/__init__.py
  qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/topology/templates/topology/index.html
  qpid-dispatch-0.8.0/console/dispatch-dashboard/enabled/_4030_dispatch_overv_panel.py
  qpid-dispatch-0.8.0/console/dispatch-dashboard/enabled/_4050_dispatch_topology_panel.py
  qpid-dispatch-0.8.0/console/hawtio/README.md
  qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/index.html
  qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/html/tmplListChart.html
  qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/html/tmplListTree.html
  qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/html/tmplOverviewTree.html
  qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/lib/rhea-min.js
  qpid-dispatch-0.8.0/console/stand-alone/bower_components/angular-patternfly/dist/angular-patternfly.min.js
  qpid-dispatch-0.8.0/console/stand-alone/bower_components/angular-patternfly/dist/styles/angular-patternfly.min.css
  qpid-dispatch-0.8.0/console/stand-alone/plugin/css/dispatchpf.css
  qpid-dispatch-0.8.0/console/stand-alone/plugin/data/places1.json
  qpid-dispatch-0.8.0/console/stand-alone/plugin/data/world-110m.json
  qpid-dispatch-0.8.0/console/stand-alone/plugin/html/tmplChartConfig.html
  qpid-dispatch-0.8.0/console/stand-alone/plugin/html/tmplListChart.html
  qpid-dispatch-0.8.0/console/stand-alone/plugin/html/tmplListTree.html
  qpid-dispatch-0.8.0/console/stand-alone/plugin/html/tmplOverviewTree.html
  qpid-dispatch-0.8.0/console/stand-alone/plugin/lib/rhea-min.js
  qpid-dispatch-0.8.0/console/test/css/mock.css
  qpid-dispatch-0.8.0/console/test/lib/rhea-min.js
  qpid-dispatch-0.8.0/console/test/mock/__init__.py
  qpid-dispatch-0.8.0/console/test/topologies/schema.json
  qpid-dispatch-0.8.0/console/test/topologies/config-1/R.0.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.0.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.1.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.10.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.100.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.101.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.102.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.103.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.104.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.105.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.106.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.107.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.108.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.11.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.111.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.113.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.114.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.115.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.116.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.118.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.119.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.12.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.120.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.121.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.123.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.124.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.125.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.126.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.127.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.128.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.129.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.13.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.130.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.131.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.132.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.134.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.135.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.136.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.137.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.138.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.139.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.14.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.140.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.141.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.142.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.145.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.146.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.147.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.148.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.149.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.15.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.150.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.151.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.152.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.153.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.154.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.155.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.157.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.159.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.16.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.17.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.18.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.19.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.2.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.20.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.21.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.22.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.23.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.24.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.25.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.26.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.27.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.28.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.29.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.3.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.30.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.31.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.32.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.33.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.34.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.35.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.36.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.37.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.38.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.39.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.4.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.40.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.41.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.42.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.43.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.44.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.45.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.46.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.47.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.48.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.49.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.5.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.50.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.51.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.52.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.53.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.54.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.55.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.56.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.57.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.58.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.59.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.6.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.60.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.61.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.62.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.63.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.64.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.65.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.66.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.67.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.69.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.7.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.70.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.71.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.74.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.75.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.78.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.8.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.82.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.83.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.85.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.87.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.88.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.9.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.91.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.92.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.93.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.95.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.96.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.97.json
  qpid-dispatch-0.8.0/console/test/topologies/config-160/R.99.json
  qpid-dispatch-0.8.0/console/test/topologies/config-4/R.0.json
  qpid-dispatch-0.8.0/console/test/topologies/config-4/R.1.json
  qpid-dispatch-0.8.0/console/test/topologies/config-4/R.2.json
  qpid-dispatch-0.8.0/console/test/topologies/config-4/R.3.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.0.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.1.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.10.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.11.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.12.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.13.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.14.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.15.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.16.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.17.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.18.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.19.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.2.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.20.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.21.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.22.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.23.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.24.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.25.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.26.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.27.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.28.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.29.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.3.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.30.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.31.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.32.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.33.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.34.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.35.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.36.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.37.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.38.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.39.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.4.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.5.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.6.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.7.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.8.json
  qpid-dispatch-0.8.0/console/test/topologies/config-40/R.9.json
  qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.0.json
  qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.1.json
  qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.2.json
  qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.3.json
  qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.4.json
  qpid-dispatch-0.8.0/console/test/topologies/config-6/QDR.5.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.0.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.1.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.10.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.11.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.12.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.13.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.14.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.15.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.16.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.17.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.18.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.19.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.2.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.20.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.21.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.22.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.23.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.24.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.25.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.26.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.27.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.28.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.29.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.3.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.30.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.31.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.32.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.33.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.34.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.35.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.36.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.37.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.38.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.39.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.4.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.40.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.41.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.42.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.43.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.44.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.45.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.46.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.47.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.48.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.49.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.5.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.50.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.51.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.52.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.53.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.54.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.55.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.56.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.57.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.58.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.59.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.6.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.60.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.61.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.62.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.63.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.64.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.65.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.66.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.67.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.68.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.69.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.7.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.70.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.71.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.72.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.73.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.74.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.75.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.76.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.77.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.78.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.79.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.8.json
  qpid-dispatch-0.8.0/console/test/topologies/config-80/R.9.json
  qpid-dispatch-0.8.0/doc/asciidoc.conf.in
  qpid-dispatch-0.8.0/doc/notes/code-conventions.txt
  qpid-dispatch-0.8.0/dockerfiles/README.md
  qpid-dispatch-0.8.0/python/qpid_dispatch/management/qdrouter.json
  qpid-dispatch-0.8.0/tests/system_tests_http.txt
  qpid-dispatch-0.8.0/tests/valgrind.supp
  qpid-dispatch-0.8.0/tests/config-0-empty/qdrouterd-empty.conf
  qpid-dispatch-0.8.0/tests/config-2/gencerts.sh
  qpid-dispatch-0.8.0/tests/displayname_files/profile_names1.json
  qpid-dispatch-0.8.0/tests/displayname_files/profile_names2.json
  qpid-dispatch-0.8.0/tests/policy-2/policy-photoserver-sasl.conf.in
  qpid-dispatch-0.8.0/tests/policy-2/test-router-with-policy.json.in
  qpid-dispatch-0.8.0/tests/policy-3/test-sender-receiver-limits.json
  qpid-dispatch-0.8.0/tests/ssl_certs/client-password-file.txt
  qpid-dispatch-0.8.0/tests/ssl_certs/gencerts.sh
  qpid-dispatch-0.8.0/tests/ssl_certs/gencerts_openssl.sh
  qpid-dispatch-0.8.0/tests/ssl_certs/server-password-file-bad.txt
  qpid-dispatch-0.8.0/tests/ssl_certs/server-password-file.txt
  qpid-dispatch-0.8.0/tests/ssl_certs/v3_ca.ext

*******************************



On 29 March 2017 at 12:32, Ted Ross <tr...@redhat.com> wrote:
> The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> evaluation.
>
> Build Artifacts:
>
>     https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
>
> New Features:
>
>     DISPATCH-103 - Websocket Listeners
>     DISPATCH-195 - Add support for transactional messages in the Router
>     DISPATCH-441 - Support password environment variable in qdrouter config
>     DISPATCH-467 - Terminus renaming for autoLinks
>     DISPATCH-529 - Address annotation for Multi-Tenancy
>     DISPATCH-726 - Connection Property for Failover Servers
>
> Improvements:
>
>     DISPATCH-113 - expose NodeTracker::last_topology_change in management
>     DISPATCH-542 - Popup text for clients should indicate if the client is a
> sender or receiver
>     DISPATCH-543 - Initial load of topology page fetches too much
> information
>     DISPATCH-544 - Add ability to hide the info panel on the left of the
> topology page
>     DISPATCH-552 - Allow only one tree node to be expanded if there is a
> large number of routers
>     DISPATCH-553 - Add statistic counter to the "log" entity to count log
> events per severity
>     DISPATCH-559 - qdstat - Request only the columns that will be used in
> the display
>     DISPATCH-561 - Create python program that returns fake management data
>     DISPATCH-568 - Iterator module cleanup
>     DISPATCH-570 - Add some counts to qdstat -g
>     DISPATCH-572 - Adding log info with proton transport id and related
> remote IP/port
>     DISPATCH-576 - Use new log entity statistic counter in console
>     DISPATCH-578 - Dispatch trace logging forces all proton tracing on
>     DISPATCH-579 - Expose software version via management
>     DISPATCH-592 - Attempt to auto-login to the host:port that served the
> web page
>     DISPATCH-597 - Log enhancements
>     DISPATCH-600 - Support secure websockets
>     DISPATCH-602 - Add a favicon to the stand-alone router site
>     DISPATCH-606 - Default session window is too small, causing performance
> bottlenecks
>     DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> systems
>     DISPATCH-629 - Add a protocol-version to the inter-router protocol to
> enable backward compatibility
>     DISPATCH-641 - Make containerId attribute work with clients
>
> Bugs Fixed:
>
>     DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
>     DISPATCH-216 - system_tests_protocol_family fails on systems with no
> IPv6
>     DISPATCH-296 - segfault on router startup
>     DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
>     DISPATCH-314 - If a router has a normal listener, show it in a different
> color on the topology page
>     DISPATCH-324 - Improve initial layout of topology node
>     DISPATCH-344 - memory growth after repeated calls from qdstat -m
>     DISPATCH-352 - Crash with empty configuration file
>     DISPATCH-355 - query fails with what seems to be the error of a previous
> command
>     DISPATCH-357 - Address field is empty for link routed links in the
> qdstat "links" output
>     DISPATCH-433 - Navigating to console from bookmark displays empty page
> with just toolbars
>     DISPATCH-451 - [AMQP] Hard coded session capacity should be configurable
>     DISPATCH-503 - [display_name] successful test runs  have non-ascii
> characters in router log
>     DISPATCH-504 - [display_name] successful test runs have invalid message
> errors  in router log
>     DISPATCH-506 - Detach with no "error" sent by router on client TCP
> connection dropped
>     DISPATCH-516 - Core dump when displayname IO adapter receives message
> with no reply-to
>     DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> 0.7.0
>     DISPATCH-527 - The $displayname address is currently available. It
> should not be available to external users
>     DISPATCH-530 - Cannot connect using Firefox 48+
>     DISPATCH-534 - Node selection and location is lost when the topology
> changes
>     DISPATCH-536 - Circular buffer overflow errors occur when there are a
> large number of routers
>     DISPATCH-538 - Highlighted path between routers sometimes doesn't
> unhighlight
>     DISPATCH-540 - Clients with both in and out links are rendered in yellow
>     DISPATCH-541 - Highlighted path between routers contains black arrows
>     DISPATCH-546 - Crosssection popup position is incorrect
>     DISPATCH-547 - Stand-alone version can't download generated config file
> for new nodes
>     DISPATCH-554 - Topology nodes and links are too far apart when there are
> a large number of routers
>     DISPATCH-556 - qdstat fails at high scale
>     DISPATCH-557 - High connection rates cause problems in the Python
> management agent
>     DISPATCH-560 - [console] Only use the color red to indicate a
> failure/issue.
>     DISPATCH-563 - Topology graph flashes and redraws a few seconds after it
> is 1st drawn
>     DISPATCH-564 - Error when switching routers on Entities page
>     DISPATCH-565 - Error fetching log on Entities page
>     DISPATCH-566 - Message annotations are not propagated to brokers on a
> linkRoute
>     DISPATCH-567 - Slight but persistent memory leak when running java
> messenger producer and consumer
>     DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t enum
> values.
>     DISPATCH-573 - Memory leaks on shutdown
>     DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
>     DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
>     DISPATCH-581 - detach with closed=false propagated as closed=true on
> link route
>     DISPATCH-582 - Memory Leak with reactor client
>     DISPATCH-583 - Random segmentation fault
>     DISPATCH-585 - Firefox dropdown and buttons on list page have incorrect
> padding
>     DISPATCH-586 - Dispatch crash on running c sender and receiver
>     DISPATCH-587 - Provide feedback when loading log entries
>     DISPATCH-588 - Schema is not loaded if auto-login is enabled
>     DISPATCH-589 - Missing links on topology page
>     DISPATCH-594 - Log file over-written every time the router is restarted
>     DISPATCH-595 - dispositions propagated after link detach on link route
>     DISPATCH-596 - error is lost from rejected state in relayed disposition
>     DISPATCH-598 - Router crash when calling sender and session close
> methods in onLinkFLow()
>     DISPATCH-599 - Link routing : messages is not transferred if sender
> detach link immediately
>     DISPATCH-601 - Valgrind errors in dispatch tests
>     DISPATCH-603 - address resource leak
>     DISPATCH-604 - Management - Link connection-id does not match identities
> of connections
>     DISPATCH-605 - Memory Leak with multple sender/receivers in one session
>     DISPATCH-607 - Handle empty response from GET-MGMT-NODES
>     DISPATCH-608 - Links not cleaned up when a close is sent without being
> preceeded by a detach and end
>     DISPATCH-609 - Name attribute is duplicated in QUERY response
>     DISPATCH-610 - crash in qdr_link_cleanup_CT
>     DISPATCH-611 - Router core dump with old config file
>     DISPATCH-612 - Add support for GCC equivalent compiler options
>     DISPATCH-613 - Remove semi-colon not needed after function definition
>     DISPATCH-614 - strerror_r on Solaris does not return char*
>     DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
>     DISPATCH-616 - Arithmetic operations not allowed on void * pointer
>     DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> _POSIX_HOST_NAME_MAX is defined instead
>     DISPATCH-618 - Revert eventfd on Solaris
>     DISPATCH-619 - Use memalign instead of posix_memalign which is not
> defined on Solaris
>     DISPATCH-620 - no-strict-aliasing is only supported with GCC
>     DISPATCH-621 - Add missing string.h include for Solaris compiler
>     DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler error
> to avoid undefined symbol on Solaris
>     DISPATCH-623 - Unreachable code (qd_field_iterator_free after a return
> statement) detected on Solaris
>     DISPATCH-624 - Add Atomic operations support on Solaris
>     DISPATCH-626 - Add hints for getaddrinfo on Solaris
>     DISPATCH-628 - [PATCH] Multiple connections per autoLink and linkRoute
> overwrites connection handle
>     DISPATCH-631 - Tests should be made conditional to skip tests for SASL
> features that are not available
>     DISPATCH-633 - Creating connectors and addresses returns success codes
> of two different types.
>     DISPATCH-634 - Dynamic Targets are unsupported
>     DISPATCH-635 - The Ubuntu CI tests that involve two routers are failing
>     DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is required;
> however, cmake complains with 0.14
>     DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated fail
> when cyrus-sasl-plain is not installed
>     DISPATCH-640 - containerId field conflics with the connector name
>     DISPATCH-642 - Fix recognition of Artemis broker on topology page
>     DISPATCH-643 - Duplicate log messages show up on normal AMQP close
>     DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a pipe
> issue in Daemon mode
>     DISPATCH-646 - Link route tests which test the drain feature fail
> intermittently
>     DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> master
>     DISPATCH-727 - qdmanage identity reporting and lookup are broken
>     DISPATCH-728 - crash on shutdown with connector
>     DISPATCH-729 - password-file option doesn't work correctly
>     DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
>     DISPATCH-732 - CONN_MGR log module is used in connection_manager.c but
> is missing from log schema
>     DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> intermittently
>
> ---------------------------------------------------------------------
> 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.8.0 Release Candidate 2

Posted by Robbie Gemmell <ro...@gmail.com>.
I gave the licence related changes a quick look and ran RAT
with+without the new excludes file, output looked good, thanks Ganesh.

Robbie

On 6 April 2017 at 21:30, Ted Ross <tr...@redhat.com> wrote:
> I've built Qpid Dispatch Router 0.8.0 RC2.  The following issues have been
> resolved since RC1:
>
>     DISPATCH-735 - Crash on startup parsing JSON conf file with "address"
> entity
>     DISPATCH-736 - 3 system tests in the test suite are failing on RHEL 6.4
>     DISPATCH-740 - Remove tooltipsy.min.js and code associated with it
>
> Build Artifacts:
>
>     https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc2/
>
> I will start a vote for this release candidate tomorrow if I don't hear any
> complaints.
>
> Thanks,
>
> -Ted
>
> On 03/29/2017 07:32 AM, Ted Ross wrote:
>>
>> The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
>> evaluation.
>>
>> Build Artifacts:
>>
>>     https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
>>
>> New Features:
>>
>>     DISPATCH-103 - Websocket Listeners
>>     DISPATCH-195 - Add support for transactional messages in the Router
>>     DISPATCH-441 - Support password environment variable in qdrouter
>> config
>>     DISPATCH-467 - Terminus renaming for autoLinks
>>     DISPATCH-529 - Address annotation for Multi-Tenancy
>>     DISPATCH-726 - Connection Property for Failover Servers
>>
>> Improvements:
>>
>>     DISPATCH-113 - expose NodeTracker::last_topology_change in management
>>     DISPATCH-542 - Popup text for clients should indicate if the client
>> is a sender or receiver
>>     DISPATCH-543 - Initial load of topology page fetches too much
>> information
>>     DISPATCH-544 - Add ability to hide the info panel on the left of the
>> topology page
>>     DISPATCH-552 - Allow only one tree node to be expanded if there is a
>> large number of routers
>>     DISPATCH-553 - Add statistic counter to the "log" entity to count
>> log events per severity
>>     DISPATCH-559 - qdstat - Request only the columns that will be used
>> in the display
>>     DISPATCH-561 - Create python program that returns fake management data
>>     DISPATCH-568 - Iterator module cleanup
>>     DISPATCH-570 - Add some counts to qdstat -g
>>     DISPATCH-572 - Adding log info with proton transport id and related
>> remote IP/port
>>     DISPATCH-576 - Use new log entity statistic counter in console
>>     DISPATCH-578 - Dispatch trace logging forces all proton tracing on
>>     DISPATCH-579 - Expose software version via management
>>     DISPATCH-592 - Attempt to auto-login to the host:port that served
>> the web page
>>     DISPATCH-597 - Log enhancements
>>     DISPATCH-600 - Support secure websockets
>>     DISPATCH-602 - Add a favicon to the stand-alone router site
>>     DISPATCH-606 - Default session window is too small, causing
>> performance bottlenecks
>>     DISPATCH-627 - BatchedSettlement test fails with timeout on slower
>> systems
>>     DISPATCH-629 - Add a protocol-version to the inter-router protocol
>> to enable backward compatibility
>>     DISPATCH-641 - Make containerId attribute work with clients
>>
>> Bugs Fixed:
>>
>>     DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
>>     DISPATCH-216 - system_tests_protocol_family fails on systems with no
>> IPv6
>>     DISPATCH-296 - segfault on router startup
>>     DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
>>     DISPATCH-314 - If a router has a normal listener, show it in a
>> different color on the topology page
>>     DISPATCH-324 - Improve initial layout of topology node
>>     DISPATCH-344 - memory growth after repeated calls from qdstat -m
>>     DISPATCH-352 - Crash with empty configuration file
>>     DISPATCH-355 - query fails with what seems to be the error of a
>> previous command
>>     DISPATCH-357 - Address field is empty for link routed links in the
>> qdstat "links" output
>>     DISPATCH-433 - Navigating to console from bookmark displays empty
>> page with just toolbars
>>     DISPATCH-451 - [AMQP] Hard coded session capacity should be
>> configurable
>>     DISPATCH-503 - [display_name] successful test runs  have non-ascii
>> characters in router log
>>     DISPATCH-504 - [display_name] successful test runs have invalid
>> message errors  in router log
>>     DISPATCH-506 - Detach with no "error" sent by router on client TCP
>> connection dropped
>>     DISPATCH-516 - Core dump when displayname IO adapter receives
>> message with no reply-to
>>     DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
>> 0.7.0
>>     DISPATCH-527 - The $displayname address is currently available. It
>> should not be available to external users
>>     DISPATCH-530 - Cannot connect using Firefox 48+
>>     DISPATCH-534 - Node selection and location is lost when the topology
>> changes
>>     DISPATCH-536 - Circular buffer overflow errors occur when there are
>> a large number of routers
>>     DISPATCH-538 - Highlighted path between routers sometimes doesn't
>> unhighlight
>>     DISPATCH-540 - Clients with both in and out links are rendered in
>> yellow
>>     DISPATCH-541 - Highlighted path between routers contains black arrows
>>     DISPATCH-546 - Crosssection popup position is incorrect
>>     DISPATCH-547 - Stand-alone version can't download generated config
>> file for new nodes
>>     DISPATCH-554 - Topology nodes and links are too far apart when there
>> are a large number of routers
>>     DISPATCH-556 - qdstat fails at high scale
>>     DISPATCH-557 - High connection rates cause problems in the Python
>> management agent
>>     DISPATCH-560 - [console] Only use the color red to indicate a
>> failure/issue.
>>     DISPATCH-563 - Topology graph flashes and redraws a few seconds
>> after it is 1st drawn
>>     DISPATCH-564 - Error when switching routers on Entities page
>>     DISPATCH-565 - Error fetching log on Entities page
>>     DISPATCH-566 - Message annotations are not propagated to brokers on
>> a linkRoute
>>     DISPATCH-567 - Slight but persistent memory leak when running java
>> messenger producer and consumer
>>     DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
>> enum values.
>>     DISPATCH-573 - Memory leaks on shutdown
>>     DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
>>     DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
>>     DISPATCH-581 - detach with closed=false propagated as closed=true on
>> link route
>>     DISPATCH-582 - Memory Leak with reactor client
>>     DISPATCH-583 - Random segmentation fault
>>     DISPATCH-585 - Firefox dropdown and buttons on list page have
>> incorrect padding
>>     DISPATCH-586 - Dispatch crash on running c sender and receiver
>>     DISPATCH-587 - Provide feedback when loading log entries
>>     DISPATCH-588 - Schema is not loaded if auto-login is enabled
>>     DISPATCH-589 - Missing links on topology page
>>     DISPATCH-594 - Log file over-written every time the router is
>> restarted
>>     DISPATCH-595 - dispositions propagated after link detach on link route
>>     DISPATCH-596 - error is lost from rejected state in relayed
>> disposition
>>     DISPATCH-598 - Router crash when calling sender and session close
>> methods in onLinkFLow()
>>     DISPATCH-599 - Link routing : messages is not transferred if sender
>> detach link immediately
>>     DISPATCH-601 - Valgrind errors in dispatch tests
>>     DISPATCH-603 - address resource leak
>>     DISPATCH-604 - Management - Link connection-id does not match
>> identities of connections
>>     DISPATCH-605 - Memory Leak with multple sender/receivers in one
>> session
>>     DISPATCH-607 - Handle empty response from GET-MGMT-NODES
>>     DISPATCH-608 - Links not cleaned up when a close is sent without
>> being preceeded by a detach and end
>>     DISPATCH-609 - Name attribute is duplicated in QUERY response
>>     DISPATCH-610 - crash in qdr_link_cleanup_CT
>>     DISPATCH-611 - Router core dump with old config file
>>     DISPATCH-612 - Add support for GCC equivalent compiler options
>>     DISPATCH-613 - Remove semi-colon not needed after function definition
>>     DISPATCH-614 - strerror_r on Solaris does not return char*
>>     DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
>>     DISPATCH-616 - Arithmetic operations not allowed on void * pointer
>>     DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
>> _POSIX_HOST_NAME_MAX is defined instead
>>     DISPATCH-618 - Revert eventfd on Solaris
>>     DISPATCH-619 - Use memalign instead of posix_memalign which is not
>> defined on Solaris
>>     DISPATCH-620 - no-strict-aliasing is only supported with GCC
>>     DISPATCH-621 - Add missing string.h include for Solaris compiler
>>     DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
>> error to avoid undefined symbol on Solaris
>>     DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
>> return statement) detected on Solaris
>>     DISPATCH-624 - Add Atomic operations support on Solaris
>>     DISPATCH-626 - Add hints for getaddrinfo on Solaris
>>     DISPATCH-628 - [PATCH] Multiple connections per autoLink and
>> linkRoute overwrites connection handle
>>     DISPATCH-631 - Tests should be made conditional to skip tests for
>> SASL features that are not available
>>     DISPATCH-633 - Creating connectors and addresses returns success
>> codes of two different types.
>>     DISPATCH-634 - Dynamic Targets are unsupported
>>     DISPATCH-635 - The Ubuntu CI tests that involve two routers are
>> failing
>>     DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
>> required; however, cmake complains with 0.14
>>     DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
>> fail when cyrus-sasl-plain is not installed
>>     DISPATCH-640 - containerId field conflics with the connector name
>>     DISPATCH-642 - Fix recognition of Artemis broker on topology page
>>     DISPATCH-643 - Duplicate log messages show up on normal AMQP close
>>     DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
>> pipe issue in Daemon mode
>>     DISPATCH-646 - Link route tests which test the drain feature fail
>> intermittently
>>     DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
>> master
>>     DISPATCH-727 - qdmanage identity reporting and lookup are broken
>>     DISPATCH-728 - crash on shutdown with connector
>>     DISPATCH-729 - password-file option doesn't work correctly
>>     DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
>>     DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
>> but is missing from log schema
>>     DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
>> intermittently
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>
> --
> Ted Ross
> Senior Principal Software Engineer
> Red Hat
> 314 Littleton Road
> Westford, MA 01886
> tross@redhat.com     T: +1-978-392-3950     M: +1-978-399-4122
>
> ---------------------------------------------------------------------
> 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.8.0 Release Candidate 2

Posted by Ken Giusti <kg...@redhat.com>.
+1

oslo.messaging Call and Cast functional tests pass
ombt2 rpc call and notify tests show no change in performance wrt 0.7.0

-K

----- Original Message -----
> From: "Ted Ross" <tr...@redhat.com>
> To: users@qpid.apache.org
> Sent: Thursday, April 6, 2017 4:30:18 PM
> Subject: Qpid Dispatch Router 0.8.0 Release Candidate 2
> 
> I've built Qpid Dispatch Router 0.8.0 RC2.  The following issues have
> been resolved since RC1:
> 
>      DISPATCH-735 - Crash on startup parsing JSON conf file with
> "address" entity
>      DISPATCH-736 - 3 system tests in the test suite are failing on RHEL 6.4
>      DISPATCH-740 - Remove tooltipsy.min.js and code associated with it
> 
> Build Artifacts:
> 
>      https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc2/
> 
> I will start a vote for this release candidate tomorrow if I don't hear
> any complaints.
> 
> Thanks,
> 
> -Ted
> 
> On 03/29/2017 07:32 AM, Ted Ross wrote:
> > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> > evaluation.
> >
> > Build Artifacts:
> >
> >     https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
> >
> > New Features:
> >
> >     DISPATCH-103 - Websocket Listeners
> >     DISPATCH-195 - Add support for transactional messages in the Router
> >     DISPATCH-441 - Support password environment variable in qdrouter config
> >     DISPATCH-467 - Terminus renaming for autoLinks
> >     DISPATCH-529 - Address annotation for Multi-Tenancy
> >     DISPATCH-726 - Connection Property for Failover Servers
> >
> > Improvements:
> >
> >     DISPATCH-113 - expose NodeTracker::last_topology_change in management
> >     DISPATCH-542 - Popup text for clients should indicate if the client
> > is a sender or receiver
> >     DISPATCH-543 - Initial load of topology page fetches too much
> > information
> >     DISPATCH-544 - Add ability to hide the info panel on the left of the
> > topology page
> >     DISPATCH-552 - Allow only one tree node to be expanded if there is a
> > large number of routers
> >     DISPATCH-553 - Add statistic counter to the "log" entity to count
> > log events per severity
> >     DISPATCH-559 - qdstat - Request only the columns that will be used
> > in the display
> >     DISPATCH-561 - Create python program that returns fake management data
> >     DISPATCH-568 - Iterator module cleanup
> >     DISPATCH-570 - Add some counts to qdstat -g
> >     DISPATCH-572 - Adding log info with proton transport id and related
> > remote IP/port
> >     DISPATCH-576 - Use new log entity statistic counter in console
> >     DISPATCH-578 - Dispatch trace logging forces all proton tracing on
> >     DISPATCH-579 - Expose software version via management
> >     DISPATCH-592 - Attempt to auto-login to the host:port that served
> > the web page
> >     DISPATCH-597 - Log enhancements
> >     DISPATCH-600 - Support secure websockets
> >     DISPATCH-602 - Add a favicon to the stand-alone router site
> >     DISPATCH-606 - Default session window is too small, causing
> > performance bottlenecks
> >     DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> > systems
> >     DISPATCH-629 - Add a protocol-version to the inter-router protocol
> > to enable backward compatibility
> >     DISPATCH-641 - Make containerId attribute work with clients
> >
> > Bugs Fixed:
> >
> >     DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
> >     DISPATCH-216 - system_tests_protocol_family fails on systems with no
> > IPv6
> >     DISPATCH-296 - segfault on router startup
> >     DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
> >     DISPATCH-314 - If a router has a normal listener, show it in a
> > different color on the topology page
> >     DISPATCH-324 - Improve initial layout of topology node
> >     DISPATCH-344 - memory growth after repeated calls from qdstat -m
> >     DISPATCH-352 - Crash with empty configuration file
> >     DISPATCH-355 - query fails with what seems to be the error of a
> > previous command
> >     DISPATCH-357 - Address field is empty for link routed links in the
> > qdstat "links" output
> >     DISPATCH-433 - Navigating to console from bookmark displays empty
> > page with just toolbars
> >     DISPATCH-451 - [AMQP] Hard coded session capacity should be
> > configurable
> >     DISPATCH-503 - [display_name] successful test runs  have non-ascii
> > characters in router log
> >     DISPATCH-504 - [display_name] successful test runs have invalid
> > message errors  in router log
> >     DISPATCH-506 - Detach with no "error" sent by router on client TCP
> > connection dropped
> >     DISPATCH-516 - Core dump when displayname IO adapter receives
> > message with no reply-to
> >     DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> > 0.7.0
> >     DISPATCH-527 - The $displayname address is currently available. It
> > should not be available to external users
> >     DISPATCH-530 - Cannot connect using Firefox 48+
> >     DISPATCH-534 - Node selection and location is lost when the topology
> > changes
> >     DISPATCH-536 - Circular buffer overflow errors occur when there are
> > a large number of routers
> >     DISPATCH-538 - Highlighted path between routers sometimes doesn't
> > unhighlight
> >     DISPATCH-540 - Clients with both in and out links are rendered in
> > yellow
> >     DISPATCH-541 - Highlighted path between routers contains black arrows
> >     DISPATCH-546 - Crosssection popup position is incorrect
> >     DISPATCH-547 - Stand-alone version can't download generated config
> > file for new nodes
> >     DISPATCH-554 - Topology nodes and links are too far apart when there
> > are a large number of routers
> >     DISPATCH-556 - qdstat fails at high scale
> >     DISPATCH-557 - High connection rates cause problems in the Python
> > management agent
> >     DISPATCH-560 - [console] Only use the color red to indicate a
> > failure/issue.
> >     DISPATCH-563 - Topology graph flashes and redraws a few seconds
> > after it is 1st drawn
> >     DISPATCH-564 - Error when switching routers on Entities page
> >     DISPATCH-565 - Error fetching log on Entities page
> >     DISPATCH-566 - Message annotations are not propagated to brokers on
> > a linkRoute
> >     DISPATCH-567 - Slight but persistent memory leak when running java
> > messenger producer and consumer
> >     DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> > enum values.
> >     DISPATCH-573 - Memory leaks on shutdown
> >     DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
> >     DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
> >     DISPATCH-581 - detach with closed=false propagated as closed=true on
> > link route
> >     DISPATCH-582 - Memory Leak with reactor client
> >     DISPATCH-583 - Random segmentation fault
> >     DISPATCH-585 - Firefox dropdown and buttons on list page have
> > incorrect padding
> >     DISPATCH-586 - Dispatch crash on running c sender and receiver
> >     DISPATCH-587 - Provide feedback when loading log entries
> >     DISPATCH-588 - Schema is not loaded if auto-login is enabled
> >     DISPATCH-589 - Missing links on topology page
> >     DISPATCH-594 - Log file over-written every time the router is restarted
> >     DISPATCH-595 - dispositions propagated after link detach on link route
> >     DISPATCH-596 - error is lost from rejected state in relayed disposition
> >     DISPATCH-598 - Router crash when calling sender and session close
> > methods in onLinkFLow()
> >     DISPATCH-599 - Link routing : messages is not transferred if sender
> > detach link immediately
> >     DISPATCH-601 - Valgrind errors in dispatch tests
> >     DISPATCH-603 - address resource leak
> >     DISPATCH-604 - Management - Link connection-id does not match
> > identities of connections
> >     DISPATCH-605 - Memory Leak with multple sender/receivers in one session
> >     DISPATCH-607 - Handle empty response from GET-MGMT-NODES
> >     DISPATCH-608 - Links not cleaned up when a close is sent without
> > being preceeded by a detach and end
> >     DISPATCH-609 - Name attribute is duplicated in QUERY response
> >     DISPATCH-610 - crash in qdr_link_cleanup_CT
> >     DISPATCH-611 - Router core dump with old config file
> >     DISPATCH-612 - Add support for GCC equivalent compiler options
> >     DISPATCH-613 - Remove semi-colon not needed after function definition
> >     DISPATCH-614 - strerror_r on Solaris does not return char*
> >     DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
> >     DISPATCH-616 - Arithmetic operations not allowed on void * pointer
> >     DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> > _POSIX_HOST_NAME_MAX is defined instead
> >     DISPATCH-618 - Revert eventfd on Solaris
> >     DISPATCH-619 - Use memalign instead of posix_memalign which is not
> > defined on Solaris
> >     DISPATCH-620 - no-strict-aliasing is only supported with GCC
> >     DISPATCH-621 - Add missing string.h include for Solaris compiler
> >     DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> > error to avoid undefined symbol on Solaris
> >     DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> > return statement) detected on Solaris
> >     DISPATCH-624 - Add Atomic operations support on Solaris
> >     DISPATCH-626 - Add hints for getaddrinfo on Solaris
> >     DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> > linkRoute overwrites connection handle
> >     DISPATCH-631 - Tests should be made conditional to skip tests for
> > SASL features that are not available
> >     DISPATCH-633 - Creating connectors and addresses returns success
> > codes of two different types.
> >     DISPATCH-634 - Dynamic Targets are unsupported
> >     DISPATCH-635 - The Ubuntu CI tests that involve two routers are failing
> >     DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> > required; however, cmake complains with 0.14
> >     DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> > fail when cyrus-sasl-plain is not installed
> >     DISPATCH-640 - containerId field conflics with the connector name
> >     DISPATCH-642 - Fix recognition of Artemis broker on topology page
> >     DISPATCH-643 - Duplicate log messages show up on normal AMQP close
> >     DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> > pipe issue in Daemon mode
> >     DISPATCH-646 - Link route tests which test the drain feature fail
> > intermittently
> >     DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> > master
> >     DISPATCH-727 - qdmanage identity reporting and lookup are broken
> >     DISPATCH-728 - crash on shutdown with connector
> >     DISPATCH-729 - password-file option doesn't work correctly
> >     DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
> >     DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> > but is missing from log schema
> >     DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> > intermittently
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> 
> --
> Ted Ross
> Senior Principal Software Engineer
> Red Hat
> 314 Littleton Road
> Westford, MA 01886
> tross@redhat.com     T: +1-978-392-3950     M: +1-978-399-4122
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
> 
> 

-- 
-K

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Qpid Dispatch Router 0.8.0 Release Candidate 2

Posted by Ted Ross <tr...@redhat.com>.
I've built Qpid Dispatch Router 0.8.0 RC2.  The following issues have 
been resolved since RC1:

     DISPATCH-735 - Crash on startup parsing JSON conf file with 
"address" entity
     DISPATCH-736 - 3 system tests in the test suite are failing on RHEL 6.4
     DISPATCH-740 - Remove tooltipsy.min.js and code associated with it

Build Artifacts:

     https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc2/

I will start a vote for this release candidate tomorrow if I don't hear 
any complaints.

Thanks,

-Ted

On 03/29/2017 07:32 AM, Ted Ross wrote:
> The first release candidate for Qpid Dispatch Router 0.8.0 is ready for
> evaluation.
>
> Build Artifacts:
>
>     https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/
>
> New Features:
>
>     DISPATCH-103 - Websocket Listeners
>     DISPATCH-195 - Add support for transactional messages in the Router
>     DISPATCH-441 - Support password environment variable in qdrouter config
>     DISPATCH-467 - Terminus renaming for autoLinks
>     DISPATCH-529 - Address annotation for Multi-Tenancy
>     DISPATCH-726 - Connection Property for Failover Servers
>
> Improvements:
>
>     DISPATCH-113 - expose NodeTracker::last_topology_change in management
>     DISPATCH-542 - Popup text for clients should indicate if the client
> is a sender or receiver
>     DISPATCH-543 - Initial load of topology page fetches too much
> information
>     DISPATCH-544 - Add ability to hide the info panel on the left of the
> topology page
>     DISPATCH-552 - Allow only one tree node to be expanded if there is a
> large number of routers
>     DISPATCH-553 - Add statistic counter to the "log" entity to count
> log events per severity
>     DISPATCH-559 - qdstat - Request only the columns that will be used
> in the display
>     DISPATCH-561 - Create python program that returns fake management data
>     DISPATCH-568 - Iterator module cleanup
>     DISPATCH-570 - Add some counts to qdstat -g
>     DISPATCH-572 - Adding log info with proton transport id and related
> remote IP/port
>     DISPATCH-576 - Use new log entity statistic counter in console
>     DISPATCH-578 - Dispatch trace logging forces all proton tracing on
>     DISPATCH-579 - Expose software version via management
>     DISPATCH-592 - Attempt to auto-login to the host:port that served
> the web page
>     DISPATCH-597 - Log enhancements
>     DISPATCH-600 - Support secure websockets
>     DISPATCH-602 - Add a favicon to the stand-alone router site
>     DISPATCH-606 - Default session window is too small, causing
> performance bottlenecks
>     DISPATCH-627 - BatchedSettlement test fails with timeout on slower
> systems
>     DISPATCH-629 - Add a protocol-version to the inter-router protocol
> to enable backward compatibility
>     DISPATCH-641 - Make containerId attribute work with clients
>
> Bugs Fixed:
>
>     DISPATCH-55 - Qdrouterd does not exit when service port is unavailable
>     DISPATCH-216 - system_tests_protocol_family fails on systems with no
> IPv6
>     DISPATCH-296 - segfault on router startup
>     DISPATCH-301 - Some unit tests fail with workerThreads are set to 4
>     DISPATCH-314 - If a router has a normal listener, show it in a
> different color on the topology page
>     DISPATCH-324 - Improve initial layout of topology node
>     DISPATCH-344 - memory growth after repeated calls from qdstat -m
>     DISPATCH-352 - Crash with empty configuration file
>     DISPATCH-355 - query fails with what seems to be the error of a
> previous command
>     DISPATCH-357 - Address field is empty for link routed links in the
> qdstat "links" output
>     DISPATCH-433 - Navigating to console from bookmark displays empty
> page with just toolbars
>     DISPATCH-451 - [AMQP] Hard coded session capacity should be
> configurable
>     DISPATCH-503 - [display_name] successful test runs  have non-ascii
> characters in router log
>     DISPATCH-504 - [display_name] successful test runs have invalid
> message errors  in router log
>     DISPATCH-506 - Detach with no "error" sent by router on client TCP
> connection dropped
>     DISPATCH-516 - Core dump when displayname IO adapter receives
> message with no reply-to
>     DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch
> 0.7.0
>     DISPATCH-527 - The $displayname address is currently available. It
> should not be available to external users
>     DISPATCH-530 - Cannot connect using Firefox 48+
>     DISPATCH-534 - Node selection and location is lost when the topology
> changes
>     DISPATCH-536 - Circular buffer overflow errors occur when there are
> a large number of routers
>     DISPATCH-538 - Highlighted path between routers sometimes doesn't
> unhighlight
>     DISPATCH-540 - Clients with both in and out links are rendered in
> yellow
>     DISPATCH-541 - Highlighted path between routers contains black arrows
>     DISPATCH-546 - Crosssection popup position is incorrect
>     DISPATCH-547 - Stand-alone version can't download generated config
> file for new nodes
>     DISPATCH-554 - Topology nodes and links are too far apart when there
> are a large number of routers
>     DISPATCH-556 - qdstat fails at high scale
>     DISPATCH-557 - High connection rates cause problems in the Python
> management agent
>     DISPATCH-560 - [console] Only use the color red to indicate a
> failure/issue.
>     DISPATCH-563 - Topology graph flashes and redraws a few seconds
> after it is 1st drawn
>     DISPATCH-564 - Error when switching routers on Entities page
>     DISPATCH-565 - Error fetching log on Entities page
>     DISPATCH-566 - Message annotations are not propagated to brokers on
> a linkRoute
>     DISPATCH-567 - Slight but persistent memory leak when running java
> messenger producer and consumer
>     DISPATCH-569 - Dispatch does not compile due to new pn_event_type_t
> enum values.
>     DISPATCH-573 - Memory leaks on shutdown
>     DISPATCH-574 - Restore Qpid dispatch docs into man and book folders
>     DISPATCH-577 - Server logs show unexpected POLLNVAL errors.
>     DISPATCH-581 - detach with closed=false propagated as closed=true on
> link route
>     DISPATCH-582 - Memory Leak with reactor client
>     DISPATCH-583 - Random segmentation fault
>     DISPATCH-585 - Firefox dropdown and buttons on list page have
> incorrect padding
>     DISPATCH-586 - Dispatch crash on running c sender and receiver
>     DISPATCH-587 - Provide feedback when loading log entries
>     DISPATCH-588 - Schema is not loaded if auto-login is enabled
>     DISPATCH-589 - Missing links on topology page
>     DISPATCH-594 - Log file over-written every time the router is restarted
>     DISPATCH-595 - dispositions propagated after link detach on link route
>     DISPATCH-596 - error is lost from rejected state in relayed disposition
>     DISPATCH-598 - Router crash when calling sender and session close
> methods in onLinkFLow()
>     DISPATCH-599 - Link routing : messages is not transferred if sender
> detach link immediately
>     DISPATCH-601 - Valgrind errors in dispatch tests
>     DISPATCH-603 - address resource leak
>     DISPATCH-604 - Management - Link connection-id does not match
> identities of connections
>     DISPATCH-605 - Memory Leak with multple sender/receivers in one session
>     DISPATCH-607 - Handle empty response from GET-MGMT-NODES
>     DISPATCH-608 - Links not cleaned up when a close is sent without
> being preceeded by a detach and end
>     DISPATCH-609 - Name attribute is duplicated in QUERY response
>     DISPATCH-610 - crash in qdr_link_cleanup_CT
>     DISPATCH-611 - Router core dump with old config file
>     DISPATCH-612 - Add support for GCC equivalent compiler options
>     DISPATCH-613 - Remove semi-colon not needed after function definition
>     DISPATCH-614 - strerror_r on Solaris does not return char*
>     DISPATCH-615 - SunStudio doesn't convert pointers to bool correctly
>     DISPATCH-616 - Arithmetic operations not allowed on void * pointer
>     DISPATCH-617 - Define HOST_NAME_MAX on Unix OSes where
> _POSIX_HOST_NAME_MAX is defined instead
>     DISPATCH-618 - Revert eventfd on Solaris
>     DISPATCH-619 - Use memalign instead of posix_memalign which is not
> defined on Solaris
>     DISPATCH-620 - no-strict-aliasing is only supported with GCC
>     DISPATCH-621 - Add missing string.h include for Solaris compiler
>     DISPATCH-622 - use "-lpthread" instead of "-pthread" as compiler
> error to avoid undefined symbol on Solaris
>     DISPATCH-623 - Unreachable code (qd_field_iterator_free after a
> return statement) detected on Solaris
>     DISPATCH-624 - Add Atomic operations support on Solaris
>     DISPATCH-626 - Add hints for getaddrinfo on Solaris
>     DISPATCH-628 - [PATCH] Multiple connections per autoLink and
> linkRoute overwrites connection handle
>     DISPATCH-631 - Tests should be made conditional to skip tests for
> SASL features that are not available
>     DISPATCH-633 - Creating connectors and addresses returns success
> codes of two different types.
>     DISPATCH-634 - Dynamic Targets are unsupported
>     DISPATCH-635 - The Ubuntu CI tests that involve two routers are failing
>     DISPATCH-636 - README claims qpid-proton-c-devel >= 0.13 is
> required; however, cmake complains with 0.14
>     DISPATCH-637 - system_tests_sasl_plain and system_tests_deprecated
> fail when cyrus-sasl-plain is not installed
>     DISPATCH-640 - containerId field conflics with the connector name
>     DISPATCH-642 - Fix recognition of Artemis broker on topology page
>     DISPATCH-643 - Duplicate log messages show up on normal AMQP close
>     DISPATCH-644 - Fix qdrouterd generating exit code 1 because of a
> pipe issue in Daemon mode
>     DISPATCH-646 - Link route tests which test the drain feature fail
> intermittently
>     DISPATCH-647 - Coverity scan reported memory leaks in Qpid Dispatch
> master
>     DISPATCH-727 - qdmanage identity reporting and lookup are broken
>     DISPATCH-728 - crash on shutdown with connector
>     DISPATCH-729 - password-file option doesn't work correctly
>     DISPATCH-730 - Coverity scan reported errors in Qpid Dispatch master
>     DISPATCH-732 - CONN_MGR log module is used in connection_manager.c
> but is missing from log schema
>     DISPATCH-733 - First ssl test in system_tests_qdmanage.py fails
> intermittently
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

-- 
Ted Ross
Senior Principal Software Engineer
Red Hat
314 Littleton Road
Westford, MA 01886
tross@redhat.com     T: +1-978-392-3950     M: +1-978-399-4122

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org