[jira] [Commented] (PROTON-1720) [ruby] support for SSL configuration via connection options

2017-12-15 Thread ASF subversion and git services (JIRA) 

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

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

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

PROTON-1720: [ruby] Add missing connection options, update Connection API.


> [ruby] support for SSL configuration via connection options
> ---
>
> Key: PROTON-1720
> URL: https://issues.apache.org/jira/browse/PROTON-1720
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: ruby-binding
>Affects Versions: proton-c-0.18.1
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> Add SSL configuration options to container, SSL tests and examples.



--
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-1721) [ruby] resovler errors are not handled correctly

2017-12-15 Thread ASF subversion and git services (JIRA) 

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

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

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

PROTON-1721 [ruby] resovler errors are not handled correctly

Catch exceptions raised by TCPServer.new/TCPSocket.new and convert into error 
events.


> [ruby] resovler errors are not handled correctly
> 
>
> Key: PROTON-1721
> URL: https://issues.apache.org/jira/browse/PROTON-1721
> Project: Qpid Proton
>  Issue Type: Bug
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> Exceptions raised by TCPSocket.new/TCPServer.new are raised out of 
> Container#connnect/listen instead of being turned into error events. 



--
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-1537) ruby: update API in line with new C++ API changes

2017-12-15 Thread ASF subversion and git services (JIRA) 

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

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

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

PROTON-1537: [ruby] added Tracker#abort


> ruby: update API in line with new C++ API changes
> -
>
> Key: PROTON-1537
> URL: https://issues.apache.org/jira/browse/PROTON-1537
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: ruby-binding
>Affects Versions: proton-c-0.17.0
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> Update the ruby Container interface in line with the new C++ container API
> Deprecate Reactor (use Container instead)
> Deprecate or remove Messenger API.



--
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-1537) ruby: update API in line with new C++ API changes

2017-12-15 Thread ASF subversion and git services (JIRA) 

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

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

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

PROTON-1537: [ruby] Fix all -W2 warnings in self-tests


> ruby: update API in line with new C++ API changes
> -
>
> Key: PROTON-1537
> URL: https://issues.apache.org/jira/browse/PROTON-1537
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: ruby-binding
>Affects Versions: proton-c-0.17.0
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> Update the ruby Container interface in line with the new C++ container API
> Deprecate Reactor (use Container instead)
> Deprecate or remove Messenger API.



--
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-1721) [ruby] resovler errors are not handled correctly

2017-12-15 Thread Alan Conway (JIRA) 

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

Alan Conway resolved PROTON-1721.
-
   Resolution: Fixed
Fix Version/s: proton-c-0.19.0

> [ruby] resovler errors are not handled correctly
> 
>
> Key: PROTON-1721
> URL: https://issues.apache.org/jira/browse/PROTON-1721
> Project: Qpid Proton
>  Issue Type: Bug
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> Exceptions raised by TCPSocket.new/TCPServer.new are raised out of 
> Container#connnect/listen instead of being turned into error events. 



--
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-1537) ruby: update API in line with new C++ API changes

2017-12-15 Thread ASF subversion and git services (JIRA) 

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

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

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

PROTON-1537: [ruby] Replace head/next with each

Connection provides each_session, Connection and Session provide each_link,
each_sender, each_receiver


> ruby: update API in line with new C++ API changes
> -
>
> Key: PROTON-1537
> URL: https://issues.apache.org/jira/browse/PROTON-1537
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: ruby-binding
>Affects Versions: proton-c-0.17.0
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> Update the ruby Container interface in line with the new C++ container API
> Deprecate Reactor (use Container instead)
> Deprecate or remove Messenger API.



--
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-1721) [ruby] resovler errors are not handled correctly

2017-12-15 Thread ASF subversion and git services (JIRA) 

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

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

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

PROTON-1721 [ruby] resovler errors are not handled correctly

Catch exceptions raised by TCPServer.new/TCPSocket.new and convert into error 
events.


> [ruby] resovler errors are not handled correctly
> 
>
> Key: PROTON-1721
> URL: https://issues.apache.org/jira/browse/PROTON-1721
> Project: Qpid Proton
>  Issue Type: Bug
>Reporter: Alan Conway
>Assignee: Alan Conway
>
> Exceptions raised by TCPSocket.new/TCPServer.new are raised out of 
> Container#connnect/listen instead of being turned into error events. 



