[jira] [Updated] (QPIDJMS-373) Support for OAuth flow and setting of "Authorization" Header for WS upgrade request

2018-04-05 Thread Michael Bolz (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated QPIDJMS-373: - Description: Add support for OAuth flow ("client_credentials" and "password") (-and setting of

[jira] [Commented] (QPIDJMS-373) Support for OAuth flow and setting of "Authorization" Header for WS upgrade request

2018-04-05 Thread Michael Bolz (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427954#comment-16427954 ] Michael Bolz commented on QPIDJMS-373: -- Using some sort of callback was also an approach I had in

[jira] [Commented] (QPIDJMS-375) Enable setting of an "Authorization" Header during WebSocket connection handshake.

2018-04-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427891#comment-16427891 ] ASF GitHub Bot commented on QPIDJMS-375: GitHub user mibo opened a pull request:

[jira] [Updated] (QPIDJMS-375) Enable setting of an "Authorization" Header during WebSocket connection handshake.

2018-04-05 Thread Michael Bolz (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bolz updated QPIDJMS-375: - Description: Add support for setting of an "Authorization" Header during WebSocket connection

[GitHub] qpid-jms pull request #18: QPIDJMS-375: Added transport.ws.authorizationHead...

2018-04-05 Thread mibo
GitHub user mibo opened a pull request: https://github.com/apache/qpid-jms/pull/18 QPIDJMS-375: Added transport.ws.authorizationHeader option As described in the JIRA item: https://issues.apache.org/jira/browse/QPIDJMS-375 According tests will follow (however the

[jira] [Created] (QPIDJMS-375) Enable setting of an "Authorization" Header during WebSocket connection handshake.

2018-04-05 Thread Michael Bolz (JIRA)
Michael Bolz created QPIDJMS-375: Summary: Enable setting of an "Authorization" Header during WebSocket connection handshake. Key: QPIDJMS-375 URL: https://issues.apache.org/jira/browse/QPIDJMS-375

[jira] [Commented] (PROTON-1805) [MacOS] Fuzzer issues in fuzz-connection-driver & fuzz-message-decode

2018-04-05 Thread Roddie Kieley (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427818#comment-16427818 ] Roddie Kieley commented on PROTON-1805: --- [~gemmellr] That's interesting re: the os version

[ANNOUNCE] Apache Qpid for Java 6.1.6 released

2018-04-05 Thread Alex Rudyy
The Apache Qpid (https://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid for Java 6.1.6. This release addresses defects and enhancements in Qpid Broker-J (previously known as Qpid Broker for Java). The release is available now from our website:

[ANNOUNCE] Apache Qpid Broker-J 7.0.3 released

2018-04-05 Thread Alex Rudyy
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Broker-J 7.0.3. This release addresses defects and enhancements in Qpid Broker-J The release is available now from our website: https://qpid.apache.org/download.html Release

[jira] [Resolved] (DISPATCH-952) qdrouterd seg fault after reporting "too many sessions"

2018-04-05 Thread Ganesh Murthy (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-952. Resolution: Fixed > qdrouterd seg fault after reporting "too many sessions" >

[jira] [Commented] (DISPATCH-952) qdrouterd seg fault after reporting "too many sessions"

2018-04-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427578#comment-16427578 ] ASF GitHub Bot commented on DISPATCH-952: - Github user asfgit closed the pull request at:

[jira] [Commented] (DISPATCH-952) qdrouterd seg fault after reporting "too many sessions"

2018-04-05 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427575#comment-16427575 ] ASF subversion and git services commented on DISPATCH-952: -- Commit

[GitHub] qpid-dispatch pull request #280: DISPATCH-952 - Outgoing links initiated by ...

2018-04-05 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/280 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPIDJMS-374) Double encoded query parameters

2018-04-05 Thread Timothy Bish (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-374. -- Resolution: Fixed Assignee: Timothy Bish Fix Version/s: 0.32.0 > Double

[jira] [Commented] (QPIDJMS-374) Double encoded query parameters

2018-04-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427539#comment-16427539 ] ASF GitHub Bot commented on QPIDJMS-374: Github user asfgit closed the pull request at:

[jira] [Commented] (QPIDJMS-374) Double encoded query parameters

2018-04-05 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427538#comment-16427538 ] ASF subversion and git services commented on QPIDJMS-374: - Commit

[GitHub] qpid-jms pull request #17: QPIDJMS-374: Use getRawQuery to avoid double enco...

2018-04-05 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/qpid-jms/pull/17 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Closed] (PROTON-1728) [proton-c] Reorganize the source tree now that Proton J is split off

2018-04-05 Thread Justin Ross (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-1728. --- Resolution: Done

[jira] [Commented] (PROTON-1728) [proton-c] Reorganize the source tree now that Proton J is split off

2018-04-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427493#comment-16427493 ] ASF GitHub Bot commented on PROTON-1728: Github user ssorj closed the pull request at:

[jira] [Commented] (PROTON-1638) Need to improve proton-c build tree layout

2018-04-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427492#comment-16427492 ] ASF GitHub Bot commented on PROTON-1638: Github user ssorj closed the pull request at:

[GitHub] qpid-proton pull request #132: PROTON-1728: WIP: Reorganize the source tree ...

2018-04-05 Thread ssorj
Github user ssorj closed the pull request at: https://github.com/apache/qpid-proton/pull/132 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton pull request #136: WIP - Remove deprecated bindings and APIs

2018-04-05 Thread ssorj
Github user ssorj closed the pull request at: https://github.com/apache/qpid-proton/pull/136 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton pull request #138: WIP - Remove obsolete docs and test code

2018-04-05 Thread ssorj
Github user ssorj closed the pull request at: https://github.com/apache/qpid-proton/pull/138 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton pull request #140: PROTON-1638, PROTON-1728: Reorganize the sour...

2018-04-05 Thread ssorj
Github user ssorj closed the pull request at: https://github.com/apache/qpid-proton/pull/140 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1806) Release qpid_proton gem with heartbeating implemented

2018-04-05 Thread Miha Plesko (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427412#comment-16427412 ] Miha Plesko commented on PROTON-1806: - Thanks guys for releasing so early, we already have PR open to

[jira] [Commented] (DISPATCH-956) Zero out the memory after calling NEW or new_*

2018-04-05 Thread Ganesh Murthy (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427411#comment-16427411 ] Ganesh Murthy commented on DISPATCH-956: Yes, changing NEW and new_* to zero out the memory is

[jira] [Commented] (DISPATCH-956) Zero out the memory after calling NEW or new_*

2018-04-05 Thread Ted Ross (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427406#comment-16427406 ] Ted Ross commented on DISPATCH-956: --- Also, it's not clear what you are proposing. Are you suggesting

[jira] [Commented] (DISPATCH-956) Zero out the memory after calling NEW or new_*

2018-04-05 Thread Ted Ross (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427396#comment-16427396 ] Ted Ross commented on DISPATCH-956: --- I prefer to not blindly take the overhead of zeroing all

[jira] [Updated] (DISPATCH-956) Zero out the memory after calling NEW or new_*

2018-04-05 Thread Ganesh Murthy (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-956: --- Fix Version/s: (was: 1.1.0) > Zero out the memory after calling NEW or new_* >

[GitHub] qpid-dispatch pull request #281: NO-JIRA: Update some doc attribute names

2018-04-05 Thread bhardesty
GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/281 NO-JIRA: Update some doc attribute names You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch update-doc-attributes

[GitHub] qpid-dispatch pull request #280: DISPATCH-952 - Outgoing links initiated by ...

2018-04-05 Thread ganeshmurthy
GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/280 DISPATCH-952 - Outgoing links initiated by the router will share a si… …ngle session You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (DISPATCH-952) qdrouterd seg fault after reporting "too many sessions"

2018-04-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427330#comment-16427330 ] ASF GitHub Bot commented on DISPATCH-952: - GitHub user ganeshmurthy opened a pull request:

[jira] [Created] (DISPATCH-956) Zero out the memory after calling NEW or new_*

2018-04-05 Thread Ganesh Murthy (JIRA)
Ganesh Murthy created DISPATCH-956: -- Summary: Zero out the memory after calling NEW or new_* Key: DISPATCH-956 URL: https://issues.apache.org/jira/browse/DISPATCH-956 Project: Qpid Dispatch

[GitHub] qpid-dispatch pull request #279: Dispatch 952 1

2018-04-05 Thread ganeshmurthy
Github user ganeshmurthy closed the pull request at: https://github.com/apache/qpid-dispatch/pull/279 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-918) Improve router config consistency and metadata

2018-04-05 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/DISPATCH-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427263#comment-16427263 ] ASF subversion and git services commented on DISPATCH-918: -- Commit

[GitHub] qpid-dispatch pull request #279: Dispatch 952 1

2018-04-05 Thread ganeshmurthy
Github user ganeshmurthy commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/279#discussion_r179512687 --- Diff: src/container.c --- @@ -756,8 +756,16 @@ qd_link_t *qd_link(qd_node_t *node, qd_connection_t *conn, qd_direction_t dir, c

[GitHub] qpid-dispatch pull request #279: Dispatch 952 1

2018-04-05 Thread alanconway
Github user alanconway commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/279#discussion_r179510287 --- Diff: src/container.c --- @@ -756,8 +756,16 @@ qd_link_t *qd_link(qd_node_t *node, qd_connection_t *conn, qd_direction_t dir, c

[GitHub] qpid-dispatch pull request #279: Dispatch 952 1

2018-04-05 Thread alanconway
Github user alanconway commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/279#discussion_r179509985 --- Diff: src/container.c --- @@ -769,11 +777,12 @@ qd_link_t *qd_link(qd_node_t *node, qd_connection_t *conn, qd_direction_t dir, c

[jira] [Assigned] (QPID-8153) [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as part of TLS handshake

2018-04-05 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8153: Assignee: Keith Wall > [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as part of TLS >

[jira] [Updated] (QPID-8153) [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as part of TLS handshake

2018-04-05 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8153: - Status: Reviewable (was: In Progress) > [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as part of

[jira] [Commented] (QPID-8135) [JMS AMQP 0-x] Connection URL options for end-to-end encryption keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'war

2018-04-05 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427111#comment-16427111 ] ASF subversion and git services commented on QPID-8135: --- Commit

[jira] [Updated] (QPID-8135) [JMS AMQP 0-x] Connection URL options for end-to-end encryption keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'warn'

2018-04-05 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8135: - Status: Reviewable (was: In Progress) > [JMS AMQP 0-x] Connection URL options for end-to-end encryption

[jira] [Assigned] (QPID-8135) [JMS AMQP 0-x] Connection URL options for end-to-end encryption keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'warn

2018-04-05 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8135: Assignee: Keith Wall > [JMS AMQP 0-x] Connection URL options for end-to-end encryption >

[jira] [Commented] (QPID-8153) [JMS AMQP 0-x] JMS AMQP 0-x should be able to send SNI as part of TLS handshake

2018-04-05 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427110#comment-16427110 ] ASF subversion and git services commented on QPID-8153: --- Commit

[jira] [Updated] (QPID-8135) [JMS AMQP 0-x] Connection URL options for end-to-end encryption keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'warn'

2018-04-05 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8135: - Summary: [JMS AMQP 0-x] Connection URL options for end-to-end encryption keystore/trustore passwords can

[jira] [Updated] (QPID-8135) [JMS AMQP 0-x] Connection URL options for end to end encryption keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'warn'

2018-04-05 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8135: - Summary: [JMS AMQP 0-x] Connection URL options for end to end encryption keystore/trustore passwords can

[jira] [Commented] (PROTON-1806) Release qpid_proton gem with heartbeating implemented

2018-04-05 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427081#comment-16427081 ] Alan Conway commented on PROTON-1806: - Please note there is a new feature Container#schedule in 0.22

[jira] [Resolved] (PROTON-1820) [ruby] Container#schedule does not work if called from handler

2018-04-05 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1820. - Resolution: Fixed > [ruby] Container#schedule does not work if called from handler >

[jira] [Updated] (PROTON-1820) [ruby] Container#schedule does not work if called from handler

2018-04-05 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1820: Description: The Container#schedule method does not work if called from a handler function.  

[jira] [Commented] (PROTON-1820) [ruby] Container#schedule does not work if called from handler

2018-04-05 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427041#comment-16427041 ] ASF subversion and git services commented on PROTON-1820: - Commit

[jira] [Commented] (PROTON-1820) [ruby] Container#schedule does not work if called from handler

2018-04-05 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427040#comment-16427040 ] ASF subversion and git services commented on PROTON-1820: - Commit

[jira] [Commented] (QPIDJMS-373) Support for OAuth flow and setting of "Authorization" Header for WS upgrade request

2018-04-05 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426983#comment-16426983 ] Robbie Gemmell commented on QPIDJMS-373: Sounds like you are thinking of something more general

[jira] [Comment Edited] (QPIDJMS-373) Support for OAuth flow and setting of "Authorization" Header for WS upgrade request

2018-04-05 Thread Rob Godfrey (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426828#comment-16426828 ] Rob Godfrey edited comment on QPIDJMS-373 at 4/5/18 12:27 PM: -- [~gemmellr]

[jira] [Commented] (QPIDJMS-373) Support for OAuth flow and setting of "Authorization" Header for WS upgrade request

2018-04-05 Thread Rob Godfrey (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426828#comment-16426828 ] Rob Godfrey commented on QPIDJMS-373: - [~gemmellr] Registering a callback would be a nice general

[jira] [Commented] (QPID-8138) [Broker-J] Report authenticated user principals and groups as part of ACL and/or operational logging

2018-04-05 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPID-8138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426807#comment-16426807 ] Keith Wall commented on QPID-8138: -- I am wondering if this is required required. The REST API exposes

[jira] [Commented] (QPIDJMS-373) Support for OAuth flow and setting of "Authorization" Header for WS upgrade request

2018-04-05 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426753#comment-16426753 ] Robbie Gemmell commented on QPIDJMS-373: Creating your own transport factory is what I was