[jira] [Commented] (QPIDJMS-259) Allow client to influence the attach properties of the link underlying a consumer
[
https://issues.apache.org/jira/browse/QPIDJMS-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995215#comment-16995215
]
Neeraj Makam commented on QPIDJMS-259:
--
Bumping up for visibility...
I am also looking for this change. Is there a way for vendor specific
properties to be set on performatives?
> Allow client to influence the attach properties of the link underlying a
> consumer
> -
>
> Key: QPIDJMS-259
> URL: https://issues.apache.org/jira/browse/QPIDJMS-259
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
>Reporter: Keith Wall
>Priority: Major
>
> As a user of the Qpid JMS Client, I currently have no way to enable features
> of the Qpid Broker for Java's features such as consumer priority or arrival
> time filtering.
> To enable these features for AMQP 1.0 I need a way to influence the link
> attachment properties that are sent when the JMS Consumer is created.
> In the 0-x Qpid JMS Client the Destination addresses were overloaded with
> this extra information. Binding URLs had special arguments such as
> {{x-priority='10'}} which the client, with hardcoded knowledge, knew had to
> be passed to {{basic.consume}}/{{message.subscribe}}. ADDRs were slightly
> nicer insofar as the subscribe arguments cold be set to arbitrary name/value
> pairs. Encoding the information in the address, whilst ugly, did mean users
> of the messaging integration products (such as Spring), could access the
> features without coding.
> It would be nice if the Qpid JMS Client had an unobtrusive vendor specific
> mechanism, that allows a application to influence the properties of any AMQP
> performative.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2163) Use java.util.logging to log trace frames PN_TRACE_FRM instead of stdout
[ https://issues.apache.org/jira/browse/PROTON-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish updated PROTON-2163: Priority: Minor (was: Major) > Use java.util.logging to log trace frames PN_TRACE_FRM instead of stdout > > > Key: PROTON-2163 > URL: https://issues.apache.org/jira/browse/PROTON-2163 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: proton-j-0.33.3 >Reporter: Connie Yau >Priority: Minor > Original Estimate: 2m > Remaining Estimate: 2m > > If PN_TRACE_FRM=1, the AMQP trace frames are logged to standard out. It would > be nice to use java.util.logging.Logger so customers have the option of > logging to a text file instead of STDOUT. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2163) Use java.util.logging to log trace frames PN_TRACE_FRM instead of stdout
[
https://issues.apache.org/jira/browse/PROTON-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995014#comment-16995014
]
Timothy A. Bish commented on PROTON-2163:
-
The library already supports an option for those who want to capture frame data
via a logging framework like the JUL logger or an abstraction library like
slf4j. The
[ProtocolTracer|https://github.com/apache/qpid-proton-j/blob/master/proton-j/src/main/java/org/apache/qpid/proton/engine/impl/ProtocolTracer.java]
interface in the proton-j library can be set on the Transport and your logging
can then write out frame data based on configuration. We use this approach in
the Qpid JMS client and other projects like ActiveMQ use it as well.
You could use the tracer as follows, tailoring the output to your own desired
format:
{code:java}
if (isTraceFrames()) {
((TransportImpl) protonTransport).setProtocolTracer(new ProtocolTracer() {
@Override
public void receivedFrame(TransportFrame transportFrame) {
TRACE_FRAMES.trace("RECV: {}", transportFrame.getBody());
}
@Override
public void sentFrame(TransportFrame transportFrame) {
TRACE_FRAMES.trace("SENT: {}", transportFrame.getBody());
}
});
}{code}
> Use java.util.logging to log trace frames PN_TRACE_FRM instead of stdout
>
>
> Key: PROTON-2163
> URL: https://issues.apache.org/jira/browse/PROTON-2163
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Affects Versions: proton-j-0.33.3
>Reporter: Connie Yau
>Priority: Major
> Original Estimate: 2m
> Remaining Estimate: 2m
>
> If PN_TRACE_FRM=1, the AMQP trace frames are logged to standard out. It would
> be nice to use java.util.logging.Logger so customers have the option of
> logging to a text file instead of STDOUT.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2163) Use java.util.logging to log trace frames PN_TRACE_FRM instead of stdout
Connie Yau created PROTON-2163: -- Summary: Use java.util.logging to log trace frames PN_TRACE_FRM instead of stdout Key: PROTON-2163 URL: https://issues.apache.org/jira/browse/PROTON-2163 Project: Qpid Proton Issue Type: Improvement Components: proton-j Affects Versions: proton-j-0.33.3 Reporter: Connie Yau If PN_TRACE_FRM=1, the AMQP trace frames are logged to standard out. It would be nice to use java.util.logging.Logger so customers have the option of logging to a text file instead of STDOUT. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[VOTE] Release Qpid Dispatch Router 1.10.0 (RC1)
Hello All, Please cast your vote on this thread to release RC1 as the official Qpid Dispatch Router version 1.10.0. RC1 of Qpid Dispatch Router version 1.10.0 can be found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.10.0-rc1/ The following features, improvements, and bug fixes are introduced in 1.10.0: Features - DISPATCH-1441 - optparse python library deprecated, migrate to argparse DISPATCH-1442 - Add a metadata field to the router management entity DISPATCH-1463 - Detect deliveries that are stuck in the router for a long time DISPATCH-1467 - Add build option to enable Address Sanitizer build (ASAN) Improvements - DISPATCH-1186 - qdstat to include csv output format DISPATCH-1358 - Port console to patternfly 4 / React DISPATCH-1369 - Update console dependencies to avoid npm security warnings DISPATCH-1399 - Allow arrows on console's topology page to be disabled DISPATCH-1409 - Update qdstat -l output to include the current credit DISPATCH-1411 - Add timestamp and router name to header of qdstat output DISPATCH-1412 - Policy C code performance issue: reload python module for each call DISPATCH-1416 - Policy log could include denial counts on connection close DISPATCH-1419 - Add status to connector mgmt schema DISPATCH-1427 - Allow policy to define user (group) specific connection limits DISPATCH-1434 - Add new attribute saslPasswordFile to the connector entity DISPATCH-1438 - Have ctest parse the routers debug dump files for memory pool leaks DISPATCH-1439 - Expose create time/last transfer time through the Connection management entity DISPATCH-1440 - Deprecate the passwordFile field in sslProfile and consolidate all password scenarios to use the password field DISPATCH-1445 - Update saslPassword attribute in connector entity to use openssl style prefixes DISPATCH-1446 - system_tests_qdmanage failing on test_get_log DISPATCH-1450 - Add build option to enable thread sanitizer build DISPATCH-1454 - system_tests_one_router failing due to changes in qpid-proton DISPATCH-1455 - Two system tests failing after optparse to argparse migration DISPATCH-1465 - system_tests_policy.test_verify_z_connection_stats fails DISPATCH-1466 - flake8 errors in system_test.py DISPATCH-1471 - [test] When string comparison asserts fail the strings are not printed DISPATCH-1480 - Address Sanitizer leak in system_tests_multi_phase DISPATCH-1491 - bottleneck adding or removing addresses in mobile address engine DISPATCH-1500 - inefficiencies in handling large MAU messages DISPATCH-1507 - Don't collapse small number of edge routers and clients into single circle DISPATCH-1516 - Trace log the peer delivery id and link id when linking and unlinking peers Bug fixes - DISPATCH-1172 - Link routes and auto links activated on wrong connections if many route-container conns exist DISPATCH-1258 - Crash executing http test DISPATCH-1377 - system_tests_topology_disposition failing on machine with python3 only DISPATCH-1418 - The default forwarding treatment is not overridden by the treatment in the address configuration DISPATCH-1421 - Attaching link to unavailable address sets source address to null in attach reply DISPATCH-1423 - Multicast sender with no receiver has first 250 messages released DISPATCH-1426 - Repetitive receiver fail over causes memory leak DISPATCH-1428 - route connection not indexed by 'connection' field of connector DISPATCH-1431 - system_tests_one_router_failing on test_19_semantics_multicast DISPATCH-1433 - system_tests_delivery_abort failing due to receiver connecting late DISPATCH-1443 - Unable to run ctest on Centos 8 DISPATCH-1453 - Adding "defaultDistribution: unavailable" overrides the regular handling of transaction coordinator link refusal DISPATCH-1460 - Router control messages for local subscribers hang in Q2 holdoff DISPATCH-1461 - Crashed router due to terminus address overflow DISPATCH-1462 - [policy] Test for IPv6 leaves socket open DISPATCH-1468 - out-of-bounds array access in qd_entity_refresh_connector DISPATCH-1473 - [test] test_command fail on python 2.7 DISPATCH-1474 - Console message path skips one router hop DISPATCH-1475 - Seg fault in qdr_link_cleanup_CT after 12,400+ connections DISPATCH-1476 - [tools] New proton logging breaks Scraper DISPATCH-1477 - Crash router by deleting authServicePlugin entity through management call DISPATCH-1481 - Multicast producers should block on credit until consumers are present DISPATCH-1483 - Link counters for dispositions are not incremented for outgoing links DISPATCH-1485 - qdstat --limit 0 seems to cause infinit loop DISPATCH-1488 - link-routed transaction coordination broken due to 'declared' state truncation DISPATCH-1492 - Router asserts when client connects to edge listener DISPATCH-1493 - qdst
[GitHub] [qpid-dispatch] dependabot[bot] commented on issue #624: Bump angular from 1.5.11 to 1.7.9 in /console/stand-alone
dependabot[bot] commented on issue #624: Bump angular from 1.5.11 to 1.7.9 in /console/stand-alone URL: https://github.com/apache/qpid-dispatch/pull/624#issuecomment-565128011 Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`. 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] [Updated] (DISPATCH-1450) Add build option to enable thread sanitizer build
[ https://issues.apache.org/jira/browse/DISPATCH-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1450: Issue Type: Improvement (was: Test) > Add build option to enable thread sanitizer build > - > > Key: DISPATCH-1450 > URL: https://issues.apache.org/jira/browse/DISPATCH-1450 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Tests >Affects Versions: 1.9.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Labels: tsan > Fix For: 1.10.0 > > > Update cmake to support building qdrouterd with thread sanitizing turned on > (tsan). > This should be configurable via a cmake option (default to off). > See the proton cmake files for a guide. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1485) qdstat --limit 0 seems to cause infinit loop
[ https://issues.apache.org/jira/browse/DISPATCH-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1485: Issue Type: Bug (was: New Feature) > qdstat --limit 0 seems to cause infinit loop > > > Key: DISPATCH-1485 > URL: https://issues.apache.org/jira/browse/DISPATCH-1485 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tools >Affects Versions: 1.9.0 >Reporter: Gordon Sim >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.10.0 > > > I tried 0 as the value for --limit hopeing it would imply unlimited (seems a > little nicer than picking some arbitrary large number). The client seems to > go into an infinit loop of some kind, never exiting and burning up lots of > cpu and eventually memory. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1467) Add build option to enable Address Sanitizer build (ASAN)
[ https://issues.apache.org/jira/browse/DISPATCH-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1467: Issue Type: New Feature (was: Task) > Add build option to enable Address Sanitizer build (ASAN) > - > > Key: DISPATCH-1467 > URL: https://issues.apache.org/jira/browse/DISPATCH-1467 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Tests >Affects Versions: 1.9.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.10.0 > > > Work item. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] dependabot[bot] commented on issue #624: Bump angular from 1.5.11 to 1.7.9 in /console/stand-alone
dependabot[bot] commented on issue #624: Bump angular from 1.5.11 to 1.7.9 in /console/stand-alone URL: https://github.com/apache/qpid-dispatch/pull/624#issuecomment-565114292 Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`. 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] (PROTON-2162) [c] Regression with aborted transfers: connection closes with framing error
Charles E. Rolke created PROTON-2162:
Summary: [c] Regression with aborted transfers: connection closes
with framing error
Key: PROTON-2162
URL: https://issues.apache.org/jira/browse/PROTON-2162
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: proton-c-0.29.0
Environment: Fedora 29, debug build
Reporter: Charles E. Rolke
Using normal example code:
* run build/cpp/examples/direct_recv
* run build/c/examples/send-abort
Tested against 0.27.1, 0.28.0, 0.29.0, and 0.30.1-rc1
In all cases direct_recv exits with a 'receiver read failure' upon receiving
the first aborted transfer.
In older versions (before 0.30.x) send_abort receives a close with error:
{noformat}
0 -> @close(24) [error=@error(29) [condition=:"proton:io",
description="Connection reset by peer - on write to :5672 (connection
aborted)"]]
{noformat}
In the 0.30.1-rc1 version the send_abort receives a close with error:
{noformat}
AMQP:FRAME:0 -> @close(24) [error=@error(29)
[condition=:"amqp:connection:framing-error", description="connection aborted"]]
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-proton] ssorj commented on issue #223: Fix errors in the Python tutorial
ssorj commented on issue #223: Fix errors in the Python tutorial URL: https://github.com/apache/qpid-proton/pull/223#issuecomment-565062157 That looks great! Ship it, I say. 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] [Updated] (DISPATCH-1186) qdstat to include csv output format
[ https://issues.apache.org/jira/browse/DISPATCH-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1186: Affects Version/s: 1.9.0 > qdstat to include csv output format > --- > > Key: DISPATCH-1186 > URL: https://issues.apache.org/jira/browse/DISPATCH-1186 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Management Agent >Affects Versions: 1.4.1, 1.9.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.10.0 > > > qdstat text output is difficult to manage after a cut and paste. For > instance, _qdstat -l_ shows some rows where the columns are blank. This > makes it difficult to reconstruct the original display given just the body > text. See _qdstat -l_ example in > [https://raw.githubusercontent.com/apache/qpid-dispatch/master/docs/books/user-guide/monitoring-using-qdstat.adoc] > Even having a two-word column title "conn id" adds confusion. > With a CSV format and quoted strings this table could be communicated through > email, chat, or Jira with authority. Readers would not have to guess about > which data goes in which columns. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1369) Update console dependencies to avoid npm security warnings
[ https://issues.apache.org/jira/browse/DISPATCH-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1369: Issue Type: Improvement (was: Task) > Update console dependencies to avoid npm security warnings > -- > > Key: DISPATCH-1369 > URL: https://issues.apache.org/jira/browse/DISPATCH-1369 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 1.8.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > Labels: security > Fix For: 1.10.0 > > > Running npm audit in the stand-alone console directory results in 51 moderate > security warnings. > The underlying npm package dependencies should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1377) system_tests_topology_disposition failing on machine with python3 only
[
https://issues.apache.org/jira/browse/DISPATCH-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1377:
Issue Type: Bug (was: Improvement)
> system_tests_topology_disposition failing on machine with python3 only
> --
>
> Key: DISPATCH-1377
> URL: https://issues.apache.org/jira/browse/DISPATCH-1377
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.8.0
>Reporter: Ganesh Murthy
>Assignee: Charles E. Rolke
>Priority: Major
> Fix For: 1.10.0
>
>
> The following is the output of the test failure
>
> {noformat}
> Stacktrace
> test_01_delete_spurious_connector
> (system_tests_topology_disposition.TopologyDispositionTests) ... ok
> test_02_topology_disposition
> (system_tests_topology_disposition.TopologyDispositionTests) ... ok
> test_03_connection_id_propagation
> (system_tests_topology_disposition.TopologyDispositionTests) ... ok
> test_04_scraper_tool
> (system_tests_topology_disposition.TopologyDispositionTests) ... FAIL
> ==
> FAIL: test_04_scraper_tool
> (system_tests_topology_disposition.TopologyDispositionTests)
> --
> Traceback (most recent call last):
> File "/opt/interconnect-src/tests/system_tests_topology_disposition.py",
> line 459, in test_04_scraper_tool
> self.assertEqual ( None, error )
> AssertionError: None != 'Process 7713 error: exit code 126, expec[311
> chars]'{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1412) Policy C code performance issue: reload python module for each call
[ https://issues.apache.org/jira/browse/DISPATCH-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1412: Affects Version/s: 1.9.0 > Policy C code performance issue: reload python module for each call > > > Key: DISPATCH-1412 > URL: https://issues.apache.org/jira/browse/DISPATCH-1412 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Policy Engine >Affects Versions: 1.8.0, 1.9.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Labels: performance > Fix For: 1.10.0 > > > The module could be loaded once for the lifetime of the router instance. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1419) Add status to connector mgmt schema
[ https://issues.apache.org/jira/browse/DISPATCH-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1419: Component/s: Management Agent > Add status to connector mgmt schema > --- > > Key: DISPATCH-1419 > URL: https://issues.apache.org/jira/browse/DISPATCH-1419 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Management Agent >Reporter: Gordon Sim >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.10.0 > > > It would be very useful to be able to query a specific connector and > determine whether there is a connection triggered by that connector that is > active and if not ideally get the error message from the last connection > attempt. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1419) Add status to connector mgmt schema
[ https://issues.apache.org/jira/browse/DISPATCH-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1419: Issue Type: Improvement (was: Bug) > Add status to connector mgmt schema > --- > > Key: DISPATCH-1419 > URL: https://issues.apache.org/jira/browse/DISPATCH-1419 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.10.0 > > > It would be very useful to be able to query a specific connector and > determine whether there is a connection triggered by that connector that is > active and if not ideally get the error message from the last connection > attempt. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1421) Attaching link to unavailable address sets source address to null in attach reply
[
https://issues.apache.org/jira/browse/DISPATCH-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1421:
Component/s: Container
> Attaching link to unavailable address sets source address to null in attach
> reply
> -
>
> Key: DISPATCH-1421
> URL: https://issues.apache.org/jira/browse/DISPATCH-1421
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.9.0
>Reporter: Ulf Lilleengen
>Assignee: Gordon Sim
>Priority: Major
> Fix For: 1.10.0
>
>
> An AMQP client attaches to an address with source address set to 'bar' and
> target address 'remote/foo1' (which the router does not know about):
>
> {code:java}
> [425203913:0] -> Attach{name='space2.bar.fwd2.out', handle=0, role=SENDER,
> sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='bar',
> durable=UNSETTLED_STATE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
> dynamicNodeProperties=null, distributionMode=null, filter=null,
> defaultOutcome=null, outcomes=null, capabilities=null},
> target=Target{address='remote1/foo1', durable=NONE, expiryPolicy=SESSION_END,
> timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
> unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
> maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null} {code}
>
> As the router does not know about 'remote/foo1', it sets target=null, but
> also source address to 'null' (this is actually null, not the string 'null',
> proton-j is doing the formatting):
> {code:java}
> [425203913:0] <- Attach{name='space2.bar.fwd2.out', handle=0, role=RECEIVER,
> sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
> durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
> dynamicNodeProperties=null, distributionMode=null, filter=null,
> defaultOutcome=null, outcomes=null, capabilities=null}, target=null,
> unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
> maxMessageSize=0, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [425203913:0] <- Detach{handle=0, closed=true,
> error=Error{condition=qd:no-route-to-dest, description='No route to the
> destination node', info=null}} {code}
>
> This can be handled in client code, but the question is if the router should
> keep address='bar' in the replied attach or not.
>
> Possibly related: https://issues.apache.org/jira/browse/DISPATCH-962 (CC
> [~robbie])
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1421) Attaching link to unavailable address sets source address to null in attach reply
[
https://issues.apache.org/jira/browse/DISPATCH-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1421:
Affects Version/s: 1.9.0
> Attaching link to unavailable address sets source address to null in attach
> reply
> -
>
> Key: DISPATCH-1421
> URL: https://issues.apache.org/jira/browse/DISPATCH-1421
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.9.0
>Reporter: Ulf Lilleengen
>Assignee: Gordon Sim
>Priority: Major
> Fix For: 1.10.0
>
>
> An AMQP client attaches to an address with source address set to 'bar' and
> target address 'remote/foo1' (which the router does not know about):
>
> {code:java}
> [425203913:0] -> Attach{name='space2.bar.fwd2.out', handle=0, role=SENDER,
> sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='bar',
> durable=UNSETTLED_STATE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
> dynamicNodeProperties=null, distributionMode=null, filter=null,
> defaultOutcome=null, outcomes=null, capabilities=null},
> target=Target{address='remote1/foo1', durable=NONE, expiryPolicy=SESSION_END,
> timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
> unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
> maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
> properties=null} {code}
>
> As the router does not know about 'remote/foo1', it sets target=null, but
> also source address to 'null' (this is actually null, not the string 'null',
> proton-j is doing the formatting):
> {code:java}
> [425203913:0] <- Attach{name='space2.bar.fwd2.out', handle=0, role=RECEIVER,
> sndSettleMode=MIXED, rcvSettleMode=FIRST, source=Source{address='null',
> durable=NONE, expiryPolicy=SESSION_END, timeout=0, dynamic=false,
> dynamicNodeProperties=null, distributionMode=null, filter=null,
> defaultOutcome=null, outcomes=null, capabilities=null}, target=null,
> unsettled=null, incompleteUnsettled=false, initialDeliveryCount=0,
> maxMessageSize=0, offeredCapabilities=null, desiredCapabilities=null,
> properties=null}
> [425203913:0] <- Detach{handle=0, closed=true,
> error=Error{condition=qd:no-route-to-dest, description='No route to the
> destination node', info=null}} {code}
>
> This can be handled in client code, but the question is if the router should
> keep address='bar' in the replied attach or not.
>
> Possibly related: https://issues.apache.org/jira/browse/DISPATCH-962 (CC
> [~robbie])
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1431) system_tests_one_router_failing on test_19_semantics_multicast
[
https://issues.apache.org/jira/browse/DISPATCH-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1431:
Issue Type: Bug (was: Improvement)
> system_tests_one_router_failing on test_19_semantics_multicast
> --
>
> Key: DISPATCH-1431
> URL: https://issues.apache.org/jira/browse/DISPATCH-1431
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.9.0
>Reporter: Ganesh Murthy
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.10.0
>
>
> Turn on valgrind and compile the router code.
> {noformat}
> make clean
> cmake .. -DUSE_VALGRIND=Yes -DVALGRIND_XML=Yes
> make install{noformat}
> Then run test_19_semantics_multicast
> {noformat}
> [gmurthy@localhost build]$ /usr/bin/python
> "/home/gmurthy/opensource/qpid-dispatch/build/tests/run.py" "-m" "unittest"
> "-v" "system_tests_one_router.OneRouterTest.test_19_semantics_multicast"
> test_19_semantics_multicast (system_tests_one_router.OneRouterTest) ...
> FAIL==
> FAIL: test_19_semantics_multicast (system_tests_one_router.OneRouterTest)
> --
> Traceback (most recent call last):
> File
> "/home/gmurthy/opensource/qpid-dispatch/tests/system_tests_one_router.py",
> line 264, in test_19_semantics_multicast
> self.assertEqual(None, test.error)
> AssertionError: None != u'Timeout Expired: sent=1
> rcvd=0/1/0'--
> Ran 1 test in 65.460sFAILED (failures=1)
> [gmurthy@localhost build]$
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1438) Have ctest parse the routers debug dump files for memory pool leaks
[ https://issues.apache.org/jira/browse/DISPATCH-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1438: Issue Type: Improvement (was: Test) > Have ctest parse the routers debug dump files for memory pool leaks > --- > > Key: DISPATCH-1438 > URL: https://issues.apache.org/jira/browse/DISPATCH-1438 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Tests >Affects Versions: 1.9.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Minor > Labels: memory-bug > Fix For: 1.10.0 > > > When the router has been built for Debug via -DCMAKE_BUILD_TYPE=Debug it will > write a debug dump file on shutdown. > This debug dump file reports how many pool objects remain in thread on > shutdown. > A large number of in-thread pooled objects on shutdown may indicate a memory > leak. > It would be useful to have ctest parse these files and report any in-thread > objects at the end of a test run. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1466) flake8 errors in system_test.py
[
https://issues.apache.org/jira/browse/DISPATCH-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1466.
-
Resolution: Fixed
> flake8 errors in system_test.py
> ---
>
> Key: DISPATCH-1466
> URL: https://issues.apache.org/jira/browse/DISPATCH-1466
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tests
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.10.0
>
>
> {noformat}
> 63: py36 run-test: commands[0] | flake8 --count /foo/qpid-dispatch/python
> /foo/qpid-dispatch/console /foo/qpid-dispatch/docs /foo/qpid-dispatch/tests
> /foo/qpid-dispatch/tools --show-source
> --ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503
> 63: /foo/qpid-dispatch/tests/system_test.py:208:69: F821 undefined name 'host'
> 63: raise Exception("wait_port timeout on host %s port %s: %s"%(host,
> port, e)) {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1512) python checker failing due to wrong variable name
[
https://issues.apache.org/jira/browse/DISPATCH-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1512:
Issue Type: Bug (was: Improvement)
> python checker failing due to wrong variable name
> -
>
> Key: DISPATCH-1512
> URL: https://issues.apache.org/jira/browse/DISPATCH-1512
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.10.0
>
>
> {noformat}
> 63: /foo/qpid-dispatch/python/qpid_dispatch_internal/router/node.py:559:44:
> F821 undefined name 'addr'
> 63: self.adapter.unmap_destination(addr, self.maskbit)
> 63:^
> 63: /foo/qpid-dispatch/python/qpid_dispatch_internal/router/node.py:560:97:
> F821 undefined name 'addr'
> 63: self.log(LOG_DEBUG, "Remote destination %s unmapped from
> router %s" % (self._logify(addr), self.id))
> 63:
> ^
> 63: 2 {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1517) delivery count is not incremented for undeliverable messages
[ https://issues.apache.org/jira/browse/DISPATCH-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1517: Affects Version/s: 1.9.0 > delivery count is not incremented for undeliverable messages > > > Key: DISPATCH-1517 > URL: https://issues.apache.org/jira/browse/DISPATCH-1517 > Project: Qpid Dispatch > Issue Type: Improvement >Affects Versions: 1.9.0 >Reporter: Gordon Sim >Assignee: Ken Giusti >Priority: Major > Fix For: 1.10.0 > > Attachments: dispatch-1517.py > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1517) delivery count is not incremented for undeliverable messages
[ https://issues.apache.org/jira/browse/DISPATCH-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1517: Issue Type: Bug (was: Improvement) > delivery count is not incremented for undeliverable messages > > > Key: DISPATCH-1517 > URL: https://issues.apache.org/jira/browse/DISPATCH-1517 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 1.9.0 >Reporter: Gordon Sim >Assignee: Ken Giusti >Priority: Major > Fix For: 1.10.0 > > Attachments: dispatch-1517.py > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-proton] mprahl commented on issue #223: Fix errors in the Python tutorial
mprahl commented on issue #223: Fix errors in the Python tutorial URL: https://github.com/apache/qpid-proton/pull/223#issuecomment-565021841 Thanks @ssorj. How does this look? 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