--
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-1537) ruby: update API in line with new C++ API changes

2017-12-15 Thread ASF subversion and git services (JIRA) 

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

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

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

PROTON-1537: [ruby] Fix all -W2 warnings in self-tests


> ruby: update API in line with new C++ API changes
> -
>
> Key: PROTON-1537
> URL: https://issues.apache.org/jira/browse/PROTON-1537
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: ruby-binding
>Affects Versions: proton-c-0.17.0
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> Update the ruby Container interface in line with the new C++ container API
> Deprecate Reactor (use Container instead)
> Deprecate or remove Messenger API.



--
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-1537) ruby: update API in line with new C++ API changes

2017-12-15 Thread ASF subversion and git services (JIRA) 

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

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

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

PROTON-1537: [ruby] added Tracker#abort


> ruby: update API in line with new C++ API changes
> -
>
> Key: PROTON-1537
> URL: https://issues.apache.org/jira/browse/PROTON-1537
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: ruby-binding
>Affects Versions: proton-c-0.17.0
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> Update the ruby Container interface in line with the new C++ container API
> Deprecate Reactor (use Container instead)
> Deprecate or remove Messenger API.



--
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-1537) ruby: update API in line with new C++ API changes

2017-12-15 Thread ASF subversion and git services (JIRA) 

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

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

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

PROTON-1537: [ruby] Replace head/next with each

Connection provides each_session, Connection and Session provide each_link,
each_sender, each_receiver


> ruby: update API in line with new C++ API changes
> -
>
> Key: PROTON-1537
> URL: https://issues.apache.org/jira/browse/PROTON-1537
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: ruby-binding
>Affects Versions: proton-c-0.17.0
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> Update the ruby Container interface in line with the new C++ container API
> Deprecate Reactor (use Container instead)
> Deprecate or remove Messenger API.



--
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] (PROTON-1721) [ruby] resovler errors are not handled correctly

2017-12-15 Thread Alan Conway (JIRA) 
Alan Conway created PROTON-1721:
---

 Summary: [ruby] resovler errors are not handled correctly
 Key: PROTON-1721
 URL: https://issues.apache.org/jira/browse/PROTON-1721
 Project: Qpid Proton
  Issue Type: Bug
Reporter: Alan Conway
Assignee: Alan Conway


Exceptions raised by TCPSocket.new/TCPServer.new are raised out of 
Container#connnect/listen instead of being turned into error events. 



--
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

Re: Review Request 64645: authorization support for sasl delegation plugin

2017-12-15 Thread Chug Rolke 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/64645/#review193976
---



This seems like a decent approach for starters.

It may have an issue when multiple vhosts come in to the router on the same 
port. All of the connections then are sent to the same authServicePlugin 
authService port for authentication and authz. In the current policy scheme the 
policy is decided later when the AMQP Open frame's hostname field is used as 
the name of the vhost policy. Then the user name is looked up in that vhost 
policy section.


tests/system_tests_authz_service_plugin.py
Lines 67 (patched)


My system gets an error running authservice.py as the file is not in 
os.getcwd() but four levels of directory up. It works with

cls.tester.popen([os.path.join(os.path.dirname(os.path.abspath(__file__)), 
'authservice.py'), '-a', '127.0.0.1:%d' % cls.auth_service_port, '-c', 
os.getcwd()], expect=Process.RUNNING)

and having 'chmod +x authservice.py'


- Chug Rolke


