[jira] [Resolved] (PROTON-1960) [Go Electron] Unable to send a message larger than 16k in size
[ https://issues.apache.org/jira/browse/PROTON-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1960. - Resolution: Fixed Fix Version/s: proton-c-0.27.0 > [Go Electron] Unable to send a message larger than 16k in size > -- > > Key: PROTON-1960 > URL: https://issues.apache.org/jira/browse/PROTON-1960 > Project: Qpid Proton > Issue Type: Bug >Reporter: Rob KIng >Assignee: Alan Conway >Priority: Major > Fix For: proton-c-0.27.0 > > > Unable to send a message larger than 16k in size from a sending program using > the Go electron bindings to the qpidd broker. Attempting to send a message of > this size causes the program to hang in the electron package. Some discussion > and some debug output from the broker can be found at > [http://qpid.2158936.n2.nabble.com/Go-Electron-Large-Messages-Fail-To-Send-td7680219.html] > Issue can be recreated using a slightly modified version of send.go in the > electron package [https://play.golang.org/p/2dQ4jdlKHKi] sending to qpidd > version 1.38 -- 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-1960) [Go Electron] Unable to send a message larger than 16k in size
[ https://issues.apache.org/jira/browse/PROTON-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673658#comment-16673658 ] Alan Conway commented on PROTON-1960: - The go1 branch is supposed to point at the latest official release, but I just realized it had fallen behind. I've just updated it to 0.26. Unfortunately the fix you need was made just after the 0.26 release, so it'll show up in 0.27. I'll take care not to dawdle on updating the go-get branch next time! The releases are pretty regular (every couple months or so), ask on the qpid-dev list for a more official estimate. > [Go Electron] Unable to send a message larger than 16k in size > -- > > Key: PROTON-1960 > URL: https://issues.apache.org/jira/browse/PROTON-1960 > Project: Qpid Proton > Issue Type: Bug >Reporter: Rob KIng >Assignee: Alan Conway >Priority: Major > > Unable to send a message larger than 16k in size from a sending program using > the Go electron bindings to the qpidd broker. Attempting to send a message of > this size causes the program to hang in the electron package. Some discussion > and some debug output from the broker can be found at > [http://qpid.2158936.n2.nabble.com/Go-Electron-Large-Messages-Fail-To-Send-td7680219.html] > Issue can be recreated using a slightly modified version of send.go in the > electron package [https://play.golang.org/p/2dQ4jdlKHKi] sending to qpidd > version 1.38 -- 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-1947) [cpp] not correctly locating jsoncpp library on some platforms
[ https://issues.apache.org/jira/browse/PROTON-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673651#comment-16673651 ] ASF subversion and git services commented on PROTON-1947: - Commit ab82a8b8e92f2dff3fa8d03d9c11403439420bba in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=ab82a8b ] PROTON-1947: [cpp] not locating jsoncpp library on some platforms CMake was not adding the INCLUDE_DIR locations found by FindJsonCpp so a non-standard installation would be found but cause a compile failure. > [cpp] not correctly locating jsoncpp library on some platforms > -- > > Key: PROTON-1947 > URL: https://issues.apache.org/jira/browse/PROTON-1947 > Project: Qpid Proton > Issue Type: Sub-task > Components: cpp-binding >Affects Versions: proton-c-0.25.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Major > -- 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-1944) 0.27.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673653#comment-16673653 ] ASF subversion and git services commented on PROTON-1944: - Commit 5b5927de939c83162b543801532c61fdb0434826 in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5b5927d ] PROTON-1926, PROTON-1944: restore versions for 0.26.0-rc2 This reverts commit 1b554aad70452d6501cb3e13a6c10186d14e9dc9. > 0.27.0 release tasks > > > Key: PROTON-1944 > URL: https://issues.apache.org/jira/browse/PROTON-1944 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.27.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] [Commented] (PROTON-1926) 0.26.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673647#comment-16673647 ] ASF subversion and git services commented on PROTON-1926: - Commit fd518f29b532c4e692ca7684b0917234e4bfff1d in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=fd518f2 ] PROTON-1926: update versions for 0.26.0-rc1 > 0.26.0 release tasks > > > Key: PROTON-1926 > URL: https://issues.apache.org/jira/browse/PROTON-1926 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.26.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] [Commented] (PROTON-1926) 0.26.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673652#comment-16673652 ] ASF subversion and git services commented on PROTON-1926: - Commit 5b5927de939c83162b543801532c61fdb0434826 in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5b5927d ] PROTON-1926, PROTON-1944: restore versions for 0.26.0-rc2 This reverts commit 1b554aad70452d6501cb3e13a6c10186d14e9dc9. > 0.26.0 release tasks > > > Key: PROTON-1926 > URL: https://issues.apache.org/jira/browse/PROTON-1926 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.26.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] [Commented] (PROTON-1944) 0.27.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673648#comment-16673648 ] ASF subversion and git services commented on PROTON-1944: - Commit 1b554aad70452d6501cb3e13a6c10186d14e9dc9 in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1b554aa ] PROTON-1944, PROTON-1926: update versions for 0.27.0-SNAPSHOT > 0.27.0 release tasks > > > Key: PROTON-1944 > URL: https://issues.apache.org/jira/browse/PROTON-1944 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.27.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] [Commented] (PROTON-1926) 0.26.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673649#comment-16673649 ] ASF subversion and git services commented on PROTON-1926: - Commit 1b554aad70452d6501cb3e13a6c10186d14e9dc9 in qpid-proton's branch refs/heads/go1 from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1b554aa ] PROTON-1944, PROTON-1926: update versions for 0.27.0-SNAPSHOT > 0.26.0 release tasks > > > Key: PROTON-1926 > URL: https://issues.apache.org/jira/browse/PROTON-1926 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.26.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] [Commented] (PROTON-1946) [cpp] connection config file parser mis-handling TLS defaults
[
https://issues.apache.org/jira/browse/PROTON-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673650#comment-16673650
]
ASF subversion and git services commented on PROTON-1946:
-
Commit b34215170680ebb2f6b60604374c58f598b45803 in qpid-proton's branch
refs/heads/go1 from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b342151 ]
PROTON-1946: [cpp] connection config parser incorrect defaults
- Change default "host" to "localhost" (was "")
- Only throw proton::error, don't leak jsoncpp exceptions
- Add tests for SASL/TLS behavior
- Treat explicit "null" valued field as equivalent to a missing field
> [cpp] connection config file parser mis-handling TLS defaults
> -
>
> Key: PROTON-1946
> URL: https://issues.apache.org/jira/browse/PROTON-1946
> Project: Qpid Proton
> Issue Type: Sub-task
> Components: cpp-binding
>Affects Versions: proton-c-0.25.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Major
>
> The C++ connection configuration parser mis-handles default values in several
> ways:
> * tls is not enabled unless there is a tls: {} section - it should be
> enabled (with default config) if scheme: amqps is present even if there is no
> tls section
> * in several cases an explicit 'field: null' is treated differently (as an
> error) from field being absent (use default value). null and absent should be
> equivalent.
> * Host defaults to "", it should be "localhost"
> * Some exceptions from jsoncpp are leaked, they should be wrapped in
> proton::error
> * Need additional tests to cover all of the above
--
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-1161) Handle edge routers in the console
[ https://issues.apache.org/jira/browse/DISPATCH-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673629#comment-16673629 ] ASF subversion and git services commented on DISPATCH-1161: --- Commit ca22c9d134221f79917b0413acfa09862a6ef0ce in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=ca22c9d ] DISPATCH-1161 Fix traffic animation on console's topology page for edge routers > Handle edge routers in the console > -- > > Key: DISPATCH-1161 > URL: https://issues.apache.org/jira/browse/DISPATCH-1161 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 1.4.1 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > > Show edge routers on the console's topology page. > * Show them on the diagram in a unique color or size > * Add them to the legend > * Consolidate mulitple edge routers attached to a router as a group icon > * Whem mouseover link between router and edge routers, show traffic stats > for busiest edge routers -- 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-1161) Handle edge routers in the console
[ https://issues.apache.org/jira/browse/DISPATCH-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673585#comment-16673585 ] ASF subversion and git services commented on DISPATCH-1161: --- Commit 5c17437484ed73f935c437d859762cf6520e324f in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=5c17437 ] DISPATCH-1161 Fix console test > Handle edge routers in the console > -- > > Key: DISPATCH-1161 > URL: https://issues.apache.org/jira/browse/DISPATCH-1161 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 1.4.1 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > > Show edge routers on the console's topology page. > * Show them on the diagram in a unique color or size > * Add them to the legend > * Consolidate mulitple edge routers attached to a router as a group icon > * Whem mouseover link between router and edge routers, show traffic stats > for busiest edge routers -- 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-1165) Generate egress-link histograms for more kinds of connections
[ https://issues.apache.org/jira/browse/DISPATCH-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-1165: --- Description: Presently, the router only generates ingress histograms for outgoing links on connections with the normal role. It is appropriate to also generate histograms for route-container and edge roles. was: Presently, the router only generates egress histograms for outgoing links on connections with the normal role. It is appropriate to also generate histograms for route-container and edge roles. > Generate egress-link histograms for more kinds of connections > - > > Key: DISPATCH-1165 > URL: https://issues.apache.org/jira/browse/DISPATCH-1165 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Minor > Fix For: 1.5.0 > > > Presently, the router only generates ingress histograms for outgoing links on > connections with the normal role. It is appropriate to also generate > histograms for route-container and edge roles. > -- 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] (DISPATCH-1165) Generate egress-link histograms for more kinds of connections
Ted Ross created DISPATCH-1165: -- Summary: Generate egress-link histograms for more kinds of connections Key: DISPATCH-1165 URL: https://issues.apache.org/jira/browse/DISPATCH-1165 Project: Qpid Dispatch Issue Type: Improvement Components: Router Node Reporter: Ted Ross Assignee: Ted Ross Fix For: 1.5.0 Presently, the router only generates egress histograms for outgoing links on connections with the normal role. It is appropriate to also generate histograms for route-container and edge roles. -- 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-1158) Add background map to console's topology page
[ https://issues.apache.org/jira/browse/DISPATCH-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673216#comment-16673216 ] ASF GitHub Bot commented on DISPATCH-1158: -- Github user ErnieAllen closed the pull request at: https://github.com/apache/qpid-dispatch/pull/408 > Add background map to console's topology page > - > > Key: DISPATCH-1158 > URL: https://issues.apache.org/jira/browse/DISPATCH-1158 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 1.4.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > > It should: > * show a world map > * allow panning > * wrap (if a country is panned off one side it should show up on other side) > * allow zooming in/out > * pin routers to a geo location (if a router is moved to a geographic > location, it should stay there when the map is panned/zoomed) > * remember router's pinned location > * remember pan and zoom settings > * allow changing of land and ocean colors > * -- 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 #408: ernie-DISPATCH-1158 Add background map to c...
Github user ErnieAllen closed the pull request at: https://github.com/apache/qpid-dispatch/pull/408 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1960) [Go Electron] Unable to send a message larger than 16k in size
[ https://issues.apache.org/jira/browse/PROTON-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673194#comment-16673194 ] Rob KIng commented on PROTON-1960: -- Apologies I thought my go get was pulling the code from master however now realised it's actually pulling it from the go1 branch. Doing a git clone from master and rebuilding does indeed fix the issue! Many thanks for that. What is your policy for updating the go1 branch? > [Go Electron] Unable to send a message larger than 16k in size > -- > > Key: PROTON-1960 > URL: https://issues.apache.org/jira/browse/PROTON-1960 > Project: Qpid Proton > Issue Type: Bug >Reporter: Rob KIng >Assignee: Alan Conway >Priority: Major > > Unable to send a message larger than 16k in size from a sending program using > the Go electron bindings to the qpidd broker. Attempting to send a message of > this size causes the program to hang in the electron package. Some discussion > and some debug output from the broker can be found at > [http://qpid.2158936.n2.nabble.com/Go-Electron-Large-Messages-Fail-To-Send-td7680219.html] > Issue can be recreated using a slightly modified version of send.go in the > electron package [https://play.golang.org/p/2dQ4jdlKHKi] sending to qpidd > version 1.38 -- 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] (QPIDJMS-420) Improve performance of MessageConsumer processing
[ https://issues.apache.org/jira/browse/QPIDJMS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-420. -- Resolution: Fixed > Improve performance of MessageConsumer processing > - > > Key: QPIDJMS-420 > URL: https://issues.apache.org/jira/browse/QPIDJMS-420 > Project: Qpid JMS > Issue Type: Improvement > Components: qpid-jms-client >Affects Versions: 0.37.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Minor > Fix For: 0.38.0 > > > Refactor some of the code paths that handling inbound message processing and > eventually queue or deliver inbound messages to the MessageConsumer. > -- 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-8256) [Broker-J] Update Guava to version 27.0
[
https://issues.apache.org/jira/browse/QPID-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8256:
-
Issue Type: Improvement (was: Bug)
> [Broker-J] Update Guava to version 27.0
> ---
>
> Key: QPID-8256
> URL: https://issues.apache.org/jira/browse/QPID-8256
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.7,
> qpid-java-6.1.8
>
>
> The Qpid Broker depends on an older guava version 0.22 which is affected by
> vulnerability
> [CVE-2018-10237|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10237].
> It does not look like vulnerability
> [CVE-2018-10237|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10237]
> can be exploited with Qpid Broker, as impacted guava classes
> {{AtomicDoubleArray}} and {{CompoundOrdering}} are not used directly within
> Qpid Broker 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] [Commented] (DISPATCH-1164) Failing to compile the router when only python3 is installed
[ https://issues.apache.org/jira/browse/DISPATCH-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673091#comment-16673091 ] ASF subversion and git services commented on DISPATCH-1164: --- Commit 04802507f2c06c2ca7ef47f2318c8b99e49150b8 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=0480250 ] DISPATCH-1164 - Updated config.sh to default to python2 if both are present. This is the same default that the reset of the build system uses. > Failing to compile the router when only python3 is installed > > > Key: DISPATCH-1164 > URL: https://issues.apache.org/jira/browse/DISPATCH-1164 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Fernando Giorgetti >Assignee: Fernando Giorgetti >Priority: Major > Fix For: 1.5.0 > > > While performing LP test on RHEL8 Beta, with just python36 installed, I am > seeing an error in my attempt to source the "config.sh" script. > I am basically seeing two problems here: > # It is using a static "python" executable (and here I have just python3 in > my PATH) > # The "print" statement is not using parenthesis > -- 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-8256) [Broker-J] Update Guava to version 27.0
Alex Rudyy created QPID-8256:
Summary: [Broker-J] Update Guava to version 27.0
Key: QPID-8256
URL: https://issues.apache.org/jira/browse/QPID-8256
Project: Qpid
Issue Type: Bug
Components: Broker-J
Reporter: Alex Rudyy
Fix For: qpid-java-6.1.8, qpid-java-broker-7.1.0,
qpid-java-broker-7.0.7
The Qpid Broker depends on an older guava version 0.22 which is affected by
vulnerability
[CVE-2018-10237|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10237].
It does not look like vulnerability
[CVE-2018-10237|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10237]
can be exploited with Qpid Broker, as impacted guava classes
{{AtomicDoubleArray}} and {{CompoundOrdering}} are not used directly within
Qpid Broker 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] [Commented] (PROTON-19) Dynamic language bindings forbid context from being null for connectors and listeners.
[ https://issues.apache.org/jira/browse/PROTON-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672932#comment-16672932 ] Robbie Gemmell commented on PROTON-19: -- For later reference, the above commit was actually intended for PROTON-1961. > Dynamic language bindings forbid context from being null for connectors and > listeners. > -- > > Key: PROTON-19 > URL: https://issues.apache.org/jira/browse/PROTON-19 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce >Priority: Blocker > Attachments: > 0001-Removes-the-not-null-restriction-on-contexts-for-lis.patch > > > The swig contracts currently forbid setting the context for either a > connector or a listener to null, even though such states are allowed. This > patch fixes that, removing the 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] (QPID-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand
[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8245: - Attachment: (was: 0008-QPID-8245-Dispose-QpidByteBuffer-on-decoding-FieldTa.patch) > [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand > -- > > Key: QPID-8245 > URL: https://issues.apache.org/jira/browse/QPID-8245 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > At the moment all field table properties are decoded when decode > functionality is invoked. For use cases when only some of the field table > properties are queried, the decoding functionality can be changed to stop > decoding on getting the requested property. Potentially, such approach can > improve the performance of routing transient messages when destinations are > bound to the routing exchange using selector filters. As filter expression > contains only some properties, the decoding of message headers can be stopped > on getting all fields specified in selector expression. > The idea is illustrated by Rob Godfrey on > [QPID-8238|https://issues.apache.org/jira/browse/QPID-8238?focusedCommentId=16601936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16601936] -- 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-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand
[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8245: - Attachment: (was: 0007-QPID-8245-Change-decoding-to-decode-only-value-for-t.patch) > [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand > -- > > Key: QPID-8245 > URL: https://issues.apache.org/jira/browse/QPID-8245 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > At the moment all field table properties are decoded when decode > functionality is invoked. For use cases when only some of the field table > properties are queried, the decoding functionality can be changed to stop > decoding on getting the requested property. Potentially, such approach can > improve the performance of routing transient messages when destinations are > bound to the routing exchange using selector filters. As filter expression > contains only some properties, the decoding of message headers can be stopped > on getting all fields specified in selector expression. > The idea is illustrated by Rob Godfrey on > [QPID-8238|https://issues.apache.org/jira/browse/QPID-8238?focusedCommentId=16601936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16601936] -- 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-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors
[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8238: - Attachment: (was: performance-test-results.tar.gz) > [Broker-J] Improve performance of asynchronous publishing of transient > messages into topic exchange having queues bound using non-overlapping > selectors > > > Key: QPID-8238 > URL: https://issues.apache.org/jira/browse/QPID-8238 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.6 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.7 > > > The performance of asynchronous publishing of transient messages into topic > exchange which routes messages into queues bound using non-overlapping > selectors is 2-3 times slower than performance of 0.32 broker. The > performance degradation is observed with AMQP 0.9, though, I suspect that the > AMQP 0-10 protocol could be affected as well. > I was running tests with 10 concurrent producers publishing messages on > separate connections using the same routing key into 10 different queues > (subscribers queues) bound to the exchange using non-overlapping selectors. > My testing showed that performance of 7.0 broker for this particular use case > was 2-3 times worse than performance of 0.32 broker. > The following factors contributed to degradation of performance: > • Copying data from direct memory into heap memory whilst decoding > message headers. Due to this factor, the decoding of message headers is > around twice slower. It seems it contributes around 70% to total performance > degradation > • The message routing algorithm is slower due to need to support a new > feature to route messages into bound exchanges (in addition to queues) using > replacement routing key. > • AMQ short strings caching contributes 5-10% to total performance > degradation. The caching was added to manage heap space more efficiently. > The numbers provided here could be inaccurate due instrumentation overhead > whilst profiling the issue. > Potentially, caching can be turned off but that will not improve performance > much. > On other hand, adding of additional caching of strings to amqp-short-strings > would improve the performance a bit. Whilst evaluating selectors, the fields > used in selector expressions are represented as java strings but they get > converted every time into amqp-short-strings when looking up for message > header values. If 10 queues are bound to the exchange using the same binding > key, the selector expression is evaluated 10 times for the incoming message. > Thus, all selector field names are get converted into amqp-short-strings 10 > times as well. It seems adding caching here can improve the performance. -- 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-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand
[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8245: - Attachment: (was: 0006-QPID-8245-some-code-clean-up.patch) > [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand > -- > > Key: QPID-8245 > URL: https://issues.apache.org/jira/browse/QPID-8245 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > At the moment all field table properties are decoded when decode > functionality is invoked. For use cases when only some of the field table > properties are queried, the decoding functionality can be changed to stop > decoding on getting the requested property. Potentially, such approach can > improve the performance of routing transient messages when destinations are > bound to the routing exchange using selector filters. As filter expression > contains only some properties, the decoding of message headers can be stopped > on getting all fields specified in selector expression. > The idea is illustrated by Rob Godfrey on > [QPID-8238|https://issues.apache.org/jira/browse/QPID-8238?focusedCommentId=16601936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16601936] -- 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-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand
[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8245: - Attachment: (was: 0005-QPID-8245-Remove-methods-getXXX-in-order-to-simplify.patch) > [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand > -- > > Key: QPID-8245 > URL: https://issues.apache.org/jira/browse/QPID-8245 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > Attachments: 0006-QPID-8245-some-code-clean-up.patch, > 0007-QPID-8245-Change-decoding-to-decode-only-value-for-t.patch, > 0008-QPID-8245-Dispose-QpidByteBuffer-on-decoding-FieldTa.patch > > > At the moment all field table properties are decoded when decode > functionality is invoked. For use cases when only some of the field table > properties are queried, the decoding functionality can be changed to stop > decoding on getting the requested property. Potentially, such approach can > improve the performance of routing transient messages when destinations are > bound to the routing exchange using selector filters. As filter expression > contains only some properties, the decoding of message headers can be stopped > on getting all fields specified in selector expression. > The idea is illustrated by Rob Godfrey on > [QPID-8238|https://issues.apache.org/jira/browse/QPID-8238?focusedCommentId=16601936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16601936] -- 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-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand
[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8245: - Attachment: (was: 0003-QPID-8245-Remove-FiledTable-setters-methods-modifyin.patch) > [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand > -- > > Key: QPID-8245 > URL: https://issues.apache.org/jira/browse/QPID-8245 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > Attachments: 0006-QPID-8245-some-code-clean-up.patch, > 0007-QPID-8245-Change-decoding-to-decode-only-value-for-t.patch, > 0008-QPID-8245-Dispose-QpidByteBuffer-on-decoding-FieldTa.patch > > > At the moment all field table properties are decoded when decode > functionality is invoked. For use cases when only some of the field table > properties are queried, the decoding functionality can be changed to stop > decoding on getting the requested property. Potentially, such approach can > improve the performance of routing transient messages when destinations are > bound to the routing exchange using selector filters. As filter expression > contains only some properties, the decoding of message headers can be stopped > on getting all fields specified in selector expression. > The idea is illustrated by Rob Godfrey on > [QPID-8238|https://issues.apache.org/jira/browse/QPID-8238?focusedCommentId=16601936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16601936] -- 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-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand
[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8245: - Attachment: (was: 0004-QPID-8245-Decode-field-table-properties-when-require.patch) > [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand > -- > > Key: QPID-8245 > URL: https://issues.apache.org/jira/browse/QPID-8245 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > Attachments: 0006-QPID-8245-some-code-clean-up.patch, > 0007-QPID-8245-Change-decoding-to-decode-only-value-for-t.patch, > 0008-QPID-8245-Dispose-QpidByteBuffer-on-decoding-FieldTa.patch > > > At the moment all field table properties are decoded when decode > functionality is invoked. For use cases when only some of the field table > properties are queried, the decoding functionality can be changed to stop > decoding on getting the requested property. Potentially, such approach can > improve the performance of routing transient messages when destinations are > bound to the routing exchange using selector filters. As filter expression > contains only some properties, the decoding of message headers can be stopped > on getting all fields specified in selector expression. > The idea is illustrated by Rob Godfrey on > [QPID-8238|https://issues.apache.org/jira/browse/QPID-8238?focusedCommentId=16601936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16601936] -- 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-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors
[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8238: - Attachment: performance-test-results.tar.gz > [Broker-J] Improve performance of asynchronous publishing of transient > messages into topic exchange having queues bound using non-overlapping > selectors > > > Key: QPID-8238 > URL: https://issues.apache.org/jira/browse/QPID-8238 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.6 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.7 > > Attachments: performance-test-results.tar.gz > > > The performance of asynchronous publishing of transient messages into topic > exchange which routes messages into queues bound using non-overlapping > selectors is 2-3 times slower than performance of 0.32 broker. The > performance degradation is observed with AMQP 0.9, though, I suspect that the > AMQP 0-10 protocol could be affected as well. > I was running tests with 10 concurrent producers publishing messages on > separate connections using the same routing key into 10 different queues > (subscribers queues) bound to the exchange using non-overlapping selectors. > My testing showed that performance of 7.0 broker for this particular use case > was 2-3 times worse than performance of 0.32 broker. > The following factors contributed to degradation of performance: > • Copying data from direct memory into heap memory whilst decoding > message headers. Due to this factor, the decoding of message headers is > around twice slower. It seems it contributes around 70% to total performance > degradation > • The message routing algorithm is slower due to need to support a new > feature to route messages into bound exchanges (in addition to queues) using > replacement routing key. > • AMQ short strings caching contributes 5-10% to total performance > degradation. The caching was added to manage heap space more efficiently. > The numbers provided here could be inaccurate due instrumentation overhead > whilst profiling the issue. > Potentially, caching can be turned off but that will not improve performance > much. > On other hand, adding of additional caching of strings to amqp-short-strings > would improve the performance a bit. Whilst evaluating selectors, the fields > used in selector expressions are represented as java strings but they get > converted every time into amqp-short-strings when looking up for message > header values. If 10 queues are bound to the exchange using the same binding > key, the selector expression is evaluated 10 times for the incoming message. > Thus, all selector field names are get converted into amqp-short-strings 10 > times as well. It seems adding caching here can improve the performance. -- 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-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand
[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8245: - Attachment: (was: 0001-QPID-8245-Broker-J-Stop-rellocating-message-headers-.patch) > [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand > -- > > Key: QPID-8245 > URL: https://issues.apache.org/jira/browse/QPID-8245 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > Attachments: > 0003-QPID-8245-Remove-FiledTable-setters-methods-modifyin.patch, > 0004-QPID-8245-Decode-field-table-properties-when-require.patch, > 0005-QPID-8245-Remove-methods-getXXX-in-order-to-simplify.patch, > 0006-QPID-8245-some-code-clean-up.patch, > 0007-QPID-8245-Change-decoding-to-decode-only-value-for-t.patch, > 0008-QPID-8245-Dispose-QpidByteBuffer-on-decoding-FieldTa.patch > > > At the moment all field table properties are decoded when decode > functionality is invoked. For use cases when only some of the field table > properties are queried, the decoding functionality can be changed to stop > decoding on getting the requested property. Potentially, such approach can > improve the performance of routing transient messages when destinations are > bound to the routing exchange using selector filters. As filter expression > contains only some properties, the decoding of message headers can be stopped > on getting all fields specified in selector expression. > The idea is illustrated by Rob Godfrey on > [QPID-8238|https://issues.apache.org/jira/browse/QPID-8238?focusedCommentId=16601936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16601936] -- 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-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand
[jira] [Updated] (QPID-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors
[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8238: - Attachment: (was: 0001-QPID-8238-Use-java.lang.String-for-keys-and-values-i.patch) > [Broker-J] Improve performance of asynchronous publishing of transient > messages into topic exchange having queues bound using non-overlapping > selectors > > > Key: QPID-8238 > URL: https://issues.apache.org/jira/browse/QPID-8238 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.6 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.7 > > > The performance of asynchronous publishing of transient messages into topic > exchange which routes messages into queues bound using non-overlapping > selectors is 2-3 times slower than performance of 0.32 broker. The > performance degradation is observed with AMQP 0.9, though, I suspect that the > AMQP 0-10 protocol could be affected as well. > I was running tests with 10 concurrent producers publishing messages on > separate connections using the same routing key into 10 different queues > (subscribers queues) bound to the exchange using non-overlapping selectors. > My testing showed that performance of 7.0 broker for this particular use case > was 2-3 times worse than performance of 0.32 broker. > The following factors contributed to degradation of performance: > • Copying data from direct memory into heap memory whilst decoding > message headers. Due to this factor, the decoding of message headers is > around twice slower. It seems it contributes around 70% to total performance > degradation > • The message routing algorithm is slower due to need to support a new > feature to route messages into bound exchanges (in addition to queues) using > replacement routing key. > • AMQ short strings caching contributes 5-10% to total performance > degradation. The caching was added to manage heap space more efficiently. > The numbers provided here could be inaccurate due instrumentation overhead > whilst profiling the issue. > Potentially, caching can be turned off but that will not improve performance > much. > On other hand, adding of additional caching of strings to amqp-short-strings > would improve the performance a bit. Whilst evaluating selectors, the fields > used in selector expressions are represented as java strings but they get > converted every time into amqp-short-strings when looking up for message > header values. If 10 queues are bound to the exchange using the same binding > key, the selector expression is evaluated 10 times for the incoming message. > Thus, all selector field names are get converted into amqp-short-strings 10 > times as well. It seems adding caching here can improve the performance. -- 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-7885) [Java Broker] Support Java 9 and 11
[ https://issues.apache.org/jira/browse/QPID-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672873#comment-16672873 ] ASF subversion and git services commented on QPID-7885: --- Commit b1e8865c9f680df3d67dd5307d2972110da4e0a1 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=b1e8865 ] QPID-7885: [Broker-J] Add derby as runtime dependency when running perftests > [Java Broker] Support Java 9 and 11 > --- > > Key: QPID-7885 > URL: https://issues.apache.org/jira/browse/QPID-7885 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Lorenz Quack >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > With the Java 9 on the horizon it is time to get Qpid's Java components ready. > * make sure component compile with JDK9 > * make sure components run with JRE9 > The task of modularization of broker-j is excluded from this JIRA, as it > seems, that many existing modules need to export the same packages which is > not permitted by Jigsaw module system. Some classes need to be moved into > separate packages which requires more substantial refactoring. -- 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
