[jira] [Resolved] (PROTON-1632) Split SO versions by library

2017-10-16 Thread Justin Ross (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross resolved PROTON-1632.
-
Resolution: Done

> Split SO versions by library
> 
>
> Key: PROTON-1632
> URL: https://issues.apache.org/jira/browse/PROTON-1632
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: proton-c-0.18.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1632) Split SO versions by library

2017-10-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206702#comment-16206702
 ] 

ASF GitHub Bot commented on PROTON-1632:


Github user ssorj commented on the issue:

https://github.com/apache/qpid-proton/pull/126
  
https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7c252e9


> Split SO versions by library
> 
>
> Key: PROTON-1632
> URL: https://issues.apache.org/jira/browse/PROTON-1632
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: proton-c-0.18.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1632) Split SO versions by library

2017-10-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206703#comment-16206703
 ] 

ASF GitHub Bot commented on PROTON-1632:


Github user ssorj closed the pull request at:

https://github.com/apache/qpid-proton/pull/126


> Split SO versions by library
> 
>
> Key: PROTON-1632
> URL: https://issues.apache.org/jira/browse/PROTON-1632
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: proton-c-0.18.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton pull request #126: PROTON-1632: WIP: Split library versions

2017-10-16 Thread ssorj 
Github user ssorj closed the pull request at:

https://github.com/apache/qpid-proton/pull/126


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton issue #126: PROTON-1632: WIP: Split library versions

2017-10-16 Thread ssorj 
Github user ssorj commented on the issue:

https://github.com/apache/qpid-proton/pull/126
  
https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7c252e9


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1543) Various improvements to the docs and examples

2017-10-16 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206699#comment-16206699
 ] 

ASF subversion and git services commented on PROTON-1543:
-

Commit a49e36db8ff9aa9003248ccd78b8a3251162a198 in qpid-proton's branch 
refs/heads/master from [~jr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=a49e36d ]

PROTON-1543: Make sure deprecated API is visibly marked in generated API docs


> Various improvements to the docs and examples
> -
>
> Key: PROTON-1543
> URL: https://issues.apache.org/jira/browse/PROTON-1543
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: examples, proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
>  Labels: documentation
> Fix For: proton-c-0.18.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1632) Split SO versions by library

2017-10-16 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206698#comment-16206698
 ] 

ASF subversion and git services commented on PROTON-1632:
-

Commit 7c252e9cbd1b7ff9f038ba96f8486b0d61de4298 in qpid-proton's branch 
refs/heads/master from [~jr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7c252e9 ]

PROTON-1632: Split library versions


> Split SO versions by library
> 
>
> Key: PROTON-1632
> URL: https://issues.apache.org/jira/browse/PROTON-1632
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: proton-c-0.18.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (DISPATCH-857) Router crash when ctrl-c on router that has a libwebsockets listener connected to a console