On Dec. 15, 2017, 6:20 p.m., Gordon Sim wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/64645/
> ---
> 
> (Updated Dec. 15, 2017, 6:20 p.m.)
> 
> 
> Review request for qpid, Chug Rolke, Ganesh Murthy, and Ted Ross.
> 
> 
> Bugs: DISPATCH-901
> https://issues.apache.org/jira/browse/DISPATCH-901
> 
> 
> Repository: qpid-dispatch
> 
> 
> Description
> ---
> 
> If the client specifies its desire for the ADDRESS-AUTHZ capacbility, the 
> authorization service, if it supports this, will return a set of permissions 
> in the properties of the open frame. The properties will have an 
> address-authz key, whose value is a map of address (or wildcard pattern) to 
> an array of permissions. The only permissions recognised at present by this 
> patch are 'send' and 'recv'.
> 
> 
> Diffs
> -
> 
>   src/policy.c 22cc79f 
>   src/remote_sasl.c e3c969b 
>   tests/CMakeLists.txt 0c6454c 
>   tests/authservice.py PRE-CREATION 
>   tests/system_tests_authz_service_plugin.py PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/64645/diff/2/
> 
> 
> Testing
> ---
> 
> Added new systems tests using proton python based dummy auth service.
> 
> 
> Thanks,
> 
> Gordon Sim
> 
>

[jira] [Created] (DISPATCH-904) Add charts to overview page

2017-12-15 Thread Ernest Allen (JIRA) 
Ernest Allen created DISPATCH-904:
-

 Summary: Add charts to overview page
 Key: DISPATCH-904
 URL: https://issues.apache.org/jira/browse/DISPATCH-904
 Project: Qpid Dispatch
  Issue Type: Improvement
  Components: Console
Affects Versions: 1.0.0
Reporter: Ernest Allen
Assignee: Ernest Allen


a. Total message throughput rate
b. Total outstanding messages (messages in flight)
c. List of most active clients with their message throughput and rates
d. more to come



--
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-903) Use patternfly library for charts for consistency and mantainability

2017-12-15 Thread Ernest Allen (JIRA) 
Ernest Allen created DISPATCH-903:
-

 Summary: Use patternfly library for charts for consistency and 
mantainability
 Key: DISPATCH-903
 URL: https://issues.apache.org/jira/browse/DISPATCH-903
 Project: Qpid Dispatch
  Issue Type: Improvement
  Components: Console
Affects Versions: 1.0.0
Reporter: Ernest Allen
Assignee: Ernest Allen


Switch to using the c3 charting library that is used by patternfly. This will 
be more consistent with other patternfly compliant consoles.

Some homegrown features may not be possible in c3:
- stacked aggregate charts




--
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

Re: Review Request 64645: authorization support for sasl delegation plugin

2017-12-15 Thread Gordon Sim 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/64645/
---

(Updated Dec. 15, 2017, 6:20 p.m.)


Review request for qpid, Chug Rolke, Ganesh Murthy, and Ted Ross.


Changes
---

Updated to always use the permissions from the auth service even if config 
based policy is also in place (this is one option, an alternative could be to 
always overwrite any auth service policies from config or to somehow try and 
combine them)


Bugs: DISPATCH-901
https://issues.apache.org/jira/browse/DISPATCH-901


Repository: qpid-dispatch


Description
---

If the client specifies its desire for the ADDRESS-AUTHZ capacbility, the 
authorization service, if it supports this, will return a set of permissions in 
the properties of the open frame. The properties will have an address-authz 
key, whose value is a map of address (or wildcard pattern) to an array of 
permissions. The only permissions recognised at present by this patch are 
'send' and 'recv'.


Diffs (updated)
-

  src/policy.c 22cc79f 
  src/remote_sasl.c e3c969b 
  tests/CMakeLists.txt 0c6454c 
  tests/authservice.py PRE-CREATION 
  tests/system_tests_authz_service_plugin.py PRE-CREATION 


Diff: https://reviews.apache.org/r/64645/diff/2/

Changes: https://reviews.apache.org/r/64645/diff/1-2/


Testing
---

Added new systems tests using proton python based dummy auth service.


Thanks,

Gordon Sim

[jira] [Updated] (DISPATCH-902) Intermittent crash with link to broker when broker closed

2017-12-15 Thread Kim van der Riet (JIRA) 

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

Kim van der Riet updated DISPATCH-902:
--
Description: 
When using dispatch in a 2-node configuration with a broker between them:

{noformat}
9002   10001   100019003
sender > dispatch1 -> qpid-cpp -> dispatch2 -> receiver
{noformat}

and initializing in the following order:
# start dispatch1
# start dispatch2
# start qpid-cpp
# wait for "Link Route Activated" messages on both dispatch nodes
# stop qpid-cpp

