[jira] [Commented] (PROTON-1764) Slow performance seen when running Go client
[
https://issues.apache.org/jira/browse/PROTON-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379414#comment-16379414
]
Alan Conway commented on PROTON-1764:
-
It is expected that the go client spend a lot of time in the C library - the C
library is doing all the protocol work, the Go code is managing network IO and
providing the Go API. However I agree that the Go client is a lot slower (4x
slower in my simple test) than the C or C++ clients, so I will investigate
where the time is being spent. I suspect inefficient movement of data between
the IO and protocol goroutines inside the library.
> Slow performance seen when running Go client
>
>
> Key: PROTON-1764
> URL: https://issues.apache.org/jira/browse/PROTON-1764
> Project: Qpid Proton
> Issue Type: Bug
> Components: go-binding
>Affects Versions: proton-c-0.18.1
>Reporter: Aaron Smith
>Assignee: Alan Conway
>Priority: Major
>
> Slower than expected message deliver rate seen while running simple
> benchmarking test. Setup:
> Client(Go) Sender -> QPID Router -> Client Receiver(Go)
> Profiling of reveals that a large percentage of time is spent in wrapper call
> from Go to c.
> Not sure if the call to C from Go is the issue.
>
> Here's the pointer for sender/receiver (both uses qpid go-binding).
> Sender (with '-limit' option, it sends AMQP messages in 10sec for
> benchmarking):
>
> [https://github.com/redhat-nfvpe/service-assurance-poc/tree/master/tools/sa-bench]
> Receiver (based on electron sample):
> [http://kagaribi.s1061123.net/receive.go]
> Here are the results:
> {noformat}
> [root@nfvha-comp-01 sa-bench]# ./sa-bench -mode limit
> amqp://127.0.0.1:5672/collectd/telemetry
> sending AMQP in 10 seconds...Done!
> Total: 171908 sent (duration:10.000103521s, mesg/sec: 17190.62204096157)
> [root@nfvha-comp-01 electron_sample]# ./receive -prefetch 12
> amqp://127.0.0.1:5672/collectd/telemetry
> Listening on 1 connections
> ^C2018/02/15 01:44:51 Total: 171908 received.
> 2018/02/15 01:44:51 captured interrupt, stopping profiler and exiting...
> {noformat}
> Both program can collect profile data using '-pprofile' option as following:
> {noformat}
> [root@nfvha-comp-01 sa-bench]# ./sa-bench -mode limit -pprofile profile.out
> amqp://127.0.0.1:5672/collectd/telemetry
> sending AMQP in 10 seconds...Done!
> Total: 189305 sent (duration:10.000111611s, mesg/sec: 18930.2887171546)
> [root@nfvha-comp-01 sa-bench]# go tool pprof sa-bench profile.out
> File: sa-bench
> Build ID: 7ffec7b98a532892d7b9932b70b7451866cd4e5e
> Type: cpu
> Time: Feb 15, 2018 at 1:49am (EST)
> Duration: 10.11s, Total samples = 15.75s (155.79%)
> Entering interactive mode (type "help" for commands, "o" for options)
> (pprof) top5
> Showing nodes accounting for 9990ms, 63.43% of 15750ms total
> Dropped 200 nodes (cum <= 78.75ms)
> Showing top 5 nodes out of 144
> flat flat% sum%cum cum%
> 6750ms 42.86% 42.86% 7080ms 44.95% runtime.cgocall
> /usr/local/go/src/runtime/cgocall.go
> 1570ms 9.97% 52.83% 1590ms 10.10% syscall.Syscall
> /usr/local/go/src/syscall/asm_linux_amd64.s
> 800ms 5.08% 57.90% 800ms 5.08% runtime.futex
> /usr/local/go/src/runtime/sys_linux_amd64.s
> 440ms 2.79% 60.70% 770ms 4.89% runtime.runqgrab
> /usr/local/go/src/runtime/proc.go
> 430ms 2.73% 63.43% 1070ms 6.79% runtime.selectgo
> /usr/local/go/src/runtime/select.go
> [root@nfvha-comp-01 electron_sample]# ./receive -prefetch 12 -pprofile
> profile.out amqp://127.0.0.1:5672/collectd/telemetry
> Listening on 1 connections
> ^C2018/02/15 01:49:25 Total: 181422 received.
> 2018/02/15 01:49:25 captured interrupt, stopping profiler and exiting...
> [root@nfvha-comp-01 electron_sample]# go tool pprof receive profile.out
> File: receive
> Build ID: 66addd89d429ca678cbd6e336872bc604406f83e
> Type: cpu
> Time: Feb 15, 2018 at 1:49am (EST)
> Duration: 14.78s, Total samples = 16.60s (112.31%)
> Entering interactive mode (type "help" for commands, "o" for options)
> (pprof) top 5
> Showing nodes accounting for 10620ms, 63.98% of 16600ms total
> Dropped 160 nodes (cum <= 83ms)
> Showing top 5 nodes out of 124
> flat flat% sum%cum cum%
> 5730ms 34.52% 34.52% 5960ms 35.90% runtime.cgocall
> /usr/local/go/src/runtime/cgocall.go
> 2190ms 13.19% 47.71% 2220ms 13.37% syscall.Syscall
> /usr/local/go/src/syscall/asm_linux_amd64.s
> 1070ms 6.45% 54.16% 1070ms 6.45% runtime.epollwait
> /usr/local/go/src/runtime/sys_linux_amd64.s
> 860ms 5.18% 59.34% 4430ms 26.69% runtime.findrunnable
> /usr/local/go/src/runtime/proc.go
> 770ms 4.64% 63.98% 1130ms 6.81% runtime.runqgrab
> /usr/local/go/src/runtime/proc.go
> (pprof) {noformat}
>
--
This message was
[jira] [Resolved] (DISPATCH-911) Add link and address level counters at the global router level
[ https://issues.apache.org/jira/browse/DISPATCH-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-911. --- Resolution: Fixed > Add link and address level counters at the global router level > -- > > Key: DISPATCH-911 > URL: https://issues.apache.org/jira/browse/DISPATCH-911 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Management Agent >Reporter: Ernest Allen >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.1.0 > > > Link already has the following counters - > presettledCount > droppedPresettledCount > acceptedCount > rejectedCount > releasedCount > modifiedCount > Address already has the following counters > deliveriesIngress > deliveriesEgress > deliveriesTransit > 1. Add the above link and address counters to the global router level as well. > 2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as > address and global counters > 3. Add router memory footprint as a global statistic -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-911) Add link and address level counters at the global router level
[ https://issues.apache.org/jira/browse/DISPATCH-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-911: -- Affects Version/s: (was: 1.0.0) > Add link and address level counters at the global router level > -- > > Key: DISPATCH-911 > URL: https://issues.apache.org/jira/browse/DISPATCH-911 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Management Agent >Reporter: Ernest Allen >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.1.0 > > > Link already has the following counters - > presettledCount > droppedPresettledCount > acceptedCount > rejectedCount > releasedCount > modifiedCount > Address already has the following counters > deliveriesIngress > deliveriesEgress > deliveriesTransit > 1. Add the above link and address counters to the global router level as well. > 2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as > address and global counters > 3. Add router memory footprint as a global statistic -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-911) Add link and address level counters at the global router level
[ https://issues.apache.org/jira/browse/DISPATCH-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-911: -- Issue Type: New Feature (was: Improvement) > Add link and address level counters at the global router level > -- > > Key: DISPATCH-911 > URL: https://issues.apache.org/jira/browse/DISPATCH-911 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Management Agent >Reporter: Ernest Allen >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.1.0 > > > Link already has the following counters - > presettledCount > droppedPresettledCount > acceptedCount > rejectedCount > releasedCount > modifiedCount > Address already has the following counters > deliveriesIngress > deliveriesEgress > deliveriesTransit > 1. Add the above link and address counters to the global router level as well. > 2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as > address and global counters > 3. Add router memory footprint as a global statistic -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf
[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved DISPATCH-878.
---
Resolution: Fixed
> qdrouterd should log real port if port 0 was specified for the listener port
> property in qdrouterd.conf
> ---
>
> Key: DISPATCH-878
> URL: https://issues.apache.org/jira/browse/DISPATCH-878
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Environment: OS: Red Hat Linux Server release 6.4
> Dispatch version: 0.7.0
>Reporter: Jeremy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.1.0
>
>
> For such a qdrouterd.conf configuration:
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> *port: 5673*
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> }
> {noformat}
> qdrouterd logs the port as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:5673 proto=any, role=normal
> {noformat}
> When specifying port 0, so that the dispatch router runs on a random
> available port, the log is as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
> {noformat}
> qdrouterd process can log instead the real port that was randomly chosen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-911) Add link and address level counters at the global router level
[ https://issues.apache.org/jira/browse/DISPATCH-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379385#comment-16379385 ] ASF GitHub Bot commented on DISPATCH-911: - Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/254 > Add link and address level counters at the global router level > -- > > Key: DISPATCH-911 > URL: https://issues.apache.org/jira/browse/DISPATCH-911 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Management Agent >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.1.0 > > > Link already has the following counters - > presettledCount > droppedPresettledCount > acceptedCount > rejectedCount > releasedCount > modifiedCount > Address already has the following counters > deliveriesIngress > deliveriesEgress > deliveriesTransit > 1. Add the above link and address counters to the global router level as well. > 2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as > address and global counters > 3. Add router memory footprint as a global statistic -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-911) Add link and address level counters at the global router level
[ https://issues.apache.org/jira/browse/DISPATCH-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379384#comment-16379384 ] ASF subversion and git services commented on DISPATCH-911: -- Commit b6805c0ce324b15dcd29937978cbb303c08c5394 in qpid-dispatch's branch refs/heads/master from [~tr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=b6805c0 ] DISPATCH-911 - (from Ganesh Murthy) Add global delivery counts This closes #254 > Add link and address level counters at the global router level > -- > > Key: DISPATCH-911 > URL: https://issues.apache.org/jira/browse/DISPATCH-911 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Management Agent >Affects Versions: 1.0.0 >Reporter: Ernest Allen >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.1.0 > > > Link already has the following counters - > presettledCount > droppedPresettledCount > acceptedCount > rejectedCount > releasedCount > modifiedCount > Address already has the following counters > deliveriesIngress > deliveriesEgress > deliveriesTransit > 1. Add the above link and address counters to the global router level as well. > 2. Add routeContainerDeliveriesEgress and routeContainerDeliveriesIngress as > address and global counters > 3. Add router memory footprint as a global statistic -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #254: DISPATCH-911 - Added global delivery counts
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/254 --- - 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
[ https://issues.apache.org/jira/browse/DISPATCH-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379373#comment-16379373 ] ASF subversion and git services commented on DISPATCH-918: -- Commit 257321d0f8d0d835df47eff2004ef8d4852f46fb in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=257321d ] DISPATCH-918 - Initial modifications to Python schema code to introduce and use the deprecationName attribute. Also modified dir to direction in linkRoute and autoLink and they use the deprecationName attribute. This closes #261 > Improve router config consistency and metadata > -- > > Key: DISPATCH-918 > URL: https://issues.apache.org/jira/browse/DISPATCH-918 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Justin Ross >Assignee: Ganesh Murthy >Priority: Major > > Proposed changes from review. The items marked PRIO1 are more important. > All changes must be backward-compatible. > [https://docs.google.com/spreadsheets/d/14ugjxlc-ETYZXwN9eWD-D1YWrRAfydj9EJNmyUaZrD0/edit?usp=sharing] > This also includes flags we'd like to get added to the metadata so we can > generate better docs from it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #261: DISPATCH-918 - Initial modifications to Pyt...
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/261 --- - 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
[ https://issues.apache.org/jira/browse/DISPATCH-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379374#comment-16379374 ] ASF GitHub Bot commented on DISPATCH-918: - Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/261 > Improve router config consistency and metadata > -- > > Key: DISPATCH-918 > URL: https://issues.apache.org/jira/browse/DISPATCH-918 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Justin Ross >Assignee: Ganesh Murthy >Priority: Major > > Proposed changes from review. The items marked PRIO1 are more important. > All changes must be backward-compatible. > [https://docs.google.com/spreadsheets/d/14ugjxlc-ETYZXwN9eWD-D1YWrRAfydj9EJNmyUaZrD0/edit?usp=sharing] > This also includes flags we'd like to get added to the metadata so we can > generate better docs from it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf
[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379308#comment-16379308
]
ASF subversion and git services commented on DISPATCH-878:
--
Commit e3f025aee515874e53329a7a806a77500fd8af1d in qpid-dispatch's branch
refs/heads/master from [~tr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=e3f025a ]
DISPATCH-878 - (from Ganesh Murthy) If a listener is configured with port '0',
assign and log a dynamic port.
This closes #245.
> qdrouterd should log real port if port 0 was specified for the listener port
> property in qdrouterd.conf
> ---
>
> Key: DISPATCH-878
> URL: https://issues.apache.org/jira/browse/DISPATCH-878
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Environment: OS: Red Hat Linux Server release 6.4
> Dispatch version: 0.7.0
>Reporter: Jeremy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.1.0
>
>
> For such a qdrouterd.conf configuration:
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> *port: 5673*
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> }
> {noformat}
> qdrouterd logs the port as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:5673 proto=any, role=normal
> {noformat}
> When specifying port 0, so that the dispatch router runs on a random
> available port, the log is as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
> {noformat}
> qdrouterd process can log instead the real port that was randomly chosen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf
[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379310#comment-16379310
]
ASF GitHub Bot commented on DISPATCH-878:
-
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-dispatch/pull/245
> qdrouterd should log real port if port 0 was specified for the listener port
> property in qdrouterd.conf
> ---
>
> Key: DISPATCH-878
> URL: https://issues.apache.org/jira/browse/DISPATCH-878
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Environment: OS: Red Hat Linux Server release 6.4
> Dispatch version: 0.7.0
>Reporter: Jeremy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.1.0
>
>
> For such a qdrouterd.conf configuration:
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> *port: 5673*
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> }
> {noformat}
> qdrouterd logs the port as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:5673 proto=any, role=normal
> {noformat}
> When specifying port 0, so that the dispatch router runs on a random
> available port, the log is as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
> {noformat}
> qdrouterd process can log instead the real port that was randomly chosen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #262: Crolke 918 vhost hostname
Github user ChugR commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/262#discussion_r171073403
--- Diff: console/config/schema.json ---
@@ -1273,6 +1273,10 @@
"type": "map",
"description": "A map where each key is a user group name and
the value is a map of the corresponding settings for that group."
},
+"hostname": {
+ "type": "string",
+ "description": "The vhost name."
+},
--- End diff --
will do.
---
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #245: DISPATCH-878 - Added code to display the ac...
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/245 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf
[
https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-878:
--
Fix Version/s: 1.1.0
> qdrouterd should log real port if port 0 was specified for the listener port
> property in qdrouterd.conf
> ---
>
> Key: DISPATCH-878
> URL: https://issues.apache.org/jira/browse/DISPATCH-878
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Environment: OS: Red Hat Linux Server release 6.4
> Dispatch version: 0.7.0
>Reporter: Jeremy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.1.0
>
>
> For such a qdrouterd.conf configuration:
> {noformat}
> router {
> mode: standalone
> id: Router.A
> }
> listener {
> host: 0.0.0.0
> *port: 5673*
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> }
> {noformat}
> qdrouterd logs the port as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:5673 proto=any, role=normal
> {noformat}
> When specifying port 0, so that the dispatch router runs on a random
> available port, the log is as such:
> {noformat}
> CONN_MGR (info) Configured Listener: 0.0.0.0:0 proto=any, role=normal
> {noformat}
> qdrouterd process can log instead the real port that was randomly chosen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1766) [cpp] seg fault in reconnect test
[
https://issues.apache.org/jira/browse/PROTON-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379253#comment-16379253
]
ASF subversion and git services commented on PROTON-1766:
-
Commit 0774a4caa637481c438d40b5bbc815ff8fcbba25 in qpid-proton's branch
refs/heads/master from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=0774a4c ]
PROTON-1766: [c-epoll] Fix initialization order race
Set the pn_connection_t backpointer *after* the pconnection has been set up.
Otherwise there is a race with pn_connection_wake() on connections that are
re-used after pn_proactor_release_connection()
> [cpp] seg fault in reconnect test
> -
>
> Key: PROTON-1766
> URL: https://issues.apache.org/jira/browse/PROTON-1766
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding, proton-c
>Affects Versions: proton-c-0.20.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
> Fix For: proton-c-0.21.0
>
>
> See [https://issues.jboss.org/browse/ENTMQCL-600] for details and reproducer
> code, summary:
>
> Using the to be attached reproducer and broker configuration:
> Running amqsender
> ./amqsender microseconds>
> e.g.
> ./amqsender testbox111:5672 testbox111:5673 anon anon Q1 1
> You can reproduce the coredump with just one broker
> 1. keep slave down
> 2. start master broker
> 3. run amqsender with a very low frequency
> 4. kill master broker
> This should reproduce the coredump.
> The reproducer has events implemented for on_transport_close yet we see:
> {code}
> .
> .
> .
> [0x7fffec0169b0]:(PN_TRANSPORT, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_CONNECTION_WAKE, pn_connection<0x7fffec000b90>)
> AMQSender::on_connection_wake pn_connection<0x7fffec000b90>
> [0x7fffec0169b0]:(PN_TRANSPORT_TAIL_CLOSED, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT_ERROR, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT_HEAD_CLOSED, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT_CLOSED, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_CONNECTION_INIT, pn_connection<0x7fffec000b90>)
> Thread 1 "amqsender" received signal SIGSEGV, Segmentation fault.
> 0x772bcdd0 in pthread_mutex_lock () from /lib64/libpthread.so.0
> Missing separate debuginfos, use: dnf debuginfo-install
> cyrus-sasl-gssapi-2.1.26-26.2.fc24.x86_64
> cyrus-sasl-lib-2.1.26-26.2.fc24.x86_64 cyrus-sasl-md5-2.1.26-26.2.fc24.x86_64
> cyrus-sasl-plain-2.1.26-26.2.fc24.x86_64
> cyrus-sasl-scram-2.1.26-26.2.fc24.x86_64 keyutils-libs-1.5.9-8.fc24.x86_64
> krb5-libs-1.14.4-7.fc25.x86_64 libcom_err-1.43.3-1.fc25.x86_64
> libcrypt-nss-2.24-4.fc25.x86_64 libdb-5.3.28-16.fc25.x86_64
> libgcc-6.3.1-1.fc25.x86_64 libselinux-2.5-13.fc25.x86_64
> libstdc++-6.3.1-1.fc25.x86_64 nss-softokn-freebl-3.28.3-1.1.fc25.x86_64
> openssl-libs-1.0.2k-1.fc25.x86_64 pcre-8.40-5.fc25.x86_64
> zlib-1.2.8-10.fc24.x86_64
> (gdb) bt
> #0 0x772bcdd0 in pthread_mutex_lock () from /lib64/libpthread.so.0
> #1 0x776dc4fa in lock (m=0x1a0) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:112
> #2 0x776dcc09 in wake (ctx=0x7fffec2b8ac0) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:436
> #3 0x776def0e in pn_connection_wake (c=0x7fffec000b90) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:1302
> #4 0x77b81b82 in proton::container::impl::connection_work_queue::add
> (this=0x7fffec001d30, f=...) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/bindings/cpp/src/proactor_container_impl.cpp:118
> #5 0x77bacde5 in proton::work_queue::add (this=0x7fffec001cd8,
> f=...) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/bindings/cpp/src/work_queue.cpp:43
> #6 0x0040536f in AMQSender::send (this=this@entry=0x7fffd960,
> strMsg="7578") at ../attachments/AMQSender.cpp:42
> #7 0x0040328f in main (argc=, argv=0x7fffdbd8) at
> ../attachments/amqsend.cpp:20
> (gdb) frame 2
> #2 0x776dcc09 in wake (ctx=0x7fffec2b8ac0) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:436
> 436 lock(>eventfd_mutex);
> (gdb) print p
> $3 = (pn_proactor_t *) 0x0
> (gdb)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #262: Crolke 918 vhost hostname
Github user ganeshmurthy commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/262#discussion_r171011913
--- Diff: console/config/schema.json ---
@@ -1273,6 +1273,10 @@
"type": "map",
"description": "A map where each key is a user group name and
the value is a map of the corresponding settings for that group."
},
+"hostname": {
--- End diff --
yes, agreed
---
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #262: Crolke 918 vhost hostname
Github user ChugR commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/262#discussion_r170987746
--- Diff: console/config/schema.json ---
@@ -1273,6 +1273,10 @@
"type": "map",
"description": "A map where each key is a user group name and
the value is a map of the corresponding settings for that group."
},
+"hostname": {
--- End diff --
Can't be used until you check it in...
---
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #253: Enhanced link-statistics
Github user bhardesty commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/253#discussion_r170986612
--- Diff: python/qpid_dispatch/management/qdrouter.json ---
@@ -1325,6 +1329,10 @@
"lastTopoChange": {
"description": "Timestamp showing the most recent
change to this node's neighborhood.",
"type": "integer"
+},
+"index": {
+"description": "Index number for this router node used
in statistics histograms. This index is specific to this router.",
--- End diff --
Minor suggestion for the description:
> The index number used in statistics histograms for this router node. This
index is specific to this router.
---
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #253: Enhanced link-statistics
Github user bhardesty commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/253#discussion_r170986013
--- Diff: python/qpid_dispatch/management/qdrouter.json ---
@@ -1207,6 +1207,10 @@
"type": "integer",
"graph": true,
"description": "The total number of modified
deliveries."
+},
+"ingressHistogram": {
+"type": "list",
+"description": "For outgoing links on normal
connections. This is a histogram with a value per interior router node. The
value is a count of settled deliveries on this link that ingressed the network
at the specific interior router."
--- End diff --
Suggestion for the description:
> For outgoing links on normal connections, this histogram shows the number
of settled deliveries on the link that ingressed the network at each interior
router node.
Also, what constitutes a "normal" connection? Does that need to be defined?
---
-
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
[ https://issues.apache.org/jira/browse/DISPATCH-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378896#comment-16378896 ] ASF GitHub Bot commented on DISPATCH-918: - Github user ganeshmurthy commented on the issue: https://github.com/apache/qpid-dispatch/pull/261 Specifying the "dir" attribute only will generate a warning that will tell you that you are using a deprecated attribute. The warning will look something like this - 2018-02-27 11:34:41.138705 -0500 AGENT (warning) Attribute 'dir' of entity 'linkRoute' has been deprecated. Use 'direction' instead The router will still start If both 'dir' and 'direction' attributes are specified, the router will display the following error and fail to start - 2018-02-27 11:36:54.911916 -0500 MAIN (critical) Router start-up failed: Python: Exception: Cannot load configuration file test.conf: org.apache.qpid.dispatch.router.config.linkRoute: Both 'dir' and 'direction' cannot be specified for entity 'linkRoute' > Improve router config consistency and metadata > -- > > Key: DISPATCH-918 > URL: https://issues.apache.org/jira/browse/DISPATCH-918 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Justin Ross >Assignee: Ganesh Murthy >Priority: Major > > Proposed changes from review. The items marked PRIO1 are more important. > All changes must be backward-compatible. > [https://docs.google.com/spreadsheets/d/14ugjxlc-ETYZXwN9eWD-D1YWrRAfydj9EJNmyUaZrD0/edit?usp=sharing] > This also includes flags we'd like to get added to the metadata so we can > generate better docs from it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch issue #261: DISPATCH-918 - Initial modifications to Python sch...
Github user ganeshmurthy commented on the issue: https://github.com/apache/qpid-dispatch/pull/261 Specifying the "dir" attribute only will generate a warning that will tell you that you are using a deprecated attribute. The warning will look something like this - 2018-02-27 11:34:41.138705 -0500 AGENT (warning) Attribute 'dir' of entity 'linkRoute' has been deprecated. Use 'direction' instead The router will still start If both 'dir' and 'direction' attributes are specified, the router will display the following error and fail to start - 2018-02-27 11:36:54.911916 -0500 MAIN (critical) Router start-up failed: Python: Exception: Cannot load configuration file test.conf: org.apache.qpid.dispatch.router.config.linkRoute: Both 'dir' and 'direction' cannot be specified for entity 'linkRoute' --- - 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
[ https://issues.apache.org/jira/browse/DISPATCH-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378881#comment-16378881 ] ASF GitHub Bot commented on DISPATCH-918: - Github user bhardesty commented on the issue: https://github.com/apache/qpid-dispatch/pull/261 The "dir" -> "direction" doc updates look good. If someone attempts to use a deprecated attribute, will the operation still succeed (in addition to the deprecation log warning)? Or will the operation fail? > Improve router config consistency and metadata > -- > > Key: DISPATCH-918 > URL: https://issues.apache.org/jira/browse/DISPATCH-918 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Justin Ross >Assignee: Ganesh Murthy >Priority: Major > > Proposed changes from review. The items marked PRIO1 are more important. > All changes must be backward-compatible. > [https://docs.google.com/spreadsheets/d/14ugjxlc-ETYZXwN9eWD-D1YWrRAfydj9EJNmyUaZrD0/edit?usp=sharing] > This also includes flags we'd like to get added to the metadata so we can > generate better docs from it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch issue #261: DISPATCH-918 - Initial modifications to Python sch...
Github user bhardesty commented on the issue: https://github.com/apache/qpid-dispatch/pull/261 The "dir" -> "direction" doc updates look good. If someone attempts to use a deprecated attribute, will the operation still succeed (in addition to the deprecation log warning)? Or will the operation fail? --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1777) 0.22.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1777: --- Fix Version/s: (was: proton-c-0.21.0) proton-c-0.22.0 > 0.22.0 release tasks > > > Key: PROTON-1777 > URL: https://issues.apache.org/jira/browse/PROTON-1777 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.22.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1777) 0.22.0 release tasks
Robbie Gemmell created PROTON-1777: -- Summary: 0.22.0 release tasks Key: PROTON-1777 URL: https://issues.apache.org/jira/browse/PROTON-1777 Project: Qpid Proton Issue Type: Task Components: proton-c, release Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: proton-c-0.21.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1752) 0.21.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1752: --- Fix Version/s: proton-c-0.21.0 > 0.21.0 release tasks > > > Key: PROTON-1752 > URL: https://issues.apache.org/jira/browse/PROTON-1752 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.21.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1773) Access after free in pn_proactor_disconnect
[
https://issues.apache.org/jira/browse/PROTON-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-1773:
---
Summary: Access after free in pn_proactor_disconnect (was: Access after
free in proactor_disconnect)
> Access after free in pn_proactor_disconnect
> ---
>
> Key: PROTON-1773
> URL: https://issues.apache.org/jira/browse/PROTON-1773
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, proton-c
>Affects Versions: proton-c-0.21.0
>Reporter: Andrew Stitcher
>Assignee: Alan Conway
>Priority: Blocker
> Fix For: proton-c-0.21.0
>
>
> The fix for PROTON-1734 may have caused a sporadic access after free problem
> detected in one of the new tests in cpp-container_test.
> {noformat}
> 10: TEST: test_container_mt_stop()
> 10: ==11269== Invalid read of size 8
> 10: ==11269==at 0x59772E4: pn_proactor_disconnect (epoll.c:2128)
> 10: ==11269==by 0x4E6156F:
> proton::container::impl::stop(proton::error_condition const&)
> (proactor_container_impl.cpp:763)
> 10: ==11269==by 0x4E5F2D8: proton::container::stop() (container.cpp:80)
> 10: ==11269==by 0x409ED4: (anonymous namespace)::test_container_mt_stop()
> (container_test.cpp:344)
> 10: ==11269==by 0x404811: main (container_test.cpp:368)
> 10: ==11269== Address 0x6e27748 is 1,256 bytes inside a block of size 1,808
> free'd
> 10: ==11269==at 0x4C2BDEC: free (in
> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> 10: ==11269==by 0x5975221: pconnection_process (epoll.c:1174)
> 10: ==11269==by 0x5975C3E: process_inbound_wake (epoll.c:1962)
> 10: ==11269==by 0x5975C3E: proactor_do_epoll (epoll.c:1999)
> 10: ==11269==by 0x4E6336B: proton::container::impl::thread()
> (proactor_container_impl.cpp:670)
> 10: ==11269==by 0x4E639A3: proton::container::impl::run(int)
> (proactor_container_impl.cpp:721)
> 10: ==11269==by 0x513EA5F: ??? (in
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19)
> 10: ==11269==by 0x60C3183: start_thread (pthread_create.c:312)
> 10: ==11269==by 0x56A503C: clone (clone.S:111)
> 10: ==11269==
> 10/46 Test #10: cpp-container_test ...***Failed2.53 sec
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1773) Access after free in proactor_disconnect
[
https://issues.apache.org/jira/browse/PROTON-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-1773:
---
Summary: Access after free in proactor_disconnect (was: Access after free
possibly created by recent fix)
> Access after free in proactor_disconnect
>
>
> Key: PROTON-1773
> URL: https://issues.apache.org/jira/browse/PROTON-1773
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, proton-c
>Affects Versions: proton-c-0.21.0
>Reporter: Andrew Stitcher
>Assignee: Alan Conway
>Priority: Blocker
> Fix For: proton-c-0.21.0
>
>
> The fix for PROTON-1734 may have caused a sporadic access after free problem
> detected in one of the new tests in cpp-container_test.
> {noformat}
> 10: TEST: test_container_mt_stop()
> 10: ==11269== Invalid read of size 8
> 10: ==11269==at 0x59772E4: pn_proactor_disconnect (epoll.c:2128)
> 10: ==11269==by 0x4E6156F:
> proton::container::impl::stop(proton::error_condition const&)
> (proactor_container_impl.cpp:763)
> 10: ==11269==by 0x4E5F2D8: proton::container::stop() (container.cpp:80)
> 10: ==11269==by 0x409ED4: (anonymous namespace)::test_container_mt_stop()
> (container_test.cpp:344)
> 10: ==11269==by 0x404811: main (container_test.cpp:368)
> 10: ==11269== Address 0x6e27748 is 1,256 bytes inside a block of size 1,808
> free'd
> 10: ==11269==at 0x4C2BDEC: free (in
> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> 10: ==11269==by 0x5975221: pconnection_process (epoll.c:1174)
> 10: ==11269==by 0x5975C3E: process_inbound_wake (epoll.c:1962)
> 10: ==11269==by 0x5975C3E: proactor_do_epoll (epoll.c:1999)
> 10: ==11269==by 0x4E6336B: proton::container::impl::thread()
> (proactor_container_impl.cpp:670)
> 10: ==11269==by 0x4E639A3: proton::container::impl::run(int)
> (proactor_container_impl.cpp:721)
> 10: ==11269==by 0x513EA5F: ??? (in
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19)
> 10: ==11269==by 0x60C3183: start_thread (pthread_create.c:312)
> 10: ==11269==by 0x56A503C: clone (clone.S:111)
> 10: ==11269==
> 10/46 Test #10: cpp-container_test ...***Failed2.53 sec
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1770) [cpp] win_iocp fix for seg fault in reconnect test
[
https://issues.apache.org/jira/browse/PROTON-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-1770:
---
Summary: [cpp] win_iocp fix for seg fault in reconnect test (was: CLONE -
[cpp] win_iocp fix for seg fault in reconnect test)
> [cpp] win_iocp fix for seg fault in reconnect test
> --
>
> Key: PROTON-1770
> URL: https://issues.apache.org/jira/browse/PROTON-1770
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding, proton-c
>Affects Versions: proton-c-0.20.0
>Reporter: Alan Conway
>Assignee: Cliff Jansen
>Priority: Major
> Fix For: proton-c-0.22.0
>
>
> See [https://issues.jboss.org/browse/ENTMQCL-600] for details and reproducer
> code, summary:
>
> Using the to be attached reproducer and broker configuration:
> Running amqsender
> ./amqsender microseconds>
> e.g.
> ./amqsender testbox111:5672 testbox111:5673 anon anon Q1 1
> You can reproduce the coredump with just one broker
> 1. keep slave down
> 2. start master broker
> 3. run amqsender with a very low frequency
> 4. kill master broker
> This should reproduce the coredump.
> The reproducer has events implemented for on_transport_close yet we see:
> {code}
> .
> .
> .
> [0x7fffec0169b0]:(PN_TRANSPORT, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_CONNECTION_WAKE, pn_connection<0x7fffec000b90>)
> AMQSender::on_connection_wake pn_connection<0x7fffec000b90>
> [0x7fffec0169b0]:(PN_TRANSPORT_TAIL_CLOSED, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT_ERROR, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT_HEAD_CLOSED, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_TRANSPORT_CLOSED, pn_transport<0x7fffec0169b0>)
> [0x7fffec0169b0]:(PN_CONNECTION_INIT, pn_connection<0x7fffec000b90>)
> Thread 1 "amqsender" received signal SIGSEGV, Segmentation fault.
> 0x772bcdd0 in pthread_mutex_lock () from /lib64/libpthread.so.0
> Missing separate debuginfos, use: dnf debuginfo-install
> cyrus-sasl-gssapi-2.1.26-26.2.fc24.x86_64
> cyrus-sasl-lib-2.1.26-26.2.fc24.x86_64 cyrus-sasl-md5-2.1.26-26.2.fc24.x86_64
> cyrus-sasl-plain-2.1.26-26.2.fc24.x86_64
> cyrus-sasl-scram-2.1.26-26.2.fc24.x86_64 keyutils-libs-1.5.9-8.fc24.x86_64
> krb5-libs-1.14.4-7.fc25.x86_64 libcom_err-1.43.3-1.fc25.x86_64
> libcrypt-nss-2.24-4.fc25.x86_64 libdb-5.3.28-16.fc25.x86_64
> libgcc-6.3.1-1.fc25.x86_64 libselinux-2.5-13.fc25.x86_64
> libstdc++-6.3.1-1.fc25.x86_64 nss-softokn-freebl-3.28.3-1.1.fc25.x86_64
> openssl-libs-1.0.2k-1.fc25.x86_64 pcre-8.40-5.fc25.x86_64
> zlib-1.2.8-10.fc24.x86_64
> (gdb) bt
> #0 0x772bcdd0 in pthread_mutex_lock () from /lib64/libpthread.so.0
> #1 0x776dc4fa in lock (m=0x1a0) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:112
> #2 0x776dcc09 in wake (ctx=0x7fffec2b8ac0) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:436
> #3 0x776def0e in pn_connection_wake (c=0x7fffec000b90) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:1302
> #4 0x77b81b82 in proton::container::impl::connection_work_queue::add
> (this=0x7fffec001d30, f=...) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/bindings/cpp/src/proactor_container_impl.cpp:118
> #5 0x77bacde5 in proton::work_queue::add (this=0x7fffec001cd8,
> f=...) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/bindings/cpp/src/work_queue.cpp:43
> #6 0x0040536f in AMQSender::send (this=this@entry=0x7fffd960,
> strMsg="7578") at ../attachments/AMQSender.cpp:42
> #7 0x0040328f in main (argc=, argv=0x7fffdbd8) at
> ../attachments/amqsend.cpp:20
> (gdb) frame 2
> #2 0x776dcc09 in wake (ctx=0x7fffec2b8ac0) at
> /home/rkieley/LocalProjects/src/rh/rh-qpid-proton/proton-c/src/proactor/epoll.c:436
> 436 lock(>eventfd_mutex);
> (gdb) print p
> $3 = (pn_proactor_t *) 0x0
> (gdb)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8112) [Broker-J] Release Qpid Broker-J 7.0.2
[ https://issues.apache.org/jira/browse/QPID-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8112: Assignee: Alex Rudyy > [Broker-J] Release Qpid Broker-J 7.0.2 > -- > > Key: QPID-8112 > URL: https://issues.apache.org/jira/browse/QPID-8112 > Project: Qpid > Issue Type: Task > Components: Broker-J >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.0.2 > > > Release Qpid Broker-J following instructions provided at > [https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Broker-J] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8112) [Broker-J] Release Qpid Broker-J 7.0.2
Alex Rudyy created QPID-8112: Summary: [Broker-J] Release Qpid Broker-J 7.0.2 Key: QPID-8112 URL: https://issues.apache.org/jira/browse/QPID-8112 Project: Qpid Issue Type: Task Components: Broker-J Reporter: Alex Rudyy Fix For: qpid-java-broker-7.0.2 Release Qpid Broker-J following instructions provided at [https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Broker-J] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid Proton-J 0.26.0 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Proton-J 0.26.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.26.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] [Commented] (QPID-8103) [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
[
https://issues.apache.org/jira/browse/QPID-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378383#comment-16378383
]
ASF subversion and git services commented on QPID-8103:
---
Commit 9cd0e2f98a525e59755b168ea0301cf8e9a51dc4 in qpid-broker-j's branch
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=9cd0e2f ]
QPID-8103: [Broker-J] Remove file committed by mistake
(cherry picked from commit 0a3c7a2fee6d6c078aabf5ee4592a4a77cb0cd68)
> [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
> --
>
> Key: QPID-8103
> URL: https://issues.apache.org/jira/browse/QPID-8103
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-broker-7.0.2
>
> Attachments:
> 0001-QPID-8103-Broker-J-WMC-Query-UI-Add-ability-to-downl.patch
>
>
> The usefulness of the Query UI is currently hampered by the fact that it is
> impossible to download the results of the query. A useful improvement would
> be a button allowing the results of the query to be downloaded, say as a CSV.
> The {{QueryServlet}} would need to accept an optional format that allowed the
> desired format to be specified.
> Also the results table does not permit the copy gesture. There is no good
> reason for this restriction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8103) [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
[
https://issues.apache.org/jira/browse/QPID-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378381#comment-16378381
]
ASF subversion and git services commented on QPID-8103:
---
Commit 686712e83fd21c3e569e3e317bc462dcbf5ebdcd in qpid-broker-j's branch
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=686712e ]
QPID-8103: [Broker-J] [WMC] [Query UI] Add ability to download query results as
CSV
(cherry picked from commit a2920afbc2ce92345c18c1add3e6d310358d4c69)
> [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
> --
>
> Key: QPID-8103
> URL: https://issues.apache.org/jira/browse/QPID-8103
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-broker-7.0.2
>
> Attachments:
> 0001-QPID-8103-Broker-J-WMC-Query-UI-Add-ability-to-downl.patch
>
>
> The usefulness of the Query UI is currently hampered by the fact that it is
> impossible to download the results of the query. A useful improvement would
> be a button allowing the results of the query to be downloaded, say as a CSV.
> The {{QueryServlet}} would need to accept an optional format that allowed the
> desired format to be specified.
> Also the results table does not permit the copy gesture. There is no good
> reason for this restriction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8103) [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
[
https://issues.apache.org/jira/browse/QPID-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378379#comment-16378379
]
ASF subversion and git services commented on QPID-8103:
---
Commit 2a9ffe312d0d4a90e18efd10b49b35fc627a66ff in qpid-broker-j's branch
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=2a9ffe3 ]
QPID-8103: [Broker-J] Import Common CSV sources from revision
'eede739d18c69722ff39e8e42df6b68ae7627082'
(cherry picked from commit 8758e7c826943a399bf5c6ee2a1f53db188d9f2d)
> [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
> --
>
> Key: QPID-8103
> URL: https://issues.apache.org/jira/browse/QPID-8103
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-broker-7.0.2
>
> Attachments:
> 0001-QPID-8103-Broker-J-WMC-Query-UI-Add-ability-to-downl.patch
>
>
> The usefulness of the Query UI is currently hampered by the fact that it is
> impossible to download the results of the query. A useful improvement would
> be a button allowing the results of the query to be downloaded, say as a CSV.
> The {{QueryServlet}} would need to accept an optional format that allowed the
> desired format to be specified.
> Also the results table does not permit the copy gesture. There is no good
> reason for this restriction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8103) [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
[
https://issues.apache.org/jira/browse/QPID-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378380#comment-16378380
]
ASF subversion and git services commented on QPID-8103:
---
Commit 94e1fd648ab34a495319f1d40666c5f130b9a2bf in qpid-broker-j's branch
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=94e1fd6 ]
QPID-8103: [Broker-J] Leave minimalistic implementation of CSV format
(cherry picked from commit 8d0e68fc5178e976696e96ed28d4ccdb820300f4)
> [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
> --
>
> Key: QPID-8103
> URL: https://issues.apache.org/jira/browse/QPID-8103
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-broker-7.0.2
>
> Attachments:
> 0001-QPID-8103-Broker-J-WMC-Query-UI-Add-ability-to-downl.patch
>
>
> The usefulness of the Query UI is currently hampered by the fact that it is
> impossible to download the results of the query. A useful improvement would
> be a button allowing the results of the query to be downloaded, say as a CSV.
> The {{QueryServlet}} would need to accept an optional format that allowed the
> desired format to be specified.
> Also the results table does not permit the copy gesture. There is no good
> reason for this restriction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8103) [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
[
https://issues.apache.org/jira/browse/QPID-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378382#comment-16378382
]
ASF subversion and git services commented on QPID-8103:
---
Commit 6a66466e84767f8bdd65e72365608efe3d298e56 in qpid-broker-j's branch
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=6a66466 ]
QPID-8103: [Broker-J] Reduce code duplication
(cherry picked from commit 0314c2a9cc7b98488bcb506214cec9b7c13784ca)
> [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
> --
>
> Key: QPID-8103
> URL: https://issues.apache.org/jira/browse/QPID-8103
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-broker-7.0.2
>
> Attachments:
> 0001-QPID-8103-Broker-J-WMC-Query-UI-Add-ability-to-downl.patch
>
>
> The usefulness of the Query UI is currently hampered by the fact that it is
> impossible to download the results of the query. A useful improvement would
> be a button allowing the results of the query to be downloaded, say as a CSV.
> The {{QueryServlet}} would need to accept an optional format that allowed the
> desired format to be specified.
> Also the results table does not permit the copy gesture. There is no good
> reason for this restriction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1767) allow the Transport to expose an output buffer that is not read-only
[ https://issues.apache.org/jira/browse/PROTON-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1767: --- Summary: allow the Transport to expose an output buffer that is not read-only (was: [proton-j] Allow the Transport to expose an output buffer that is not read-only) > allow the Transport to expose an output buffer that is not read-only > > > Key: PROTON-1767 > URL: https://issues.apache.org/jira/browse/PROTON-1767 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: proton-j-0.25.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: proton-j-0.26.0 > > > In some cases the read-only output buffer exposed by TransportImpl by calling > head() or getOutputBuffer() can lead to extra intermediate copies of the > buffer based on the IO framework being used to transmit the bytes (such as > current Netty releases). This is due to the fact that the read-only buffer > reports that it doesn't have a backing array so the frameworks try to work > around this to optimize the transfer of bytes. For uses who are aware of > this and can ensure they never tamper with the buffer contents that aren't > consumed we should let them choose to expose a writable duplicate of the > output buffer. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1756) avoid creating a Runnable on every Transfer frame send
[ https://issues.apache.org/jira/browse/PROTON-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1756: --- Summary: avoid creating a Runnable on every Transfer frame send (was: [Proton-J] Runnable created on every Transfer frame send) > avoid creating a Runnable on every Transfer frame send > -- > > Key: PROTON-1756 > URL: https://issues.apache.org/jira/browse/PROTON-1756 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: proton-j-0.25.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Trivial > Fix For: proton-j-0.26.0 > > > On each outbound Transfer frame the TransportImpl creates a new Runnable to > handle overflow which sets the more value on the Transfer and rewrites the > frame body. We can use a single instance to handle this and reduce the > amount of garbage create on send. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8103) [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
[
https://issues.apache.org/jira/browse/QPID-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378345#comment-16378345
]
ASF subversion and git services commented on QPID-8103:
---
Commit 0a3c7a2fee6d6c078aabf5ee4592a4a77cb0cd68 in qpid-broker-j's branch
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=0a3c7a2 ]
QPID-8103: [Broker-J] Remove file committed by mistake
> [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
> --
>
> Key: QPID-8103
> URL: https://issues.apache.org/jira/browse/QPID-8103
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-broker-7.0.2
>
> Attachments:
> 0001-QPID-8103-Broker-J-WMC-Query-UI-Add-ability-to-downl.patch
>
>
> The usefulness of the Query UI is currently hampered by the fact that it is
> impossible to download the results of the query. A useful improvement would
> be a button allowing the results of the query to be downloaded, say as a CSV.
> The {{QueryServlet}} would need to accept an optional format that allowed the
> desired format to be specified.
> Also the results table does not permit the copy gesture. There is no good
> reason for this restriction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8103) [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
[
https://issues.apache.org/jira/browse/QPID-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378340#comment-16378340
]
ASF subversion and git services commented on QPID-8103:
---
Commit 0314c2a9cc7b98488bcb506214cec9b7c13784ca in qpid-broker-j's branch
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=0314c2a ]
QPID-8103: [Broker-J] Reduce code duplication
> [Broker-J] [WMC] [Query UI] Add ability to download results as CSV
> --
>
> Key: QPID-8103
> URL: https://issues.apache.org/jira/browse/QPID-8103
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Keith Wall
>Assignee: Alex Rudyy
>Priority: Minor
> Fix For: qpid-java-broker-7.0.2
>
> Attachments:
> 0001-QPID-8103-Broker-J-WMC-Query-UI-Add-ability-to-downl.patch
>
>
> The usefulness of the Query UI is currently hampered by the fact that it is
> impossible to download the results of the query. A useful improvement would
> be a button allowing the results of the query to be downloaded, say as a CSV.
> The {{QueryServlet}} would need to accept an optional format that allowed the
> desired format to be specified.
> Also the results table does not permit the copy gesture. There is no good
> reason for this restriction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