2017-10-16 Thread Ganesh Murthy (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DISPATCH-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy reassigned DISPATCH-857:
--

Assignee: Ganesh Murthy

> Router crash when ctrl-c on router that has a libwebsockets listener 
> connected to a console
> ---
>
> Key: DISPATCH-857
> URL: https://issues.apache.org/jira/browse/DISPATCH-857
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 1.0.0
>Reporter: Ernest Allen
>Assignee: Ganesh Murthy
>
> The router will core under the following circumstances:
> - checkout the latest proton and dispatch. build and install
> - start a router using qpid-dispatch/tests/config-1/A.conf (not as a daemon)
> - start a console by browsing to localhost:5673
> - after the console connects, ctrl-c out of the router
> ^C2017-10-16 14:54:36.776194 -0400 SERVER (notice) Shut Down
> 2017-10-16 14:54:36.776305 -0400 ROUTER_CORE (info) Router Core thread exited
> 2017-10-16 14:54:36.776639 -0400 SERVER (info) HTTP server thread exit
> 2017-10-16 14:54:36.776909 -0400 SERVER (info) Connection from 10.10.123.4 
> (to 0.0.0.0:5673) failed: amqp:connection:framing-error connection aborted
> qdrouterd: /home/eallen/qpid-dispatch/src/posix/threading.c:57: 
> sys_mutex_lock: Assertion `result == 0' failed.
> Aborted (core dumped)
> Since this only happens after a console has connected, it may be related to 
> DISPATCH-855 which causes the 0.8.0 router to crash after the console 
> connection unexpectedly closed.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-857) Router crash when ctrl-c on router that has a libwebsockets listener connected to a console

2017-10-16 Thread Ernest Allen (JIRA) 
Ernest Allen created DISPATCH-857:
-

 Summary: Router crash when ctrl-c on router that has a 
libwebsockets listener connected to a console
 Key: DISPATCH-857
 URL: https://issues.apache.org/jira/browse/DISPATCH-857
 Project: Qpid Dispatch
  Issue Type: Bug
  Components: Container
Affects Versions: 1.0.0
Reporter: Ernest Allen


The router will core under the following circumstances:

- checkout the latest proton and dispatch. build and install
- start a router using qpid-dispatch/tests/config-1/A.conf (not as a daemon)
- start a console by browsing to localhost:5673
- after the console connects, ctrl-c out of the router

^C2017-10-16 14:54:36.776194 -0400 SERVER (notice) Shut Down
2017-10-16 14:54:36.776305 -0400 ROUTER_CORE (info) Router Core thread exited
2017-10-16 14:54:36.776639 -0400 SERVER (info) HTTP server thread exit
2017-10-16 14:54:36.776909 -0400 SERVER (info) Connection from 10.10.123.4 (to 
0.0.0.0:5673) failed: amqp:connection:framing-error connection aborted
qdrouterd: /home/eallen/qpid-dispatch/src/posix/threading.c:57: sys_mutex_lock: 
Assertion `result == 0' failed.
Aborted (core dumped)

Since this only happens after a console has connected, it may be related to 
DISPATCH-855 which causes the 0.8.0 router to crash after the console 
connection unexpectedly closed.

 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (DISPATCH-855) Router crash when disconnecting from console

2017-10-16 Thread Ernest Allen (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DISPATCH-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ernest Allen updated DISPATCH-855:
--
Component/s: (was: Routing Engine)
 Container

> Router crash when disconnecting from console
> 
>
> Key: DISPATCH-855
> URL: https://issues.apache.org/jira/browse/DISPATCH-855
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Container
>Affects Versions: 0.8.0
>Reporter: Ernest Allen
>
> The router will crash if it receives a connection from a console and then the 
> console disconnects.
> To reproduce:
> - dnf install qpid-dispatch-router
> - dnf install qpid-dispatch-tools
> - create a config file with an http listener named A.conf that contains:
> router {
> mode: standalone
> id: A
> }
> listener {
> port: 5673
> host: 0.0.0.0
> http: true
> saslMechanisms: ANONYMOUS
> name: Console Listener
> }
> - start the router
> $ qdrouterd --config A.conf
> - connect a console: browse to localhost:5673
> - close the browser window
> - the router crashes
> Here is the output from the router:
> qdrouterd --config /usr/local/etc/qpid-dispatch/A.conf 
> 2017-10-10 13:37:20.279849 -0400 SERVER (info) Container Name: A
> 2017-10-10 13:37:20.279926 -0400 ROUTER (info) Router started in Standalone 
> mode
> 2017-10-10 13:37:20.280273 -0400 ROUTER_CORE (info) Router Core thread 
> running. 0/A
> 2017-10-10 13:37:20.280290 -0400 ROUTER_CORE (info) In-process subscription 
> M/$management
> 2017-10-10 13:37:20.333194 -0400 AGENT (info) Activating management agent on 
> $_management_internal
> 2017-10-10 13:37:20.333276 -0400 ROUTER_CORE (info) In-process subscription 
> L/$management
> 2017-10-10 13:37:20.10 -0400 ROUTER_CORE (info) In-process subscription 
> L/$_management_internal
> 2017-10-10 13:37:20.333608 -0400 CONN_MGR (info) Configured Listener: 
> localhost:5673 proto=any, role=normal, http
> 2017-10-10 13:37:20.333725 -0400 SERVER (info) HTTP server thread running
> 2017-10-10 13:37:20.333825 -0400 SERVER (notice) Listening for HTTP on 
> localhost:5673
> 2017-10-10 13:37:20.336628 -0400 POLICY (info) Policy configured 
> maxConnections: 65535, policyDir: '', access rules enabled: 'false'
> 2017-10-10 13:37:20.341923 -0400 POLICY (info) Policy fallback defaultVhost 
> is defined: '$default'
> 2017-10-10 13:37:20.342088 -0400 SERVER (info) Operational, 4 Threads Running
> 2017-10-10 13:37:57.114258 -0400 CONTAINER (notice) Aborting link 
> '68c3979a-9bdf-7e4e-b578-ecfcd8925acb' due to parent connection end
> 2017-10-10 13:37:57.114304 -0400 CONTAINER (notice) Aborting link 
> '5ec6b95c-3885-984e-995d-297f2841ca02' due to parent connection end
> Segmentation fault (core dumped)
> Here is a backtrace:
> (gdb) bt
> #0  0x0010 in ?? ()
> #1  0x779379fe in pn_class_decref (clazz=0x7fffe4019b60, 
> clazz@entry=0x77b6ec00 , object=0x7fffe4019b40)
> at /usr/src/debug/qpid-proton-0.17.0/proton-c/src/core/object/object.c:91
> #2  0x77937c2f in pn_decref (object=)
> at /usr/src/debug/qpid-proton-0.17.0/proton-c/src/core/object/object.c:253
> #3  0x77944732 in pn_collector_free (collector=)
> at /usr/src/debug/qpid-proton-0.17.0/proton-c/src/core/event.c:108
> #4  0x77bb6bcc in qd_connection_free (ctx=0x7fffe400c290)
> at /usr/src/debug/qpid-dispatch-0.8.0/src/server.c:169
> #5  0x77bbaa21 in callback_amqpws (wsi=0x7fffe400a640, 
> reason=, user=0x7fffe400a850, in=0x0, len=0)
> at /usr/src/debug/qpid-dispatch-0.8.0/src/http-libwebsockets.c:496
> #6  0x76cffe6c in lws_close_free_wsi (wsi=wsi@entry=0x7fffe400a640, 
> reason=reason@entry=LWS_CLOSE_STATUS_NOSTATUS)
> at /usr/src/debug/libwebsockets-2.1.1/lib/libwebsockets.c:518
> #7  0x76d0179e in lws_service_fd_tsi (
> context=context@entry=0x559e08d0, pollfd=, 
> tsi=tsi@entry=0) at /usr/src/debug/libwebsockets-2.1.1/lib/service.c:1117
> #8  0x76d0bc73 in lws_plat_service_tsi (context=0x559e08d0, 
> timeout_ms=, tsi=tsi@entry=0)
> at /usr/src/debug/libwebsockets-2.1.1/lib/lws-plat-unix.c:184
> #9  0x76d0be47 in lws_plat_service (context=, 
> timeout_ms=)
> at /usr/src/debug/libwebsockets-2.1.1/lib/lws-plat-unix.c:204
> #10 0x76d01d55 in lws_service (context=, 
> timeout_ms=)
> at /usr/src/debug/libwebsockets-2.1.1/lib/service.c:1139
> #11 0x77bbb76c in http_thread_run (v=0x559f45f0)
> at /usr/src/debug/qpid-dispatch-0.8.0/src/http-libwebsockets.c:536
> #12 0x7770e6ca in start_thread () from /lib64/libpthread.so.0
> #13 0x76a39f7f in clone () from /lib64/libc.so.6
> Notes:
> $ rpm -qa | grep dispatch
> qpid-dispatch-debuginfo-0.8.0-2.fc25.x86_64
> qpid-dispatch-tools-0.8.0-2.fc25.x86_64
>