then the dispatch nodes will core after a random amount of time and after 
sending a random number of 
{noformat}
(info) Connection to localhost:10001 failed: proton:io Connection refused - on 
read from localhost:10001
{noformat}
messages.

The stack trace is as follows for all occurrences:
{noformat}
Thread 3 "qdrouterd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffea269700 (LWP 10954)]
pn_transport_tail_closed (transport=0x0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/transport.c:3044
3044bool pn_transport_tail_closed(pn_transport_t *transport) { return 
transport->tail_closed; }
(gdb) thread apply all bt

Thread 5 (Thread 0x7fffe9267700 (LWP 10956)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x775185ca in start_thread (arg=0x7fffe9267700) at 
pthread_create.c:333
#5  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fffe9a68700 (LWP 10955)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x775185ca in start_thread (arg=0x7fffe9a68700) at 
pthread_create.c:333
#5  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fffea269700 (LWP 10954)):
#0  pn_transport_tail_closed (transport=0x0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/transport.c:3044
#1  0x7794f4f9 in pn_connection_driver_read_closed 
(d=d@entry=0x7fffdc054288) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/connection_driver.c:109
#2  0x77731ef1 in pconnection_rclosed (pc=0x7fffdc053ce0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:898
#3  pconnection_process (pc=0x7fffdc053ce0, events=, 
timeout=timeout@entry=false, topup=topup@entry=false) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1084
#4  0x77732945 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2007
#5  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#6  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#7  0x775185ca in start_thread (arg=0x7fffea269700) at 
pthread_create.c:333
#8  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fffeaa6a700 (LWP 10953)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x77ba2949 in sys_cond_wait (cond=, 
held_mutex=) at 
/home/kpvdr/RedHat/qpid-dispatch/src/posix/threading.c:91
#2  0x77bb0cf5 in router_core_thread (arg=0x8f8c90) at 
/home/kpvdr/RedHat/qpid-dispatch/src/router_core/router_core_thread.c:66
#3  0x775185ca in start_thread (arg=0x7fffeaa6a700) at 
pthread_create.c:333
#4  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x77fbb180 (LWP 10946)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=arg@entry=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x77bbc2f0 in qd_server_run (qd=) at 
/

[jira] [Updated] (DISPATCH-902) Intermittent crash with link to broker when broker closed

2017-12-15 Thread Kim van der Riet (JIRA) 

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

Kim van der Riet updated DISPATCH-902:
--
Description: 
When using dispatch in a 2-node configuration with a broker between them:

{noformat}
9002   10001   100019003
sender > dispatch1 -> qpid-cpp -> dispatch2 -> receiver
{noformat}

and initializing in the following order:
# start dispatch1
# start dispatch2
# start qpid-cpp
# wait for "Link Route Activated" messages on both dispatch nodes
# stop qpid-cpp

then the dispatch nodes will core after a random amount of time and after 
sending a random number of 
{noformat}
(info) Connection to localhost:10001 failed: proton:io Connection refused - on 
read from localhost:10001
{noformat}
messages.

The stack trace is as follows for all occurrences:
{noformat}
Thread 3 "qdrouterd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffea269700 (LWP 10954)]
pn_transport_tail_closed (transport=0x0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/transport.c:3044
3044bool pn_transport_tail_closed(pn_transport_t *transport) { return 
transport->tail_closed; }
(gdb) thread apply all bt

Thread 5 (Thread 0x7fffe9267700 (LWP 10956)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x775185ca in start_thread (arg=0x7fffe9267700) at 
pthread_create.c:333
#5  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fffe9a68700 (LWP 10955)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x775185ca in start_thread (arg=0x7fffe9a68700) at 
pthread_create.c:333
#5  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fffea269700 (LWP 10954)):
#0  pn_transport_tail_closed (transport=0x0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/transport.c:3044
#1  0x7794f4f9 in pn_connection_driver_read_closed 
(d=d@entry=0x7fffdc054288) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/connection_driver.c:109
#2  0x77731ef1 in pconnection_rclosed (pc=0x7fffdc053ce0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:898
#3  pconnection_process (pc=0x7fffdc053ce0, events=, 
timeout=timeout@entry=false, topup=topup@entry=false) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1084
#4  0x77732945 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2007
#5  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#6  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#7  0x775185ca in start_thread (arg=0x7fffea269700) at 
pthread_create.c:333
#8  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fffeaa6a700 (LWP 10953)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x77ba2949 in sys_cond_wait (cond=, 
held_mutex=) at 
/home/kpvdr/RedHat/qpid-dispatch/src/posix/threading.c:91
#2  0x77bb0cf5 in router_core_thread (arg=0x8f8c90) at 
/home/kpvdr/RedHat/qpid-dispatch/src/router_core/router_core_thread.c:66
#3  0x775185ca in start_thread (arg=0x7fffeaa6a700) at 
pthread_create.c:333
#4  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x77fbb180 (LWP 10946)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=arg@entry=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x77bbc2f0 in qd_server_run (qd=) at 
/

