[jira] [Created] (PROTON-2013) [OSX] Travis CI xcode7.3 10.11 image fails to run
Roddie Kieley created PROTON-2013:
-
Summary: [OSX] Travis CI xcode7.3 10.11 image fails to run
Key: PROTON-2013
URL: https://issues.apache.org/jira/browse/PROTON-2013
Project: Qpid Proton
Issue Type: Bug
Reporter: Roddie Kieley
Assignee: Roddie Kieley
At the moment the travis ci macOS
[job|https://travis-ci.org/apache/qpid-proton/jobs/498838017] for xcode7.3
fails to run. This travis macOS image is based on 10.11 and the configuration
utilizes brew to install required packages.
The brew package install fails with
{code:java}
Error: You are using macOS 10.11.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Discourse, Twitter or IRC. You are responsible for resolving any issues you
experience, as you are running this old version.
Error: Your Xcode (7.3.1) is outdated.
Please update to Xcode 8.2.1 (or delete it).
Xcode can be updated from the App Store.
Error: A newer Command Line Tools release is available.
Update them from Software Update in the App Store.
The command "brew install libuv swig" failed and exited with 1 during .
Your build has been stopped.{code}
--
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-1273) 'to' field not authorized against valid targets for anonymous sender
[ https://issues.apache.org/jira/browse/DISPATCH-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780822#comment-16780822 ] ASF GitHub Bot commented on DISPATCH-1273: -- codecov-io commented on issue #452: DISPATCH-1273: enforce target policy for anonymous senders URL: https://github.com/apache/qpid-dispatch/pull/452#issuecomment-468231203 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=h1) Report > Merging [#452](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=desc) into [master](https://codecov.io/gh/apache/qpid-dispatch/commit/8e94c5cf6f98083af3066b8cff2fd5aa0b176027?src=pr&el=desc) will **increase** coverage by `0.04%`. > The diff coverage is `87.87%`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=tree) ```diff @@Coverage Diff @@ ## master #452 +/- ## == + Coverage86.8% 86.85% +0.04% == Files 85 85 Lines 1875618787 +31 == + Hits1628216317 +35 + Misses 2474 2470 -4 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=tree) | Coverage Δ | | |---|---|---| | [src/router\_node.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9ub2RlLmM=) | `94.15% <100%> (+0.06%)` | :arrow_up: | | [src/policy.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3BvbGljeS5j) | `85.29% <80.95%> (-0.16%)` | :arrow_down: | | [...c/router\_core/modules/test\_hooks/core\_test\_hooks.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL21vZHVsZXMvdGVzdF9ob29rcy9jb3JlX3Rlc3RfaG9va3MuYw==) | `92.67% <0%> (-1.28%)` | :arrow_down: | | [src/iterator.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL2l0ZXJhdG9yLmM=) | `93.45% <0%> (-0.22%)` | :arrow_down: | | [src/router\_core/connections.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2Nvbm5lY3Rpb25zLmM=) | `94.63% <0%> (+0.12%)` | :arrow_up: | | [src/container.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL2NvbnRhaW5lci5j) | `78.31% <0%> (+0.18%)` | :arrow_up: | | [src/router\_core/route\_tables.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL3JvdXRlX3RhYmxlcy5j) | `76.92% <0%> (+0.24%)` | :arrow_up: | | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3BhcnNlLmM=) | `88.54% <0%> (+0.25%)` | :arrow_up: | | [src/router\_core/transfer.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL3RyYW5zZmVyLmM=) | `91.21% <0%> (+0.43%)` | :arrow_up: | | ... and [2 more](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree-more) | | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=footer). Last update [8e94c5c...ee82bac](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on 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 > 'to' field not authorized against valid targets for anonymous sender > > > Key: DISPATCH-1273 > URL: https://issues.apache.org/jira/browse/DISPATCH-1273 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > Fix For: 1.6.0 > > > With following policy, attempts to attach a sender link to 'bar' will fail as > expected, but if an anonymous sender is attached and a message is sent to > 'bar', it gets through
[GitHub] codecov-io edited a comment on issue #452: DISPATCH-1273: enforce target policy for anonymous senders
codecov-io edited a comment on issue #452: DISPATCH-1273: enforce target policy for anonymous senders URL: https://github.com/apache/qpid-dispatch/pull/452#issuecomment-468231203 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=h1) Report > Merging [#452](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=desc) into [master](https://codecov.io/gh/apache/qpid-dispatch/commit/8e94c5cf6f98083af3066b8cff2fd5aa0b176027?src=pr&el=desc) will **increase** coverage by `0.04%`. > The diff coverage is `87.87%`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=tree) ```diff @@Coverage Diff @@ ## master #452 +/- ## == + Coverage86.8% 86.85% +0.04% == Files 85 85 Lines 1875618787 +31 == + Hits1628216317 +35 + Misses 2474 2470 -4 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=tree) | Coverage Δ | | |---|---|---| | [src/router\_node.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9ub2RlLmM=) | `94.15% <100%> (+0.06%)` | :arrow_up: | | [src/policy.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3BvbGljeS5j) | `85.29% <80.95%> (-0.16%)` | :arrow_down: | | [...c/router\_core/modules/test\_hooks/core\_test\_hooks.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL21vZHVsZXMvdGVzdF9ob29rcy9jb3JlX3Rlc3RfaG9va3MuYw==) | `92.67% <0%> (-1.28%)` | :arrow_down: | | [src/iterator.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL2l0ZXJhdG9yLmM=) | `93.45% <0%> (-0.22%)` | :arrow_down: | | [src/router\_core/connections.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2Nvbm5lY3Rpb25zLmM=) | `94.63% <0%> (+0.12%)` | :arrow_up: | | [src/container.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL2NvbnRhaW5lci5j) | `78.31% <0%> (+0.18%)` | :arrow_up: | | [src/router\_core/route\_tables.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL3JvdXRlX3RhYmxlcy5j) | `76.92% <0%> (+0.24%)` | :arrow_up: | | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3BhcnNlLmM=) | `88.54% <0%> (+0.25%)` | :arrow_up: | | [src/router\_core/transfer.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL3RyYW5zZmVyLmM=) | `91.21% <0%> (+0.43%)` | :arrow_up: | | ... and [2 more](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree-more) | | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=footer). Last update [8e94c5c...ee82bac](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on 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-1273) 'to' field not authorized against valid targets for anonymous sender
[
https://issues.apache.org/jira/browse/DISPATCH-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780788#comment-16780788
]
ASF GitHub Bot commented on DISPATCH-1273:
--
asfgit commented on pull request #452: DISPATCH-1273: enforce target policy for
anonymous senders
URL: https://github.com/apache/qpid-dispatch/pull/452
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> 'to' field not authorized against valid targets for anonymous sender
>
>
> Key: DISPATCH-1273
> URL: https://issues.apache.org/jira/browse/DISPATCH-1273
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>Priority: Major
>
> With following policy, attempts to attach a sender link to 'bar' will fail as
> expected, but if an anonymous sender is attached and a message is sent to
> 'bar', it gets through.
>
> {noformat}
> [
> ["vhost",
> {
> "id": "$default",
> "allowUnknownUser": true,
> "groups": {
> "$default" : {
> "users": "*",
> "remoteHosts": "*",
> "allowDynamicSource": true,
> "allowAnonymousSender": true,
> "sources": "*",
> "targets": "foo"
> }
> }
> }
> ]
> ]
> {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] [Assigned] (DISPATCH-1273) 'to' field not authorized against valid targets for anonymous sender
[
https://issues.apache.org/jira/browse/DISPATCH-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned DISPATCH-1273:
Assignee: Gordon Sim
> 'to' field not authorized against valid targets for anonymous sender
>
>
> Key: DISPATCH-1273
> URL: https://issues.apache.org/jira/browse/DISPATCH-1273
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>Priority: Major
>
> With following policy, attempts to attach a sender link to 'bar' will fail as
> expected, but if an anonymous sender is attached and a message is sent to
> 'bar', it gets through.
>
> {noformat}
> [
> ["vhost",
> {
> "id": "$default",
> "allowUnknownUser": true,
> "groups": {
> "$default" : {
> "users": "*",
> "remoteHosts": "*",
> "allowDynamicSource": true,
> "allowAnonymousSender": true,
> "sources": "*",
> "targets": "foo"
> }
> }
> }
> ]
> ]
> {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-1273) 'to' field not authorized against valid targets for anonymous sender
[
https://issues.apache.org/jira/browse/DISPATCH-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780795#comment-16780795
]
ASF GitHub Bot commented on DISPATCH-1273:
--
grs commented on issue #452: DISPATCH-1273: enforce target policy for anonymous
senders
URL: https://github.com/apache/qpid-dispatch/pull/452#issuecomment-468374412
@ted-ross @ganeshmurthy many thanks!
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> 'to' field not authorized against valid targets for anonymous sender
>
>
> Key: DISPATCH-1273
> URL: https://issues.apache.org/jira/browse/DISPATCH-1273
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>Priority: Major
> Fix For: 1.6.0
>
>
> With following policy, attempts to attach a sender link to 'bar' will fail as
> expected, but if an anonymous sender is attached and a message is sent to
> 'bar', it gets through.
>
> {noformat}
> [
> ["vhost",
> {
> "id": "$default",
> "allowUnknownUser": true,
> "groups": {
> "$default" : {
> "users": "*",
> "remoteHosts": "*",
> "allowDynamicSource": true,
> "allowAnonymousSender": true,
> "sources": "*",
> "targets": "foo"
> }
> }
> }
> ]
> ]
> {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] grs commented on issue #452: DISPATCH-1273: enforce target policy for anonymous senders
grs commented on issue #452: DISPATCH-1273: enforce target policy for anonymous senders URL: https://github.com/apache/qpid-dispatch/pull/452#issuecomment-468374412 @ted-ross @ganeshmurthy many thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on 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] [Resolved] (DISPATCH-1273) 'to' field not authorized against valid targets for anonymous sender
[
https://issues.apache.org/jira/browse/DISPATCH-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved DISPATCH-1273.
--
Resolution: Fixed
Fix Version/s: 1.6.0
> 'to' field not authorized against valid targets for anonymous sender
>
>
> Key: DISPATCH-1273
> URL: https://issues.apache.org/jira/browse/DISPATCH-1273
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>Priority: Major
> Fix For: 1.6.0
>
>
> With following policy, attempts to attach a sender link to 'bar' will fail as
> expected, but if an anonymous sender is attached and a message is sent to
> 'bar', it gets through.
>
> {noformat}
> [
> ["vhost",
> {
> "id": "$default",
> "allowUnknownUser": true,
> "groups": {
> "$default" : {
> "users": "*",
> "remoteHosts": "*",
> "allowDynamicSource": true,
> "allowAnonymousSender": true,
> "sources": "*",
> "targets": "foo"
> }
> }
> }
> ]
> ]
> {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] [Updated] (PROTON-1998) add headers and SASL frames to protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-1998:
---
Description:
Unlike Proton, Proton-J does not provide SASL frame trace if environment
variable PN_TRACE_FRM is set. It would be useful if Proton-J had this ability
too to help diagnose SASL negotiation problem.
Proton's SASL frame trace looks like this:
{code:java}
[0x7fc112c03a00]: -> SASL
[0x7fc112c03a00]: <- SASL
[0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
[sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
[0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
initial-response=b"guest@Oslo.local"]
[0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
[0x7fc112c03a00]: -> AMQP
[0x7fc112c03a00]:0 -> @open(16)
[container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
channel-max=32767]{code}
The "SASL" and "AMQP" notices to mark send/receive of the associated headers
are similarly omitted by proton-j and would be useful to add.
was:
Unlike Proton, Proton-J does not provide SASL frame trace if environment
variable PN_TRACE_FRM is set. It would be useful if Proton-J had this ability
too to help diagnose SASL negotiation problem.
Proton's SASL frame trace looks like this:
{code:java}
[0x7fc112c03a00]: -> SASL
[0x7fc112c03a00]: <- SASL
[0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
[sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
[0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
initial-response=b"guest@Oslo.local"]
[0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
[0x7fc112c03a00]: -> AMQP
[0x7fc112c03a00]:0 -> @open(16)
[container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
channel-max=32767]{code}
> add headers and SASL frames to protocol trace
> -
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: proton-j-0.32.0
>
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
> The "SASL" and "AMQP" notices to mark send/receive of the associated headers
> are similarly omitted by proton-j and would be useful to add.
--
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-1273) 'to' field not authorized against valid targets for anonymous sender
[
https://issues.apache.org/jira/browse/DISPATCH-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780787#comment-16780787
]
ASF subversion and git services commented on DISPATCH-1273:
---
Commit ee82bac3d890f652bc5776c5b3954e6b30bde9c0 in qpid-dispatch's branch
refs/heads/master from Gordon Sim
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=ee82bac ]
DISPATCH-1273: check permission to send to target for anonymous sender links
> 'to' field not authorized against valid targets for anonymous sender
>
>
> Key: DISPATCH-1273
> URL: https://issues.apache.org/jira/browse/DISPATCH-1273
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>Priority: Major
>
> With following policy, attempts to attach a sender link to 'bar' will fail as
> expected, but if an anonymous sender is attached and a message is sent to
> 'bar', it gets through.
>
> {noformat}
> [
> ["vhost",
> {
> "id": "$default",
> "allowUnknownUser": true,
> "groups": {
> "$default" : {
> "users": "*",
> "remoteHosts": "*",
> "allowDynamicSource": true,
> "allowAnonymousSender": true,
> "sources": "*",
> "targets": "foo"
> }
> }
> }
> ]
> ]
> {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] asfgit merged pull request #452: DISPATCH-1273: enforce target policy for anonymous senders
asfgit merged pull request #452: DISPATCH-1273: enforce target policy for anonymous senders URL: https://github.com/apache/qpid-dispatch/pull/452 This is an automated message from the Apache Git Service. To respond to the message, please log on 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] (PROTON-1998) add headers and SASL frames to protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-1998:
---
Summary: add headers and SASL frames to protocol trace (was: [Proton-J]
add headers and SASL frames to protocol trace)
> add headers and SASL frames to protocol trace
> -
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: proton-j-0.32.0
>
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
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] (PROTON-1998) [Proton-J] add headers and SASL frames to protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-1998:
---
Summary: [Proton-J] add headers and SASL frames to protocol trace (was:
[Proton-J] Add SASL protocol trace)
> [Proton-J] add headers and SASL frames to protocol trace
>
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: proton-j-0.32.0
>
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
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] (PROTON-1998) [Proton-J] Add SASL protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-1998:
---
Fix Version/s: proton-j-0.32.0
> [Proton-J] Add SASL protocol trace
> --
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Assignee: Robbie Gemmell
>Priority: Minor
> Fix For: proton-j-0.32.0
>
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
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] [Assigned] (PROTON-1998) [Proton-J] Add SASL protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reassigned PROTON-1998:
--
Assignee: Robbie Gemmell
> [Proton-J] Add SASL protocol trace
> --
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Assignee: Robbie Gemmell
>Priority: Minor
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
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-1273) 'to' field not authorized against valid targets for anonymous sender
[
https://issues.apache.org/jira/browse/DISPATCH-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780378#comment-16780378
]
ASF GitHub Bot commented on DISPATCH-1273:
--
codecov-io commented on issue #452: DISPATCH-1273: enforce target policy for
anonymous senders
URL: https://github.com/apache/qpid-dispatch/pull/452#issuecomment-468231203
#
[Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=h1)
Report
> Merging
[#452](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=desc) into
[master](https://codecov.io/gh/apache/qpid-dispatch/commit/8e94c5cf6f98083af3066b8cff2fd5aa0b176027?src=pr&el=desc)
will **increase** coverage by `0.03%`.
> The diff coverage is `87.87%`.
[](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=tree)
```diff
@@Coverage Diff @@
## master #452 +/- ##
==
+ Coverage86.8% 86.84% +0.03%
==
Files 85 85
Lines 1875618787 +31
==
+ Hits1628216315 +33
+ Misses 2474 2472 -2
```
| [Impacted
Files](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=tree) |
Coverage Δ | |
|---|---|---|
|
[src/router\_node.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9ub2RlLmM=)
| `94.15% <100%> (+0.06%)` | :arrow_up: |
|
[src/policy.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3BvbGljeS5j)
| `85.29% <80.95%> (-0.16%)` | :arrow_down: |
|
[...c/router\_core/modules/test\_hooks/core\_test\_hooks.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL21vZHVsZXMvdGVzdF9ob29rcy9jb3JlX3Rlc3RfaG9va3MuYw==)
| `92.67% <0%> (-1.28%)` | :arrow_down: |
|
[src/router\_core/agent\_link.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2xpbmsuYw==)
| `63.84% <0%> (-0.57%)` | :arrow_down: |
|
[src/iterator.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL2l0ZXJhdG9yLmM=)
| `93.45% <0%> (-0.22%)` | :arrow_down: |
|
[src/router\_core/connections.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2Nvbm5lY3Rpb25zLmM=)
| `94.63% <0%> (+0.12%)` | :arrow_up: |
|
[src/container.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL2NvbnRhaW5lci5j)
| `78.31% <0%> (+0.18%)` | :arrow_up: |
|
[src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3BhcnNlLmM=)
| `88.54% <0%> (+0.25%)` | :arrow_up: |
|
[src/router\_core/transfer.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL3RyYW5zZmVyLmM=)
| `91.21% <0%> (+0.43%)` | :arrow_up: |
| ... and [2
more](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree-more)
| |
--
[Continue to review full report at
Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=continue).
> **Legend** - [Click here to learn
more](https://docs.codecov.io/docs/codecov-delta)
> `Δ = absolute (impact)`, `ø = not affected`, `? = missing data`
> Powered by
[Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=footer).
Last update
[8e94c5c...ee82bac](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=lastupdated).
Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments).
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> 'to' field not authorized against valid targets for anonymous sender
>
>
> Key: DISPATCH-1273
> URL: https://issues.apache.org/jira/browse/DISPATCH-1273
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Gordon Sim
>Priority: Major
>
> With following policy, attempts to attach a sender link to 'bar' will fail as
> expected, but if an anonymous sender is attached and a message is sent to
> 'bar', it gets through.
>
> {noformat}
> [
> ["vhost",
> {
> "id":
[GitHub] codecov-io commented on issue #452: DISPATCH-1273: enforce target policy for anonymous senders
codecov-io commented on issue #452: DISPATCH-1273: enforce target policy for anonymous senders URL: https://github.com/apache/qpid-dispatch/pull/452#issuecomment-468231203 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=h1) Report > Merging [#452](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=desc) into [master](https://codecov.io/gh/apache/qpid-dispatch/commit/8e94c5cf6f98083af3066b8cff2fd5aa0b176027?src=pr&el=desc) will **increase** coverage by `0.03%`. > The diff coverage is `87.87%`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=tree) ```diff @@Coverage Diff @@ ## master #452 +/- ## == + Coverage86.8% 86.84% +0.03% == Files 85 85 Lines 1875618787 +31 == + Hits1628216315 +33 + Misses 2474 2472 -2 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=tree) | Coverage Δ | | |---|---|---| | [src/router\_node.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9ub2RlLmM=) | `94.15% <100%> (+0.06%)` | :arrow_up: | | [src/policy.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3BvbGljeS5j) | `85.29% <80.95%> (-0.16%)` | :arrow_down: | | [...c/router\_core/modules/test\_hooks/core\_test\_hooks.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL21vZHVsZXMvdGVzdF9ob29rcy9jb3JlX3Rlc3RfaG9va3MuYw==) | `92.67% <0%> (-1.28%)` | :arrow_down: | | [src/router\_core/agent\_link.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2xpbmsuYw==) | `63.84% <0%> (-0.57%)` | :arrow_down: | | [src/iterator.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL2l0ZXJhdG9yLmM=) | `93.45% <0%> (-0.22%)` | :arrow_down: | | [src/router\_core/connections.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL2Nvbm5lY3Rpb25zLmM=) | `94.63% <0%> (+0.12%)` | :arrow_up: | | [src/container.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL2NvbnRhaW5lci5j) | `78.31% <0%> (+0.18%)` | :arrow_up: | | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3BhcnNlLmM=) | `88.54% <0%> (+0.25%)` | :arrow_up: | | [src/router\_core/transfer.c](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree#diff-c3JjL3JvdXRlcl9jb3JlL3RyYW5zZmVyLmM=) | `91.21% <0%> (+0.43%)` | :arrow_up: | | ... and [2 more](https://codecov.io/gh/apache/qpid-dispatch/pull/452/diff?src=pr&el=tree-more) | | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=footer). Last update [8e94c5c...ee82bac](https://codecov.io/gh/apache/qpid-dispatch/pull/452?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on 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-1273) 'to' field not authorized against valid targets for anonymous sender
[
https://issues.apache.org/jira/browse/DISPATCH-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780367#comment-16780367
]
ASF GitHub Bot commented on DISPATCH-1273:
--
grs commented on pull request #452: DISPATCH-1273: enforce target policy for
anonymous senders
URL: https://github.com/apache/qpid-dispatch/pull/452
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> 'to' field not authorized against valid targets for anonymous sender
>
>
> Key: DISPATCH-1273
> URL: https://issues.apache.org/jira/browse/DISPATCH-1273
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.5.0
>Reporter: Gordon Sim
>Priority: Major
>
> With following policy, attempts to attach a sender link to 'bar' will fail as
> expected, but if an anonymous sender is attached and a message is sent to
> 'bar', it gets through.
>
> {noformat}
> [
> ["vhost",
> {
> "id": "$default",
> "allowUnknownUser": true,
> "groups": {
> "$default" : {
> "users": "*",
> "remoteHosts": "*",
> "allowDynamicSource": true,
> "allowAnonymousSender": true,
> "sources": "*",
> "targets": "foo"
> }
> }
> }
> ]
> ]
> {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] grs opened a new pull request #452: DISPATCH-1273: enforce target policy for anonymous senders
grs opened a new pull request #452: DISPATCH-1273: enforce target policy for anonymous senders URL: https://github.com/apache/qpid-dispatch/pull/452 This is an automated message from the Apache Git Service. To respond to the message, please log on 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] (PROTON-1998) [Proton-J] Add SASL protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780362#comment-16780362
]
ASF GitHub Bot commented on PROTON-1998:
asfgit commented on pull request #31: PROTON-1998: add SASL protocol trace
logging (v2)
URL: https://github.com/apache/qpid-proton-j/pull/31
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> [Proton-J] Add SASL protocol trace
> --
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Priority: Minor
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
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] (PROTON-1998) [Proton-J] Add SASL protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780361#comment-16780361
]
ASF subversion and git services commented on PROTON-1998:
-
Commit fd58931a95904ffc441c41a5e9dfb6a56091e437 in qpid-proton-j's branch
refs/heads/master from Robert Gemmell
[ https://gitbox.apache.org/repos/asf?p=qpid-proton-j.git;h=fd58931 ]
PROTON-1998: add SASL protocol trace logging
Changes from Keith Wall with subsequent updates from me.
This closes #31.
This closes #30 (original changes).
> [Proton-J] Add SASL protocol trace
> --
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Priority: Minor
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
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] (PROTON-1998) [Proton-J] Add SASL protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780363#comment-16780363
]
ASF GitHub Bot commented on PROTON-1998:
asfgit commented on pull request #30: PROTON-1998: Add SASL protocol trace
URL: https://github.com/apache/qpid-proton-j/pull/30
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> [Proton-J] Add SASL protocol trace
> --
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Priority: Minor
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
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] asfgit closed pull request #31: PROTON-1998: add SASL protocol trace logging (v2)
asfgit closed pull request #31: PROTON-1998: add SASL protocol trace logging (v2) URL: https://github.com/apache/qpid-proton-j/pull/31 This is an automated message from the Apache Git Service. To respond to the message, please log on 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] asfgit closed pull request #30: PROTON-1998: Add SASL protocol trace
asfgit closed pull request #30: PROTON-1998: Add SASL protocol trace URL: https://github.com/apache/qpid-proton-j/pull/30 This is an automated message from the Apache Git Service. To respond to the message, please log on 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] [Closed] (PROTON-2012) Unexpected Proton Event Link_REMOTE_CLOSE causes MessageProducer to close and then never start again
[
https://issues.apache.org/jira/browse/PROTON-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell closed PROTON-2012.
--
Resolution: Invalid
Please ask questions on the mailing lists. This isnt a proton-j bug report.
It is logging the remote close event because it has in fact been remotely
closed, by Service Bus, for some reason. Prior discussions suggest ServiceBus
closes 'idle' producers after some period.
The client does not automatically recreate producers in cases they are remotely
closed, the application needs to handle use of the closed sender failing.
> Unexpected Proton Event Link_REMOTE_CLOSE causes MessageProducer to close and
> then never start again
>
>
> Key: PROTON-2012
> URL: https://issues.apache.org/jira/browse/PROTON-2012
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Environment: Spring boot, Apache Camel, Docker, Qpid JMS
>Reporter: mayur
>Priority: Major
>
> I am using Qpid AMQP in Spring Route. JMS Message Queue is on Azure Service
> Bus.
> Once Spring app is started and couple of messages are consumed from queue,
> processed and forwarded to next queue destination, I am seeing below events
> in logs. After the events MessageProducer is closed.
> The App is still able to consume the message and process it, but its no more
> able to forward the message on Queue.
> How can these events be avoided ?
> 2019-02-28 07:58:46.425 TRACE 1 --- [windows.net:-1]]
> o.a.qpid.jms.provider.amqp.AmqpProvider : New Proton Event: LINK_REMOTE_CLOSE
> 2019-02-28 07:58:46.425 TRACE 1 --- [windows.net:-1]]
> o.a.q.j.t.netty.NettyTcpTransport : Attempted write of: 17 bytes
> 2019-02-28 07:58:46.426 TRACE 1 --- [windows.net:-1]]
> o.a.qpid.jms.provider.amqp.AmqpProvider : New Proton Event: LINK_LOCAL_CLOSE
> 2019-02-28 07:58:46.426 TRACE 1 --- [windows.net:-1]]
> o.a.qpid.jms.provider.amqp.AmqpProvider : New Proton Event: LINK_FINAL
> 2019-02-28 07:58:46.426 INFO 1 --- [-5f7cc449aefd:1]
> org.apache.qpid.jms.JmsSession : A JMS MessageProducer has been closed:
> JmsProducerInfo \{ ID:0df49cdb-8e6d-4d33-9b56-5f7cc449aefd:1:1:1, destination
> = ZIP_INCOMING_QA }
> 2019-02-28 07:59:12.705 TRACE 1 --- [ntLoopGroup-2-1]
> o.a.q.j.t.netty.NettyTcpTransport : New data read: 8 bytes incoming:
> PooledUnsafeDirectByteBuf(ridx: 0, widx: 8, cap: 37)
> 2019-02-28 07:59:30.511 TRACE 1 --- [windows.net:-1]]
> o.a.qpid.jms.provider.amqp.AmqpProvider : IdleTimeoutCheck rescheduling with
> delay: 6
> 2019-02-28 07:59:39.057 TRACE 1 --- [ntLoopGroup-2-1]
> o.a.q.j.t.netty.NettyTcpTransport : New data read: 8 bytes incoming:
> PooledUnsafeDirectByteBuf(ridx: 0, widx: 8, cap: 37)
--
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] (PROTON-2012) Unexpected Proton Event Link_REMOTE_CLOSE causes MessageProducer to close and then never start again
mayur created PROTON-2012:
-
Summary: Unexpected Proton Event Link_REMOTE_CLOSE causes
MessageProducer to close and then never start again
Key: PROTON-2012
URL: https://issues.apache.org/jira/browse/PROTON-2012
Project: Qpid Proton
Issue Type: Bug
Components: proton-j
Environment: Spring boot, Apache Camel, Docker, Qpid JMS
Reporter: mayur
I am using Qpid AMQP in Spring Route. JMS Message Queue is on Azure Service Bus.
Once Spring app is started and couple of messages are consumed from queue,
processed and forwarded to next queue destination, I am seeing below events in
logs. After the events MessageProducer is closed.
The App is still able to consume the message and process it, but its no more
able to forward the message on Queue.
How can these events be avoided ?
2019-02-28 07:58:46.425 TRACE 1 --- [windows.net:-1]]
o.a.qpid.jms.provider.amqp.AmqpProvider : New Proton Event: LINK_REMOTE_CLOSE
2019-02-28 07:58:46.425 TRACE 1 --- [windows.net:-1]]
o.a.q.j.t.netty.NettyTcpTransport : Attempted write of: 17 bytes
2019-02-28 07:58:46.426 TRACE 1 --- [windows.net:-1]]
o.a.qpid.jms.provider.amqp.AmqpProvider : New Proton Event: LINK_LOCAL_CLOSE
2019-02-28 07:58:46.426 TRACE 1 --- [windows.net:-1]]
o.a.qpid.jms.provider.amqp.AmqpProvider : New Proton Event: LINK_FINAL
2019-02-28 07:58:46.426 INFO 1 --- [-5f7cc449aefd:1]
org.apache.qpid.jms.JmsSession : A JMS MessageProducer has been closed:
JmsProducerInfo \{ ID:0df49cdb-8e6d-4d33-9b56-5f7cc449aefd:1:1:1, destination =
ZIP_INCOMING_QA }
2019-02-28 07:59:12.705 TRACE 1 --- [ntLoopGroup-2-1]
o.a.q.j.t.netty.NettyTcpTransport : New data read: 8 bytes incoming:
PooledUnsafeDirectByteBuf(ridx: 0, widx: 8, cap: 37)
2019-02-28 07:59:30.511 TRACE 1 --- [windows.net:-1]]
o.a.qpid.jms.provider.amqp.AmqpProvider : IdleTimeoutCheck rescheduling with
delay: 6
2019-02-28 07:59:39.057 TRACE 1 --- [ntLoopGroup-2-1]
o.a.q.j.t.netty.NettyTcpTransport : New data read: 8 bytes incoming:
PooledUnsafeDirectByteBuf(ridx: 0, widx: 8, cap: 37)
--
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] (PROTON-1998) [Proton-J] Add SASL protocol trace
[
https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780240#comment-16780240
]
ASF GitHub Bot commented on PROTON-1998:
k-wall commented on issue #31: PROTON-1998: add SASL protocol trace logging (v2)
URL: https://github.com/apache/qpid-proton-j/pull/31#issuecomment-468178174
Thanks Robbie. LGTM
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
> [Proton-J] Add SASL protocol trace
> --
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
>Reporter: Keith Wall
>Priority: Minor
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment
> variable PN_TRACE_FRM is set. It would be useful if Proton-J had this
> ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16)
> [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1",
> channel-max=32767]{code}
--
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] k-wall commented on issue #31: PROTON-1998: add SASL protocol trace logging (v2)
k-wall commented on issue #31: PROTON-1998: add SASL protocol trace logging (v2) URL: https://github.com/apache/qpid-proton-j/pull/31#issuecomment-468178174 Thanks Robbie. LGTM This is an automated message from the Apache Git Service. To respond to the message, please log on 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