[jira] [Commented] (PROTON-1481) Improve the capability to inject work into serialised contexts

2017-10-16 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206449#comment-16206449
 ] 

ASF subversion and git services commented on PROTON-1481:
-

Commit 463aaf2b4143ac5e23d550d275468d14ea4e1b93 in qpid-proton's branch 
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=463aaf2 ]

PROTON-1481: [C++ binding] Move work API internals into internal namespace


> Improve the capability to inject work into serialised contexts
> --
>
> Key: PROTON-1481
> URL: https://issues.apache.org/jira/browse/PROTON-1481
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: proton-c-0.18.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1618) Give unambiguous indication when server listen operation succeeds or fails

2017-10-16 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206303#comment-16206303
 ] 

ASF subversion and git services commented on PROTON-1618:
-

Commit b4e0edd2cab25b95a6fa245d00c35928de01550e in qpid-proton's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b4e0edd ]

PROTON-1618: c++ provide separate test_port implementation

Break unwanted dependency between C++ and C test trees.


> Give unambiguous indication when server listen operation succeeds or fails
> --
>
> Key: PROTON-1618
> URL: https://issues.apache.org/jira/browse/PROTON-1618
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Alan Conway
>  Labels: api
> Fix For: proton-c-0.18.0
>
>
> The C proactor API provides events to indicate when an async listen operation 
> has succeeded or failed, but the semantics are a little unclear. The C++ API 
> lacks the required events.
> Simplify & clarify the C API, and add the missing events in C++.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[ANNOUNCE] Apache Qpid Proton-J 0.23.0 released