[jira] [Updated] (DISPATCH-902) Intermittent crash with link to broker when broker closed

2017-12-15 Thread Kim van der Riet (JIRA) 

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

Kim van der Riet updated DISPATCH-902:
--
Description: 
When using dispatch in a 2-node configuration with a broker between them:

{noformat}
9002   10001   100019003
sender > dispatch1 -> qpid-cpp -> dispatch2 -> receiver
{noformat}

and initializing in the following order:
# start dispatch1
# start dispatch2
# start qpid-cpp
# wait for "Link Route Activated" messages on both dispatch nodes
# stop qpid-cpp

then the dispatch nodes will core after a random amount of time and after 
sending a random number of 
{noformat}
(info) Connection to localhost:10001 failed: proton:io Connection refused - on 
read from localhost:10001
{noformat}
messages.

The stack trace is as follows for all occurrences:
{noformat}
Thread 3 "qdrouterd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffea269700 (LWP 10954)]
pn_transport_tail_closed (transport=0x0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/transport.c:3044
3044bool pn_transport_tail_closed(pn_transport_t *transport) { return 
transport->tail_closed; }
(gdb) thread apply all bt

Thread 5 (Thread 0x7fffe9267700 (LWP 10956)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x775185ca in start_thread (arg=0x7fffe9267700) at 
pthread_create.c:333
#5  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fffe9a68700 (LWP 10955)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x775185ca in start_thread (arg=0x7fffe9a68700) at 
pthread_create.c:333
#5  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fffea269700 (LWP 10954)):
#0  pn_transport_tail_closed (transport=0x0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/transport.c:3044
#1  0x7794f4f9 in pn_connection_driver_read_closed 
(d=d@entry=0x7fffdc054288) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/connection_driver.c:109
#2  0x77731ef1 in pconnection_rclosed (pc=0x7fffdc053ce0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:898
#3  pconnection_process (pc=0x7fffdc053ce0, events=, 
timeout=timeout@entry=false, topup=topup@entry=false) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1084
#4  0x77732945 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2007
#5  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#6  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#7  0x775185ca in start_thread (arg=0x7fffea269700) at 
pthread_create.c:333
#8  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fffeaa6a700 (LWP 10953)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x77ba2949 in sys_cond_wait (cond=, 
held_mutex=) at 
/home/kpvdr/RedHat/qpid-dispatch/src/posix/threading.c:91
#2  0x77bb0cf5 in router_core_thread (arg=0x8f8c90) at 
/home/kpvdr/RedHat/qpid-dispatch/src/router_core/router_core_thread.c:66
#3  0x775185ca in start_thread (arg=0x7fffeaa6a700) at 
pthread_create.c:333
#4  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x77fbb180 (LWP 10946)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=arg@entry=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x77bbc2f0 in qd_server_run (qd=) at 
/

[jira] [Updated] (DISPATCH-902) Intermittent crash with link to broker when broker closed

2017-12-15 Thread Kim van der Riet (JIRA) 

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

Kim van der Riet updated DISPATCH-902:
--
Attachment: qdrouterd.node1.conf
qdrouterd.node2.conf
qpidd.d2n.conf

Config files for the two dispatch nodes and for qpid-cpp attached.

