[jira] [Updated] (DISPATCH-1339) Multiple consoles attached to a router are showing as separate icons
[ https://issues.apache.org/jira/browse/DISPATCH-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1339: Fix Version/s: 1.8.0 > Multiple consoles attached to a router are showing as separate icons > > > Key: DISPATCH-1339 > URL: https://issues.apache.org/jira/browse/DISPATCH-1339 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 1.7.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > Fix For: 1.8.0 > > > If multiple consoles are attached to a single router, and those consoles are > originating from multiple ip addresses, then each console is appearing as a > separate icon on the topology view. > All consoles attached to a router should be collapsed into a single icon. > When that icon is clicked, the popup should show the list of connections. -- 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-1340) Show settlement rate and delayed deliveries in client popup
[ https://issues.apache.org/jira/browse/DISPATCH-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1340: Fix Version/s: 1.8.0 > Show settlement rate and delayed deliveries in client popup > --- > > Key: DISPATCH-1340 > URL: https://issues.apache.org/jira/browse/DISPATCH-1340 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 1.7.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > Fix For: 1.8.0 > > > On the console's topology page, if you click on a client you will see a popup > that shows the connections for all clients of that type. > If you click on a connection, you will see a list of links for that > connection. > The info displayed for a link should contain the settlement rate, delayed > deliveries, a capacity percent = undelivered/capacity. -- 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] [Closed] (DISPATCH-898) Vhost user group settings define an attribute that is not implemented
[ https://issues.apache.org/jira/browse/DISPATCH-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy closed DISPATCH-898. -- > Vhost user group settings define an attribute that is not implemented > - > > Key: DISPATCH-898 > URL: https://issues.apache.org/jira/browse/DISPATCH-898 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 1.5.0 > > > The attribute should be removed from the schema until it is implemented. -- 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-1122) Authenticated username not printed
[
https://issues.apache.org/jira/browse/DISPATCH-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1122:
Fix Version/s: 1.4.0
> Authenticated username not printed
> --
>
> Key: DISPATCH-1122
> URL: https://issues.apache.org/jira/browse/DISPATCH-1122
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ulf Lilleengen
>Priority: Major
> Fix For: 1.4.0
>
>
> When using the remote authentication service, the username that was
> authenticated is not printed due to a incorrect format string.
>
> Currently the output is:
>
> {{2018-09-17 00:08:32.899183 + AUTHSERVICE (info) authenticated as }}
>
> without the username added.
--
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] [Closed] (DISPATCH-1122) Authenticated username not printed
[
https://issues.apache.org/jira/browse/DISPATCH-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy closed DISPATCH-1122.
---
> Authenticated username not printed
> --
>
> Key: DISPATCH-1122
> URL: https://issues.apache.org/jira/browse/DISPATCH-1122
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ulf Lilleengen
>Priority: Major
> Fix For: 1.4.0
>
>
> When using the remote authentication service, the username that was
> authenticated is not printed due to a incorrect format string.
>
> Currently the output is:
>
> {{2018-09-17 00:08:32.899183 + AUTHSERVICE (info) authenticated as }}
>
> without the username added.
--
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] (QPID-8316) [Broker-J][AMQP 0-8..0-91] The meta data of flowed to disk messages continue to occupy heap memory
[ https://issues.apache.org/jira/browse/QPID-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8316: - Description: A regression in heap memory utilization was introduced in message validation functionality implemented as part of IBAMQ-8318. The message metadata is loaded into heap for message validation and continue to remain in heap until message is consumed. The flow to disk functionality does not clean metadata objects as message is not considered as being resided in memory. The issue can be mitigated by increasing heap size. was:A regression in heap memory utilization was introduced in message validation functionality implemented as part of IBAMQ-8318. The message metadata is loaded into heap for message validation and continue to remain in heap until message is consumed. The flow to disk functionality does not clean metadata objects as message is not considered as being resided in memory. > [Broker-J][AMQP 0-8..0-91] The meta data of flowed to disk messages continue > to occupy heap memory > -- > > Key: QPID-8316 > URL: https://issues.apache.org/jira/browse/QPID-8316 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.7, qpid-java-broker-7.1.1, > qpid-java-broker-7.1.2, qpid-java-broker-7.1.3 >Reporter: Alex Rudyy >Priority: Critical > Fix For: qpid-java-broker-7.0.8, qpid-java-broker-7.1.4 > > > A regression in heap memory utilization was introduced in message validation > functionality implemented as part of IBAMQ-8318. The message metadata is > loaded into heap for message validation and continue to remain in heap until > message is consumed. The flow to disk functionality does not clean metadata > objects as message is not considered as being resided in memory. > The issue can be mitigated by increasing heap size. -- 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-898) Vhost user group settings define an attribute that is not implemented
[ https://issues.apache.org/jira/browse/DISPATCH-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-898: --- Affects Version/s: 1.4.0 > Vhost user group settings define an attribute that is not implemented > - > > Key: DISPATCH-898 > URL: https://issues.apache.org/jira/browse/DISPATCH-898 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > > The attribute should be removed from the schema until it is implemented. -- 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-898) Vhost user group settings define an attribute that is not implemented
[ https://issues.apache.org/jira/browse/DISPATCH-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-898: --- Fix Version/s: 1.5.0 > Vhost user group settings define an attribute that is not implemented > - > > Key: DISPATCH-898 > URL: https://issues.apache.org/jira/browse/DISPATCH-898 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 1.5.0 > > > The attribute should be removed from the schema until it is implemented. -- 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-8316) [Broker-J][AMQP 0-8..0-91] The meta data of flowed to disk messages continue to occupy heap memory
Alex Rudyy created QPID-8316: Summary: [Broker-J][AMQP 0-8..0-91] The meta data of flowed to disk messages continue to occupy heap memory Key: QPID-8316 URL: https://issues.apache.org/jira/browse/QPID-8316 Project: Qpid Issue Type: Bug Components: Broker-J Affects Versions: qpid-java-broker-7.1.3, qpid-java-broker-7.1.2, qpid-java-broker-7.1.1, qpid-java-broker-7.0.7 Reporter: Alex Rudyy Fix For: qpid-java-broker-7.0.8, qpid-java-broker-7.1.4 A regression in heap memory utilization was introduced in message validation functionality implemented as part of IBAMQ-8318. The message metadata is loaded into heap for message validation and continue to remain in heap until message is consumed. The flow to disk functionality does not clean metadata objects as message is not considered as being resided in memory. -- 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] (QPID-8316) [Broker-J][AMQP 0-8..0-91] The meta data of flowed to disk messages continue to occupy heap memory
[ https://issues.apache.org/jira/browse/QPID-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8316: - Priority: Critical (was: Major) > [Broker-J][AMQP 0-8..0-91] The meta data of flowed to disk messages continue > to occupy heap memory > -- > > Key: QPID-8316 > URL: https://issues.apache.org/jira/browse/QPID-8316 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.7, qpid-java-broker-7.1.1, > qpid-java-broker-7.1.2, qpid-java-broker-7.1.3 >Reporter: Alex Rudyy >Priority: Critical > Fix For: qpid-java-broker-7.0.8, qpid-java-broker-7.1.4 > > > A regression in heap memory utilization was introduced in message validation > functionality implemented as part of IBAMQ-8318. The message metadata is > loaded into heap for message validation and continue to remain in heap until > message is consumed. The flow to disk functionality does not clean metadata > objects as message is not considered as being resided in memory. -- 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-1337) Fallback Destination for Unreachable Addresses
[
https://issues.apache.org/jira/browse/DISPATCH-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-1337:
---
Summary: Fallback Destination for Unreachable Addresses (was: Alternate
Destination for Unreachable Addresses)
> Fallback Destination for Unreachable Addresses
> --
>
> Key: DISPATCH-1337
> URL: https://issues.apache.org/jira/browse/DISPATCH-1337
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Router Node
>Reporter: Ted Ross
>Assignee: Ted Ross
>Priority: Major
> Fix For: 1.8.0
>
>
> This feature allows addresses to be configured such that an alternate
> destination can be used to receive messages that are not deliverable to any
> normal consumers on the address.
> Typically, this feature will be used to allow a message broker to store
> messages that are not routable directly to consumers. When one or more
> consumers are attached in the router network, messages shall be delivered
> directly to the consumers. Where there are no reachable consumers,
> deliveries shall then be diverted to the alternate destination. Once
> consumers re-connect to the network, messages shall again be delivered
> directly.
> When a consumer comes online after messages have been stored in a broker, it
> shall receive the stored messages interleaved with new messages from
> producers. No attempt shall be made by the router network to preserve the
> original delivery order of the messages.
> This feature can be configured by adding the attribute
> {noformat}
> alternate: yes
> {noformat}
> to an address configuration. This attribute tells the router that any address
> matching the configuration that appears shall support the alternate
> destination capability.
> There are two ways to create an alternate destination for an address:
> Using auto-links:
> An auto-link (or a pair of auto-links) can be configured to create an
> alternate waypoint for an address. For example, assume that there is a
> route-container connector or listener for a broker called "alternate-broker".
> {noformat}
> address {
> prefix: position_update
> alternate: yes
> }
> autoLink {
> address: position_update.338
> direction: in
> connection: alternate-broker
> alternate: yes
> }
> autoLink {
> address: position_update.338
> direction: out
> connection: alternate-broker
> alternate: yes
> }
> {noformat}
> The above configuration will use a queue on the broker called
> "position_update.338" as the alternate destination for direct consumers.
> Furthermore, since there are both _in_ and _out_ auto-links, the router(s)
> shall send queued messages to newly attached direct consumers.
> Using terminus capabilities:
> As an alternative to using auto-links, the broker (or any other process) can
> attach sending and receiving links to the address with terminus-capability
> "qd.alternate". This will create the same behavior as the above example.
--
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] [Closed] (DISPATCH-760) Inefficiencies handling message annotations
[
https://issues.apache.org/jira/browse/DISPATCH-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy closed DISPATCH-760.
--
> Inefficiencies handling message annotations
> ---
>
> Key: DISPATCH-760
> URL: https://issues.apache.org/jira/browse/DISPATCH-760
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 0.8.0
> Environment: Fedora 25 laptop
> Single router, 8 worker threads, single receiver, single sender. Messages
> have 200 100-byte annotations.
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: DISPATCH-760-ALL-WORKERS.svg,
> DISPATCH-760-core-thread.svg
>
>
> The router as a whole spends a lot of time managing annotations. With routers
> and other intermediaries adding and stripping annotations, improvements in
> this area could be valuable.
> Testing a stand-alone router gets these results.
> ||N 100-byte annotations || msg/S throughput||
> |0 | 30,000 |
> |1 | 22,500 |
> |2 | 20,500 |
> |5 | 15,500 |
> | 10 | 10,000 |
> | 20 | 5,500 |
> | 50 | 2,400 |
> | 100 | 1,200 |
> | 200 |500 |
> Application 'perf' provides some visibility into where the threads are
> spending their time. View the attached .svg files to see what the core thread
> and an aggregation of the remaining threads are busy doing.
> The worker threads are spending ~85% of their time composing messages while
> the core thread is spending 90+% of its time deleting deliveries with a
> majority of its time in qd_parse_free().
> A 'top' thread snapshot shows several worker threads completely idle. The
> core thread has tid=32631.
> {noformat}
> PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
> 32633 chug 20 0 858376 137708 8484 R 26.7 0.9 0:33.99 qdrouterd
> 32632 chug 20 0 858376 137708 8484 S 20.0 0.9 0:34.63 qdrouterd
> 32631 chug 20 0 858376 137708 8484 S 13.3 0.9 0:30.13 qdrouterd
> 32635 chug 20 0 858376 137708 8484 R 13.3 0.9 0:34.26 qdrouterd
> 32636 chug 20 0 858376 137708 8484 S 13.3 0.9 0:34.80 qdrouterd
> 32638 chug 20 0 858376 137708 8484 S 13.3 0.9 0:34.34 qdrouterd
> 32616 chug 20 0 858376 137708 8484 S 6.7 0.9 0:35.48 qdrouterd
> 32634 chug 20 0 858376 137708 8484 S 6.7 0.9 0:34.09 qdrouterd
> 32637 chug 20 0 858376 137708 8484 S 6.7 0.9 0:34.42 qdrouterd
> {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] (DISPATCH-1329) Edge router system test needs skip test convenience switches
[ https://issues.apache.org/jira/browse/DISPATCH-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1329: Affects Version/s: 1.7.0 > Edge router system test needs skip test convenience switches > > > Key: DISPATCH-1329 > URL: https://issues.apache.org/jira/browse/DISPATCH-1329 > Project: Qpid Dispatch > Issue Type: Improvement >Affects Versions: 1.7.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 1.8.0 > > > See system_tests_topology_disposition.py cls.skip and the application to > skipTest for a model. -- 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] codecov-io edited a comment on issue #506: Added Alternate-Destination feature
codecov-io edited a comment on issue #506: Added Alternate-Destination feature URL: https://github.com/apache/qpid-dispatch/pull/506#issuecomment-493596321 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/506?src=pr=h1) Report > :exclamation: No coverage uploaded for pull request base (`master@7d3f860`). [Click here to learn what that means](https://docs.codecov.io/docs/error-reference#section-missing-base-commit). > The diff coverage is `93.12%`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/506?src=pr=tree) ```diff @@Coverage Diff@@ ## master #506 +/- ## = Coverage ? 87.01% = Files ? 87 Lines ?19434 Branches ?0 = Hits ?16910 Misses? 2524 Partials ?0 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/506?src=pr=tree) | Coverage Δ | | |---|---|---| | [src/amqp.c](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree#diff-c3JjL2FtcXAuYw==) | `0% <ø> (ø)` | | | [src/router\_core/forwarder.c](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2ZvcndhcmRlci5j) | `93.79% <100%> (ø)` | | | [src/router\_core/agent\_config\_address.c](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2NvbmZpZ19hZGRyZXNzLmM=) | `78.59% <100%> (ø)` | | | [src/router\_core/route\_control.c](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL3JvdXRlX2NvbnRyb2wuYw==) | `97.89% <100%> (ø)` | | | [src/router\_core/agent\_config\_auto\_link.c](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2NvbmZpZ19hdXRvX2xpbmsuYw==) | `79.83% <100%> (ø)` | | | [src/router\_core/agent\_router.c](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X3JvdXRlci5j) | `91.13% <100%> (ø)` | | | [...core/modules/address\_lookup\_client/lookup\_client.c](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL21vZHVsZXMvYWRkcmVzc19sb29rdXBfY2xpZW50L2xvb2t1cF9jbGllbnQuYw==) | `92.6% <100%> (ø)` | | | [src/router\_core/agent\_address.c](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2FkZHJlc3MuYw==) | `90.4% <100%> (ø)` | | | [src/router\_config.c](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb25maWcuYw==) | `96.41% <100%> (ø)` | | | [src/router\_core/modules/edge\_router/addr\_proxy.c](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL21vZHVsZXMvZWRnZV9yb3V0ZXIvYWRkcl9wcm94eS5j) | `92.7% <80%> (ø)` | | | ... and [3 more](https://codecov.io/gh/apache/qpid-dispatch/pull/506/diff?src=pr=tree-more) | | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/506?src=pr=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/506?src=pr=footer). Last update [7d3f860...c92de9e](https://codecov.io/gh/apache/qpid-dispatch/pull/506?src=pr=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8315) update perftests visualisation csv dep to version available in maven central
[ https://issues.apache.org/jira/browse/QPID-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-8315: - Affects Version/s: qpid-java-broker-7.0.7 Fix Version/s: qpid-java-broker-7.0.8 > update perftests visualisation csv dep to version available in maven central > > > Key: QPID-8315 > URL: https://issues.apache.org/jira/browse/QPID-8315 > Project: Qpid > Issue Type: Task > Components: Java Performance Tests >Affects Versions: qpid-java-broker-7.0.7, qpid-java-broker-7.1.3 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Trivial > Fix For: qpid-java-broker-7.0.8, qpid-java-broker-7.1.4 > > > Currently the version of csv processing dep used for the visualisation module > requires defining an additional repository, but newer versions are released > to Maven Central so we should now update and use one of those instead. -- 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-8315) update perftests visualisation csv dep to version available in maven central
[ https://issues.apache.org/jira/browse/QPID-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846006#comment-16846006 ] ASF subversion and git services commented on QPID-8315: --- Commit ed13d6abc72d0b1d36b319feacb0eccdf30cb1fc in qpid-broker-j's branch refs/heads/7.0.x from Robert Gemmell [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=ed13d6a ] QPID-8315: update csv handling dep to new version, available from maven central (cherry picked from commit b3e77760f2a4d9e5b8afd07a335a4384acabe969) > update perftests visualisation csv dep to version available in maven central > > > Key: QPID-8315 > URL: https://issues.apache.org/jira/browse/QPID-8315 > Project: Qpid > Issue Type: Task > Components: Java Performance Tests >Affects Versions: qpid-java-broker-7.1.3 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Trivial > Fix For: qpid-java-broker-7.1.4 > > > Currently the version of csv processing dep used for the visualisation module > requires defining an additional repository, but newer versions are released > to Maven Central so we should now update and use one of those instead. -- 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