2017-10-16 Thread Robbie Gemmell 
The Apache Qpid (http://qpid.apache.org) community is pleased to announce
the immediate availability of Apache Qpid Proton-J 0.23.0.

Apache Qpid Proton-J is a messaging library for the Advanced Message Queuing
Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It can be used
in a wide range of messaging applications including brokers, clients,
routers, bridges, proxies, and more.

The release is available now from our website:
http://qpid.apache.org/download.html

Binaries are also available via Maven Central:
http://qpid.apache.org/maven.html

Release notes can be found at:
http://qpid.apache.org/releases/qpid-proton-j-0.23.0/release-notes.html

Thanks to all involved,
Robbie

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPIDJMS-341) update to proton-j 0.23.0

2017-10-16 Thread Robbie Gemmell (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPIDJMS-341.

Resolution: Fixed

> update to proton-j 0.23.0
> -
>
> Key: QPIDJMS-341
> URL: https://issues.apache.org/jira/browse/QPIDJMS-341
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Trivial
> Fix For: 0.27.0
>
>
> update to latest proton-j



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDJMS-341) update to proton-j 0.23.0

2017-10-16 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPIDJMS-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206127#comment-16206127
 ] 

ASF subversion and git services commented on QPIDJMS-341:
-

Commit 1f9bf005fdf2e53f54f1f0ff7cb7b640939fb8af in qpid-jms's branch 
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=1f9bf00 ]

QPIDJMS-341: update to proton-j-0.23.0


> update to proton-j 0.23.0
> -
>
> Key: QPIDJMS-341
> URL: https://issues.apache.org/jira/browse/QPIDJMS-341
> Project: Qpid JMS
>  Issue Type: Task
>  Components: qpid-jms-client
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Trivial
> Fix For: 0.27.0
>
>
> update to latest proton-j



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPIDJMS-341) update to proton-j 0.23.0

2017-10-16 Thread Robbie Gemmell (JIRA) 
Robbie Gemmell created QPIDJMS-341:
--

 Summary: update to proton-j 0.23.0
 Key: QPIDJMS-341
 URL: https://issues.apache.org/jira/browse/QPIDJMS-341
 Project: Qpid JMS
  Issue Type: Task
  Components: qpid-jms-client
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
Priority: Trivial
 Fix For: 0.27.0


update to latest proton-j



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPIDJMS-335) SCRAM-SHA mechanism impls erroneously escape "=" and "," in the password during processing

2017-10-16 Thread Robbie Gemmell (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPIDJMS-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPIDJMS-335.

Resolution: Fixed

> SCRAM-SHA mechanism impls erroneously escape "=" and "," in the password 
> during processing
> --
>
> Key: QPIDJMS-335
> URL: https://issues.apache.org/jira/browse/QPIDJMS-335
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.26.0
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.27.0
>
>
> Per discussion on 
> http://mail-archives.apache.org/mod_mbox/qpid-users/201710.mbox/%3C1507290028737-0.post%40n2.nabble.com%3E
>  the client is erroneously escaping "=" and "," during password handling, 
> whereas the SCRAM mechanisms only require this for the username and some 
> other cases, causing authentication to fail when they are present as the 
> wrong value is used to compute the details sent to the server.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDJMS-335) SCRAM-SHA mechanism impls erroneously escape "=" and "," in the password during processing