> Intermittent crash with link to broker when broker closed
> -
>
> Key: DISPATCH-902
> URL: https://issues.apache.org/jira/browse/DISPATCH-902
> Project: Qpid Dispatch
>  Issue Type: Bug
>Reporter: Kim van der Riet
> Attachments: qdrouterd.node1.conf, qdrouterd.node2.conf, 
> qpidd.d2n.conf
>
>
> When using dispatch in a 2-node configuration with a broker between them:
> {noformat}
> 9002   10001   100019003
> sender > dispatch1 -> qpid-cpp -> dispatch2 -> receiver
> {noformat}
> and initializing in the following order:
> # start dispatch1
> # start dispatch2
> # start qpid-cpp
> # wait for "Link Route Activated" messages on both dispatch nodes
> # stop qpid-cpp
> then the dispatch nodes will core after a random amount of time and after 
> sending a random number of 
> {noformat}
> (info) Connection to localhost:10001 failed: proton:io Connection refused - 
> on read from localhost:10001
> {noformat}
> messages.
> The stack trace is as follows for all occurrences:
> {noformat}
> Thread 3 "qdrouterd" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffea269700 (LWP 10954)]
> pn_transport_tail_closed (transport=0x0) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/core/transport.c:3044
> 3044  bool pn_transport_tail_closed(pn_transport_t *transport) { return 
> transport->tail_closed; }
> (gdb) thread apply all bt
> Thread 5 (Thread 0x7fffe9267700 (LWP 10956)):
> #0  0x767eb6d3 in epoll_wait () at 
> ../sysdeps/unix/syscall-template.S:84
> #1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
> can_block=can_block@entry=true) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
> #2  0x777337ca in pn_proactor_wait (p=) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
> #3  0x77bbc219 in thread_run (arg=0x89ec20) at 
> /home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
> #4  0x775185ca in start_thread (arg=0x7fffe9267700) at 
> pthread_create.c:333
> #5  0x767eb0cd in clone () at 
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> Thread 4 (Thread 0x7fffe9a68700 (LWP 10955)):
> #0  0x767eb6d3 in epoll_wait () at 
> ../sysdeps/unix/syscall-template.S:84
> #1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
> can_block=can_block@entry=true) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
> #2  0x777337ca in pn_proactor_wait (p=) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
> #3  0x77bbc219 in thread_run (arg=0x89ec20) at 
> /home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
> #4  0x775185ca in start_thread (arg=0x7fffe9a68700) at 
> pthread_create.c:333
> #5  0x767eb0cd in clone () at 
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> Thread 3 (Thread 0x7fffea269700 (LWP 10954)):
> #0  pn_transport_tail_closed (transport=0x0) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/core/transport.c:3044
> #1  0x7794f4f9 in pn_connection_driver_read_closed 
> (d=d@entry=0x7fffdc054288) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/core/connection_driver.c:109
> #2  0x77731ef1 in pconnection_rclosed (pc=0x7fffdc053ce0) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:898
> #3  pconnection_process (pc=0x7fffdc053ce0, events=, 
> timeout=timeout@entry=false, topup=topup@entry=false) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1084
> #4  0x77732945 in proactor_do_epoll (p=0x89b550, 
> can_block=can_block@entry=true) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2007
> #5  0x777337ca in pn_proactor_wait (p=) at 
> /home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
> #6  0x77bbc219 in thread_run (arg=0x89ec20) at 
> /home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
> #7  0x775185ca in start_thread (arg=0x7fffea269700) at 
> pthread_create.c:333
> #8  0x767eb0cd in clone () at 
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> Thread 2 (Thread 0x7fffeaa6a700 (LWP 10953)):
> #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
> ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
> #1  0x77ba2949 in sys_cond_wait (cond=, 
> held_mutex=) at 
> /home/kpvdr/RedHat/qpid-dispatch/src/posix/threading.c:91
> #2  0x77bb0cf5 in router_core_thread (arg=0x8f8c90) at 
> /home/kpvdr/RedHat/qpid-dispatch/src/router_core/router_core_thread.c:66

[jira] [Created] (DISPATCH-902) Intermittent crash with link to broker when broker closed

2017-12-15 Thread Kim van der Riet (JIRA) 
Kim van der Riet created DISPATCH-902:
-

 Summary: Intermittent crash with link to broker when broker closed
 Key: DISPATCH-902
 URL: https://issues.apache.org/jira/browse/DISPATCH-902
 Project: Qpid Dispatch
  Issue Type: Bug
