[GitHub] [qpid-dispatch] ganeshmurthy commented on issue #521: Dispatch 1359 2
ganeshmurthy commented on issue #521: Dispatch 1359 2 URL: https://github.com/apache/qpid-dispatch/pull/521#issuecomment-501084509 @ChugR , your commit seems to piggy back on my commit. Can you please pull your changes into your single commit and push it to master branch ? Thanks This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] ChugR opened a new pull request #521: Dispatch 1359 2
ChugR opened a new pull request #521: Dispatch 1359 2 URL: https://github.com/apache/qpid-dispatch/pull/521 Rehash of ganeshmurthy's PR with: * convenience of specifying timeouts on cmake command line * hiding magic numbers in cmake variables This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] ganeshmurthy closed pull request #520: DISPATCH-1359 - Set timeout on system tests to 300 seconds and rest o…
ganeshmurthy closed pull request #520: DISPATCH-1359 - Set timeout on system tests to 300 seconds and rest o… URL: https://github.com/apache/qpid-dispatch/pull/520 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1359) Set ctest timeout to 300 seconds.
[ https://issues.apache.org/jira/browse/DISPATCH-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861497#comment-16861497 ] ASF GitHub Bot commented on DISPATCH-1359: -- ganeshmurthy commented on pull request #520: DISPATCH-1359 - Set timeout on system tests to 300 seconds and rest o… URL: https://github.com/apache/qpid-dispatch/pull/520 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Set ctest timeout to 300 seconds. > - > > Key: DISPATCH-1359 > URL: https://issues.apache.org/jira/browse/DISPATCH-1359 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Minor > > Currently when running system tests, ctest has a default timeout of 1500 > seconds which is way too long. So for example, system_tests_edge_router if it > should hang for some reason, gets terminated by ctest only after 1500 seconds > (25 mins). This is way too long. > We need to set a smaller more reasonable timeout per test for ctest. > system_tests_edge_router is the longest executing test in the test suite. > Looking at how long it takes to execute on a slow Travis system, we have > reached the conclusion that 300 seconds would be a good timeout value for > ctest. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1365) Table of links with delayed deliveries is showing all endpoint links
Ernest Allen created DISPATCH-1365: -- Summary: Table of links with delayed deliveries is showing all endpoint links Key: DISPATCH-1365 URL: https://issues.apache.org/jira/browse/DISPATCH-1365 Project: Qpid Dispatch Issue Type: Bug Components: Console Affects Versions: 1.8.0 Reporter: Ernest Allen Assignee: Ernest Allen On the console's overview page, the table that should show only the endpoint links with delayed deliveries is showing all endpoint links. The table should be filtered to only show enpoint links where the number of delayed deliveries has increased in the last minute. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1364) "make install" does not install qpid_dispatch[_site.py] files in the correct location
[
https://issues.apache.org/jira/browse/DISPATCH-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated DISPATCH-1364:
-
Description:
Building and install qdr from source (cmake ; make install) ends up
putting qdr's python library modules in the wrong directory (not in the default
python search path).
Specifically, these files are incorrectly installed in a "site-packages"
sub-directory:
By default ubuntu's python does not use "site-packages" for installing 3rd
party python packages - it uses "dist-packages" instead.
The default python paths in ubuntu are:
{quote}>>> import sys
>>> sys.path
['', '/usr/lib/python36.zip', '/usr/lib/python3.6',
'/usr/lib/python3.6/lib-dynload', *'/usr/local/lib/python3.6/dist-packages'*,
'/usr/lib/python3/dist-packages']
{quote}
For example, proton correctly puts its python files in
/usr/local/lib/python3.6/dist-packages/
on ubuntu, while dispatch drops its packages into
/usr/local/lib/python3.6/site-packages/
was:
Building and install qdr from source (cmake ; make install) ends up
putting qdr's python library modules in the wrong directory (not in the default
python search path).
Specifically, these files are incorrectly installed in
/usr/lib/python3.6/site-packages when -DCMAKE_INSTALL_PREFIX=/usr
The default python paths in ubuntu are:
{quote}>>> import sys
>>> sys.path
['', '/usr/lib/python36.zip', '/usr/lib/python3.6',
'/usr/lib/python3.6/lib-dynload', '/usr/local/lib/python3.6/dist-packages',
'/usr/lib/python3/dist-packages']
{quote}
For example proton puts its python files in
/usr/local/lib/python3.6/dist-packages/
when the same /usr install prefix is used.
> "make install" does not install qpid_dispatch[_site.py] files in the correct
> location
> -
>
> Key: DISPATCH-1364
> URL: https://issues.apache.org/jira/browse/DISPATCH-1364
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tools
>Affects Versions: 1.8.0
>Reporter: Ken Giusti
>Priority: Major
> Fix For: 1.9.0
>
>
> Building and install qdr from source (cmake ; make install) ends up
> putting qdr's python library modules in the wrong directory (not in the
> default python search path).
> Specifically, these files are incorrectly installed in a "site-packages"
> sub-directory:
> By default ubuntu's python does not use "site-packages" for installing 3rd
> party python packages - it uses "dist-packages" instead.
> The default python paths in ubuntu are:
> {quote}>>> import sys
> >>> sys.path
> ['', '/usr/lib/python36.zip', '/usr/lib/python3.6',
> '/usr/lib/python3.6/lib-dynload', *'/usr/local/lib/python3.6/dist-packages'*,
> '/usr/lib/python3/dist-packages']
> {quote}
>
> For example, proton correctly puts its python files in
> /usr/local/lib/python3.6/dist-packages/
> on ubuntu, while dispatch drops its packages into
> /usr/local/lib/python3.6/site-packages/
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[RESULT] [VOTE] Release Apache Qpid Dispatch 1.8.0
There were 5 binding +1 votes, no other votes received. The vote has passed. I will add the files to the dist release repo and create the final tag shortly. The website will be updated after the release has had time to sync to the mirrors. Thanks to everybody for testing/voting. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1)
+1 * Validated signatures and checksums * Checked for presence of LICENSE and NOTICE files * Ran mvn apache-rat:check, no files with missing license headers found. * Built from source against Proton 0.28.0 in Fedora 29 and ran system tests. On Fri, Jun 7, 2019 at 11:23 AM Ganesh Murthy wrote: > > Hello All, > Please cast your vote on this thread to release RC1 as the > official Qpid Dispatch Router version 1.8.0. > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > The following features, improvements, and bug fixes are introduced in 1.8.0: > > Features - >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > Improvements - > DISPATCH-1308 - Console access to the force-close a connection feature > DISPATCH-1320 - Make it easier to use separate logos for upstream > and downstream masthead > DISPATCH-1321 - Set rpath for qpid-proton (and other dependencies) > when they are found in nonstandard location > DISPATCH-1329 - Edge router system test needs skip test convenience > switches > DISPATCH-1340 - Show settlement rate and delayed deliveries in client > popup > DISPATCH-1341 - Add list of delayed links to console's overview page > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > DISPATCH-1356 - Remove the dotted line around routers that > indicates the router is fixed. > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > Bug fixes - > DISPATCH-974 - Getting connections via the router management > protocol causes AMQP framing errors > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - system_tests_ssl > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > DISPATCH-1317 - HTTP system test is failing on python2.6 > DISPATCH-1318 - edge_router system test failing > DISPATCH-1322 - Edge router drops disposition when remote receiver closes > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > autoLink entity. Add address and externalAddress instead. > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape function > DISPATCH-1325 - Sender connections to edge router that connect > 'too soon' never get credit > DISPATCH-1326 - Anonymous messages are released by edge router > even if there is a receiver for the messages > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > decrement on link detach > DISPATCH-1334 - Background map on topology page incorrect height > DISPATCH-1335 - After adding client, topology page shows new icon > in upper-left corner > DISPATCH-1339 - Multiple consoles attached to a router are showing > as separate icons > > > Thanks. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1362) Shutdown crash when trying to clean up fallback addresses
[
https://issues.apache.org/jira/browse/DISPATCH-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-1362:
---
Fix Version/s: 1.9.0
> Shutdown crash when trying to clean up fallback addresses
> -
>
> Key: DISPATCH-1362
> URL: https://issues.apache.org/jira/browse/DISPATCH-1362
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
>Priority: Major
> Fix For: 1.9.0
>
>
> The following backtrace is occasionally seen when the router is being
> shutdown during the system_tests_fallback_dest
>
> {noformat}
> (gdb) bt
> #0 0x7f32afe4757f in raise () from /lib64/libc.so.6
> #1 0x7f32afe31895 in abort () from /lib64/libc.so.6
> #2 0x7f32afe8a9c7 in __libc_message () from /lib64/libc.so.6
> #3 0x7f32afe912cc in malloc_printerr () from /lib64/libc.so.6
> #4 0x7f32afe951ee in free_check.part () from /lib64/libc.so.6
> #5 0x7f32b051ba59 in qd_hash_remove_by_handle (h=,
> handle=) at
> /home/gmurthy/opensource/qpid-dispatch/src/hash.c:328
> #6 0x7f32b0540cbc in qdr_core_remove_address (core=core@entry=0x1b02230,
> addr=0x1b210d8) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:492
> #7 0x7f32b05347eb in qdr_check_addr_CT (addr=,
> core=0x1b02230) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:1176
> #8 qdr_check_addr_CT (core=core@entry=0x1b02230, addr=) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:1158
> #9 0x7f32b0540dbc in qdr_core_remove_address (core=core@entry=0x1b02230,
> addr=0x1b21318) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:524
> #10 0x7f32b0541420 in qdr_core_free (core=0x1b02230) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:148
> #11 0x7f32b054fa23 in qd_router_free (router=0x1af3650) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_node.c:1772
> #12 0x7f32b051a2b5 in qd_dispatch_free (qd=0x16df1c0) at
> /home/gmurthy/opensource/qpid-dispatch/src/dispatch.c:359
> #13 0x004026c6 in main_process (config_path=0x7ffe3a46c069
> "INT.A.conf", python_pkgdir=, test_hooks=,
> fd=2) at /home/gmurthy/opensource/qpid-dispatch/router/src/main.c:116
> #14 0x00402409 in main (argc=5, argv=0x7ffe3a46bc08) at
> /home/gmurthy/opensource/qpid-dispatch/router/src/main.c:369{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1362) Shutdown crash when trying to clean up fallback addresses
[
https://issues.apache.org/jira/browse/DISPATCH-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved DISPATCH-1362.
Resolution: Fixed
> Shutdown crash when trying to clean up fallback addresses
> -
>
> Key: DISPATCH-1362
> URL: https://issues.apache.org/jira/browse/DISPATCH-1362
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
>Priority: Major
> Fix For: 1.9.0
>
>
> The following backtrace is occasionally seen when the router is being
> shutdown during the system_tests_fallback_dest
>
> {noformat}
> (gdb) bt
> #0 0x7f32afe4757f in raise () from /lib64/libc.so.6
> #1 0x7f32afe31895 in abort () from /lib64/libc.so.6
> #2 0x7f32afe8a9c7 in __libc_message () from /lib64/libc.so.6
> #3 0x7f32afe912cc in malloc_printerr () from /lib64/libc.so.6
> #4 0x7f32afe951ee in free_check.part () from /lib64/libc.so.6
> #5 0x7f32b051ba59 in qd_hash_remove_by_handle (h=,
> handle=) at
> /home/gmurthy/opensource/qpid-dispatch/src/hash.c:328
> #6 0x7f32b0540cbc in qdr_core_remove_address (core=core@entry=0x1b02230,
> addr=0x1b210d8) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:492
> #7 0x7f32b05347eb in qdr_check_addr_CT (addr=,
> core=0x1b02230) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:1176
> #8 qdr_check_addr_CT (core=core@entry=0x1b02230, addr=) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:1158
> #9 0x7f32b0540dbc in qdr_core_remove_address (core=core@entry=0x1b02230,
> addr=0x1b21318) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:524
> #10 0x7f32b0541420 in qdr_core_free (core=0x1b02230) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:148
> #11 0x7f32b054fa23 in qd_router_free (router=0x1af3650) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_node.c:1772
> #12 0x7f32b051a2b5 in qd_dispatch_free (qd=0x16df1c0) at
> /home/gmurthy/opensource/qpid-dispatch/src/dispatch.c:359
> #13 0x004026c6 in main_process (config_path=0x7ffe3a46c069
> "INT.A.conf", python_pkgdir=, test_hooks=,
> fd=2) at /home/gmurthy/opensource/qpid-dispatch/router/src/main.c:116
> #14 0x00402409 in main (argc=5, argv=0x7ffe3a46bc08) at
> /home/gmurthy/opensource/qpid-dispatch/router/src/main.c:369{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1362) Shutdown crash when trying to clean up fallback addresses
[
https://issues.apache.org/jira/browse/DISPATCH-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861332#comment-16861332
]
ASF subversion and git services commented on DISPATCH-1362:
---
Commit 2d42c9c645934332f1e5262fa4fa1a1cf9a30a37 in qpid-dispatch's branch
refs/heads/master from Ted Ross
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=2d42c9c ]
DISPATCH-1362 - Remove recursive call to qdr_check_addr_CT during core
shutdown. This removes a window of opportunity for an invalid free during
shutdown.
This closes #519
> Shutdown crash when trying to clean up fallback addresses
> -
>
> Key: DISPATCH-1362
> URL: https://issues.apache.org/jira/browse/DISPATCH-1362
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
>Priority: Major
>
> The following backtrace is occasionally seen when the router is being
> shutdown during the system_tests_fallback_dest
>
> {noformat}
> (gdb) bt
> #0 0x7f32afe4757f in raise () from /lib64/libc.so.6
> #1 0x7f32afe31895 in abort () from /lib64/libc.so.6
> #2 0x7f32afe8a9c7 in __libc_message () from /lib64/libc.so.6
> #3 0x7f32afe912cc in malloc_printerr () from /lib64/libc.so.6
> #4 0x7f32afe951ee in free_check.part () from /lib64/libc.so.6
> #5 0x7f32b051ba59 in qd_hash_remove_by_handle (h=,
> handle=) at
> /home/gmurthy/opensource/qpid-dispatch/src/hash.c:328
> #6 0x7f32b0540cbc in qdr_core_remove_address (core=core@entry=0x1b02230,
> addr=0x1b210d8) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:492
> #7 0x7f32b05347eb in qdr_check_addr_CT (addr=,
> core=0x1b02230) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:1176
> #8 qdr_check_addr_CT (core=core@entry=0x1b02230, addr=) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:1158
> #9 0x7f32b0540dbc in qdr_core_remove_address (core=core@entry=0x1b02230,
> addr=0x1b21318) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:524
> #10 0x7f32b0541420 in qdr_core_free (core=0x1b02230) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:148
> #11 0x7f32b054fa23 in qd_router_free (router=0x1af3650) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_node.c:1772
> #12 0x7f32b051a2b5 in qd_dispatch_free (qd=0x16df1c0) at
> /home/gmurthy/opensource/qpid-dispatch/src/dispatch.c:359
> #13 0x004026c6 in main_process (config_path=0x7ffe3a46c069
> "INT.A.conf", python_pkgdir=, test_hooks=,
> fd=2) at /home/gmurthy/opensource/qpid-dispatch/router/src/main.c:116
> #14 0x00402409 in main (argc=5, argv=0x7ffe3a46bc08) at
> /home/gmurthy/opensource/qpid-dispatch/router/src/main.c:369{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] asfgit closed pull request #519: DISPATCH-1362 - Remove recursive call to qdr_check_addr_CT during cor…
asfgit closed pull request #519: DISPATCH-1362 - Remove recursive call to qdr_check_addr_CT during cor… URL: https://github.com/apache/qpid-dispatch/pull/519 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1362) Shutdown crash when trying to clean up fallback addresses
[
https://issues.apache.org/jira/browse/DISPATCH-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861333#comment-16861333
]
ASF GitHub Bot commented on DISPATCH-1362:
--
asfgit commented on pull request #519: DISPATCH-1362 - Remove recursive call to
qdr_check_addr_CT during cor…
URL: https://github.com/apache/qpid-dispatch/pull/519
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Shutdown crash when trying to clean up fallback addresses
> -
>
> Key: DISPATCH-1362
> URL: https://issues.apache.org/jira/browse/DISPATCH-1362
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
>Priority: Major
>
> The following backtrace is occasionally seen when the router is being
> shutdown during the system_tests_fallback_dest
>
> {noformat}
> (gdb) bt
> #0 0x7f32afe4757f in raise () from /lib64/libc.so.6
> #1 0x7f32afe31895 in abort () from /lib64/libc.so.6
> #2 0x7f32afe8a9c7 in __libc_message () from /lib64/libc.so.6
> #3 0x7f32afe912cc in malloc_printerr () from /lib64/libc.so.6
> #4 0x7f32afe951ee in free_check.part () from /lib64/libc.so.6
> #5 0x7f32b051ba59 in qd_hash_remove_by_handle (h=,
> handle=) at
> /home/gmurthy/opensource/qpid-dispatch/src/hash.c:328
> #6 0x7f32b0540cbc in qdr_core_remove_address (core=core@entry=0x1b02230,
> addr=0x1b210d8) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:492
> #7 0x7f32b05347eb in qdr_check_addr_CT (addr=,
> core=0x1b02230) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:1176
> #8 qdr_check_addr_CT (core=core@entry=0x1b02230, addr=) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:1158
> #9 0x7f32b0540dbc in qdr_core_remove_address (core=core@entry=0x1b02230,
> addr=0x1b21318) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:524
> #10 0x7f32b0541420 in qdr_core_free (core=0x1b02230) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:148
> #11 0x7f32b054fa23 in qd_router_free (router=0x1af3650) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_node.c:1772
> #12 0x7f32b051a2b5 in qd_dispatch_free (qd=0x16df1c0) at
> /home/gmurthy/opensource/qpid-dispatch/src/dispatch.c:359
> #13 0x004026c6 in main_process (config_path=0x7ffe3a46c069
> "INT.A.conf", python_pkgdir=, test_hooks=,
> fd=2) at /home/gmurthy/opensource/qpid-dispatch/router/src/main.c:116
> #14 0x00402409 in main (argc=5, argv=0x7ffe3a46bc08) at
> /home/gmurthy/opensource/qpid-dispatch/router/src/main.c:369{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1359) Set ctest timeout to 300 seconds.
[ https://issues.apache.org/jira/browse/DISPATCH-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861268#comment-16861268 ] ASF GitHub Bot commented on DISPATCH-1359: -- ganeshmurthy commented on pull request #520: DISPATCH-1359 - Set timeout on system tests to 300 seconds and rest o… URL: https://github.com/apache/qpid-dispatch/pull/520 …f the tests to 10 seconds This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Set ctest timeout to 300 seconds. > - > > Key: DISPATCH-1359 > URL: https://issues.apache.org/jira/browse/DISPATCH-1359 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Minor > > Currently when running system tests, ctest has a default timeout of 1500 > seconds which is way too long. So for example, system_tests_edge_router if it > should hang for some reason, gets terminated by ctest only after 1500 seconds > (25 mins). This is way too long. > We need to set a smaller more reasonable timeout per test for ctest. > system_tests_edge_router is the longest executing test in the test suite. > Looking at how long it takes to execute on a slow Travis system, we have > reached the conclusion that 300 seconds would be a good timeout value for > ctest. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] ganeshmurthy opened a new pull request #520: DISPATCH-1359 - Set timeout on system tests to 300 seconds and rest o…
ganeshmurthy opened a new pull request #520: DISPATCH-1359 - Set timeout on system tests to 300 seconds and rest o… URL: https://github.com/apache/qpid-dispatch/pull/520 …f the tests to 10 seconds This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1364) "make install" does not install qpid_dispatch[_site.py] files in the correct location
Ken Giusti created DISPATCH-1364:
Summary: "make install" does not install qpid_dispatch[_site.py]
files in the correct location
Key: DISPATCH-1364
URL: https://issues.apache.org/jira/browse/DISPATCH-1364
Project: Qpid Dispatch
Issue Type: Bug
Components: Tools
Affects Versions: 1.8.0
Reporter: Ken Giusti
Fix For: 1.9.0
Building and install qdr from source (cmake ; make install) ends up
putting qdr's python library modules in the wrong directory (not in the default
python search path).
Specifically, these files are incorrectly installed in
/usr/lib/python3.6/site-packages when -DCMAKE_INSTALL_PREFIX=/usr
The default python paths in ubuntu are:
{quote}>>> import sys
>>> sys.path
['', '/usr/lib/python36.zip', '/usr/lib/python3.6',
'/usr/lib/python3.6/lib-dynload', '/usr/local/lib/python3.6/dist-packages',
'/usr/lib/python3/dist-packages']
{quote}
For example proton puts its python files in
/usr/local/lib/python3.6/dist-packages/
when the same /usr install prefix is used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1)
On Tue, Jun 11, 2019 at 12:21 PM Michael Goulish wrote: > executive summary: I change my vote to *+1* > > but with JIRAs. > > > OK! I have something. > > I didn't remember it, but my notes show that I have seen this exact failure > before, also after a clean install. > ( I mean the authz failure. The other one, the http failure is already > explained.) > > So this means that the problem has got to be with my machine setup --- > there is some package that the authz test requires that I do not install > after a clean OS upgrade. > > I do have a great plethora of SASL and SSL packages installed, so I don't > know what it might be, and I am having trouble tracing into the Python > code. If anyone has a clue, please let me know. > > But, since the problem is limited to the test not warning about a required > package, I will do two things: > > 1. raise a JIRA, > > 2. and change my vote to > > *+1* > YAY! Thanks Mick > > > > > On Tue, Jun 11, 2019 at 12:04 PM Ganesh Murthy wrote: > > > On Tue, Jun 11, 2019 at 11:58 AM Michael Goulish > > wrote: > > > > > Of course I will not change my vote based on a suggestion ( from me and > > > Gordon ) that the failure I am seeing might be caused by a missing > > > package. > > > > > > What I will do is start looking into this to see if that is indeed the > > > case. > > > And then we will make a change that detects and warns about that case. > > > And then I will change my vote. > > > > > Agreed, fair enough. > > > > > > > > > > > > > > On Tue, Jun 11, 2019 at 11:28 AM Chuck Rolke > wrote: > > > > > > > +1 > > > > > > > > * Checked checksums > > > > * Build/test Fedora 29, python 3 > > > > * Fails system_tests_http (known problem, not a regression) > > > > * Build/test Fedora 28, python 2 > > > > * Occasional test fail system_tests_fallback_dest > > > > known problem in new test code and not in mission code; fix is > > > already > > > > on master; not a regression > > > > > > > > > > > > - Original Message - > > > > > From: "Ganesh Murthy" > > > > > To: us...@qpid.apache.org, dev@qpid.apache.org > > > > > Sent: Friday, June 7, 2019 11:23:40 AM > > > > > Subject: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1) > > > > > > > > > > Hello All, > > > > > Please cast your vote on this thread to release RC1 as the > > > > > official Qpid Dispatch Router version 1.8.0. > > > > > > > > > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > > > > > > > > > The following features, improvements, and bug fixes are introduced > in > > > > 1.8.0: > > > > > > > > > > Features - > > > > >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > > > > > > > > > Improvements - > > > > > DISPATCH-1308 - Console access to the force-close a connection > > > > feature > > > > > DISPATCH-1320 - Make it easier to use separate logos for > upstream > > > > > and downstream masthead > > > > > DISPATCH-1321 - Set rpath for qpid-proton (and other > > dependencies) > > > > > when they are found in nonstandard location > > > > > DISPATCH-1329 - Edge router system test needs skip test > > convenience > > > > > switches > > > > > DISPATCH-1340 - Show settlement rate and delayed deliveries in > > > client > > > > > popup > > > > > DISPATCH-1341 - Add list of delayed links to console's overview > > > page > > > > > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > > > > > DISPATCH-1356 - Remove the dotted line around routers that > > > > > indicates the router is fixed. > > > > > DISPATCH-1357 - Change the name of the 'Kill' feature to > 'Close' > > > > > > > > > > Bug fixes - > > > > > DISPATCH-974 - Getting connections via the router management > > > > > protocol causes AMQP framing errors > > > > > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > > > > > system_tests_ssl > > > > > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > > > > > DISPATCH-1317 - HTTP system test is failing on python2.6 > > > > > DISPATCH-1318 - edge_router system test failing > > > > > DISPATCH-1322 - Edge router drops disposition when remote > > receiver > > > > closes > > > > > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > > > > > autoLink entity. Add address and externalAddress instead. > > > > > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape > > function > > > > > DISPATCH-1325 - Sender connections to edge router that connect > > > > > 'too soon' never get credit > > > > > DISPATCH-1326 - Anonymous messages are released by edge router > > > > > even if there is a receiver for the messages > > > > > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > > > > > decrement on link detach > > > > > DISPATCH-1334 - Background map on topology page incorrect > height > > > > > DISPATCH-1335 - After adding client,
Re: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1)
executive summary: I change my vote to *+1* but with JIRAs. OK! I have something. I didn't remember it, but my notes show that I have seen this exact failure before, also after a clean install. ( I mean the authz failure. The other one, the http failure is already explained.) So this means that the problem has got to be with my machine setup --- there is some package that the authz test requires that I do not install after a clean OS upgrade. I do have a great plethora of SASL and SSL packages installed, so I don't know what it might be, and I am having trouble tracing into the Python code. If anyone has a clue, please let me know. But, since the problem is limited to the test not warning about a required package, I will do two things: 1. raise a JIRA, 2. and change my vote to *+1* On Tue, Jun 11, 2019 at 12:04 PM Ganesh Murthy wrote: > On Tue, Jun 11, 2019 at 11:58 AM Michael Goulish > wrote: > > > Of course I will not change my vote based on a suggestion ( from me and > > Gordon ) that the failure I am seeing might be caused by a missing > > package. > > > > What I will do is start looking into this to see if that is indeed the > > case. > > And then we will make a change that detects and warns about that case. > > And then I will change my vote. > > > Agreed, fair enough. > > > > > > > > > On Tue, Jun 11, 2019 at 11:28 AM Chuck Rolke wrote: > > > > > +1 > > > > > > * Checked checksums > > > * Build/test Fedora 29, python 3 > > > * Fails system_tests_http (known problem, not a regression) > > > * Build/test Fedora 28, python 2 > > > * Occasional test fail system_tests_fallback_dest > > > known problem in new test code and not in mission code; fix is > > already > > > on master; not a regression > > > > > > > > > - Original Message - > > > > From: "Ganesh Murthy" > > > > To: us...@qpid.apache.org, dev@qpid.apache.org > > > > Sent: Friday, June 7, 2019 11:23:40 AM > > > > Subject: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1) > > > > > > > > Hello All, > > > > Please cast your vote on this thread to release RC1 as the > > > > official Qpid Dispatch Router version 1.8.0. > > > > > > > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > > > > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > > > > > > > The following features, improvements, and bug fixes are introduced in > > > 1.8.0: > > > > > > > > Features - > > > >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > > > > > > > Improvements - > > > > DISPATCH-1308 - Console access to the force-close a connection > > > feature > > > > DISPATCH-1320 - Make it easier to use separate logos for upstream > > > > and downstream masthead > > > > DISPATCH-1321 - Set rpath for qpid-proton (and other > dependencies) > > > > when they are found in nonstandard location > > > > DISPATCH-1329 - Edge router system test needs skip test > convenience > > > > switches > > > > DISPATCH-1340 - Show settlement rate and delayed deliveries in > > client > > > > popup > > > > DISPATCH-1341 - Add list of delayed links to console's overview > > page > > > > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > > > > DISPATCH-1356 - Remove the dotted line around routers that > > > > indicates the router is fixed. > > > > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > > > > > > > Bug fixes - > > > > DISPATCH-974 - Getting connections via the router management > > > > protocol causes AMQP framing errors > > > > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > > > > system_tests_ssl > > > > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > > > > DISPATCH-1317 - HTTP system test is failing on python2.6 > > > > DISPATCH-1318 - edge_router system test failing > > > > DISPATCH-1322 - Edge router drops disposition when remote > receiver > > > closes > > > > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > > > > autoLink entity. Add address and externalAddress instead. > > > > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape > function > > > > DISPATCH-1325 - Sender connections to edge router that connect > > > > 'too soon' never get credit > > > > DISPATCH-1326 - Anonymous messages are released by edge router > > > > even if there is a receiver for the messages > > > > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > > > > decrement on link detach > > > > DISPATCH-1334 - Background map on topology page incorrect height > > > > DISPATCH-1335 - After adding client, topology page shows new icon > > > > in upper-left corner > > > > DISPATCH-1339 - Multiple consoles attached to a router are > showing > > > > as separate icons > > > > > > > > > > > > Thanks. > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...
[jira] [Created] (DISPATCH-1363) Remove apache rat check from main travis build and move to a sub build
Ganesh Murthy created DISPATCH-1363: --- Summary: Remove apache rat check from main travis build and move to a sub build Key: DISPATCH-1363 URL: https://issues.apache.org/jira/browse/DISPATCH-1363 Project: Qpid Dispatch Issue Type: Bug Components: Tests Affects Versions: 1.7.0 Reporter: Ganesh Murthy Currently, when a Travis build fails, we are unable to tell if the the failure was due to the rat check failure or due to a system test failure. You have to scroll all the way to the bottom of the build output page to find out if the rat check failed. An improvement would be to move the rat check to a sub build so that it is easy to visually identify if the build failure is due to the rat check or system test failure. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1)
On Tue, Jun 11, 2019 at 11:58 AM Michael Goulish wrote: > Of course I will not change my vote based on a suggestion ( from me and > Gordon ) that the failure I am seeing might be caused by a missing > package. > > What I will do is start looking into this to see if that is indeed the > case. > And then we will make a change that detects and warns about that case. > And then I will change my vote. > Agreed, fair enough. > > > > On Tue, Jun 11, 2019 at 11:28 AM Chuck Rolke wrote: > > > +1 > > > > * Checked checksums > > * Build/test Fedora 29, python 3 > > * Fails system_tests_http (known problem, not a regression) > > * Build/test Fedora 28, python 2 > > * Occasional test fail system_tests_fallback_dest > > known problem in new test code and not in mission code; fix is > already > > on master; not a regression > > > > > > - Original Message - > > > From: "Ganesh Murthy" > > > To: us...@qpid.apache.org, dev@qpid.apache.org > > > Sent: Friday, June 7, 2019 11:23:40 AM > > > Subject: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1) > > > > > > Hello All, > > > Please cast your vote on this thread to release RC1 as the > > > official Qpid Dispatch Router version 1.8.0. > > > > > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > > > > > The following features, improvements, and bug fixes are introduced in > > 1.8.0: > > > > > > Features - > > >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > > > > > Improvements - > > > DISPATCH-1308 - Console access to the force-close a connection > > feature > > > DISPATCH-1320 - Make it easier to use separate logos for upstream > > > and downstream masthead > > > DISPATCH-1321 - Set rpath for qpid-proton (and other dependencies) > > > when they are found in nonstandard location > > > DISPATCH-1329 - Edge router system test needs skip test convenience > > > switches > > > DISPATCH-1340 - Show settlement rate and delayed deliveries in > client > > > popup > > > DISPATCH-1341 - Add list of delayed links to console's overview > page > > > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > > > DISPATCH-1356 - Remove the dotted line around routers that > > > indicates the router is fixed. > > > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > > > > > Bug fixes - > > > DISPATCH-974 - Getting connections via the router management > > > protocol causes AMQP framing errors > > > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > > > system_tests_ssl > > > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > > > DISPATCH-1317 - HTTP system test is failing on python2.6 > > > DISPATCH-1318 - edge_router system test failing > > > DISPATCH-1322 - Edge router drops disposition when remote receiver > > closes > > > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > > > autoLink entity. Add address and externalAddress instead. > > > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape function > > > DISPATCH-1325 - Sender connections to edge router that connect > > > 'too soon' never get credit > > > DISPATCH-1326 - Anonymous messages are released by edge router > > > even if there is a receiver for the messages > > > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > > > decrement on link detach > > > DISPATCH-1334 - Background map on topology page incorrect height > > > DISPATCH-1335 - After adding client, topology page shows new icon > > > in upper-left corner > > > DISPATCH-1339 - Multiple consoles attached to a router are showing > > > as separate icons > > > > > > > > > Thanks. > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > > > For additional commands, e-mail: dev-h...@qpid.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > For additional commands, e-mail: users-h...@qpid.apache.org > > > > >
Re: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1)
Of course I will not change my vote based on a suggestion ( from me and Gordon ) that the failure I am seeing might be caused by a missing package. What I will do is start looking into this to see if that is indeed the case. And then we will make a change that detects and warns about that case. And then I will change my vote. On Tue, Jun 11, 2019 at 11:28 AM Chuck Rolke wrote: > +1 > > * Checked checksums > * Build/test Fedora 29, python 3 > * Fails system_tests_http (known problem, not a regression) > * Build/test Fedora 28, python 2 > * Occasional test fail system_tests_fallback_dest > known problem in new test code and not in mission code; fix is already > on master; not a regression > > > - Original Message - > > From: "Ganesh Murthy" > > To: us...@qpid.apache.org, dev@qpid.apache.org > > Sent: Friday, June 7, 2019 11:23:40 AM > > Subject: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1) > > > > Hello All, > > Please cast your vote on this thread to release RC1 as the > > official Qpid Dispatch Router version 1.8.0. > > > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > > > The following features, improvements, and bug fixes are introduced in > 1.8.0: > > > > Features - > >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > > > Improvements - > > DISPATCH-1308 - Console access to the force-close a connection > feature > > DISPATCH-1320 - Make it easier to use separate logos for upstream > > and downstream masthead > > DISPATCH-1321 - Set rpath for qpid-proton (and other dependencies) > > when they are found in nonstandard location > > DISPATCH-1329 - Edge router system test needs skip test convenience > > switches > > DISPATCH-1340 - Show settlement rate and delayed deliveries in client > > popup > > DISPATCH-1341 - Add list of delayed links to console's overview page > > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > > DISPATCH-1356 - Remove the dotted line around routers that > > indicates the router is fixed. > > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > > > Bug fixes - > > DISPATCH-974 - Getting connections via the router management > > protocol causes AMQP framing errors > > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > > system_tests_ssl > > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > > DISPATCH-1317 - HTTP system test is failing on python2.6 > > DISPATCH-1318 - edge_router system test failing > > DISPATCH-1322 - Edge router drops disposition when remote receiver > closes > > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > > autoLink entity. Add address and externalAddress instead. > > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape function > > DISPATCH-1325 - Sender connections to edge router that connect > > 'too soon' never get credit > > DISPATCH-1326 - Anonymous messages are released by edge router > > even if there is a receiver for the messages > > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > > decrement on link detach > > DISPATCH-1334 - Background map on topology page incorrect height > > DISPATCH-1335 - After adding client, topology page shows new icon > > in upper-left corner > > DISPATCH-1339 - Multiple consoles attached to a router are showing > > as separate icons > > > > > > Thanks. > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > > For additional commands, e-mail: dev-h...@qpid.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > >
Re: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1)
+1 * Checked checksums * Build/test Fedora 29, python 3 * Fails system_tests_http (known problem, not a regression) * Build/test Fedora 28, python 2 * Occasional test fail system_tests_fallback_dest known problem in new test code and not in mission code; fix is already on master; not a regression - Original Message - > From: "Ganesh Murthy" > To: us...@qpid.apache.org, dev@qpid.apache.org > Sent: Friday, June 7, 2019 11:23:40 AM > Subject: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1) > > Hello All, > Please cast your vote on this thread to release RC1 as the > official Qpid Dispatch Router version 1.8.0. > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > The following features, improvements, and bug fixes are introduced in 1.8.0: > > Features - >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > Improvements - > DISPATCH-1308 - Console access to the force-close a connection feature > DISPATCH-1320 - Make it easier to use separate logos for upstream > and downstream masthead > DISPATCH-1321 - Set rpath for qpid-proton (and other dependencies) > when they are found in nonstandard location > DISPATCH-1329 - Edge router system test needs skip test convenience > switches > DISPATCH-1340 - Show settlement rate and delayed deliveries in client > popup > DISPATCH-1341 - Add list of delayed links to console's overview page > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > DISPATCH-1356 - Remove the dotted line around routers that > indicates the router is fixed. > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > Bug fixes - > DISPATCH-974 - Getting connections via the router management > protocol causes AMQP framing errors > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > system_tests_ssl > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > DISPATCH-1317 - HTTP system test is failing on python2.6 > DISPATCH-1318 - edge_router system test failing > DISPATCH-1322 - Edge router drops disposition when remote receiver closes > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > autoLink entity. Add address and externalAddress instead. > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape function > DISPATCH-1325 - Sender connections to edge router that connect > 'too soon' never get credit > DISPATCH-1326 - Anonymous messages are released by edge router > even if there is a receiver for the messages > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > decrement on link detach > DISPATCH-1334 - Background map on topology page incorrect height > DISPATCH-1335 - After adding client, topology page shows new icon > in upper-left corner > DISPATCH-1339 - Multiple consoles attached to a router are showing > as separate icons > > > Thanks. > > - > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2044) Azure IoT Hub local-idle-timeout expired
[
https://issues.apache.org/jira/browse/PROTON-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861093#comment-16861093
]
Andreas Fendt commented on PROTON-2044:
---
Can someone help me with that?
> Azure IoT Hub local-idle-timeout expired
>
>
> Key: PROTON-2044
> URL: https://issues.apache.org/jira/browse/PROTON-2044
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: proton-c-0.24.0
> Environment: Operating System: Windows
> Python: 3.6.4
> qpid-proton: 0.24.0
>Reporter: Andreas Fendt
>Priority: Major
>
> I'm using following python code to send messages to the devices
> (*/messages/devicebound*) which are connected to the *azure iot hub*:
> {code}
> import json
> from base64 import b64encode, b64decode
> from hashlib import sha256
> from hmac import HMAC
> from time import time
> from urllib.parse import quote_plus, urlencode
> from proton import ProtonException, Message
> from proton.utils import BlockingConnection
> class IotHub:
> def __init__(self):
> self._hostname = f"example-hub.azure-devices.net"
> self._username = f"iothubow...@sas.root.example-hub.azure-devices.net"
> self._blocking_connection = None
> self._sender = None
> self.connect()
> @staticmethod
> def generate_sas_token(uri: str, policy: str, key: str, expiry: float =
> None):
> if not expiry:
> expiry = time() + 3600 # Default to 1 hour.
> encoded_uri = quote_plus(uri)
> ttl = int(expiry)
> sign_key = f"{encoded_uri}\n{ttl}"
> signature = b64encode(HMAC(b64decode(key), sign_key.encode(),
> sha256).digest())
> result = {"sr": uri, "sig": signature, "se": str(ttl)}
> if policy:
> result["skn"] = policy
> return f"SharedAccessSignature {urlencode(result)}"
> def connect(self):
> # create credentials
> password = self.generate_sas_token(self._hostname,
> "iothubowner", "key",
> time() + 31557600) # ttl = 1 Year
> # establish connection
> self._blocking_connection =
> BlockingConnection(f"amqps://{self._hostname}", allowed_mechs="PLAIN",
> user=self._username,
> password=password,
> heartbeat=30)
> self._sender =
> self._blocking_connection.create_sender("/messages/devicebound")
> def send(self, message: dict, serial_number: str):
> message =
> Message(address="/devices/{serial_number}/messages/devicebound".format(serial_number=serial_number),
> body=bytes(json.dumps(message, separators=(",",
> ":")), "utf-8"))
> message.inferred = True # disable message encoding
> self._sender.send(message, timeout=20)
> {code}
> The problem is now that when I don't send any message for some seconds I get
> following exepction while sending a message:
> {code:java}
> Connection amqps://example-hub.azure-devices.net:amqps disconnected:
> Condition('amqp:resource-limit-exceeded', 'local-idle-timeout expired')
> {code}
> Whats the reason for that? How can I solve that?
> Thank you for help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1359) Set ctest timeout to 300 seconds.
[ https://issues.apache.org/jira/browse/DISPATCH-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860805#comment-16860805 ] Robbie Gemmell commented on DISPATCH-1359: -- If thats also possible then I would entirely agree. For the Java bits we often set a specific timeout on every individual method within the test class, not just the test class or run as a whole, for the same kind of reasons you are thinking. When I asked Ganesh if the default test file timeout could be changed, I was mainly just thinking to avoid the CI jobs being killed currently because they time out themselves before the tests actually do. The suggested 300sec was from looking at the longest test file run in a slow TravisCI job, and going for something which exceeded that (by 70sec in this case) but was still suitably under the 600sec no-output timeout that Travis kills the job after (and hopefully low enough to try not running into the overall-time limit also). Not much point having a 1500sec timeout when the CI jobs typically fail long before it ever gets that far. A more specific per-test timeout would be a much better improvement if that can be done also, fixing that issue and doing a far better job of avoiding excessive wasted time in the case of typically very fast tests. As the current timeout seems to be configurable on the command line, I'd at least pick an initial value for it thats high enough to rarely be hit (exceptionally slow CI cases can always increase it with the command line option), but low enough that they make the mechanism effective in the test envs. > Set ctest timeout to 300 seconds. > - > > Key: DISPATCH-1359 > URL: https://issues.apache.org/jira/browse/DISPATCH-1359 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.7.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Minor > > Currently when running system tests, ctest has a default timeout of 1500 > seconds which is way too long. So for example, system_tests_edge_router if it > should hang for some reason, gets terminated by ctest only after 1500 seconds > (25 mins). This is way too long. > We need to set a smaller more reasonable timeout per test for ctest. > system_tests_edge_router is the longest executing test in the test suite. > Looking at how long it takes to execute on a slow Travis system, we have > reached the conclusion that 300 seconds would be a good timeout value for > ctest. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