2017-10-16 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPIDJMS-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206048#comment-16206048
 ] 

ASF subversion and git services commented on QPIDJMS-335:
-

Commit 89e8f9908c476a942e23c6762541df774db963fd in qpid-jms's branch 
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=89e8f99 ]

QPIDJMS-335: ensure SCRAM mechs only escape '=' and ',' for the username and 
not the password


> SCRAM-SHA mechanism impls erroneously escape "=" and "," in the password 
> during processing
> --
>
> Key: QPIDJMS-335
> URL: https://issues.apache.org/jira/browse/QPIDJMS-335
> Project: Qpid JMS
>  Issue Type: Bug
>  Components: qpid-jms-client
>Affects Versions: 0.26.0
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
> Fix For: 0.27.0
>
>
> Per discussion on 
> http://mail-archives.apache.org/mod_mbox/qpid-users/201710.mbox/%3C1507290028737-0.post%40n2.nabble.com%3E
>  the client is erroneously escaping "=" and "," during password handling, 
> whereas the SCRAM mechanisms only require this for the username and some 
> other cases, causing authentication to fail when they are present as the 
> wrong value is used to compute the details sent to the server.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1632) Split SO versions by library

2017-10-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205991#comment-16205991
 ] 

ASF GitHub Bot commented on PROTON-1632:


Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/126
  
Looks good to me


> Split SO versions by library
> 
>
> Key: PROTON-1632
> URL: https://issues.apache.org/jira/browse/PROTON-1632
> Project: Qpid Proton
>  Issue Type: Task
>  Components: proton-c
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: proton-c-0.18.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton issue #126: PROTON-1632: WIP: Split library versions

2017-10-16 Thread astitcher 
Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/126
  
Looks good to me


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-7972) Virtual Host Node should be in error state if the underlying Virtual Host is in error state

2017-10-16 Thread Adel Boutros (JIRA) 
Adel Boutros created QPID-7972:
--

 Summary: Virtual Host Node should be in error state if the 
underlying Virtual Host is in error state
 Key: QPID-7972
 URL: https://issues.apache.org/jira/browse/QPID-7972
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Affects Versions: qpid-java-6.1.4
Reporter: Adel Boutros


All details can be found here: 
http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-6-1-4-Broker-is-ready-even-if-an-error-is-occuring-on-startup-and-failStartupWithEre-tp7668029.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-580) Log stats should be graphable

2017-10-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205917#comment-16205917
 ] 

ASF GitHub Bot commented on DISPATCH-580:
-

Github user ganeshmurthy commented on the issue:

https://github.com/apache/qpid-dispatch/pull/210
  
Looks good @ErnieAllen feel free to check it in


> Log stats should be graphable
> -
>
> Key: DISPATCH-580
> URL: https://issues.apache.org/jira/browse/DISPATCH-580
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.8.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> The log statistics added with DISPATCH-553 are integers that could be 
> graphed. However, in order to graph them the console needs a 'graph' property 
> present in the schema for each graphable attribute in the logStats entity.
> Add a graph property to the counts in logStats.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch issue #210: DISPATCH-580 Adding graph=true for logStats statis...

2017-10-16 Thread ganeshmurthy 
Github user ganeshmurthy commented on the issue:

https://github.com/apache/qpid-dispatch/pull/210
  
Looks good @ErnieAllen feel free to check it in


---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-580) Log stats should be graphable

2017-10-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205850#comment-16205850
 ] 

ASF GitHub Bot commented on DISPATCH-580:
-

GitHub user ErnieAllen opened a pull request:

https://github.com/apache/qpid-dispatch/pull/210

DISPATCH-580 Adding graph=true for logStats statistics

Added graph=true so logStats can be graphed by the console

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ErnieAllen/qpid-dispatch ernie-dispatch-580

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/210.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #210


commit f9144afda3e056ac2d66afa5b25f5442517f0888
Author: Ernest Allen 
Date:   2017-10-16T12:55:52Z

DISPATCH-580 Adding graph=true for logStats statistics