Reporter: Kim van der Riet


When using dispatch in a 2-node configuration with a broker between them:

{noformat}
9002   10001   100019003
sender > dispatch1 -> qpid-cpp -> dispatch2 -> receiver
{noformat}

and initializing in the following order:
# start dispatch1
# start dispatch2
# start qpid-cpp
# wait for "Link Route Activated" messages on both dispatch nodes
# stop qpid-cpp

then the dispatch nodes will core after a random amount of time and after 
sending a random number of 
{noformat}
(info) Connection to localhost:10001 failed: proton:io Connection refused - on 
read from localhost:10001
{noformat}
messages.

The stack trace is as follows for all occurrences:
{noformat}
Thread 3 "qdrouterd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffea269700 (LWP 10954)]
pn_transport_tail_closed (transport=0x0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/transport.c:3044
3044bool pn_transport_tail_closed(pn_transport_t *transport) { return 
transport->tail_closed; }
(gdb) thread apply all bt

Thread 5 (Thread 0x7fffe9267700 (LWP 10956)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x775185ca in start_thread (arg=0x7fffe9267700) at 
pthread_create.c:333
#5  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fffe9a68700 (LWP 10955)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#4  0x775185ca in start_thread (arg=0x7fffe9a68700) at 
pthread_create.c:333
#5  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fffea269700 (LWP 10954)):
#0  pn_transport_tail_closed (transport=0x0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/transport.c:3044
#1  0x7794f4f9 in pn_connection_driver_read_closed 
(d=d@entry=0x7fffdc054288) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/core/connection_driver.c:109
#2  0x77731ef1 in pconnection_rclosed (pc=0x7fffdc053ce0) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:898
#3  pconnection_process (pc=0x7fffdc053ce0, events=, 
timeout=timeout@entry=false, topup=topup@entry=false) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1084
#4  0x77732945 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2007
#5  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#6  0x77bbc219 in thread_run (arg=0x89ec20) at 
/home/kpvdr/RedHat/qpid-dispatch/src/server.c:932
#7  0x775185ca in start_thread (arg=0x7fffea269700) at 
pthread_create.c:333
#8  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fffeaa6a700 (LWP 10953)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x77ba2949 in sys_cond_wait (cond=, 
held_mutex=) at 
/home/kpvdr/RedHat/qpid-dispatch/src/posix/threading.c:91
#2  0x77bb0cf5 in router_core_thread (arg=0x8f8c90) at 
/home/kpvdr/RedHat/qpid-dispatch/src/router_core/router_core_thread.c:66
#3  0x775185ca in start_thread (arg=0x7fffeaa6a700) at 
pthread_create.c:333
#4  0x767eb0cd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x77fbb180 (LWP 10946)):
#0  0x767eb6d3 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84
#1  0x777327e2 in proactor_do_epoll (p=0x89b550, 
can_block=can_block@entry=true) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:1978
#2  0x777337ca in pn_proactor_wait (p=) at 
/home/kpvdr/RedHat/qpid-proton/proton-c/src/proactor/epoll.c:2025
#3  0x77bbc2

[jira] [Created] (PROTON-1720) [ruby] support for SSL configuration via connection options

2017-12-15 Thread Alan Conway (JIRA) 
Alan Conway created PROTON-1720:
---

 Summary: [ruby] support for SSL configuration via connection 
options
 Key: PROTON-1720
 URL: https://issues.apache.org/jira/browse/PROTON-1720
 Project: Qpid Proton
  Issue Type: Bug
  Components: ruby-binding
Affects Versions: proton-c-0.18.1
Reporter: Alan Conway
Assignee: Alan Conway
 Fix For: proton-c-0.19.0


Add SSL configuration options to container, SSL tests and examples.



--
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-1717) [C proactor] Allow initialization of transport and connection before binding

2017-12-15 Thread Alan Conway (JIRA) 

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

Alan Conway resolved PROTON-1717.
-
Resolution: Fixed

> [C proactor] Allow initialization of transport and connection before binding
> 
>
> Key: PROTON-1717
> URL: https://issues.apache.org/jira/browse/PROTON-1717
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: proton-c-0.18.1
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> The C proactor allows the user to configure a connection before it is bound 
> to a transport, but does not allow configuring the transport before binding. 
> Some security configurations require this.
> Modify the proactor API to give access to both the connection and the 
> transport before the are bound together.



