[jira] [Resolved] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
[ https://issues.apache.org/jira/browse/PROTON-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1338. - Resolution: Fixed > Go: make binding compatible with older C libraries, update `go get` > > > Key: PROTON-1338 > URL: https://issues.apache.org/jira/browse/PROTON-1338 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.14.0, 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > There have been improvements to the Go binding that are not available via > `go get`. Remove the dependency on pn_connection_engine (it is a small amount > of code to rewrite in Go) so that the latest binding can be published and is > binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
[ https://issues.apache.org/jira/browse/PROTON-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627531#comment-15627531 ] ASF subversion and git services commented on PROTON-1338: - Commit d2341683babb52b8143bea9f233fb465c89ba4c3 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d234168 ] PROTON-1338: Go: update package documentation. > Go: make binding compatible with older C libraries, update `go get` > > > Key: PROTON-1338 > URL: https://issues.apache.org/jira/browse/PROTON-1338 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.14.0, 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > There have been improvements to the Go binding that are not available via > `go get`. Remove the dependency on pn_connection_engine (it is a small amount > of code to rewrite in Go) so that the latest binding can be published and is > binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
[ https://issues.apache.org/jira/browse/PROTON-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627527#comment-15627527 ] ASF subversion and git services commented on PROTON-1338: - Commit d2341683babb52b8143bea9f233fb465c89ba4c3 in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d234168 ] PROTON-1338: Go: update package documentation. > Go: make binding compatible with older C libraries, update `go get` > > > Key: PROTON-1338 > URL: https://issues.apache.org/jira/browse/PROTON-1338 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.14.0, 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > There have been improvements to the Go binding that are not available via > `go get`. Remove the dependency on pn_connection_engine (it is a small amount > of code to rewrite in Go) so that the latest binding can be published and is > binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
[ https://issues.apache.org/jira/browse/PROTON-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627528#comment-15627528 ] ASF subversion and git services commented on PROTON-1338: - Commit 500fd8853998023212d72e3ee62032ce01cee5d8 in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=500fd88 ] PROTON-1338: Go: update package documentation. Merge branch 'master' into go1 for more updated package documentation. > Go: make binding compatible with older C libraries, update `go get` > > > Key: PROTON-1338 > URL: https://issues.apache.org/jira/browse/PROTON-1338 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.14.0, 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > There have been improvements to the Go binding that are not available via > `go get`. Remove the dependency on pn_connection_engine (it is a small amount > of code to rewrite in Go) so that the latest binding can be published and is > binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
[ https://issues.apache.org/jira/browse/PROTON-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627511#comment-15627511 ] ASF subversion and git services commented on PROTON-1338: - Commit f405d29a5b0603ab37237bd605367e248a61068b in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f405d29 ] PROTON-1338: Go: update package documentation. Merge branch 'master' into go1 for updated package documentation. > Go: make binding compatible with older C libraries, update `go get` > > > Key: PROTON-1338 > URL: https://issues.apache.org/jira/browse/PROTON-1338 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.14.0, 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > There have been improvements to the Go binding that are not available via > `go get`. Remove the dependency on pn_connection_engine (it is a small amount > of code to rewrite in Go) so that the latest binding can be published and is > binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
[ https://issues.apache.org/jira/browse/PROTON-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627510#comment-15627510 ] ASF subversion and git services commented on PROTON-1338: - Commit b64d0fa630f81d58f69f844856818dd2ba315807 in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b64d0fa ] PROTON-1338: Go: update package documentation. Clarify AMQP 1.0 support to distinguish from other Go AMQP clients supporting draft versions of AMQP. > Go: make binding compatible with older C libraries, update `go get` > > > Key: PROTON-1338 > URL: https://issues.apache.org/jira/browse/PROTON-1338 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.14.0, 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > There have been improvements to the Go binding that are not available via > `go get`. Remove the dependency on pn_connection_engine (it is a small amount > of code to rewrite in Go) so that the latest binding can be published and is > binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
[ https://issues.apache.org/jira/browse/PROTON-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627508#comment-15627508 ] ASF subversion and git services commented on PROTON-1338: - Commit b64d0fa630f81d58f69f844856818dd2ba315807 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b64d0fa ] PROTON-1338: Go: update package documentation. Clarify AMQP 1.0 support to distinguish from other Go AMQP clients supporting draft versions of AMQP. > Go: make binding compatible with older C libraries, update `go get` > > > Key: PROTON-1338 > URL: https://issues.apache.org/jira/browse/PROTON-1338 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.14.0, 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > There have been improvements to the Go binding that are not available via > `go get`. Remove the dependency on pn_connection_engine (it is a small amount > of code to rewrite in Go) so that the latest binding can be published and is > binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
[ https://issues.apache.org/jira/browse/PROTON-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627469#comment-15627469 ] ASF subversion and git services commented on PROTON-1338: - Commit 7b6b8dec76f1345647de90201130f7d8bff903f1 in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7b6b8de ] PROTON-1338: Go: make binding compatible with older C libraries The Go binding is now compatible with all releases since 0.10, tested up to 0.15 Absent C library source or binary incompatible changes, it should remain so. > Go: make binding compatible with older C libraries, update `go get` > > > Key: PROTON-1338 > URL: https://issues.apache.org/jira/browse/PROTON-1338 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.14.0, 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > There have been improvements to the Go binding that are not available via > `go get`. Remove the dependency on pn_connection_engine (it is a small amount > of code to rewrite in Go) so that the latest binding can be published and is > binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1332) go: electron client leaking links/sessions in long lived connection
[ https://issues.apache.org/jira/browse/PROTON-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627464#comment-15627464 ] ASF subversion and git services commented on PROTON-1332: - Commit f8c4c279126f2143c6f9e219cd0e1b6c27b6b7f0 in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f8c4c27 ] PROTON-1332: go: electron client leaking links/sessions Was not calling proton.Link/Session.Free() so links/sessions were never freed till the connection was closed. > go: electron client leaking links/sessions in long lived connection > --- > > Key: PROTON-1332 > URL: https://issues.apache.org/jira/browse/PROTON-1332 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Affects Versions: 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > The electron library is not calling pn_session/link_free when a session/link > is closed. This means that sessions/links are never fully deleted until a > connection is closed, so creating/deleting links/session on a long-lived > connection leaks memory. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1337) [proton-j] Add methods and Sender and Receiver that allow for alternate buffer types
[ https://issues.apache.org/jira/browse/PROTON-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627467#comment-15627467 ] ASF subversion and git services commented on PROTON-1337: - Commit acf1f6eb182a62ce047270c0c6483bcd0b2eb083 in qpid-proton's branch refs/heads/go1 from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=acf1f6e ] PROTON-1337 Add alternate send and recv methods that use generic buffers Add support for clients that use other buffering types to interact with the Sender and Receiver using a ReadableBuffer and WritableBuffer abstraction. > [proton-j] Add methods and Sender and Receiver that allow for alternate > buffer types > > > Key: PROTON-1337 > URL: https://issues.apache.org/jira/browse/PROTON-1337 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: 0.15.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.16.0 > > > The current send and recv method in Sender and Receiver (as well as in > DeliveryImpl) operate on byte array types. Depending on the application the > code might actually be using some other byte buffering scheme such as > ByteBuffer etc. We can easily provide additional methods that operate on a > generic ReadableBuffer and WritableBuffer type that we define so that these > applications can operate more efficiently. > We already define WritableBuffer, the ReadableBuffer would like quite the > same. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1337) [proton-j] Add methods and Sender and Receiver that allow for alternate buffer types
[ https://issues.apache.org/jira/browse/PROTON-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627468#comment-15627468 ] ASF subversion and git services commented on PROTON-1337: - Commit 3661f90f79d24d8dee5649f4302b5a1a486a47ec in qpid-proton's branch refs/heads/go1 from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=3661f90 ] PROTON-1337 Add missing file Missed on last commit. > [proton-j] Add methods and Sender and Receiver that allow for alternate > buffer types > > > Key: PROTON-1337 > URL: https://issues.apache.org/jira/browse/PROTON-1337 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Affects Versions: 0.15.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.16.0 > > > The current send and recv method in Sender and Receiver (as well as in > DeliveryImpl) operate on byte array types. Depending on the application the > code might actually be using some other byte buffering scheme such as > ByteBuffer etc. We can easily provide additional methods that operate on a > generic ReadableBuffer and WritableBuffer type that we define so that these > applications can operate more efficiently. > We already define WritableBuffer, the ReadableBuffer would like quite the > same. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
[ https://issues.apache.org/jira/browse/PROTON-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627470#comment-15627470 ] ASF subversion and git services commented on PROTON-1338: - Commit 287eeacafbfc166529108b9f6d1bf8e839c9f9be in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=287eeac ] PROTON-1338: Go: update `go get` Merge branch 'master' into go1 to update the published `go get` version of the Go packages. The new packages are tested with C library versions 0.10 - 0.15.0 > Go: make binding compatible with older C libraries, update `go get` > > > Key: PROTON-1338 > URL: https://issues.apache.org/jira/browse/PROTON-1338 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.14.0, 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > There have been improvements to the Go binding that are not available via > `go get`. Remove the dependency on pn_connection_engine (it is a small amount > of code to rewrite in Go) so that the latest binding can be published and is > binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1333) CMake error if no C++ compiler avaliable.
[
https://issues.apache.org/jira/browse/PROTON-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627465#comment-15627465
]
ASF subversion and git services commented on PROTON-1333:
-
Commit f83c70cc5b929161ead83567a048d3f6cb9a0dd4 in qpid-proton's branch
refs/heads/go1 from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f83c70c ]
PROTON-1333: CMake error if no C++ compiler avaliable
Change if() statement to use variable name not quoted ${variable}.
> CMake error if no C++ compiler avaliable.
> -
>
> Key: PROTON-1333
> URL: https://issues.apache.org/jira/browse/PROTON-1333
> Project: Qpid Proton
> Issue Type: Bug
> Components: build
>Affects Versions: 0.15.0
>Reporter: Alan Conway
>Assignee: Alan Conway
> Fix For: 0.16.0
>
>
> If no C++ compiler is available this cmake error:
> CMake Error at proton-c/CMakeLists.txt:113 (IF):
> if given arguments:
> "STREQUAL" "SunPro"
> Unknown arguments specified
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1331) go: electron.Container.Dial returning (nil, nil)
[ https://issues.apache.org/jira/browse/PROTON-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627463#comment-15627463 ] ASF subversion and git services commented on PROTON-1331: - Commit a17d30a2de5c68fd3ffa4d34da6cefa2e727bbdb in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=a17d30a ] PROTON-1331: go: electron.Container.Dial returning (nil, nil) Scope error, creating new "err" variable instead of setting return variable. > go: electron.Container.Dial returning (nil, nil) > > > Key: PROTON-1331 > URL: https://issues.apache.org/jira/browse/PROTON-1331 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Affects Versions: 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > Error in electron.container.Dial and Accept return (nil, nil) if the > net.Dial/Accept call returns an error, instead of returning the error. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1255) connection_engine support for built-in proton SSL/SASL
[ https://issues.apache.org/jira/browse/PROTON-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627466#comment-15627466 ] ASF subversion and git services commented on PROTON-1255: - Commit 507c9356692858a81916a4a8802fbc6b2302bc5f in qpid-proton's branch refs/heads/go1 from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=507c935 ] PROTON-1255: Remove pn_connection_engine_start Bind the connection automatically in pn_connection_engine_dispatch after the user has processed the PN_CONNECTION_INIT event. This removes the need to manually call start and allows user handlers to set security settings in their handler on PN_CONNECTION_INIT, before the bind. > connection_engine support for built-in proton SSL/SASL > -- > > Key: PROTON-1255 > URL: https://issues.apache.org/jira/browse/PROTON-1255 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding, go-binding, proton-c >Affects Versions: 0.12.2 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Critical > Fix For: 0.15.0 > > > Make sure proton's built-in SSL and SASL work fully with the connection > engine for all bindings that have one (C, C++, Go) > The connection_engine also allows a secure connection to be established > externally. Check that we have sufficient hooks to pass external security > principal info to the handler via connection and transport properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
[ https://issues.apache.org/jira/browse/PROTON-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627460#comment-15627460 ] ASF subversion and git services commented on PROTON-1338: - Commit 7b6b8dec76f1345647de90201130f7d8bff903f1 in qpid-proton's branch refs/heads/master from [~aconway] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7b6b8de ] PROTON-1338: Go: make binding compatible with older C libraries The Go binding is now compatible with all releases since 0.10, tested up to 0.15 Absent C library source or binary incompatible changes, it should remain so. > Go: make binding compatible with older C libraries, update `go get` > > > Key: PROTON-1338 > URL: https://issues.apache.org/jira/browse/PROTON-1338 > Project: Qpid Proton > Issue Type: Improvement > Components: go-binding >Affects Versions: 0.14.0, 0.15.0 >Reporter: Alan Conway >Assignee: Alan Conway > Fix For: 0.16.0 > > > There have been improvements to the Go binding that are not available via > `go get`. Remove the dependency on pn_connection_engine (it is a small amount > of code to rewrite in Go) so that the latest binding can be published and is > binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1338) Go: make binding compatible with older C libraries, update `go get`
Alan Conway created PROTON-1338: --- Summary: Go: make binding compatible with older C libraries, update `go get` Key: PROTON-1338 URL: https://issues.apache.org/jira/browse/PROTON-1338 Project: Qpid Proton Issue Type: Improvement Components: go-binding Affects Versions: 0.15.0, 0.14.0 Reporter: Alan Conway Assignee: Alan Conway Fix For: 0.16.0 There have been improvements to the Go binding that are not available via `go get`. Remove the dependency on pn_connection_engine (it is a small amount of code to rewrite in Go) so that the latest binding can be published and is binary compatible with older proton C libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7486) [Java Broker] Refactor broker startup code, remove BrokerOptions
[ https://issues.apache.org/jira/browse/QPID-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627169#comment-15627169 ] ASF subversion and git services commented on QPID-7486: --- Commit 1767592 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1767592 ] QPID-7486 : Refactor broker startup code > [Java Broker] Refactor broker startup code, remove BrokerOptions > > > Key: QPID-7486 > URL: https://issues.apache.org/jira/browse/QPID-7486 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: qpid-java-6.2 > > > The code relating to the initial construction of the broker has evolved over > time leaving functionality spread across a number of different classes with > no clear division of responsibilities. > Refactor so that Main in the broker module has responsibility for parsing of > command line arguments and conversion into SystemConfig attributes, as well > as providing the hooks into the desired logging provider. > SystemLauncher (renamed from Broker) provides a thin layer of state > management (shutdown/startup) on top of the SystemConfig configured object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7486) [Java Broker] Refactor broker startup code, remove BrokerOptions
Rob Godfrey created QPID-7486: - Summary: [Java Broker] Refactor broker startup code, remove BrokerOptions Key: QPID-7486 URL: https://issues.apache.org/jira/browse/QPID-7486 Project: Qpid Issue Type: Improvement Reporter: Rob Godfrey The code relating to the initial construction of the broker has evolved over time leaving functionality spread across a number of different classes with no clear division of responsibilities. Refactor so that Main in the broker module has responsibility for parsing of command line arguments and conversion into SystemConfig attributes, as well as providing the hooks into the desired logging provider. SystemLauncher (renamed from Broker) provides a thin layer of state management (shutdown/startup) on top of the SystemConfig configured object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7486) [Java Broker] Refactor broker startup code, remove BrokerOptions
[ https://issues.apache.org/jira/browse/QPID-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-7486: -- Component/s: Java Broker > [Java Broker] Refactor broker startup code, remove BrokerOptions > > > Key: QPID-7486 > URL: https://issues.apache.org/jira/browse/QPID-7486 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey > Fix For: qpid-java-6.2 > > > The code relating to the initial construction of the broker has evolved over > time leaving functionality spread across a number of different classes with > no clear division of responsibilities. > Refactor so that Main in the broker module has responsibility for parsing of > command line arguments and conversion into SystemConfig attributes, as well > as providing the hooks into the desired logging provider. > SystemLauncher (renamed from Broker) provides a thin layer of state > management (shutdown/startup) on top of the SystemConfig configured object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7486) [Java Broker] Refactor broker startup code, remove BrokerOptions
[ https://issues.apache.org/jira/browse/QPID-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-7486: -- Fix Version/s: qpid-java-6.2 > [Java Broker] Refactor broker startup code, remove BrokerOptions > > > Key: QPID-7486 > URL: https://issues.apache.org/jira/browse/QPID-7486 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey > Fix For: qpid-java-6.2 > > > The code relating to the initial construction of the broker has evolved over > time leaving functionality spread across a number of different classes with > no clear division of responsibilities. > Refactor so that Main in the broker module has responsibility for parsing of > command line arguments and conversion into SystemConfig attributes, as well > as providing the hooks into the desired logging provider. > SystemLauncher (renamed from Broker) provides a thin layer of state > management (shutdown/startup) on top of the SystemConfig configured object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-7486) [Java Broker] Refactor broker startup code, remove BrokerOptions
[ https://issues.apache.org/jira/browse/QPID-7486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-7486: - Assignee: Rob Godfrey > [Java Broker] Refactor broker startup code, remove BrokerOptions > > > Key: QPID-7486 > URL: https://issues.apache.org/jira/browse/QPID-7486 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: qpid-java-6.2 > > > The code relating to the initial construction of the broker has evolved over > time leaving functionality spread across a number of different classes with > no clear division of responsibilities. > Refactor so that Main in the broker module has responsibility for parsing of > command line arguments and conversion into SystemConfig attributes, as well > as providing the hooks into the desired logging provider. > SystemLauncher (renamed from Broker) provides a thin layer of state > management (shutdown/startup) on top of the SystemConfig configured object. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #108: Fix memory leaks
Github user dskarbek commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/108#discussion_r86036444
--- Diff: src/router_core/router_core.c ---
@@ -106,29 +106,31 @@ void qdr_core_free(qdr_core_t *core)
sys_mutex_free(core->work_lock);
sys_mutex_free(core->id_lock);
qd_timer_free(core->work_timer);
+
for (int i = 0; i <= QD_TREATMENT_LINK_BALANCED; ++i) {
if (core->forwarders[i]) {
free(core->forwarders[i]);
}
}
-if (core->addr_hash) {
-qd_hash_free(core->addr_hash);
-}
-if (core->conn_id_hash) {
-qd_hash_free(core->conn_id_hash);
-}
-if (core->query_lock) {
-sys_mutex_free(core->query_lock);
-}
-if (core->routers_by_mask_bit) {
-free(core->routers_by_mask_bit);
-}
-if (core->control_links_by_mask_bit) {
-free(core->control_links_by_mask_bit);
+
+qdr_address_t *addr = 0;
+while ( (addr = DEQ_HEAD(core->addrs)) ) {
+qdr_core_remove_address(core, addr);
}
-if (core->data_links_by_mask_bit) {
-free(core->data_links_by_mask_bit);
+qdr_address_config_t *addr_config = 0;
+while ( (addr_config = DEQ_HEAD(core->addr_config))) {
+free_qdr_address_config_t(addr_config);
--- End diff --
this is a bug. I've got an update to the commit that fixes this which I
haven't pushed yet.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7485) [Java Broker] Make the path attribute immutable on file based authentication providers
[ https://issues.apache.org/jira/browse/QPID-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626053#comment-15626053 ] ASF subversion and git services commented on QPID-7485: --- Commit 1767524 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1767524 ] QPID-7485: Revert redundant check on changing of path attribute in file based authentication providers > [Java Broker] Make the path attribute immutable on file based authentication > providers > -- > > Key: QPID-7485 > URL: https://issues.apache.org/jira/browse/QPID-7485 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.2 >Reporter: Alex Rudyy >Assignee: Alex Rudyy > > Whilst editing password based authentication provider (plain or base64) and > setting path to a non existing file, the operation fails with 422 but the > configuration is updated and sub-sequent user modification operation (add > user/delete user/etc) fails as password file does not exists -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7485) [Java Broker] Make the path attribute immutable on file based authentication providers
[ https://issues.apache.org/jira/browse/QPID-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15626052#comment-15626052 ] ASF subversion and git services commented on QPID-7485: --- Commit 1767523 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1767523 ] QPID-7485: [Java Broker] Make the path attribute immutable on file based authentication providers > [Java Broker] Make the path attribute immutable on file based authentication > providers > -- > > Key: QPID-7485 > URL: https://issues.apache.org/jira/browse/QPID-7485 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.2 >Reporter: Alex Rudyy >Assignee: Alex Rudyy > > Whilst editing password based authentication provider (plain or base64) and > setting path to a non existing file, the operation fails with 422 but the > configuration is updated and sub-sequent user modification operation (add > user/delete user/etc) fails as password file does not exists -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7469) [Java Broker] Improve VirtualHost#publishMessage
[ https://issues.apache.org/jira/browse/QPID-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625831#comment-15625831 ] ASF subversion and git services commented on QPID-7469: --- Commit 1767514 from [~godfrer] in branch 'java/trunk' [ https://svn.apache.org/r1767514 ] QPID-7469 : fix regex > [Java Broker] Improve VirtualHost#publishMessage > > > Key: QPID-7469 > URL: https://issues.apache.org/jira/browse/QPID-7469 > Project: Qpid > Issue Type: Task > Components: Java Broker >Affects Versions: qpid-java-6.1 >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1, qpid-java-6.2 > > > * When the POST request to VirtualHost#publishMessage does not contain a body > there is a ServerError > * When the mimeType is set the message content is always interpreted as > base64. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7485) [Java Broker] Make the path attribute immutable on file based authentication providers
[ https://issues.apache.org/jira/browse/QPID-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7485: - Summary: [Java Broker] Make the path attribute immutable on file based authentication providers (was: [Java Broker] File based authentication providers should not allow changing of password file to non-existing file) > [Java Broker] Make the path attribute immutable on file based authentication > providers > -- > > Key: QPID-7485 > URL: https://issues.apache.org/jira/browse/QPID-7485 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.2 >Reporter: Alex Rudyy >Assignee: Alex Rudyy > > Whilst editing password based authentication provider (plain or base64) and > setting path to a non existing file, the operation fails with 422 but the > configuration is updated and sub-sequent user modification operation (add > user/delete user/etc) fails as password file does not exists -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7470) [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings
[ https://issues.apache.org/jira/browse/QPID-7470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625719#comment-15625719 ] Lorenz Quack commented on QPID-7470: looks good to me. > [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings > --- > > Key: QPID-7470 > URL: https://issues.apache.org/jira/browse/QPID-7470 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1, qpid-java-6.2, quid-java-6.0.6 > > > javax.xml.bind.DatatypeConverterImpl#parseBase64Binary has shortcomings that > we should address. It does not (as the java docs suggest) throw > IllegalArgumentException when the argument contains characters outside the > valid base64 value space. Instead it will skip invalid characters in the > (7-bit) ASCII range and throw a ArrayIndexOutOfBoundsException on non-ASCII > characters. > We should guard against these cases. Maybe by wrapping > javax.xml.bind.DatatypeConverterImpl in our own class and doing input > validation there. > See also (https://bugs.openjdk.java.net/browse/JDK-8168456) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7470) [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings
[ https://issues.apache.org/jira/browse/QPID-7470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-7470. Resolution: Fixed > [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings > --- > > Key: QPID-7470 > URL: https://issues.apache.org/jira/browse/QPID-7470 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1, qpid-java-6.2, quid-java-6.0.6 > > > javax.xml.bind.DatatypeConverterImpl#parseBase64Binary has shortcomings that > we should address. It does not (as the java docs suggest) throw > IllegalArgumentException when the argument contains characters outside the > valid base64 value space. Instead it will skip invalid characters in the > (7-bit) ASCII range and throw a ArrayIndexOutOfBoundsException on non-ASCII > characters. > We should guard against these cases. Maybe by wrapping > javax.xml.bind.DatatypeConverterImpl in our own class and doing input > validation there. > See also (https://bugs.openjdk.java.net/browse/JDK-8168456) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7469) [Java Broker] Improve VirtualHost#publishMessage
[
https://issues.apache.org/jira/browse/QPID-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625684#comment-15625684
]
Lorenz Quack commented on QPID-7469:
* The regexp in {{AbstractVirtualHost#publishMessage:746}} is missing the a
{{.*}} at the end.
* Do we want to add tests for this?
The rest looks good to me.
> [Java Broker] Improve VirtualHost#publishMessage
>
>
> Key: QPID-7469
> URL: https://issues.apache.org/jira/browse/QPID-7469
> Project: Qpid
> Issue Type: Task
> Components: Java Broker
>Affects Versions: qpid-java-6.1
>Reporter: Lorenz Quack
>Assignee: Keith Wall
> Fix For: qpid-java-6.1, qpid-java-6.2
>
>
> * When the POST request to VirtualHost#publishMessage does not contain a body
> there is a ServerError
> * When the mimeType is set the message content is always interpreted as
> base64.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-7471) [Java Broker] MessageConverter should respect mimeType
[ https://issues.apache.org/jira/browse/QPID-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-7471. Resolution: Fixed > [Java Broker] MessageConverter should respect mimeType > -- > > Key: QPID-7471 > URL: https://issues.apache.org/jira/browse/QPID-7471 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1, qpid-java-6.2 > > > When converting from ManageableMessage to InternalMessage the mimeType gets > lost -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7471) [Java Broker] MessageConverter should respect mimeType
[ https://issues.apache.org/jira/browse/QPID-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625604#comment-15625604 ] Lorenz Quack commented on QPID-7471: looks okay to me. > [Java Broker] MessageConverter should respect mimeType > -- > > Key: QPID-7471 > URL: https://issues.apache.org/jira/browse/QPID-7471 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1, qpid-java-6.2 > > > When converting from ManageableMessage to InternalMessage the mimeType gets > lost -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7471) [Java Broker] MessageConverter should respect mimeType
[ https://issues.apache.org/jira/browse/QPID-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7471: --- Fix Version/s: qpid-java-6.1 > [Java Broker] MessageConverter should respect mimeType > -- > > Key: QPID-7471 > URL: https://issues.apache.org/jira/browse/QPID-7471 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1, qpid-java-6.2 > > > When converting from ManageableMessage to InternalMessage the mimeType gets > lost -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-324) Improve initial layout of topology node
[ https://issues.apache.org/jira/browse/DISPATCH-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-324. --- Resolution: Fixed Fix Version/s: 0.8.0 > Improve initial layout of topology node > --- > > Key: DISPATCH-324 > URL: https://issues.apache.org/jira/browse/DISPATCH-324 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.7.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Minor > Fix For: 0.8.0 > > > When a new network of routers is encountered, the nodes on the topology page > are initially placed on a line. The d3 library's force graph then moves them > into n configuration (which can then be adjusted by the user). > That initial layout is a bit messy when there are more than 4 nodes. > It would be cleaner to initially layout the nodes in a circle. The d3 library > could then discover a more pleasing layout. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-324) Improve initial layout of topology node
[ https://issues.apache.org/jira/browse/DISPATCH-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625549#comment-15625549 ] ASF subversion and git services commented on DISPATCH-324: -- Commit 17b0f10ae7c7f4de250741fd6f0cb3fc2d3c286d in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=17b0f10 ] DISPATCH-324 Layout new nodes in sin wave and give them more time to settle > Improve initial layout of topology node > --- > > Key: DISPATCH-324 > URL: https://issues.apache.org/jira/browse/DISPATCH-324 > Project: Qpid Dispatch > Issue Type: Bug > Components: Console >Affects Versions: 0.7.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Minor > > When a new network of routers is encountered, the nodes on the topology page > are initially placed on a line. The d3 library's force graph then moves them > into n configuration (which can then be adjusted by the user). > That initial layout is a bit messy when there are more than 4 nodes. > It would be cleaner to initially layout the nodes in a circle. The d3 library > could then discover a more pleasing layout. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (DISPATCH-549) Doc book needs more detailed introduction of system concepts
[ https://issues.apache.org/jira/browse/DISPATCH-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke closed DISPATCH-549. Resolution: Fixed Fix Version/s: 0.8.0 Fixed at commit 4bd5e89 > Doc book needs more detailed introduction of system concepts > > > Key: DISPATCH-549 > URL: https://issues.apache.org/jira/browse/DISPATCH-549 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Chuck Rolke >Assignee: Chuck Rolke > Fix For: 0.8.0 > > > The docs need a 'theory of operation' chapter to have more detail than the > overview and to introduce system concepts before they are used in > configuration examples. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-555) Policy needs to be restructured as a plugin
Chuck Rolke created DISPATCH-555: Summary: Policy needs to be restructured as a plugin Key: DISPATCH-555 URL: https://issues.apache.org/jira/browse/DISPATCH-555 Project: Qpid Dispatch Issue Type: Bug Components: Policy Engine Affects Versions: 0.7.0 Reporter: Chuck Rolke The policy engine is coded in line as the sole policy provider. With small reorganization it could be a plugin and share duties with other providers. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7470) [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings
[ https://issues.apache.org/jira/browse/QPID-7470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625359#comment-15625359 ] Keith Wall commented on QPID-7470: -- Merged to the 6.1.x and 6.0.x branches. The latter required manual conflict resolution. > [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings > --- > > Key: QPID-7470 > URL: https://issues.apache.org/jira/browse/QPID-7470 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Lorenz Quack > Fix For: qpid-java-6.1, qpid-java-6.2, quid-java-6.0.6 > > > javax.xml.bind.DatatypeConverterImpl#parseBase64Binary has shortcomings that > we should address. It does not (as the java docs suggest) throw > IllegalArgumentException when the argument contains characters outside the > valid base64 value space. Instead it will skip invalid characters in the > (7-bit) ASCII range and throw a ArrayIndexOutOfBoundsException on non-ASCII > characters. > We should guard against these cases. Maybe by wrapping > javax.xml.bind.DatatypeConverterImpl in our own class and doing input > validation there. > See also (https://bugs.openjdk.java.net/browse/JDK-8168456) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-7470) [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings
[ https://issues.apache.org/jira/browse/QPID-7470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7470: Assignee: Keith Wall > [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings > --- > > Key: QPID-7470 > URL: https://issues.apache.org/jira/browse/QPID-7470 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1, qpid-java-6.2, quid-java-6.0.6 > > > javax.xml.bind.DatatypeConverterImpl#parseBase64Binary has shortcomings that > we should address. It does not (as the java docs suggest) throw > IllegalArgumentException when the argument contains characters outside the > valid base64 value space. Instead it will skip invalid characters in the > (7-bit) ASCII range and throw a ArrayIndexOutOfBoundsException on non-ASCII > characters. > We should guard against these cases. Maybe by wrapping > javax.xml.bind.DatatypeConverterImpl in our own class and doing input > validation there. > See also (https://bugs.openjdk.java.net/browse/JDK-8168456) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7470) [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings
[ https://issues.apache.org/jira/browse/QPID-7470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7470: - Status: Reviewable (was: In Progress) > [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings > --- > > Key: QPID-7470 > URL: https://issues.apache.org/jira/browse/QPID-7470 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Keith Wall > Fix For: qpid-java-6.1, qpid-java-6.2, quid-java-6.0.6 > > > javax.xml.bind.DatatypeConverterImpl#parseBase64Binary has shortcomings that > we should address. It does not (as the java docs suggest) throw > IllegalArgumentException when the argument contains characters outside the > valid base64 value space. Instead it will skip invalid characters in the > (7-bit) ASCII range and throw a ArrayIndexOutOfBoundsException on non-ASCII > characters. > We should guard against these cases. Maybe by wrapping > javax.xml.bind.DatatypeConverterImpl in our own class and doing input > validation there. > See also (https://bugs.openjdk.java.net/browse/JDK-8168456) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7470) [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings
[ https://issues.apache.org/jira/browse/QPID-7470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625357#comment-15625357 ] ASF subversion and git services commented on QPID-7470: --- Commit 1767490 from [~k-wall] in branch 'java/branches/6.0.x' [ https://svn.apache.org/r1767490 ] QPID-7470 : Wrap use of DatatypeConverter.parseBase64Binary to validate that only valid characters exist within the string Merged from branch 6.1.x with command: svn merge -c 1767487 ^/qpid/java/branches/6.1.x > [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings > --- > > Key: QPID-7470 > URL: https://issues.apache.org/jira/browse/QPID-7470 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Lorenz Quack > Fix For: qpid-java-6.1, qpid-java-6.2, quid-java-6.0.6 > > > javax.xml.bind.DatatypeConverterImpl#parseBase64Binary has shortcomings that > we should address. It does not (as the java docs suggest) throw > IllegalArgumentException when the argument contains characters outside the > valid base64 value space. Instead it will skip invalid characters in the > (7-bit) ASCII range and throw a ArrayIndexOutOfBoundsException on non-ASCII > characters. > We should guard against these cases. Maybe by wrapping > javax.xml.bind.DatatypeConverterImpl in our own class and doing input > validation there. > See also (https://bugs.openjdk.java.net/browse/JDK-8168456) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7470) [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings
[ https://issues.apache.org/jira/browse/QPID-7470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625279#comment-15625279 ] ASF subversion and git services commented on QPID-7470: --- Commit 1767487 from [~k-wall] in branch 'java/branches/6.1.x' [ https://svn.apache.org/r1767487 ] QPID-7470 : Wrap use of DatatypeConverter.parseBase64Binary to validate that only valid characters exist within the string Merged from trunk with command: svn merge -c 1766547 ^/qpid/java/trunk svn merge -c 1766553 ^/qpid/java/trunk > [Java Broker] Address javax.xml.bind.DatatypeConverter shortcomings > --- > > Key: QPID-7470 > URL: https://issues.apache.org/jira/browse/QPID-7470 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Lorenz Quack > Fix For: qpid-java-6.1, qpid-java-6.2, quid-java-6.0.6 > > > javax.xml.bind.DatatypeConverterImpl#parseBase64Binary has shortcomings that > we should address. It does not (as the java docs suggest) throw > IllegalArgumentException when the argument contains characters outside the > valid base64 value space. Instead it will skip invalid characters in the > (7-bit) ASCII range and throw a ArrayIndexOutOfBoundsException on non-ASCII > characters. > We should guard against these cases. Maybe by wrapping > javax.xml.bind.DatatypeConverterImpl in our own class and doing input > validation there. > See also (https://bugs.openjdk.java.net/browse/JDK-8168456) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7474) [Java Broker] Guard against NPE in StatisticsReportingTask
[ https://issues.apache.org/jira/browse/QPID-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625273#comment-15625273 ] ASF subversion and git services commented on QPID-7474: --- Commit 1767486 from oru...@apache.org in branch 'java/branches/6.0.x' [ https://svn.apache.org/r1767486 ] QPID-7474 : Only virtual hosts capable of processing messages should implement StatisticsGatherer merged from trunk with: svn merge -c 1766796 ^/qpid/java/trunk > [Java Broker] Guard against NPE in StatisticsReportingTask > -- > > Key: QPID-7474 > URL: https://issues.apache.org/jira/browse/QPID-7474 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0, qpid-java-6.0.4, qpid-java-6.1 >Reporter: Lorenz Quack > Fix For: qpid-java-6.1 > > > Currently when statistics gathering is enabled on the broker it iterates over > all virtual hosts and accesses their EventLogger. Some VirtualHosts (e.g., > BDBHAReplicaVirtualHost or RedirectingVirtualHost) do not have an EventLogger > and will return null causing a NullPointerException in the > StatisticsReportingTask that will be logged with a stacktrace and prevents > other VHs from reporting their statistics. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7483) [Java Broker, WMC] Address minor UI issues
[ https://issues.apache.org/jira/browse/QPID-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7483: - Description: During testing the following minor UI issues were discovered: In no particular order (numbering just for easier referencing): # Logging in occasionally fails with a 417 error response especially when the browsers developer tools are open. This is probably due to a timeout in SaslServlet (default 3000 ms). # --In view and edit of Broker: "Statistics reporting period enabled" shoud actually be "Statistics reporting reset enabled"-- FIXED QPID-7481 # The memory log viewer grid in "Auto Refresh" mode has the "jumping page" problem # The BrokerLogbackSocket seems to have a default port (6000) but it needs to be entered regardless. # When using BrokerLogbackSocket and nothing is connected to it it waits 100ms for each log event to time out. When using DEBUG this brings the broker to a crawl (e.g., broker startup ~ 4 minutes). I could imagine this also being a problem when logging over a network. Could this also be a problem for other loggers (e.g. Syslog?) # -- When changing "Number of connection threads" to 1 on a VirtualHost the following error is reported: "422 - Number of Selectors 8 on VirtualHost bdb_bdb must be greater than the connection pool size 1. Please correct the problem and retry your operation." which does not make sense. I think it should say the connection pool size must be greater than the selectors not the other way around. -- FIXED QPID-7480 # Add Port dialogue does not have a scroll bar in case it does not completely fit onto the screen. If the dialogue box resizes (e.g., by closing the Developer Tools pane in IE) only the original part of the dialogue box has a solid background. the newly exposed part is transparent. # --Creating a Base64MD5PasswordFile AuthProvider pointing to a non existing file creates it. however editing and point it to a non existing file fails with 422 but the config seems to have been updated regardless with subsequent changes (e.g. adding user) failing.-- Subject of QPID-7485 # add dialogue for SimpleLDAP AuthenticationProvider is wonky # deletion of TrustStore displays the trust store name in the confirmation dialogue as 'undefined'. # In the UI for FileGroupProvider the path field is editable but on the broker it is not resulting in 422 errors. Either we should allow editing on the broker or disallow it in the UI. # add dialogue of AclFile type is wonky # RuleBased ACL has no useful UI # If the add Queue dialogue has a scrollbar the lower part (the one you have to scroll to) is transparent. This applies to all addQueue dialogues. # dialogue layout gets messed up when dialogue has to display a scrollbar # clicking on any of a widgets "menu icons" (i.e., collapse pane, edit, goto, or close) will also trigger a drag. # dashboard browser has empty row where the query browser displays the query type. # the text elements in question/notification/warning-yellow.svg are not centred correctly in IE. In chrome and FF only the warning-yellow.svg seems of centre. was: During testing the following minor UI issues were discovered: In no particular order (numbering just for easier referencing): # Logging in occasionally fails with a 417 error response especially when the browsers developer tools are open. This is probably due to a timeout in SaslServlet (default 3000 ms). # --In view and edit of Broker: "Statistics reporting period enabled" shoud actually be "Statistics reporting reset enabled"-- FIXED QPID-7481 # The memory log viewer grid in "Auto Refresh" mode has the "jumping page" problem # The BrokerLogbackSocket seems to have a default port (6000) but it needs to be entered regardless. # When using BrokerLogbackSocket and nothing is connected to it it waits 100ms for each log event to time out. When using DEBUG this brings the broker to a crawl (e.g., broker startup ~ 4 minutes). I could imagine this also being a problem when logging over a network. Could this also be a problem for other loggers (e.g. Syslog?) # -- When changing "Number of connection threads" to 1 on a VirtualHost the following error is reported: "422 - Number of Selectors 8 on VirtualHost bdb_bdb must be greater than the connection pool size 1. Please correct the problem and retry your operation." which does not make sense. I think it should say the connection pool size must be greater than the selectors not the other way around. -- FIXED QPID-7480 # Add Port dialogue does not have a scroll bar in case it does not completely fit onto the screen. If the dialogue box resizes (e.g., by closing the Developer Tools pane in IE) only the original part of the dialogue box has a solid background. the newly exposed part is transparent. # --Creating a Base64MD5PasswordFile AuthProvider pointing to a non existing file creates it. however editing and point it to a
[jira] [Commented] (QPID-7485) [Java Broker] File based authentication providers should not allow changing of password file to non-existing file
[ https://issues.apache.org/jira/browse/QPID-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625229#comment-15625229 ] Keith Wall commented on QPID-7485: -- We agreed that the path should be marked immutable, and the corresponding change should be made to the UI > [Java Broker] File based authentication providers should not allow changing > of password file to non-existing file > - > > Key: QPID-7485 > URL: https://issues.apache.org/jira/browse/QPID-7485 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.2 >Reporter: Alex Rudyy >Assignee: Alex Rudyy > > Whilst editing password based authentication provider (plain or base64) and > setting path to a non existing file, the operation fails with 422 but the > configuration is updated and sub-sequent user modification operation (add > user/delete user/etc) fails as password file does not exists -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7485) [Java Broker] File based authentication providers should not allow changing of password file to non-existing file
[ https://issues.apache.org/jira/browse/QPID-7485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7485: - Status: Open (was: Reviewable) > [Java Broker] File based authentication providers should not allow changing > of password file to non-existing file > - > > Key: QPID-7485 > URL: https://issues.apache.org/jira/browse/QPID-7485 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, > qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, > qpid-java-6.2 >Reporter: Alex Rudyy >Assignee: Alex Rudyy > > Whilst editing password based authentication provider (plain or base64) and > setting path to a non existing file, the operation fails with 422 but the > configuration is updated and sub-sequent user modification operation (add > user/delete user/etc) fails as password file does not exists -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7483) [Java Broker, WMC] Address minor UI issues
[ https://issues.apache.org/jira/browse/QPID-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7483: - Description: During testing the following minor UI issues were discovered: In no particular order (numbering just for easier referencing): # Logging in occasionally fails with a 417 error response especially when the browsers developer tools are open. This is probably due to a timeout in SaslServlet (default 3000 ms). # --In view and edit of Broker: "Statistics reporting period enabled" shoud actually be "Statistics reporting reset enabled"-- FIXED QPID-7481 # The memory log viewer grid in "Auto Refresh" mode has the "jumping page" problem # The BrokerLogbackSocket seems to have a default port (6000) but it needs to be entered regardless. # When using BrokerLogbackSocket and nothing is connected to it it waits 100ms for each log event to time out. When using DEBUG this brings the broker to a crawl (e.g., broker startup ~ 4 minutes). I could imagine this also being a problem when logging over a network. Could this also be a problem for other loggers (e.g. Syslog?) # -- When changing "Number of connection threads" to 1 on a VirtualHost the following error is reported: "422 - Number of Selectors 8 on VirtualHost bdb_bdb must be greater than the connection pool size 1. Please correct the problem and retry your operation." which does not make sense. I think it should say the connection pool size must be greater than the selectors not the other way around. -- FIXED QPID-7480 # Add Port dialogue does not have a scroll bar in case it does not completely fit onto the screen. If the dialogue box resizes (e.g., by closing the Developer Tools pane in IE) only the original part of the dialogue box has a solid background. the newly exposed part is transparent. # --Creating a Base64MD5PasswordFile AuthProvider pointing to a non existing file creates it. however editing and point it to a non existing file fails with 422 but the config seems to have been updated regardless with subsequent changes (e.g. adding user) failing.-- Subject of QPID-7485 # --add dialogue for SimpleLDAP AuthenticationProvider is wonky-- FIXED QPID-7483 # deletion of TrustStore displays the trust store name in the confirmation dialogue as 'undefined'. # In the UI for FileGroupProvider the path field is editable but on the broker it is not resulting in 422 errors. Either we should allow editing on the broker or disallow it in the UI. # add dialogue of AclFile type is wonky # RuleBased ACL has no useful UI # If the add Queue dialogue has a scrollbar the lower part (the one you have to scroll to) is transparent. This applies to all addQueue dialogues. # dialogue layout gets messed up when dialogue has to display a scrollbar # clicking on any of a widgets "menu icons" (i.e., collapse pane, edit, goto, or close) will also trigger a drag. # dashboard browser has empty row where the query browser displays the query type. # the text elements in question/notification/warning-yellow.svg are not centred correctly in IE. In chrome and FF only the warning-yellow.svg seems of centre. was: During testing the following minor UI issues were discovered: In no particular order (numbering just for easier referencing): # Logging in occasionally fails with a 417 error response especially when the browsers developer tools are open. This is probably due to a timeout in SaslServlet (default 3000 ms). # --In view and edit of Broker: "Statistics reporting period enabled" shoud actually be "Statistics reporting reset enabled"-- FIXED QPID-7481 # The memory log viewer grid in "Auto Refresh" mode has the "jumping page" problem # The BrokerLogbackSocket seems to have a default port (6000) but it needs to be entered regardless. # When using BrokerLogbackSocket and nothing is connected to it it waits 100ms for each log event to time out. When using DEBUG this brings the broker to a crawl (e.g., broker startup ~ 4 minutes). I could imagine this also being a problem when logging over a network. Could this also be a problem for other loggers (e.g. Syslog?) # -- When changing "Number of connection threads" to 1 on a VirtualHost the following error is reported: "422 - Number of Selectors 8 on VirtualHost bdb_bdb must be greater than the connection pool size 1. Please correct the problem and retry your operation." which does not make sense. I think it should say the connection pool size must be greater than the selectors not the other way around. -- FIXED QPID-7480 # Add Port dialogue does not have a scroll bar in case it does not completely fit onto the screen. If the dialogue box resizes (e.g., by closing the Developer Tools pane in IE) only the original part of the dialogue box has a solid background. the newly exposed part is transparent. # -- Creating a Base64MD5PasswordFile AuthProvider pointing to a non existing file creates it. however
[jira] [Updated] (QPID-7483) [Java Broker, WMC] Address minor UI issues
[ https://issues.apache.org/jira/browse/QPID-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7483: - Description: During testing the following minor UI issues were discovered: In no particular order (numbering just for easier referencing): # Logging in occasionally fails with a 417 error response especially when the browsers developer tools are open. This is probably due to a timeout in SaslServlet (default 3000 ms). # --In view and edit of Broker: "Statistics reporting period enabled" shoud actually be "Statistics reporting reset enabled"-- FIXED QPID-7481 # The memory log viewer grid in "Auto Refresh" mode has the "jumping page" problem # The BrokerLogbackSocket seems to have a default port (6000) but it needs to be entered regardless. # When using BrokerLogbackSocket and nothing is connected to it it waits 100ms for each log event to time out. When using DEBUG this brings the broker to a crawl (e.g., broker startup ~ 4 minutes). I could imagine this also being a problem when logging over a network. Could this also be a problem for other loggers (e.g. Syslog?) # -- When changing "Number of connection threads" to 1 on a VirtualHost the following error is reported: "422 - Number of Selectors 8 on VirtualHost bdb_bdb must be greater than the connection pool size 1. Please correct the problem and retry your operation." which does not make sense. I think it should say the connection pool size must be greater than the selectors not the other way around. -- FIXED QPID-7480 # Add Port dialogue does not have a scroll bar in case it does not completely fit onto the screen. If the dialogue box resizes (e.g., by closing the Developer Tools pane in IE) only the original part of the dialogue box has a solid background. the newly exposed part is transparent. # -- Creating a Base64MD5PasswordFile AuthProvider pointing to a non existing file creates it. however editing and point it to a non existing file fails with 422 but the config seems to have been updated regardless with subsequent changes (e.g. adding user) failing. -- Subject of QPID-7485 # -- add dialogue for SimpleLDAP AuthenticationProvider is wonky -- FIXED QPID-7483 # deletion of TrustStore displays the trust store name in the confirmation dialogue as 'undefined'. # In the UI for FileGroupProvider the path field is editable but on the broker it is not resulting in 422 errors. Either we should allow editing on the broker or disallow it in the UI. # add dialogue of AclFile type is wonky # RuleBased ACL has no useful UI # If the add Queue dialogue has a scrollbar the lower part (the one you have to scroll to) is transparent. This applies to all addQueue dialogues. # dialogue layout gets messed up when dialogue has to display a scrollbar # clicking on any of a widgets "menu icons" (i.e., collapse pane, edit, goto, or close) will also trigger a drag. # dashboard browser has empty row where the query browser displays the query type. # the text elements in question/notification/warning-yellow.svg are not centred correctly in IE. In chrome and FF only the warning-yellow.svg seems of centre. was: During testing the following minor UI issues were discovered: In no particular order (numbering just for easier referencing): # Logging in occasionally fails with a 417 error response especially when the browsers developer tools are open. This is probably due to a timeout in SaslServlet (default 3000 ms). # In view and edit of Broker: "Statistics reporting period enabled" shoud actually be "Statistics reporting reset enabled" # The memory log viewer grid in "Auto Refresh" mode has the "jumping page" problem # The BrokerLogbackSocket seems to have a default port (6000) but it needs to be entered regardless. # When using BrokerLogbackSocket and nothing is connected to it it waits 100ms for each log event to time out. When using DEBUG this brings the broker to a crawl (e.g., broker startup ~ 4 minutes). I could imagine this also being a problem when logging over a network. Could this also be a problem for other loggers (e.g. Syslog?) # When changing "Number of connection threads" to 1 on a VirtualHost the following error is reported: "422 - Number of Selectors 8 on VirtualHost bdb_bdb must be greater than the connection pool size 1. Please correct the problem and retry your operation." which does not make sense. I think it should say the connection pool size must be greater than the selectors not the other way around. # Add Port dialogue does not have a scroll bar in case it does not completely fit onto the screen. If the dialogue box resizes (e.g., by closing the Developer Tools pane in IE) only the original part of the dialogue box has a solid background. the newly exposed part is transparent. # Creating a Base64MD5PasswordFile AuthProvider pointing to a non existing file creates it. however editing and point it to a non existing file