> Log stats should be graphable
> -
>
> Key: DISPATCH-580
> URL: https://issues.apache.org/jira/browse/DISPATCH-580
> Project: Qpid Dispatch
>  Issue Type: Bug
>  Components: Management Agent
>Affects Versions: 0.8.0
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> The log statistics added with DISPATCH-553 are integers that could be 
> graphed. However, in order to graph them the console needs a 'graph' property 
> present in the schema for each graphable attribute in the logStats entity.
> Add a graph property to the counts in logStats.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch pull request #210: DISPATCH-580 Adding graph=true for logStats...

2017-10-16 Thread ErnieAllen 
GitHub user ErnieAllen opened a pull request:

https://github.com/apache/qpid-dispatch/pull/210

DISPATCH-580 Adding graph=true for logStats statistics

Added graph=true so logStats can be graphed by the console

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ErnieAllen/qpid-dispatch ernie-dispatch-580

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/210.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #210


commit f9144afda3e056ac2d66afa5b25f5442517f0888
Author: Ernest Allen 
Date:   2017-10-16T12:55:52Z

DISPATCH-580 Adding graph=true for logStats statistics




---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-856) Return router's hostname as a read-only attribute on the router entity

2017-10-16 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/DISPATCH-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205840#comment-16205840
 ] 

ASF GitHub Bot commented on DISPATCH-856:
-

GitHub user ErnieAllen opened a pull request:

https://github.com/apache/qpid-dispatch/pull/209

DISPATCH-856 Add hostName to router entity

The router.hostName will be used by the console to visually group routers 
that are deployed on the same machine.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ErnieAllen/qpid-dispatch ernie-dispatch-856

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/209.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #209


commit 45daf229475d4059c8e128a09397d0b426bef932
Author: Ernest Allen 
Date:   2017-10-16T12:41:49Z

DISPATCH-856 Add hostName to router entity




> Return router's hostname as a read-only attribute on the router entity
> --
>
> Key: DISPATCH-856
> URL: https://issues.apache.org/jira/browse/DISPATCH-856
> Project: Qpid Dispatch
>  Issue Type: New Feature
>  Components: Management Agent
>Reporter: Ernest Allen
>Assignee: Ernest Allen
>Priority: Minor
> Fix For: 1.1.0
>
>
> It would be useful for the console to have the hostname of the machine on 
> which a router is running. Rather than a separate management call, I'd prefer 
> this to be returned as an attribute in the router entity.
> The console could then show routers that are co-located on a machine in the 
> same color.
> Ideally, there would also be a separate management call to return more 
> information about the router's host machine such as:
> - OS name and version
> - OS x86 or x64
> - machine date-time
> - machine timezone
> - memory installed
> - number of cpus
> - ipv4 and ipv6 addresses
> - geo location info (country/city or lon. lat.) (set in router's config file)
> I imagine there would be a policy that determines which of these are returned.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-dispatch pull request #209: DISPATCH-856 Add hostName to router entity

2017-10-16 Thread ErnieAllen 
GitHub user ErnieAllen opened a pull request:

https://github.com/apache/qpid-dispatch/pull/209

DISPATCH-856 Add hostName to router entity

The router.hostName will be used by the console to visually group routers 
that are deployed on the same machine.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ErnieAllen/qpid-dispatch ernie-dispatch-856

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-dispatch/pull/209.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #209


commit 45daf229475d4059c8e128a09397d0b426bef932
Author: Ernest Allen 
Date:   2017-10-16T12:41:49Z

DISPATCH-856 Add hostName to router entity




---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1542) hostname should be set on sasl-init

2017-10-16 Thread Gordon Sim (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205680#comment-16205680
 ] 

Gordon Sim commented on PROTON-1542:


The fix for PROTON-1535 allows a sasl plugin to set the hostname, which was my 
immediate need at the time, and it does not alter default behaviour or public 
API in anyway. I understood us to have agreed that we should create a new issue 
for any more general changes, and rename PROTON-1535 to make it clear it was 
just an enhancement to the new sasl plugin API. 

As to the choice of the field name, I saw there was a remote_fqdn there already 
and assumed that was the value for hostname specified by the peer. In general, 
the 'remote' qualification in proton names is always something received from 
the peer. As what I was adding was the ability to set the local value, i.e. the 
value that will be sent to the peer, I used the same basic name with prefix 
'local'. The name of the field is an internal detail, I would not have chosen 
'fqdn' had it not been there already. More important is the API to it, which in 
the plugin API is pnx_sasl_set_local_hostname which I think is clear. Arguably 
the 'local' could be dropped.