--
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-1717) [C proactor] Allow initialization of transport and connection before binding

2017-12-15 Thread ASF subversion and git services (JIRA) 

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

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

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

PROTON-1717 [C proactor] Allow initialization of transport and connection 
before binding

pn_proactor_connect and pn_listener_accept now take a pn_connection_t* and 
pn_transport_t*
Either can be NULL, in which case a connection/transport is created with no 
special config.


> [C proactor] Allow initialization of transport and connection before binding
> 
>
> Key: PROTON-1717
> URL: https://issues.apache.org/jira/browse/PROTON-1717
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: proton-c-0.18.1
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> The C proactor allows the user to configure a connection before it is bound 
> to a transport, but does not allow configuring the transport before binding. 
> Some security configurations require this.
> Modify the proactor API to give access to both the connection and the 
> transport before the are bound together.



--
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-901) add authz support to auth service plugin

2017-12-15 Thread Gordon Sim (JIRA) 

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

Gordon Sim commented on DISPATCH-901:
-

Initial patch for review and comments: https://reviews.apache.org/r/64645/

This does not yet deal with how to handle policy set in config file *and* authz 
supplied via this plugin.

> add authz support to auth service plugin
> 
>
> Key: DISPATCH-901
> URL: https://issues.apache.org/jira/browse/DISPATCH-901
> Project: Qpid Dispatch
>  Issue Type: Improvement
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>
> It would be more useful to have the auth service provide a set of permissions 
> for the user if successfully authenticated, rathe rthan having to define 
> these in config files for each router in a network.



--
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

Re: Review Request 64645: authorization support for sasl delegation plugin

2017-12-15 Thread Gordon Sim 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/64645/
---

(Updated Dec. 15, 2017, 10:45 a.m.)


Review request for qpid, Chug Rolke, Ganesh Murthy, and Ted Ross.


Bugs: DISPATCH-901
https://issues.apache.org/jira/browse/DISPATCH-901


Repository: qpid-dispatch


Description
---

If the client specifies its desire for the ADDRESS-AUTHZ capacbility, the 
authorization service, if it supports this, will return a set of permissions in 
the properties of the open frame. The properties will have an address-authz 
key, whose value is a map of address (or wildcard pattern) to an array of 
permissions. The only permissions recognised at present by this patch are 
'send' and 'recv'.


Diffs
-

  src/policy.c 22cc79f 
  src/remote_sasl.c e3c969b 
  tests/CMakeLists.txt 0c6454c 
  tests/authservice.py PRE-CREATION 
  tests/system_tests_authz_service_plugin.py PRE-CREATION 


Diff: https://reviews.apache.org/r/64645/diff/1/


Testing
---

Added new systems tests using proton python based dummy auth service.


Thanks,

Gordon Sim

[jira] [Updated] (DISPATCH-901) add authz support to auth service plugin

2017-12-15 Thread Gordon Sim (JIRA) 

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

Gordon Sim updated DISPATCH-901:

Description: It would be more useful to have the auth service provide a set 
of permissions for the user if successfully authenticated, rathe rthan having 
to define these in config files for each router in a network.

> add authz support to auth service plugin
> 
>
> Key: DISPATCH-901
> URL: https://issues.apache.org/jira/browse/DISPATCH-901
> Project: Qpid Dispatch
>  Issue Type: Improvement
>Reporter: Gordon Sim
>Assignee: Gordon Sim
>
> It would be more useful to have the auth service provide a set of permissions 
> for the user if successfully authenticated, rathe rthan having to define 
> these in config files for each router in a network.



--
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-901) add authz support to auth service plugin

2017-12-15 Thread Gordon Sim (JIRA) 
Gordon Sim created DISPATCH-901:
---

 Summary: add authz support to auth service plugin
 Key: DISPATCH-901
 URL: https://issues.apache.org/jira/browse/DISPATCH-901
 Project: Qpid Dispatch
  Issue Type: Improvement
Reporter: Gordon Sim
Assignee: Gordon Sim






--
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