Looking at the actual use in existing code of the remote_fqdn, I see it is set 
from transport.c, which suggests it is not intended as the hostname sent by the 
peer, and as you say it seems that value is never actually decoded. I had again 
assumed that pnx_sasl_get_remote_fqdn() was the accessor to what the peer set 
as the hostname.

> hostname should be set on sasl-init
> ---
>
> Key: PROTON-1542
> URL: https://issues.apache.org/jira/browse/PROTON-1542
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: proton-c
>Reporter: Gordon Sim
>Assignee: Andrew Stitcher
> Fix For: proton-c-0.19.0
>
>
> For a multi-tenant service/server, where each tenant has its own user base, 
> the hostname in the sasl-init frame provides a convenient way of determining 
> the correct tenant to authenticate for.
> At present this is not set for any proton-c based client. It is similar to 
> the SNI information included in the TLS layer initiation (if such a layer is 
> in use).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1619) C and C++ API clean up

2017-10-16 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/PROTON-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205646#comment-16205646
 ] 

ASF subversion and git services commented on PROTON-1619:
-

Commit 1ad1e656f00333be9690995a8a8e45b83ce2a01c in qpid-proton's branch 
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1ad1e65 ]

PROTON-1619: restore pn_connection_driver_log functions, deprecated.

Preserve ABI compatibility with 0.17: restore but mark deprecated.


> C and C++ API clean up
> --
>
> Key: PROTON-1619
> URL: https://issues.apache.org/jira/browse/PROTON-1619
> Project: Qpid Proton
>  Issue Type: Task
>  Components: cpp-binding, proton-c
>Reporter: Justin Ross
>Assignee: Alan Conway
> Fix For: proton-c-0.18.0
>
>
> From our review.
> Use pni_ prefix
>  - pn_log_enabled
>  - pn_logf_impl
>  - pn_vlogf_impl
> Remove or don't export
>  - pn_message_get_extra
>  - pn_message_with_extra
>  - pn_connection_driver_logf
>  - pni_parse_url



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (PROTON-1619) C and C++ API clean up

2017-10-16 Thread Alan Conway (JIRA) 

 [ 
https://issues.apache.org/jira/browse/PROTON-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan Conway resolved PROTON-1619.
-
Resolution: Fixed

> C and C++ API clean up
> --
>
> Key: PROTON-1619
> URL: https://issues.apache.org/jira/browse/PROTON-1619
> Project: Qpid Proton
>  Issue Type: Task
>  Components: cpp-binding, proton-c
>Reporter: Justin Ross
>Assignee: Alan Conway
> Fix For: proton-c-0.18.0
>
>
> From our review.
> Use pni_ prefix
>  - pn_log_enabled
>  - pn_logf_impl
>  - pn_vlogf_impl
> Remove or don't export
>  - pn_message_get_extra
>  - pn_message_with_extra
>  - pn_connection_driver_logf
>  - pni_parse_url



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-7799) Broker should be able to write a periodic dump of statistics

2017-10-16 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205481#comment-16205481
 ] 

ASF subversion and git services commented on QPID-7799:
---

Commit 4cfa7c30f149cd4e8fbc02b267e15859699bcfce in qpid-broker-j's branch 
refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=4cfa7c3 ]

QPID-7799: [Statistics Reporting] Have the statistic reporting task traverse 
associated children  (i.e. connections associated with virtualhosts) too.


> Broker should be able to write a periodic dump of statistics
> 
>
> Key: QPID-7799
> URL: https://issues.apache.org/jira/browse/QPID-7799
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
> Attachments: 
> 0001-QPID-7799-Java-Broker-Improve-statistics-reporting.patch
>
>
> To assist those running a service, the Broker should have the ability to 
> write a periodic dump of ConiguredObject statistics to the log file.   It 
> should be possible to configure the statistics dumped at runtime and be 
> configured on a per-category or per-object instance basis.   Within a HA 
> group, the configuration applied to objects belonging to a virtualhost must 
> survive a mastership change.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org