[jira] [Resolved] (QPID-8668) [Broker-J] Increase the model version to 9.1 in the docker image
[ https://issues.apache.org/jira/browse/QPID-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8668. -- Resolution: Fixed > [Broker-J] Increase the model version to 9.1 in the docker image > > > Key: QPID-8668 > URL: https://issues.apache.org/jira/browse/QPID-8668 > Project: Qpid > Issue Type: Task > Components: Broker-J > Reporter: Tomas Vavricka >Priority: Minor > Fix For: qpid-java-broker-9.2.1 > > > Model in configuration files in docker image should be updated to 9.1. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8668) [Broker-J] Increase the model version to 9.1 in the docker image
[ https://issues.apache.org/jira/browse/QPID-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8668: - Summary: [Broker-J] Increase the model version to 9.1 in the docker image (was: [Broker-J] Update model version in docker image) > [Broker-J] Increase the model version to 9.1 in the docker image > > > Key: QPID-8668 > URL: https://issues.apache.org/jira/browse/QPID-8668 > Project: Qpid > Issue Type: Task > Components: Broker-J > Reporter: Tomas Vavricka >Priority: Minor > Fix For: qpid-java-broker-9.2.1 > > > Model in configuration files in docker image should be updated to 9.1. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8668) [Broker-J] Update model version in docker image
Tomas Vavricka created QPID-8668: Summary: [Broker-J] Update model version in docker image Key: QPID-8668 URL: https://issues.apache.org/jira/browse/QPID-8668 Project: Qpid Issue Type: Task Components: Broker-J Reporter: Tomas Vavricka Fix For: qpid-java-broker-9.2.1 Model in configuration files in docker image should be updated to 9.1. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid Broker-J 9.2.0 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Broker-J 9.2.0. This is the latest release of pure java implementation of messaging broker supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org) and legacy AMQP protocols 0-10, 0-91, 0-9 and 0-8. Please visit Qpid project site for more details: http://qpid.apache.org/components/broker-j/index.html The release is available now from our website: http://qpid.apache.org/download.html The release brings bug fixes and improvements. The release notes can be found at: http://qpid.apache.org/releases/qpid-broker-j-9.2.0/release-notes.html Thanks to all involved, Qpid Team - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8666) [Broker-J] Broker plugin jdbc-provider-bone replacement
[ https://issues.apache.org/jira/browse/QPID-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8666. > [Broker-J] Broker plugin jdbc-provider-bone replacement > --- > > Key: QPID-8666 > URL: https://issues.apache.org/jira/browse/QPID-8666 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Major > Fix For: qpid-java-broker-9.2.0 > > > Broker plugin jdbc-provider-bone relies on JDBC connection pooling library > bonecp, which is no longer developed or updated. The [github project > page|https://github.com/wwadge/bonecp] states: > "BoneCP is a Java JDBC connection pool implementation that is tuned for high > performance by minimizing lock contention to give greater throughput for your > applications. It beats older connection pools such as C3P0 and DBCP but > should now be considered deprecated in favour of HikariCP". > Plugin jdbc-provider-bone should be replaced with the new one > jdbc-provider-hikaricp based on > [HikariCP|https://github.com/brettwooldridge/HikariCP] library. Both > libraries use Apache-2.0 license. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8667) [Broker-J] Database connection with client certificate authentication exposes keystore / truststore passwords
[
https://issues.apache.org/jira/browse/QPID-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8667.
> [Broker-J] Database connection with client certificate authentication exposes
> keystore / truststore passwords
> -
>
> Key: QPID-8667
> URL: https://issues.apache.org/jira/browse/QPID-8667
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.2.0
>
>
> JDBC allows to supply datasource parameters via JDBC connection string in
> form:
> jdbc:://:/?key1=value1=value2=value3
> Relevant configuration for a virtualhost for PostgreSQL looks like following:
> {code:java}
> {
> "type" : "JDBC",
> "connectionPoolType" : "BONECP",
> "connectionUrl":
> "jdbc:postgresql://:/?ssl=true=verify-full===",
> "username": "QPID",
> "password": null
> } {code}
> To make hide sensitive parameters like keystore / truststore passwords
> configuration should reference a keystore or truststore instead providing the
> RDBMS-specific parameter names:
> {code:java}
> {
> "name" : "default",
> "type" : "JDBC",
> "connectionPoolType" : "BONECP",
> "connectionUrl" :
> "jdbc:postgresql://:/?ssl=true=verify-full=",
> "keyStore" : "keystore-database",
> "keyStorePasswordPropertyName" : "sslpassword",
> "keyStorePathPropertyName" : "sslkey",
> "trustStore" : null,
> "trustStorePasswordPropertyName" : null,
> "trustStorePathPropertyName" : null,
> "username" : "QPID"
> }{code}
> Here keystore "keystore-database" is referenced, containing path to the
> keystore as well as its password (which is hidden). Path to the keystore
> should be injected into the JDBC connection string using the parameter
> "keyStorePathPropertyName", keystores password should be injected into JDBC
> connection string using the parameter "keyStorePasswordPropertyName".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8655) [Broker-J] Dependency updates for version 9.2.x
[ https://issues.apache.org/jira/browse/QPID-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8655. > [Broker-J] Dependency updates for version 9.2.x > --- > > Key: QPID-8655 > URL: https://issues.apache.org/jira/browse/QPID-8655 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > This Jira should serve for broker-j dependency updates for release 9.1.1 > Following dependencies are updated: > *runtime dependencies* > ch.qos.logback:logback-core 1.4.11 => 1.4.14 > ch.qos.logback:logback-classic 1.4.11 => 1.4.14 > com.fasterxml.jackson.core:jackson-core 2.15.3 => 2.16.1 > com.fasterxml.jackson.core:jackson-databind 2.15.3 => 2.16.1 > com.google.guava:guava 32.1.3-jre => 33.0.0-jre > org.eclipse.jetty:jetty-server 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-servlet 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-servlets 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-rewrite 11.0.18 => 11.0.19 > org.eclipse.jetty.websocket:websocket-jetty-server 11.0.18 => 11.0.19 > de.siegmar:logback-gelf 3.0.0 => 5.0.1 > org.bouncycastle:bcprov-jdk18on 1.76 => 1.77 > org.bouncycastle:bcpkix-jdk18on 1.76 => 1.77 > org.slf4:slf4j-api 2.0.9 => 2.0.10 > *test dependencies* > io.netty:netty-buffer 4.1.100.Final => 4.1.106.Final > io.netty:netty-common 4.1.100.Final => 4.1.106.Final > io.netty:netty-handler 4.1.100.Final => 4.1.106.Final > io.netty:netty-transport 4.1.100.Final => 4.1.106.Final > io.netty:netty-codec-http 4.1.100.Final => 4.1.106.Final > org.mockito:mockito-core 5.7.0 => 5.9.0 > *maven plugins* > org.codehaus.mojo:exec-maven-plugin 3.1.0 => 3.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8658) [Broker-J] Add Java 21 to the GitHub test matrix
[ https://issues.apache.org/jira/browse/QPID-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8658. > [Broker-J] Add Java 21 to the GitHub test matrix > > > Key: QPID-8658 > URL: https://issues.apache.org/jira/browse/QPID-8658 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > To guarantee the compatibility with the future LTS Java version it would be > needed to add Java 21 to the GitHub test matrix along with Java 11 and 17. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8661) [Broker-J] Apache Directory dependencies update
[ https://issues.apache.org/jira/browse/QPID-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8661. > [Broker-J] Apache Directory dependencies update > --- > > Key: QPID-8661 > URL: https://issues.apache.org/jira/browse/QPID-8661 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > New version of Apache Directory (2.0.0.AM27) was released, which is used in > broker tests with LDAP. This version removed some kerberos functionality, and > when updating the dependency version refactoring of the affected unit tests > will be needed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8648) [Broker-J] Allow for max frame size >4096 before Open frame (SASL)
[
https://issues.apache.org/jira/browse/QPID-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8648.
> [Broker-J] Allow for max frame size >4096 before Open frame (SASL)
> --
>
> Key: QPID-8648
> URL: https://issues.apache.org/jira/browse/QPID-8648
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Dan Langford
>Priority: Major
> Fix For: qpid-java-broker-9.2.0
>
>
> some modern authentication options (XOAUTH2 + JWT) require frames larger then
> 4096. consider if the max frame size (before an Open frame negotiation)
> should be larger or should be configurable with some sort of configuration or
> env variable.
>
> from a discussion on the mailing list
> {quote}The SASL process occurs first, before the Open frame. The Open frames
> are what carries each peers advertised max frame size, mainly aimed at
> later message deliveries. The AMQP 1.0 spec defines before this
> however that the SASL frames can be at-most the 'min max frame size',
> which is fixed at 512 bytes, with no way to negotiate anything larger.
> As you can probably tell, that presents a problem if things in the
> SASL negotiation want to be larger, such as is likely in e.g a newer
> XOAUTH2 mechanism that didnt exist when that decision was originally
> made.
> To simply allow some of these newer alternative mechs to work, it was
> decided to just allow things to exceed the 512byte limit since both
> sides would have to already agree on using a given mech to begin with,
> so doing an alternative like creating a custom multi-challenge
> batching sequence to shuffle the bytes wasnt really going to be adding
> much except significant complexity.
> It appears broker-j allows up to 4096, and you have now found
> something to exceed even that. It doesnt look like it allows
> configuring it, but increasing that seems to be the only option that
> would help here.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8663) [Broker-J] Deprecate AESKeyFileEncrypter
[ https://issues.apache.org/jira/browse/QPID-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8663. > [Broker-J] Deprecate AESKeyFileEncrypter > > > Key: QPID-8663 > URL: https://issues.apache.org/jira/browse/QPID-8663 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > AESKeyFileEncrypter should be marked as deprecated in favor of > AESGCMKeyFileEncrypter, documentation should be updated to discourage usage > of AESKeyFile-based configuration encryption. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8352) [Broker-J] Official Docker image for Broker-J
[ https://issues.apache.org/jira/browse/QPID-8352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8352: - Description: Currently there is no official Docker image for Broker-J. It would be great if one was provided, as there are more than a few people interested in running Broker-J in a container, shown by the handful of inflexible and un-maintained Dockerfiles/images for Broker-J floating around GitHub/Docker Hub. Apache Qpid Broker-J images on Docker Hub: https://hub.docker.com/r/apache/qpid-broker-j/tags was: Currently there is no official Docker image for Broker-J. It would be great if one was provided, as there are more than a few people interested in running Broker-J in a container, shown by the handful of inflexible and un-maintained Dockerfiles/images for Broker-J floating around GitHub/Docker Hub. > [Broker-J] Official Docker image for Broker-J > - > > Key: QPID-8352 > URL: https://issues.apache.org/jira/browse/QPID-8352 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Chris O'Brien >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > Currently there is no official Docker image for Broker-J. > It would be great if one was provided, as there are more than a few people > interested in running Broker-J in a container, shown by the handful of > inflexible and un-maintained Dockerfiles/images for Broker-J floating around > GitHub/Docker Hub. > Apache Qpid Broker-J images on Docker Hub: > https://hub.docker.com/r/apache/qpid-broker-j/tags > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8665) [Broker-J] Changing queue exclusive mode throws exception
[
https://issues.apache.org/jira/browse/QPID-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8665.
> [Broker-J] Changing queue exclusive mode throws exception
> -
>
> Key: QPID-8665
> URL: https://issues.apache.org/jira/browse/QPID-8665
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.2.0
>
>
> If queue has a consumer and exclusive mode is set to CONNECTION, then
> changing queue exclusive mode to PRINCIPAL or CONTAINER will throw exception
> below. Then no consumer is able to consume messages from queue and broker's
> webgui fails to show Edit Queue dialog again.
> Steps to reproduce:
> * set queue exclusive mode to CONNECTION in broker's webgui
> * connect to queue
> * set queue exclusive mode to PRINCIPAL or CONTAINER in broker's webgui
> * exception should be thrown
> {noformat}
> 2024-01-16T09:30:55,432Z INFO [VirtualHostNode-default-Config]
> (q.m.q.update) - [mng:uO4gG/VX(admin@/127.0.0.1:45136)]
> [vh(/default)/qu(broadcast.CAREX_TESTCALMMACC1.Public)] QUE-1017 : Update :
> "broadcast.CAREX_TESTCALMMACC1.Public" : FAILURE :
> {alternateBinding=null,exclusive=PRINCIPAL}
> 2024-01-16T09:30:55,435Z WARN [qtp398517223-54]
> (o.a.q.s.m.p.ManagementException) - Unexpected Exception
> java.lang.ClassCastException: class java.lang.String cannot be cast to class
> java.security.Principal (java.lang.String and java.security.Principal are in
> module java.base of loader 'bootstrap')
> at
> org.apache.qpid.server.queue.AbstractQueue.getOwner(AbstractQueue.java:776)
> at jdk.internal.reflect.GeneratedMethodAccessor85.invoke(Unknown
> Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.qpid.server.model.ConfiguredObjectMethodAttributeOrStatistic.getValue(ConfiguredObjectMethodAttributeOrStatistic.java:68)
> at
> org.apache.qpid.server.model.ConfiguredObjectMethodAttribute.getValue(ConfiguredObjectMethodAttribute.java:29)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.getAttribute(AbstractConfiguredObject.java:1792)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$9.lambda$getAttributes$0(AbstractConfiguredObject.java:1916)
> at java.base/java.security.AccessController.doPrivileged(Native
> Method)
> at java.base/javax.security.auth.Subject.doAs(Subject.java:361)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$9.getAttributes(AbstractConfiguredObject.java:1906)
> at
> org.apache.qpid.server.store.JsonFileConfigStore.update(JsonFileConfigStore.java:420)
> at
> org.apache.qpid.server.configuration.store.StoreConfigurationChangeListener.bulkChangeEnd(StoreConfigurationChangeListener.java:98)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.bulkChangeEnd(AbstractConfiguredObject.java:3030)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.changeAttributes(AbstractConfiguredObject.java:3065)
> at
> org.apache.qpid.server.queue.AbstractQueue.changeAttributes(AbstractQueue.java:3369)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$19.setAttributes(AbstractConfiguredObject.java:2914)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$19.execute(AbstractConfiguredObject.java:2896)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$19.execute(AbstractConfiguredObject.java:2889)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.lambda$call$0(TaskExecutorImpl.java:317)
> at java.base/java.security.AccessController.doPrivileged(Native
> Method)
> at java.base/javax.security.auth.Subject.doAs(Subject.java:361)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
> at
> com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:131)
> at
> com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleT
[jira] [Closed] (QPID-8660) [Broker-J] Logback logging disabled by inclusion of qpid-broker as a dependency
[
https://issues.apache.org/jira/browse/QPID-8660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8660.
> [Broker-J] Logback logging disabled by inclusion of qpid-broker as a
> dependency
> ---
>
> Key: QPID-8660
> URL: https://issues.apache.org/jira/browse/QPID-8660
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Adrian Pasternak
>Priority: Minor
> Fix For: qpid-java-broker-9.2.0
>
>
> Adding qpid-broker as a project dependency:
> {code:java}
>
> org.apache.qpid
> qpid-broker
> 9.1.0
> {code}
> Disables all logback logging in the application.
>
> This behavior is caused by a change:
> [https://github.com/apache/qpid-broker-j/blame/9.1.0/broker-plugins/logging-logback/src/main/java/org/apache/qpid/server/logging/logback/NoopConfigurator.java#L33]
>
> Mailing list discussion:
> [https://lists.apache.org/thread/ms9ddg0kstkdh3yq2ytxtdnlq2dyhps1]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8352) [Broker-J] Official Docker image for Broker-J
[ https://issues.apache.org/jira/browse/QPID-8352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8352. > [Broker-J] Official Docker image for Broker-J > - > > Key: QPID-8352 > URL: https://issues.apache.org/jira/browse/QPID-8352 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Chris O'Brien >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > Currently there is no official Docker image for Broker-J. > It would be great if one was provided, as there are more than a few people > interested in running Broker-J in a container, shown by the handful of > inflexible and un-maintained Dockerfiles/images for Broker-J floating around > GitHub/Docker Hub. > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8659) [Broker-J] Unit tests in QuerySettingsTest fail under some circumstances
[
https://issues.apache.org/jira/browse/QPID-8659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8659.
> [Broker-J] Unit tests in QuerySettingsTest fail under some circumstances
>
>
> Key: QPID-8659
> URL: https://issues.apache.org/jira/browse/QPID-8659
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.2.0
>
>
> Under some circumstance unit tests in QuerySettingsTest fail.
> Stacktrace:
> {code:java}
> [ERROR]
> org.apache.qpid.server.query.engine.parsing.query.QuerySettingsTest.customizeZoneIdViaQueryEngine
> -- Time elapsed: 0.007 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
> at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
> at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31)
> at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:179)
> at
> org.apache.qpid.server.query.engine.parsing.query.QuerySettingsTest.customizeZoneIdViaQueryEngine(QuerySettingsTest.java:278)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8656) [Broker-J] Selector parsing logic error when combining NOT and LIKE
[ https://issues.apache.org/jira/browse/QPID-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8656. > [Broker-J] Selector parsing logic error when combining NOT and LIKE > --- > > Key: QPID-8656 > URL: https://issues.apache.org/jira/browse/QPID-8656 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > The JMSSelectorFilter.match() gives unexpected results when combining the > LIKE and NOT operators. > The selector "NOT (entry LIKE '%aaa%')" and value "" returns true, as > expected, > The selector "NOT entry LIKE '%aaa%'" and value "" returns false, whcih > is a bug. > In both cases the method retuns true when the value is "" > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8657) [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state
[ https://issues.apache.org/jira/browse/QPID-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8657. > [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal > state > --- > > Key: QPID-8657 > URL: https://issues.apache.org/jira/browse/QPID-8657 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > Attachments: aclRequest.json, qpidErrorLog.txt, resultingAcl.json > > > When POSTing an ACL rule with unknown attributes to the Qpid HTTP management > API, the server responds with HTTP 422, Unprocessable Entity. This is > somewhat OK, however, I think maybe a 400 Bad Request would be more > appropriate. > But after the post, the broker is somehow left in a bad internal state, as > the returned Json is incomplete and unparseable. > Example POST in [^aclRequest.json] > Qpid log from the incident [^qpidErrorLog.txt] > Returned Json from subsequent GET [^resultingAcl.json] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8660) [Broker-J] Logback logging disabled by inclusion of qpid-broker as a dependency
[
https://issues.apache.org/jira/browse/QPID-8660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka resolved QPID-8660.
--
Resolution: Fixed
> [Broker-J] Logback logging disabled by inclusion of qpid-broker as a
> dependency
> ---
>
> Key: QPID-8660
> URL: https://issues.apache.org/jira/browse/QPID-8660
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Adrian Pasternak
>Priority: Minor
> Fix For: qpid-java-broker-9.2.0
>
>
> Adding qpid-broker as a project dependency:
> {code:java}
>
> org.apache.qpid
> qpid-broker
> 9.1.0
> {code}
> Disables all logback logging in the application.
>
> This behavior is caused by a change:
> [https://github.com/apache/qpid-broker-j/blame/9.1.0/broker-plugins/logging-logback/src/main/java/org/apache/qpid/server/logging/logback/NoopConfigurator.java#L33]
>
> Mailing list discussion:
> [https://lists.apache.org/thread/ms9ddg0kstkdh3yq2ytxtdnlq2dyhps1]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8663) [Broker-J] Deprecate AESKeyFileEncrypter
[ https://issues.apache.org/jira/browse/QPID-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8663: - Fix Version/s: qpid-java-broker-9.2.0 (was: qpid-java-broker-9.1.1) > [Broker-J] Deprecate AESKeyFileEncrypter > > > Key: QPID-8663 > URL: https://issues.apache.org/jira/browse/QPID-8663 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > AESKeyFileEncrypter should be marked as deprecated in favor of > AESGCMKeyFileEncrypter, documentation should be updated to discourage usage > of AESKeyFile-based configuration encryption. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8667) [Broker-J] Database connection with client certificate authentication exposes keystore / truststore passwords
[
https://issues.apache.org/jira/browse/QPID-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8667:
-
Fix Version/s: qpid-java-broker-9.2.0
(was: qpid-java-broker-9.1.1)
> [Broker-J] Database connection with client certificate authentication exposes
> keystore / truststore passwords
> -
>
> Key: QPID-8667
> URL: https://issues.apache.org/jira/browse/QPID-8667
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.2.0
>
>
> JDBC allows to supply datasource parameters via JDBC connection string in
> form:
> jdbc:://:/?key1=value1=value2=value3
> Relevant configuration for a virtualhost for PostgreSQL looks like following:
> {code:java}
> {
> "type" : "JDBC",
> "connectionPoolType" : "BONECP",
> "connectionUrl":
> "jdbc:postgresql://:/?ssl=true=verify-full===",
> "username": "QPID",
> "password": null
> } {code}
> To make hide sensitive parameters like keystore / truststore passwords
> configuration should reference a keystore or truststore instead providing the
> RDBMS-specific parameter names:
> {code:java}
> {
> "name" : "default",
> "type" : "JDBC",
> "connectionPoolType" : "BONECP",
> "connectionUrl" :
> "jdbc:postgresql://:/?ssl=true=verify-full=",
> "keyStore" : "keystore-database",
> "keyStorePasswordPropertyName" : "sslpassword",
> "keyStorePathPropertyName" : "sslkey",
> "trustStore" : null,
> "trustStorePasswordPropertyName" : null,
> "trustStorePathPropertyName" : null,
> "username" : "QPID"
> }{code}
> Here keystore "keystore-database" is referenced, containing path to the
> keystore as well as its password (which is hidden). Path to the keystore
> should be injected into the JDBC connection string using the parameter
> "keyStorePathPropertyName", keystores password should be injected into JDBC
> connection string using the parameter "keyStorePasswordPropertyName".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8665) [Broker-J] Changing queue exclusive mode throws exception
[
https://issues.apache.org/jira/browse/QPID-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8665:
-
Fix Version/s: qpid-java-broker-9.2.0
(was: qpid-java-broker-9.1.1)
> [Broker-J] Changing queue exclusive mode throws exception
> -
>
> Key: QPID-8665
> URL: https://issues.apache.org/jira/browse/QPID-8665
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.2.0
>
>
> If queue has a consumer and exclusive mode is set to CONNECTION, then
> changing queue exclusive mode to PRINCIPAL or CONTAINER will throw exception
> below. Then no consumer is able to consume messages from queue and broker's
> webgui fails to show Edit Queue dialog again.
> Steps to reproduce:
> * set queue exclusive mode to CONNECTION in broker's webgui
> * connect to queue
> * set queue exclusive mode to PRINCIPAL or CONTAINER in broker's webgui
> * exception should be thrown
> {noformat}
> 2024-01-16T09:30:55,432Z INFO [VirtualHostNode-default-Config]
> (q.m.q.update) - [mng:uO4gG/VX(admin@/127.0.0.1:45136)]
> [vh(/default)/qu(broadcast.CAREX_TESTCALMMACC1.Public)] QUE-1017 : Update :
> "broadcast.CAREX_TESTCALMMACC1.Public" : FAILURE :
> {alternateBinding=null,exclusive=PRINCIPAL}
> 2024-01-16T09:30:55,435Z WARN [qtp398517223-54]
> (o.a.q.s.m.p.ManagementException) - Unexpected Exception
> java.lang.ClassCastException: class java.lang.String cannot be cast to class
> java.security.Principal (java.lang.String and java.security.Principal are in
> module java.base of loader 'bootstrap')
> at
> org.apache.qpid.server.queue.AbstractQueue.getOwner(AbstractQueue.java:776)
> at jdk.internal.reflect.GeneratedMethodAccessor85.invoke(Unknown
> Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.qpid.server.model.ConfiguredObjectMethodAttributeOrStatistic.getValue(ConfiguredObjectMethodAttributeOrStatistic.java:68)
> at
> org.apache.qpid.server.model.ConfiguredObjectMethodAttribute.getValue(ConfiguredObjectMethodAttribute.java:29)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.getAttribute(AbstractConfiguredObject.java:1792)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$9.lambda$getAttributes$0(AbstractConfiguredObject.java:1916)
> at java.base/java.security.AccessController.doPrivileged(Native
> Method)
> at java.base/javax.security.auth.Subject.doAs(Subject.java:361)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$9.getAttributes(AbstractConfiguredObject.java:1906)
> at
> org.apache.qpid.server.store.JsonFileConfigStore.update(JsonFileConfigStore.java:420)
> at
> org.apache.qpid.server.configuration.store.StoreConfigurationChangeListener.bulkChangeEnd(StoreConfigurationChangeListener.java:98)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.bulkChangeEnd(AbstractConfiguredObject.java:3030)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.changeAttributes(AbstractConfiguredObject.java:3065)
> at
> org.apache.qpid.server.queue.AbstractQueue.changeAttributes(AbstractQueue.java:3369)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$19.setAttributes(AbstractConfiguredObject.java:2914)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$19.execute(AbstractConfiguredObject.java:2896)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$19.execute(AbstractConfiguredObject.java:2889)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.lambda$call$0(TaskExecutorImpl.java:317)
> at java.base/java.security.AccessController.doPrivileged(Native
> Method)
> at java.base/javax.security.auth.Subject.doAs(Subject.java:361)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
> at
> com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutu
[jira] [Updated] (QPID-8661) [Broker-J] Apache Directory dependencies update
[ https://issues.apache.org/jira/browse/QPID-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8661: - Fix Version/s: qpid-java-broker-9.2.0 (was: qpid-java-broker-9.1.1) > [Broker-J] Apache Directory dependencies update > --- > > Key: QPID-8661 > URL: https://issues.apache.org/jira/browse/QPID-8661 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > New version of Apache Directory (2.0.0.AM27) was released, which is used in > broker tests with LDAP. This version removed some kerberos functionality, and > when updating the dependency version refactoring of the affected unit tests > will be needed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8658) [Broker-J] Add Java 21 to the GitHub test matrix
[ https://issues.apache.org/jira/browse/QPID-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8658: - Fix Version/s: qpid-java-broker-9.2.0 (was: qpid-java-broker-9.1.1) > [Broker-J] Add Java 21 to the GitHub test matrix > > > Key: QPID-8658 > URL: https://issues.apache.org/jira/browse/QPID-8658 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > To guarantee the compatibility with the future LTS Java version it would be > needed to add Java 21 to the GitHub test matrix along with Java 11 and 17. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8660) [Broker-J] Logback logging disabled by inclusion of qpid-broker as a dependency
[
https://issues.apache.org/jira/browse/QPID-8660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8660:
-
Fix Version/s: qpid-java-broker-9.2.0
(was: qpid-java-broker-9.1.1)
> [Broker-J] Logback logging disabled by inclusion of qpid-broker as a
> dependency
> ---
>
> Key: QPID-8660
> URL: https://issues.apache.org/jira/browse/QPID-8660
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Adrian Pasternak
>Priority: Minor
> Fix For: qpid-java-broker-9.2.0
>
>
> Adding qpid-broker as a project dependency:
> {code:java}
>
> org.apache.qpid
> qpid-broker
> 9.1.0
> {code}
> Disables all logback logging in the application.
>
> This behavior is caused by a change:
> [https://github.com/apache/qpid-broker-j/blame/9.1.0/broker-plugins/logging-logback/src/main/java/org/apache/qpid/server/logging/logback/NoopConfigurator.java#L33]
>
> Mailing list discussion:
> [https://lists.apache.org/thread/ms9ddg0kstkdh3yq2ytxtdnlq2dyhps1]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8659) [Broker-J] Unit tests in QuerySettingsTest fail under some circumstances
[
https://issues.apache.org/jira/browse/QPID-8659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8659:
-
Fix Version/s: qpid-java-broker-9.2.0
(was: qpid-java-broker-9.1.1)
> [Broker-J] Unit tests in QuerySettingsTest fail under some circumstances
>
>
> Key: QPID-8659
> URL: https://issues.apache.org/jira/browse/QPID-8659
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.2.0
>
>
> Under some circumstance unit tests in QuerySettingsTest fail.
> Stacktrace:
> {code:java}
> [ERROR]
> org.apache.qpid.server.query.engine.parsing.query.QuerySettingsTest.customizeZoneIdViaQueryEngine
> -- Time elapsed: 0.007 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
> at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
> at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31)
> at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:179)
> at
> org.apache.qpid.server.query.engine.parsing.query.QuerySettingsTest.customizeZoneIdViaQueryEngine(QuerySettingsTest.java:278)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8657) [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state
[ https://issues.apache.org/jira/browse/QPID-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8657: - Fix Version/s: qpid-java-broker-9.2.0 (was: qpid-java-broker-9.1.1) > [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal > state > --- > > Key: QPID-8657 > URL: https://issues.apache.org/jira/browse/QPID-8657 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > Attachments: aclRequest.json, qpidErrorLog.txt, resultingAcl.json > > > When POSTing an ACL rule with unknown attributes to the Qpid HTTP management > API, the server responds with HTTP 422, Unprocessable Entity. This is > somewhat OK, however, I think maybe a 400 Bad Request would be more > appropriate. > But after the post, the broker is somehow left in a bad internal state, as > the returned Json is incomplete and unparseable. > Example POST in [^aclRequest.json] > Qpid log from the incident [^qpidErrorLog.txt] > Returned Json from subsequent GET [^resultingAcl.json] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8656) [Broker-J] Selector parsing logic error when combining NOT and LIKE
[ https://issues.apache.org/jira/browse/QPID-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8656: - Fix Version/s: qpid-java-broker-9.2.0 (was: qpid-java-broker-9.1.1) > [Broker-J] Selector parsing logic error when combining NOT and LIKE > --- > > Key: QPID-8656 > URL: https://issues.apache.org/jira/browse/QPID-8656 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > The JMSSelectorFilter.match() gives unexpected results when combining the > LIKE and NOT operators. > The selector "NOT (entry LIKE '%aaa%')" and value "" returns true, as > expected, > The selector "NOT entry LIKE '%aaa%'" and value "" returns false, whcih > is a bug. > In both cases the method retuns true when the value is "" > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8655) [Broker-J] Dependency updates for version 9.1.x
[ https://issues.apache.org/jira/browse/QPID-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8655: - Fix Version/s: qpid-java-broker-9.2.0 (was: qpid-java-broker-9.1.1) > [Broker-J] Dependency updates for version 9.1.x > --- > > Key: QPID-8655 > URL: https://issues.apache.org/jira/browse/QPID-8655 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > This Jira should serve for broker-j dependency updates for release 9.1.1 > Following dependencies are updated: > *runtime dependencies* > ch.qos.logback:logback-core 1.4.11 => 1.4.14 > ch.qos.logback:logback-classic 1.4.11 => 1.4.14 > com.fasterxml.jackson.core:jackson-core 2.15.3 => 2.16.1 > com.fasterxml.jackson.core:jackson-databind 2.15.3 => 2.16.1 > com.google.guava:guava 32.1.3-jre => 33.0.0-jre > org.eclipse.jetty:jetty-server 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-servlet 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-servlets 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-rewrite 11.0.18 => 11.0.19 > org.eclipse.jetty.websocket:websocket-jetty-server 11.0.18 => 11.0.19 > de.siegmar:logback-gelf 3.0.0 => 5.0.1 > org.bouncycastle:bcprov-jdk18on 1.76 => 1.77 > org.bouncycastle:bcpkix-jdk18on 1.76 => 1.77 > org.slf4:slf4j-api 2.0.9 => 2.0.10 > *test dependencies* > io.netty:netty-buffer 4.1.100.Final => 4.1.106.Final > io.netty:netty-common 4.1.100.Final => 4.1.106.Final > io.netty:netty-handler 4.1.100.Final => 4.1.106.Final > io.netty:netty-transport 4.1.100.Final => 4.1.106.Final > io.netty:netty-codec-http 4.1.100.Final => 4.1.106.Final > org.mockito:mockito-core 5.7.0 => 5.9.0 > *maven plugins* > org.codehaus.mojo:exec-maven-plugin 3.1.0 => 3.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8352) [Broker-J] Official Docker image for Broker-J
[ https://issues.apache.org/jira/browse/QPID-8352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8352: - Fix Version/s: qpid-java-broker-9.2.0 (was: qpid-java-broker-9.1.1) > [Broker-J] Official Docker image for Broker-J > - > > Key: QPID-8352 > URL: https://issues.apache.org/jira/browse/QPID-8352 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Chris O'Brien >Priority: Minor > Fix For: qpid-java-broker-9.2.0 > > > Currently there is no official Docker image for Broker-J. > It would be great if one was provided, as there are more than a few people > interested in running Broker-J in a container, shown by the handful of > inflexible and un-maintained Dockerfiles/images for Broker-J floating around > GitHub/Docker Hub. > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8666) [Broker-J] Broker plugin jdbc-provider-bone replacement
[ https://issues.apache.org/jira/browse/QPID-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8666: - Fix Version/s: qpid-java-broker-9.2.0 (was: qpid-java-broker-9.1.1) > [Broker-J] Broker plugin jdbc-provider-bone replacement > --- > > Key: QPID-8666 > URL: https://issues.apache.org/jira/browse/QPID-8666 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Major > Fix For: qpid-java-broker-9.2.0 > > > Broker plugin jdbc-provider-bone relies on JDBC connection pooling library > bonecp, which is no longer developed or updated. The [github project > page|https://github.com/wwadge/bonecp] states: > "BoneCP is a Java JDBC connection pool implementation that is tuned for high > performance by minimizing lock contention to give greater throughput for your > applications. It beats older connection pools such as C3P0 and DBCP but > should now be considered deprecated in favour of HikariCP". > Plugin jdbc-provider-bone should be replaced with the new one > jdbc-provider-hikaricp based on > [HikariCP|https://github.com/brettwooldridge/HikariCP] library. Both > libraries use Apache-2.0 license. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8648) [Broker-J] Allow for max frame size >4096 before Open frame (SASL)
[
https://issues.apache.org/jira/browse/QPID-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8648:
-
Fix Version/s: qpid-java-broker-9.2.0
(was: qpid-java-broker-9.1.1)
> [Broker-J] Allow for max frame size >4096 before Open frame (SASL)
> --
>
> Key: QPID-8648
> URL: https://issues.apache.org/jira/browse/QPID-8648
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Dan Langford
>Priority: Major
> Fix For: qpid-java-broker-9.2.0
>
>
> some modern authentication options (XOAUTH2 + JWT) require frames larger then
> 4096. consider if the max frame size (before an Open frame negotiation)
> should be larger or should be configurable with some sort of configuration or
> env variable.
>
> from a discussion on the mailing list
> {quote}The SASL process occurs first, before the Open frame. The Open frames
> are what carries each peers advertised max frame size, mainly aimed at
> later message deliveries. The AMQP 1.0 spec defines before this
> however that the SASL frames can be at-most the 'min max frame size',
> which is fixed at 512 bytes, with no way to negotiate anything larger.
> As you can probably tell, that presents a problem if things in the
> SASL negotiation want to be larger, such as is likely in e.g a newer
> XOAUTH2 mechanism that didnt exist when that decision was originally
> made.
> To simply allow some of these newer alternative mechs to work, it was
> decided to just allow things to exceed the 512byte limit since both
> sides would have to already agree on using a given mech to begin with,
> so doing an alternative like creating a custom multi-challenge
> batching sequence to shuffle the bytes wasnt really going to be adding
> much except significant complexity.
> It appears broker-j allows up to 4096, and you have now found
> something to exceed even that. It doesnt look like it allows
> configuring it, but increasing that seems to be the only option that
> would help here.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8660) [Broker-J] Logback logging disabled by inclusion of qpid-broker as a dependency
[
https://issues.apache.org/jira/browse/QPID-8660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8660:
-
Summary: [Broker-J] Logback logging disabled by inclusion of qpid-broker as
a dependency (was: Logback logging disabled by inclusion of qpid-broker as a
dependency)
> [Broker-J] Logback logging disabled by inclusion of qpid-broker as a
> dependency
> ---
>
> Key: QPID-8660
> URL: https://issues.apache.org/jira/browse/QPID-8660
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Adrian Pasternak
>Priority: Minor
> Fix For: qpid-java-broker-9.1.1
>
>
> Adding qpid-broker as a project dependency:
> {code:java}
>
> org.apache.qpid
> qpid-broker
> 9.1.0
> {code}
> Disables all logback logging in the application.
>
> This behavior is caused by a change:
> [https://github.com/apache/qpid-broker-j/blame/9.1.0/broker-plugins/logging-logback/src/main/java/org/apache/qpid/server/logging/logback/NoopConfigurator.java#L33]
>
> Mailing list discussion:
> [https://lists.apache.org/thread/ms9ddg0kstkdh3yq2ytxtdnlq2dyhps1]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8655) [Broker-J] Dependency updates for version 9.1.x
[ https://issues.apache.org/jira/browse/QPID-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8655: - Description: This Jira should serve for broker-j dependency updates for release 9.1.1 Following dependencies are updated: *runtime dependencies* ch.qos.logback:logback-core 1.4.11 => 1.4.14 ch.qos.logback:logback-classic 1.4.11 => 1.4.14 com.fasterxml.jackson.core:jackson-core 2.15.3 => 2.16.1 com.fasterxml.jackson.core:jackson-databind 2.15.3 => 2.16.1 com.google.guava:guava 32.1.3-jre => 33.0.0-jre org.eclipse.jetty:jetty-server 11.0.18 => 11.0.19 org.eclipse.jetty:jetty-servlet 11.0.18 => 11.0.19 org.eclipse.jetty:jetty-servlets 11.0.18 => 11.0.19 org.eclipse.jetty:jetty-rewrite 11.0.18 => 11.0.19 org.eclipse.jetty.websocket:websocket-jetty-server 11.0.18 => 11.0.19 de.siegmar:logback-gelf 3.0.0 => 5.0.1 org.bouncycastle:bcprov-jdk18on 1.76 => 1.77 org.bouncycastle:bcpkix-jdk18on 1.76 => 1.77 org.slf4:slf4j-api 2.0.9 => 2.0.10 *test dependencies* io.netty:netty-buffer 4.1.100.Final => 4.1.106.Final io.netty:netty-common 4.1.100.Final => 4.1.106.Final io.netty:netty-handler 4.1.100.Final => 4.1.106.Final io.netty:netty-transport 4.1.100.Final => 4.1.106.Final io.netty:netty-codec-http 4.1.100.Final => 4.1.106.Final org.mockito:mockito-core 5.7.0 => 5.9.0 *maven plugins* org.codehaus.mojo:exec-maven-plugin 3.1.0 => 3.1.1 was: This Jira should serve for broker-j dependency updates for release 9.1.1 Following dependencies are updated: runtime dependencies ch.qos.logback:logback-core 1.4.11 => 1.4.14 ch.qos.logback:logback-classic 1.4.11 => 1.4.14 com.fasterxml.jackson.core:jackson-core 2.15.3 => 2.16.1 com.fasterxml.jackson.core:jackson-databind 2.15.3 => 2.16.1 com.google.guava:guava 32.1.3-jre => 33.0.0-jre org.eclipse.jetty:jetty-server 11.0.18 => 11.0.19 org.eclipse.jetty:jetty-servlet 11.0.18 => 11.0.19 org.eclipse.jetty:jetty-servlets 11.0.18 => 11.0.19 org.eclipse.jetty:jetty-rewrite 11.0.18 => 11.0.19 org.eclipse.jetty.websocket:websocket-jetty-server 11.0.18 => 11.0.19 de.siegmar:logback-gelf 3.0.0 => 5.0.1 org.bouncycastle:bcprov-jdk18on 1.76 => 1.77 org.bouncycastle:bcpkix-jdk18on 1.76 => 1.77 org.slf4:slf4j-api 2.0.9 => 2.0.10 test dependencies io.netty:netty-buffer 4.1.100.Final => 4.1.106.Final io.netty:netty-common 4.1.100.Final => 4.1.106.Final io.netty:netty-handler 4.1.100.Final => 4.1.106.Final io.netty:netty-transport 4.1.100.Final => 4.1.106.Final io.netty:netty-codec-http 4.1.100.Final => 4.1.106.Final org.mockito:mockito-core 5.7.0 => 5.9.0 maven plugins org.codehaus.mojo:exec-maven-plugin 3.1.0 => 3.1.1 > [Broker-J] Dependency updates for version 9.1.x > --- > > Key: QPID-8655 > URL: https://issues.apache.org/jira/browse/QPID-8655 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > This Jira should serve for broker-j dependency updates for release 9.1.1 > Following dependencies are updated: > *runtime dependencies* > ch.qos.logback:logback-core 1.4.11 => 1.4.14 > ch.qos.logback:logback-classic 1.4.11 => 1.4.14 > com.fasterxml.jackson.core:jackson-core 2.15.3 => 2.16.1 > com.fasterxml.jackson.core:jackson-databind 2.15.3 => 2.16.1 > com.google.guava:guava 32.1.3-jre => 33.0.0-jre > org.eclipse.jetty:jetty-server 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-servlet 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-servlets 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-rewrite 11.0.18 => 11.0.19 > org.eclipse.jetty.websocket:websocket-jetty-server 11.0.18 => 11.0.19 > de.siegmar:logback-gelf 3.0.0 => 5.0.1 > org.bouncycastle:bcprov-jdk18on 1.76 => 1.77 > org.bouncycastle:bcpkix-jdk18on 1.76 => 1.77 > org.slf4:slf4j-api 2.0.9 => 2.0.10 > *test dependencies* > io.netty:netty-buffer 4.1.100.Final => 4.1.106.Final > io.netty:netty-common 4.1.100.Final => 4.1.106.Final > io.netty:netty-handler 4.1.100.Final => 4.1.106.Final > io.netty:netty-transport 4.1.100.Final => 4.1.106.Final > io.netty:netty-codec-http 4.1.100.Final => 4.1.106.Final > org.mockito:mockito-core 5.7.0 => 5.9.0 > *maven plugins* > org.codehaus.mojo:exec-maven-plugin 3.1.0 => 3.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8655) [Broker-J] Dependency updates for version 9.1.x
[ https://issues.apache.org/jira/browse/QPID-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8655. -- Resolution: Implemented > [Broker-J] Dependency updates for version 9.1.x > --- > > Key: QPID-8655 > URL: https://issues.apache.org/jira/browse/QPID-8655 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > This Jira should serve for broker-j dependency updates for release 9.1.1 > Following dependencies are updated: > *runtime dependencies* > ch.qos.logback:logback-core 1.4.11 => 1.4.14 > ch.qos.logback:logback-classic 1.4.11 => 1.4.14 > com.fasterxml.jackson.core:jackson-core 2.15.3 => 2.16.1 > com.fasterxml.jackson.core:jackson-databind 2.15.3 => 2.16.1 > com.google.guava:guava 32.1.3-jre => 33.0.0-jre > org.eclipse.jetty:jetty-server 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-servlet 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-servlets 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-rewrite 11.0.18 => 11.0.19 > org.eclipse.jetty.websocket:websocket-jetty-server 11.0.18 => 11.0.19 > de.siegmar:logback-gelf 3.0.0 => 5.0.1 > org.bouncycastle:bcprov-jdk18on 1.76 => 1.77 > org.bouncycastle:bcpkix-jdk18on 1.76 => 1.77 > org.slf4:slf4j-api 2.0.9 => 2.0.10 > *test dependencies* > io.netty:netty-buffer 4.1.100.Final => 4.1.106.Final > io.netty:netty-common 4.1.100.Final => 4.1.106.Final > io.netty:netty-handler 4.1.100.Final => 4.1.106.Final > io.netty:netty-transport 4.1.100.Final => 4.1.106.Final > io.netty:netty-codec-http 4.1.100.Final => 4.1.106.Final > org.mockito:mockito-core 5.7.0 => 5.9.0 > *maven plugins* > org.codehaus.mojo:exec-maven-plugin 3.1.0 => 3.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8655) [Broker-J] Dependency updates for version 9.1.x
[ https://issues.apache.org/jira/browse/QPID-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8655: - Description: This Jira should serve for broker-j dependency updates for release 9.1.1 Following dependencies are updated: runtime dependencies ch.qos.logback:logback-core 1.4.11 => 1.4.14 ch.qos.logback:logback-classic 1.4.11 => 1.4.14 com.fasterxml.jackson.core:jackson-core 2.15.3 => 2.16.1 com.fasterxml.jackson.core:jackson-databind 2.15.3 => 2.16.1 com.google.guava:guava 32.1.3-jre => 33.0.0-jre org.eclipse.jetty:jetty-server 11.0.18 => 11.0.19 org.eclipse.jetty:jetty-servlet 11.0.18 => 11.0.19 org.eclipse.jetty:jetty-servlets 11.0.18 => 11.0.19 org.eclipse.jetty:jetty-rewrite 11.0.18 => 11.0.19 org.eclipse.jetty.websocket:websocket-jetty-server 11.0.18 => 11.0.19 de.siegmar:logback-gelf 3.0.0 => 5.0.1 org.bouncycastle:bcprov-jdk18on 1.76 => 1.77 org.bouncycastle:bcpkix-jdk18on 1.76 => 1.77 org.slf4:slf4j-api 2.0.9 => 2.0.10 test dependencies io.netty:netty-buffer 4.1.100.Final => 4.1.106.Final io.netty:netty-common 4.1.100.Final => 4.1.106.Final io.netty:netty-handler 4.1.100.Final => 4.1.106.Final io.netty:netty-transport 4.1.100.Final => 4.1.106.Final io.netty:netty-codec-http 4.1.100.Final => 4.1.106.Final org.mockito:mockito-core 5.7.0 => 5.9.0 maven plugins org.codehaus.mojo:exec-maven-plugin 3.1.0 => 3.1.1 was:This Jira should serve for broker-j dependency updates for release 9.1.1 > [Broker-J] Dependency updates for version 9.1.x > --- > > Key: QPID-8655 > URL: https://issues.apache.org/jira/browse/QPID-8655 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > This Jira should serve for broker-j dependency updates for release 9.1.1 > Following dependencies are updated: > runtime dependencies > ch.qos.logback:logback-core 1.4.11 => 1.4.14 > ch.qos.logback:logback-classic 1.4.11 => 1.4.14 > com.fasterxml.jackson.core:jackson-core 2.15.3 => 2.16.1 > com.fasterxml.jackson.core:jackson-databind 2.15.3 => 2.16.1 > com.google.guava:guava 32.1.3-jre => 33.0.0-jre > org.eclipse.jetty:jetty-server 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-servlet 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-servlets 11.0.18 => 11.0.19 > org.eclipse.jetty:jetty-rewrite 11.0.18 => 11.0.19 > org.eclipse.jetty.websocket:websocket-jetty-server 11.0.18 => 11.0.19 > de.siegmar:logback-gelf 3.0.0 => 5.0.1 > org.bouncycastle:bcprov-jdk18on 1.76 => 1.77 > org.bouncycastle:bcpkix-jdk18on 1.76 => 1.77 > org.slf4:slf4j-api 2.0.9 => 2.0.10 > test dependencies > io.netty:netty-buffer 4.1.100.Final => 4.1.106.Final > io.netty:netty-common 4.1.100.Final => 4.1.106.Final > io.netty:netty-handler 4.1.100.Final => 4.1.106.Final > io.netty:netty-transport 4.1.100.Final => 4.1.106.Final > io.netty:netty-codec-http 4.1.100.Final => 4.1.106.Final > org.mockito:mockito-core 5.7.0 => 5.9.0 > maven plugins > org.codehaus.mojo:exec-maven-plugin 3.1.0 => 3.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8667) [Broker-J] Database connection with client certificate authentication exposes keystore / truststore passwords
[
https://issues.apache.org/jira/browse/QPID-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka resolved QPID-8667.
--
Resolution: Implemented
> [Broker-J] Database connection with client certificate authentication exposes
> keystore / truststore passwords
> -
>
> Key: QPID-8667
> URL: https://issues.apache.org/jira/browse/QPID-8667
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.1.1
>
>
> JDBC allows to supply datasource parameters via JDBC connection string in
> form:
> jdbc:://:/?key1=value1=value2=value3
> Relevant configuration for a virtualhost for PostgreSQL looks like following:
> {code:java}
> {
> "type" : "JDBC",
> "connectionPoolType" : "BONECP",
> "connectionUrl":
> "jdbc:postgresql://:/?ssl=true=verify-full===",
> "username": "QPID",
> "password": null
> } {code}
> To make hide sensitive parameters like keystore / truststore passwords
> configuration should reference a keystore or truststore instead providing the
> RDBMS-specific parameter names:
> {code:java}
> {
> "name" : "default",
> "type" : "JDBC",
> "connectionPoolType" : "BONECP",
> "connectionUrl" :
> "jdbc:postgresql://:/?ssl=true=verify-full=",
> "keyStore" : "keystore-database",
> "keyStorePasswordPropertyName" : "sslpassword",
> "keyStorePathPropertyName" : "sslkey",
> "trustStore" : null,
> "trustStorePasswordPropertyName" : null,
> "trustStorePathPropertyName" : null,
> "username" : "QPID"
> }{code}
> Here keystore "keystore-database" is referenced, containing path to the
> keystore as well as its password (which is hidden). Path to the keystore
> should be injected into the JDBC connection string using the parameter
> "keyStorePathPropertyName", keystores password should be injected into JDBC
> connection string using the parameter "keyStorePasswordPropertyName".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8352) [Broker-J] Official Docker image for Broker-J
[ https://issues.apache.org/jira/browse/QPID-8352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka reassigned QPID-8352: Assignee: (was: Daniil Kirilyuk) > [Broker-J] Official Docker image for Broker-J > - > > Key: QPID-8352 > URL: https://issues.apache.org/jira/browse/QPID-8352 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Chris O'Brien >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > Currently there is no official Docker image for Broker-J. > It would be great if one was provided, as there are more than a few people > interested in running Broker-J in a container, shown by the handful of > inflexible and un-maintained Dockerfiles/images for Broker-J floating around > GitHub/Docker Hub. > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8352) [Broker-J] Official Docker image for Broker-J
[ https://issues.apache.org/jira/browse/QPID-8352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8352: - Summary: [Broker-J] Official Docker image for Broker-J (was: Official Docker image for Broker-J) > [Broker-J] Official Docker image for Broker-J > - > > Key: QPID-8352 > URL: https://issues.apache.org/jira/browse/QPID-8352 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Chris O'Brien >Assignee: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > Currently there is no official Docker image for Broker-J. > It would be great if one was provided, as there are more than a few people > interested in running Broker-J in a container, shown by the handful of > inflexible and un-maintained Dockerfiles/images for Broker-J floating around > GitHub/Docker Hub. > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8648) [Broker-J] Allow for max frame size >4096 before Open frame (SASL)
[
https://issues.apache.org/jira/browse/QPID-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka resolved QPID-8648.
--
Resolution: Implemented
> [Broker-J] Allow for max frame size >4096 before Open frame (SASL)
> --
>
> Key: QPID-8648
> URL: https://issues.apache.org/jira/browse/QPID-8648
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Dan Langford
>Priority: Major
> Fix For: qpid-java-broker-9.1.1
>
>
> some modern authentication options (XOAUTH2 + JWT) require frames larger then
> 4096. consider if the max frame size (before an Open frame negotiation)
> should be larger or should be configurable with some sort of configuration or
> env variable.
>
> from a discussion on the mailing list
> {quote}The SASL process occurs first, before the Open frame. The Open frames
> are what carries each peers advertised max frame size, mainly aimed at
> later message deliveries. The AMQP 1.0 spec defines before this
> however that the SASL frames can be at-most the 'min max frame size',
> which is fixed at 512 bytes, with no way to negotiate anything larger.
> As you can probably tell, that presents a problem if things in the
> SASL negotiation want to be larger, such as is likely in e.g a newer
> XOAUTH2 mechanism that didnt exist when that decision was originally
> made.
> To simply allow some of these newer alternative mechs to work, it was
> decided to just allow things to exceed the 512byte limit since both
> sides would have to already agree on using a given mech to begin with,
> so doing an alternative like creating a custom multi-challenge
> batching sequence to shuffle the bytes wasnt really going to be adding
> much except significant complexity.
> It appears broker-j allows up to 4096, and you have now found
> something to exceed even that. It doesnt look like it allows
> configuring it, but increasing that seems to be the only option that
> would help here.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8665) [Broker-J] Changing queue exclusive mode throws exception
[
https://issues.apache.org/jira/browse/QPID-8665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka resolved QPID-8665.
--
Resolution: Fixed
> [Broker-J] Changing queue exclusive mode throws exception
> -
>
> Key: QPID-8665
> URL: https://issues.apache.org/jira/browse/QPID-8665
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.1.1
>
>
> If queue has a consumer and exclusive mode is set to CONNECTION, then
> changing queue exclusive mode to PRINCIPAL or CONTAINER will throw exception
> below. Then no consumer is able to consume messages from queue and broker's
> webgui fails to show Edit Queue dialog again.
> Steps to reproduce:
> * set queue exclusive mode to CONNECTION in broker's webgui
> * connect to queue
> * set queue exclusive mode to PRINCIPAL or CONTAINER in broker's webgui
> * exception should be thrown
> {noformat}
> 2024-01-16T09:30:55,432Z INFO [VirtualHostNode-default-Config]
> (q.m.q.update) - [mng:uO4gG/VX(admin@/127.0.0.1:45136)]
> [vh(/default)/qu(broadcast.CAREX_TESTCALMMACC1.Public)] QUE-1017 : Update :
> "broadcast.CAREX_TESTCALMMACC1.Public" : FAILURE :
> {alternateBinding=null,exclusive=PRINCIPAL}
> 2024-01-16T09:30:55,435Z WARN [qtp398517223-54]
> (o.a.q.s.m.p.ManagementException) - Unexpected Exception
> java.lang.ClassCastException: class java.lang.String cannot be cast to class
> java.security.Principal (java.lang.String and java.security.Principal are in
> module java.base of loader 'bootstrap')
> at
> org.apache.qpid.server.queue.AbstractQueue.getOwner(AbstractQueue.java:776)
> at jdk.internal.reflect.GeneratedMethodAccessor85.invoke(Unknown
> Source)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.qpid.server.model.ConfiguredObjectMethodAttributeOrStatistic.getValue(ConfiguredObjectMethodAttributeOrStatistic.java:68)
> at
> org.apache.qpid.server.model.ConfiguredObjectMethodAttribute.getValue(ConfiguredObjectMethodAttribute.java:29)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.getAttribute(AbstractConfiguredObject.java:1792)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$9.lambda$getAttributes$0(AbstractConfiguredObject.java:1916)
> at java.base/java.security.AccessController.doPrivileged(Native
> Method)
> at java.base/javax.security.auth.Subject.doAs(Subject.java:361)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$9.getAttributes(AbstractConfiguredObject.java:1906)
> at
> org.apache.qpid.server.store.JsonFileConfigStore.update(JsonFileConfigStore.java:420)
> at
> org.apache.qpid.server.configuration.store.StoreConfigurationChangeListener.bulkChangeEnd(StoreConfigurationChangeListener.java:98)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.bulkChangeEnd(AbstractConfiguredObject.java:3030)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.changeAttributes(AbstractConfiguredObject.java:3065)
> at
> org.apache.qpid.server.queue.AbstractQueue.changeAttributes(AbstractQueue.java:3369)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$19.setAttributes(AbstractConfiguredObject.java:2914)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$19.execute(AbstractConfiguredObject.java:2896)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$19.execute(AbstractConfiguredObject.java:2889)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.lambda$call$0(TaskExecutorImpl.java:317)
> at java.base/java.security.AccessController.doPrivileged(Native
> Method)
> at java.base/javax.security.auth.Subject.doAs(Subject.java:361)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
> at
> com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:131)
> at
> com.google.common.util.concurrent.InterruptibleTask.run
[jira] [Resolved] (QPID-8666) [Broker-J] Broker plugin jdbc-provider-bone replacement
[ https://issues.apache.org/jira/browse/QPID-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8666. -- Resolution: Implemented > [Broker-J] Broker plugin jdbc-provider-bone replacement > --- > > Key: QPID-8666 > URL: https://issues.apache.org/jira/browse/QPID-8666 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Major > Fix For: qpid-java-broker-9.1.1 > > > Broker plugin jdbc-provider-bone relies on JDBC connection pooling library > bonecp, which is no longer developed or updated. The [github project > page|https://github.com/wwadge/bonecp] states: > "BoneCP is a Java JDBC connection pool implementation that is tuned for high > performance by minimizing lock contention to give greater throughput for your > applications. It beats older connection pools such as C3P0 and DBCP but > should now be considered deprecated in favour of HikariCP". > Plugin jdbc-provider-bone should be replaced with the new one > jdbc-provider-hikaricp based on > [HikariCP|https://github.com/brettwooldridge/HikariCP] library. Both > libraries use Apache-2.0 license. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8663) [Broker-J] Deprecate AESKeyFileEncrypter
[ https://issues.apache.org/jira/browse/QPID-8663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8663. -- Resolution: Implemented > [Broker-J] Deprecate AESKeyFileEncrypter > > > Key: QPID-8663 > URL: https://issues.apache.org/jira/browse/QPID-8663 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > AESKeyFileEncrypter should be marked as deprecated in favor of > AESGCMKeyFileEncrypter, documentation should be updated to discourage usage > of AESKeyFile-based configuration encryption. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8659) [Broker-J] Unit tests in QuerySettingsTest fail under some circumstances
[
https://issues.apache.org/jira/browse/QPID-8659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka resolved QPID-8659.
--
Resolution: Fixed
> [Broker-J] Unit tests in QuerySettingsTest fail under some circumstances
>
>
> Key: QPID-8659
> URL: https://issues.apache.org/jira/browse/QPID-8659
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.1.1
>
>
> Under some circumstance unit tests in QuerySettingsTest fail.
> Stacktrace:
> {code:java}
> [ERROR]
> org.apache.qpid.server.query.engine.parsing.query.QuerySettingsTest.customizeZoneIdViaQueryEngine
> -- Time elapsed: 0.007 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: but was:
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
> at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
> at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31)
> at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:179)
> at
> org.apache.qpid.server.query.engine.parsing.query.QuerySettingsTest.customizeZoneIdViaQueryEngine(QuerySettingsTest.java:278)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8661) [Broker-J] Apache Directory dependencies update
[ https://issues.apache.org/jira/browse/QPID-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8661. -- Resolution: Implemented > [Broker-J] Apache Directory dependencies update > --- > > Key: QPID-8661 > URL: https://issues.apache.org/jira/browse/QPID-8661 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > New version of Apache Directory (2.0.0.AM27) was released, which is used in > broker tests with LDAP. This version removed some kerberos functionality, and > when updating the dependency version refactoring of the affected unit tests > will be needed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8660) Logback logging disabled by inclusion of qpid-broker as a dependency
[
https://issues.apache.org/jira/browse/QPID-8660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8660:
-
Fix Version/s: qpid-java-broker-9.1.1
> Logback logging disabled by inclusion of qpid-broker as a dependency
>
>
> Key: QPID-8660
> URL: https://issues.apache.org/jira/browse/QPID-8660
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.1.0
>Reporter: Adrian Pasternak
>Priority: Minor
> Fix For: qpid-java-broker-9.1.1
>
>
> Adding qpid-broker as a project dependency:
> {code:java}
>
> org.apache.qpid
> qpid-broker
> 9.1.0
> {code}
> Disables all logback logging in the application.
>
> This behavior is caused by a change:
> [https://github.com/apache/qpid-broker-j/blame/9.1.0/broker-plugins/logging-logback/src/main/java/org/apache/qpid/server/logging/logback/NoopConfigurator.java#L33]
>
> Mailing list discussion:
> [https://lists.apache.org/thread/ms9ddg0kstkdh3yq2ytxtdnlq2dyhps1]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8658) [Broker-J] Add Java 21 to the GitHub test matrix
[ https://issues.apache.org/jira/browse/QPID-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8658. -- Resolution: Implemented > [Broker-J] Add Java 21 to the GitHub test matrix > > > Key: QPID-8658 > URL: https://issues.apache.org/jira/browse/QPID-8658 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > To guarantee the compatibility with the future LTS Java version it would be > needed to add Java 21 to the GitHub test matrix along with Java 11 and 17. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8657) [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state
[ https://issues.apache.org/jira/browse/QPID-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8657. -- Resolution: Fixed > [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal > state > --- > > Key: QPID-8657 > URL: https://issues.apache.org/jira/browse/QPID-8657 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > Attachments: aclRequest.json, qpidErrorLog.txt, resultingAcl.json > > > When POSTing an ACL rule with unknown attributes to the Qpid HTTP management > API, the server responds with HTTP 422, Unprocessable Entity. This is > somewhat OK, however, I think maybe a 400 Bad Request would be more > appropriate. > But after the post, the broker is somehow left in a bad internal state, as > the returned Json is incomplete and unparseable. > Example POST in [^aclRequest.json] > Qpid log from the incident [^qpidErrorLog.txt] > Returned Json from subsequent GET [^resultingAcl.json] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8656) [Broker-J] Selector parsing logic error when combining NOT and LIKE
[ https://issues.apache.org/jira/browse/QPID-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8656. -- Resolution: Fixed > [Broker-J] Selector parsing logic error when combining NOT and LIKE > --- > > Key: QPID-8656 > URL: https://issues.apache.org/jira/browse/QPID-8656 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > The JMSSelectorFilter.match() gives unexpected results when combining the > LIKE and NOT operators. > The selector "NOT (entry LIKE '%aaa%')" and value "" returns true, as > expected, > The selector "NOT entry LIKE '%aaa%'" and value "" returns false, whcih > is a bug. > In both cases the method retuns true when the value is "" > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8657) [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal state
[ https://issues.apache.org/jira/browse/QPID-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8657: - Fix Version/s: qpid-java-broker-9.1.1 > [Broker-J] ACL - Posting unknown attributes leaves broker in bad internal > state > --- > > Key: QPID-8657 > URL: https://issues.apache.org/jira/browse/QPID-8657 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Kyrre >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > Attachments: aclRequest.json, qpidErrorLog.txt, resultingAcl.json > > > When POSTing an ACL rule with unknown attributes to the Qpid HTTP management > API, the server responds with HTTP 422, Unprocessable Entity. This is > somewhat OK, however, I think maybe a 400 Bad Request would be more > appropriate. > But after the post, the broker is somehow left in a bad internal state, as > the returned Json is incomplete and unparseable. > Example POST in [^aclRequest.json] > Qpid log from the incident [^qpidErrorLog.txt] > Returned Json from subsequent GET [^resultingAcl.json] > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8655) [Broker-J] Dependency updates for version 9.1.x
[ https://issues.apache.org/jira/browse/QPID-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8655: - Fix Version/s: qpid-java-broker-9.1.1 > [Broker-J] Dependency updates for version 9.1.x > --- > > Key: QPID-8655 > URL: https://issues.apache.org/jira/browse/QPID-8655 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.1.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.1 > > > This Jira should serve for broker-j dependency updates for release 9.1.1 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8648) [Broker-J] Allow for max frame size >4096 before Open frame (SASL)
[
https://issues.apache.org/jira/browse/QPID-8648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8648:
-
Fix Version/s: qpid-java-broker-9.1.1
> [Broker-J] Allow for max frame size >4096 before Open frame (SASL)
> --
>
> Key: QPID-8648
> URL: https://issues.apache.org/jira/browse/QPID-8648
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Dan Langford
>Priority: Major
> Fix For: qpid-java-broker-9.1.1
>
>
> some modern authentication options (XOAUTH2 + JWT) require frames larger then
> 4096. consider if the max frame size (before an Open frame negotiation)
> should be larger or should be configurable with some sort of configuration or
> env variable.
>
> from a discussion on the mailing list
> {quote}The SASL process occurs first, before the Open frame. The Open frames
> are what carries each peers advertised max frame size, mainly aimed at
> later message deliveries. The AMQP 1.0 spec defines before this
> however that the SASL frames can be at-most the 'min max frame size',
> which is fixed at 512 bytes, with no way to negotiate anything larger.
> As you can probably tell, that presents a problem if things in the
> SASL negotiation want to be larger, such as is likely in e.g a newer
> XOAUTH2 mechanism that didnt exist when that decision was originally
> made.
> To simply allow some of these newer alternative mechs to work, it was
> decided to just allow things to exceed the 512byte limit since both
> sides would have to already agree on using a given mech to begin with,
> so doing an alternative like creating a custom multi-challenge
> batching sequence to shuffle the bytes wasnt really going to be adding
> much except significant complexity.
> It appears broker-j allows up to 4096, and you have now found
> something to exceed even that. It doesnt look like it allows
> configuring it, but increasing that seems to be the only option that
> would help here.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Qpid broker Logback dependency
Hi Serhii,
Apache Qpid Broker-J 9.1.0 has just been released. Using the new version should
help as it contains logback 1.4.11.
Regards,
Tomas
On 2023/09/05 10:10:23 Serhii Zhura wrote:
> Hello.
>
> Maybe I should clarify for you where the issue is. When I'm using Logback
> with version 1.4.x+ inside my project, I got an error from
> "org.apache.qpid.server.logging.logback.NoopConfigurator".
> Error is connected with the overridden method "configure". It looks like
> that:
>
> @Override
> public void configure(LoggerContext loggerContext)
> {
> // no-op
> }
>
> But should look like this:
>
>
>
> On Mon, Sep 4, 2023 at 6:53 PM Serhii Zhura
> wrote:
>
> > Hello.
> >
> > I'm using Qpid Broker (9.0.0) together with Spring Boot 3.
> > From your side it is important to have Logback dependency with version
> > 1.2.11 and from Spring Boot side it must be higher than 1.4.x. How can I
> > deal with that? Can you upgrade the Logback version or can I do it myself
> > to be comparable with your API? If I will you 1.4.x+ right now, I will get
> > runtime error from your side which is connected with
> > "org.apache.qpid.server.logging.logback.NoopConfigurator".
> >
> > Regards,
> > Serhii Zhura
> >
>
> --
> Disclaimer: This message (including any attachments) contains confidential
> information intended for a specific individual and purpose and is protected
> by law. If you are not the intended recipient, please let us know on
> operati...@panenco.com . You should delete
> this message and are hereby notified that any disclosure, copying, or
> distribution of this message, or the taking of any action based on it, is
> strictly prohibited.
>
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[ANNOUNCE] Apache Qpid Broker-J 9.1.0 released
The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Broker-J 9.1.0. This is the latest release of pure java implementation of messaging broker supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org) and legacy AMQP protocols 0-10, 0-91, 0-9 and 0-8. Please visit Qpid project site for more details: http://qpid.apache.org/components/broker-j/index.html The release is available now from our website: http://qpid.apache.org/download.html The release brings bug fixes and improvements. The release notes can be found at: http://qpid.apache.org/releases/qpid-broker-j-9.1.0/release-notes.html Thanks to all involved, Qpid Team - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8653) [Broker-J] Code cleanup: collection type arguments, collection factory methods, lambdas
[ https://issues.apache.org/jira/browse/QPID-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8653. > [Broker-J] Code cleanup: collection type arguments, collection factory > methods, lambdas > --- > > Key: QPID-8653 > URL: https://issues.apache.org/jira/browse/QPID-8653 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > Following issues are covered with this JIRA: > 1. Explicit collection type arguments can be replaced with diamond notation > to shorten the code and to make it more readable. > 2. Empty collection methods should be refactored using java 11 factory > methods where appropriate. > 3. Anonymous types should be replaced with lambdas or method references where > appropriate. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8622) [Broker-J] Documentation about BDB licensing
[ https://issues.apache.org/jira/browse/QPID-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8622. > [Broker-J] Documentation about BDB licensing > > > Key: QPID-8622 > URL: https://issues.apache.org/jira/browse/QPID-8622 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, > qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, qpid-java-broker-7.1.0, > qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, qpid-java-broker-7.0.6, > qpid-java-broker-7.0.7, qpid-java-broker-8.0.0, qpid-java-broker-7.1.1, > qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, > qpid-java-broker-7.1.4, qpid-java-broker-7.0.9, qpid-java-broker-7.1.5, > qpid-java-broker-7.1.6, qpid-java-broker-7.1.7, qpid-java-broker-7.1.8, > qpid-java-broker-8.0.1, qpid-java-broker-7.1.9, qpid-java-broker-8.0.2, > qpid-java-broker-7.1.10, qpid-java-broker-8.0.3, qpid-java-broker-7.1.11, > qpid-java-broker-8.0.4, qpid-java-broker-7.1.12, qpid-java-broker-8.0.5, > qpid-java-broker-8.0.6, qpid-java-broker-9.0.0 >Reporter: Dan Langford >Priority: Trivial > Fix For: qpid-java-broker-9.1.0 > > > under section *9.11.3.4 Message Store* the broker book states > > Note that due to licensing concerns Qpid does not ship the BDB JE jar files. > [https://qpid.apache.org/releases/qpid-broker-j-9.0.0/book/Java-Broker-Runtime-Memory.html] > This is incorrect as of Broker-J 7.0.0 when Broker-J started shipping with > the BDB JE jar. > See QPID-7724 > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8654) [Broker-J] Delayed delivery producers data not displayed correctly in REST API
[ https://issues.apache.org/jira/browse/QPID-8654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8654. > [Broker-J] Delayed delivery producers data not displayed correctly in REST API > -- > > Key: QPID-8654 > URL: https://issues.apache.org/jira/browse/QPID-8654 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > In QPID-8602 there was added functionality to display producer details in > REST API, which doesn't consider delayed delivery cases. Their support should > be added. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8650) [Broker-J] JUnit 5 tests refactoring for broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-0-10
[ https://issues.apache.org/jira/browse/QPID-8650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8650. > [Broker-J] JUnit 5 tests refactoring for > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-0-10 > - > > Key: QPID-8650 > URL: https://issues.apache.org/jira/browse/QPID-8650 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses modules > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-0-10 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8645) [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-0-8-protocol
[ https://issues.apache.org/jira/browse/QPID-8645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8645. > [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-0-8-protocol > - > > Key: QPID-8645 > URL: https://issues.apache.org/jira/browse/QPID-8645 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses module broker-plugins/amqp-0-8-protocol -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8644) [Broker-J] JUnit 5 tests refactoring for broker-plugins/access-control
[ https://issues.apache.org/jira/browse/QPID-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8644. > [Broker-J] JUnit 5 tests refactoring for broker-plugins/access-control > -- > > Key: QPID-8644 > URL: https://issues.apache.org/jira/browse/QPID-8644 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests > ([QPID-8615|https://issues.apache.org/jira/browse/QPID-8615]), code of > separate modules should be refactored to take advantage of JUnit 5 features. > This Jira addresses module broker-plugins/access-control -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8652) [Broker-J] JUnit 5 tests refactoring for broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-10-to-1-0
[ https://issues.apache.org/jira/browse/QPID-8652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8652. > [Broker-J] JUnit 5 tests refactoring for > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-10-to-1-0 > - > > Key: QPID-8652 > URL: https://issues.apache.org/jira/browse/QPID-8652 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses modules > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-10-to-1-0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8649) [Broker-J] JUnit 5 tests refactoring for amqp-1-0-bdb-store and amqp-1-0-jdbc-store
[ https://issues.apache.org/jira/browse/QPID-8649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8649. > [Broker-J] JUnit 5 tests refactoring for amqp-1-0-bdb-store and > amqp-1-0-jdbc-store > --- > > Key: QPID-8649 > URL: https://issues.apache.org/jira/browse/QPID-8649 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses modules broker-plugins/amqp-1-0-bdb-store and > broker-plugins/amqp-1-0-jdbc-store -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8647) [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-1-0-protocol
[ https://issues.apache.org/jira/browse/QPID-8647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8647. > [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-1-0-protocol > - > > Key: QPID-8647 > URL: https://issues.apache.org/jira/browse/QPID-8647 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses module broker-plugins/amqp-1-0-protocol -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8651) [Broker-J] JUnit 5 tests refactoring for broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-1-0
[ https://issues.apache.org/jira/browse/QPID-8651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8651. > [Broker-J] JUnit 5 tests refactoring for > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-1-0 > > > Key: QPID-8651 > URL: https://issues.apache.org/jira/browse/QPID-8651 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses modules > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-1-0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8640) [Broker-J] Remove producer on link destruction
[
https://issues.apache.org/jira/browse/QPID-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8640.
> [Broker-J] Remove producer on link destruction
> --
>
> Key: QPID-8640
> URL: https://issues.apache.org/jira/browse/QPID-8640
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.1.0
>
>
> In some test scenarios following error is thrown on the client side:
> {code:java}
> proton._utils.LinkDetached: sender
> c83ab7c1-a1f4-4d3d-b7f9-527fabf9e9dd-broadcast to broadcast closed due to:
> Condition('amqp:internal-error', 'Child of type ProducerImpl already exists
> with name of c83ab7c1-a1f4-4d3d-b7f9-527fabf9e9dd-broadcast'){code}
> It seems, that producer is closed after calling sender.close() on the client
> side, but still remains to be a child of an appropriate AMQP session in
> closed state, preventing producer with the same name to be created.
> StandardReceivingLinkEndpoint#destroy() should be extended with the producer
> removal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8646) [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-0-10-protocol
[ https://issues.apache.org/jira/browse/QPID-8646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8646. > [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-0-10-protocol > -- > > Key: QPID-8646 > URL: https://issues.apache.org/jira/browse/QPID-8646 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses module broker-plugins/amqp-0-10-protocol -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8620) [Broker-J] HTTP management plugin can reveal system data or debug information
[ https://issues.apache.org/jira/browse/QPID-8620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8620. > [Broker-J] HTTP management plugin can reveal system data or debug information > - > > Key: QPID-8620 > URL: https://issues.apache.org/jira/browse/QPID-8620 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > The function writeObjectToResponse() in AbstractServlet.java reveals system > data or debug information by calling writeValue(). AbstractServlet, > RestServlet and QueryServlet return error details on exceptions. The error > details should be logged instead and a generic error message should be return > in the HttpServletResponse. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8626) [Broker-J] Dependency updates
[ https://issues.apache.org/jira/browse/QPID-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8626. > [Broker-J] Dependency updates > - > > Key: QPID-8626 > URL: https://issues.apache.org/jira/browse/QPID-8626 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > This Jira should serve for broker-j dependency updates for release 9.0.1 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8625) [Broker-J] ACL rules require full DN when using LDAP authentication
[
https://issues.apache.org/jira/browse/QPID-8625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8625.
> [Broker-J] ACL rules require full DN when using LDAP authentication
> ---
>
> Key: QPID-8625
> URL: https://issues.apache.org/jira/browse/QPID-8625
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.1.0
>
>
> Currently a reference to a LDAP user in ACL rules requires full DN, e.g.:
> {code:java}
> ACL ALLOW "cn=danlangford,ou=000,ou=People,o=MyEnterprise" ALL {code}
> It would be beneficial to allow usage of a CN instead:
> {code:java}
> ACL ALLOW "cn=danlangford" ALL {code}
> or
> {code:java}
> ACL ALLOW danlangford ALL {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8617) [Broker-J] Jetty server dependencies update
[ https://issues.apache.org/jira/browse/QPID-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8617. > [Broker-J] Jetty server dependencies update > --- > > Key: QPID-8617 > URL: https://issues.apache.org/jira/browse/QPID-8617 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > Jetty Server 9.x has reached end of community support ([github > issue|https://github.com/eclipse/jetty.project/issues/7958]). Current Jetty > version should be updated either to 10.x or 11.x. Considering that Jetty 12.x > is currently in alpha version, it would be preferable to update it to the > latest version available (11.x) to make easier further updates. > Update will include > * dependencies update > * namespaces update (javax.servlet.* migrated to jakarta.servlet.*) > * code refactoring (in few cases it may be needed to refactor logic in favor > of more actual Jetty mechanisms) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8616) [Broker-J] Privacy Violation: Heap Inspection in ManagedUser
[ https://issues.apache.org/jira/browse/QPID-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8616. > [Broker-J] Privacy Violation: Heap Inspection in ManagedUser > > > Key: QPID-8616 > URL: https://issues.apache.org/jira/browse/QPID-8616 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > Sensitive data (such as passwords) stored in memory can be leaked if memory > is not cleared after use. Often, Strings are used store sensitive data, > however, since String objects are immutable, removing the value of a String > from memory can only be done by the JVM garbage collector. The garbage > collector is not required to run unless the JVM is low on memory, so there is > no guarantee as to when garbage collection will take place. In the event of > an application crash, a memory dump of the application might reveal sensitive > data. > Approach used in QPID-8583 should be applied to class ManagedUser. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8618) [Broker-J] ACL check on link stealing
[ https://issues.apache.org/jira/browse/QPID-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8618. > [Broker-J] ACL check on link stealing > - > > Key: QPID-8618 > URL: https://issues.apache.org/jira/browse/QPID-8618 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > [AMQP 1.0 > Standard|http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-complete-v1.0-os.pdf] > section *2.6.1 Naming A Link* describes how to name a link and its > "stealing" in case of connection loss. > Java broker does support link "stealing" but it seems like that broker does > not verify whether the client attempting to "steal" the link is authorized to > do so. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8615) [Broker-J] JUnit 5 migration
[ https://issues.apache.org/jira/browse/QPID-8615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8615. > [Broker-J] JUnit 5 migration > > > Key: QPID-8615 > URL: https://issues.apache.org/jira/browse/QPID-8615 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > Broker-J currently uses JUnit 4 for unit tests as well as the system tests. > Although JUnit 4 is still being supported, it seemingly will be not developed > as actively as JUnit 5. Many open source projects are in process of migration > to JUnit 5 are have already finished the migration (see [Apache Jira > tickets|https://issues.apache.org/jira/issues/?filter=-2=text%20~%20%22junit5%20migrate%22%20order%20by%20created%20DESC]). > Migration should cover > # Dependencies update > # Migration of base junit tests class UnitTestBase and junit 4 class > QpidUnitTestRunner > # Migration of junit 4 rules to junit 5 extensions > # Annotation changes -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8621) [Broker-J] Add operation "resetStatistics" to Producer
[ https://issues.apache.org/jira/browse/QPID-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8621. > [Broker-J] Add operation "resetStatistics" to Producer > -- > > Key: QPID-8621 > URL: https://issues.apache.org/jira/browse/QPID-8621 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > QPID-8603 added functionality for resetting broker object statistics, > QPID-8602 added functionality to display producers in broker REST API. > There should be added functionality for resetting statistics for a producer > as well. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8614) [Broker-J] Deprecated reflection methods
[
https://issues.apache.org/jira/browse/QPID-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8614.
> [Broker-J] Deprecated reflection methods
>
>
> Key: QPID-8614
> URL: https://issues.apache.org/jira/browse/QPID-8614
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.1.0
>
>
> After migration to JDK 11 new deprecation warnings are seen during the broker
> build:
> {code:java}
> newInstance() in java.lang.Class has been deprecated
> {code}
> {code:java}
> isAccessible() in java.lang.reflect.AccessibleObject has been deprecated
> {code}
> The code should be refactored where applicable to get rid of them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8624) [Broker-J] Unable to auto generate self signed certificate on Java17
[
https://issues.apache.org/jira/browse/QPID-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8624.
> [Broker-J] Unable to auto generate self signed certificate on Java17
>
>
> Key: QPID-8624
> URL: https://issues.apache.org/jira/browse/QPID-8624
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Major
> Fix For: qpid-java-broker-9.1.0
>
>
> When trying to autogenerate a keystore with self signed certificate on java
> 17 environment following error is thrown:
> {code:java}
> org.apache.qpid.server.configuration.IllegalConfigurationException: Unable to
> construct keystore
> at
> org.apache.qpid.server.security.AutoGeneratedSelfSignedKeyStoreImpl.generatePrivateKeyAndCertificate(AutoGeneratedSelfSignedKeyStoreImpl.java:296)
>
> at
> org.apache.qpid.server.security.AutoGeneratedSelfSignedKeyStoreImpl.postResolve(AutoGeneratedSelfSignedKeyStoreImpl.java:169)
>
> Caused by: java.lang.IllegalAccessException: class
> org.apache.qpid.server.transport.network.security.ssl.SSLUtil cannot access
> class sun.security.tools.keytool.CertAndKeyGen (in module java.base) because
> module java.base does not export sun.security.tools.keytool to unnamed module
> @6b37576e at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Unknown
> Source) at java.base/java.lang.reflect.AccessibleObject.checkAccess(Unknown
> Source){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8613) [Broker-J] Update slf4j / logback dependencies
[ https://issues.apache.org/jira/browse/QPID-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka closed QPID-8613. > [Broker-J] Update slf4j / logback dependencies > -- > > Key: QPID-8613 > URL: https://issues.apache.org/jira/browse/QPID-8613 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > Slf4j and Logback dependencies should be updated to the latest version. It > would require small code changes due to the change in logback > ch.qos.logback.classic.spi.Configurator interface contract. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8623) [Broker-J] AESKeyFile encryption breaks SimpleLDAPAuthenticationManager user search
[
https://issues.apache.org/jira/browse/QPID-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka closed QPID-8623.
> [Broker-J] AESKeyFile encryption breaks SimpleLDAPAuthenticationManager user
> search
> ---
>
> Key: QPID-8623
> URL: https://issues.apache.org/jira/browse/QPID-8623
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Major
> Fix For: qpid-java-broker-9.1.0
>
>
> When enabling AESKeyFile configuration encryption and trying to authenticate
> via SimpleLDAPAuthenticationManager an error happens with the following
> stacktrace:
>
> {code:java}
> 2023-02-14T20:58:22,270Z WARN [qtp453021524-123]
> (o.a.q.s.s.a.m.SimpleLDAPAuthenticationManagerImpl) - Retrieving LDAP name
> for user 'xx' resulted in error.
> javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308:
> LdapErr: DSID-0C090439, comment: AcceptSecurityContext error, data 52e, v4563
> ]
> at java.naming/com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3259)
> at java.naming/com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3205)
> at java.naming/com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2991)
> at java.naming/com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2905)
> at java.naming/com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:348)
> at
> java.naming/com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxFromUrl(LdapCtxFactory.java:266)
> at
> java.naming/com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:226)
> at
> java.naming/com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:284)
> at
> java.naming/com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:185)
> at
> java.naming/com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:115)
> at
> java.naming/javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:730)
> at
> java.naming/javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305)
> at java.naming/javax.naming.InitialContext.init(InitialContext.java:236)
> at java.naming/javax.naming.InitialContext.(InitialContext.java:208)
> at
> java.naming/javax.naming.directory.InitialDirContext.(InitialDirContext.java:101)
> at
> org.apache.qpid.server.security.auth.manager.SimpleLDAPAuthenticationManagerImpl.lambda$createInitialDirContext$2(SimpleLDAPAuthenticationManagerImpl.java:602)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at java.base/javax.security.auth.Subject.doAs(Subject.java:423)
> at
> org.apache.qpid.server.security.auth.manager.SimpleLDAPAuthenticationManagerImpl.invokeContextOperationAs(SimpleLDAPAuthenticationManagerImpl.java:796)
> at
> org.apache.qpid.server.security.auth.manager.SimpleLDAPAuthenticationManagerImpl.createInitialDirContext(SimpleLDAPAuthenticationManagerImpl.java:602)
> {code}
> It seems that AESKeyFile encryption might not be working correctly with
> SimpleLDAP: perhaps the password is encrypted in the config.json isn't being
> decrypted before LDAP is checked.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8624) [Broker-J] Unable to auto generate self signed certificate on Java17
[
https://issues.apache.org/jira/browse/QPID-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8624:
-
Summary: [Broker-J] Unable to auto generate self signed certificate on
Java17 (was: [Broker-J] Unable to auto generate self signed certificate on
Java17)
> [Broker-J] Unable to auto generate self signed certificate on Java17
>
>
> Key: QPID-8624
> URL: https://issues.apache.org/jira/browse/QPID-8624
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Major
> Fix For: qpid-java-broker-9.1.0
>
>
> When trying to autogenerate a keystore with self signed certificate on java
> 17 environment following error is thrown:
> {code:java}
> org.apache.qpid.server.configuration.IllegalConfigurationException: Unable to
> construct keystore
> at
> org.apache.qpid.server.security.AutoGeneratedSelfSignedKeyStoreImpl.generatePrivateKeyAndCertificate(AutoGeneratedSelfSignedKeyStoreImpl.java:296)
>
> at
> org.apache.qpid.server.security.AutoGeneratedSelfSignedKeyStoreImpl.postResolve(AutoGeneratedSelfSignedKeyStoreImpl.java:169)
>
> Caused by: java.lang.IllegalAccessException: class
> org.apache.qpid.server.transport.network.security.ssl.SSLUtil cannot access
> class sun.security.tools.keytool.CertAndKeyGen (in module java.base) because
> module java.base does not export sun.security.tools.keytool to unnamed module
> @6b37576e at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Unknown
> Source) at java.base/java.lang.reflect.AccessibleObject.checkAccess(Unknown
> Source){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8654) [Broker-J] Delayed delivery producers data not displayed correctly in REST API
[ https://issues.apache.org/jira/browse/QPID-8654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka resolved QPID-8654. -- Resolution: Implemented > [Broker-J] Delayed delivery producers data not displayed correctly in REST API > -- > > Key: QPID-8654 > URL: https://issues.apache.org/jira/browse/QPID-8654 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > In QPID-8602 there was added functionality to display producer details in > REST API, which doesn't consider delayed delivery cases. Their support should > be added. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8654) [Broker-J] Delayed delivery producers data not displayed correctly in REST API
[ https://issues.apache.org/jira/browse/QPID-8654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8654: - Affects Version/s: qpid-java-broker-9.0.0 (was: qpid-java-broker-9.1.0) > [Broker-J] Delayed delivery producers data not displayed correctly in REST API > -- > > Key: QPID-8654 > URL: https://issues.apache.org/jira/browse/QPID-8654 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > > In QPID-8602 there was added functionality to display producer details in > REST API, which doesn't consider delayed delivery cases. Their support should > be added. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8654) [Broker-J] Delayed delivery producers data not displayed correctly in REST API
[ https://issues.apache.org/jira/browse/QPID-8654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8654: - Fix Version/s: qpid-java-broker-9.1.0 > [Broker-J] Delayed delivery producers data not displayed correctly in REST API > -- > > Key: QPID-8654 > URL: https://issues.apache.org/jira/browse/QPID-8654 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > In QPID-8602 there was added functionality to display producer details in > REST API, which doesn't consider delayed delivery cases. Their support should > be added. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8622) [Broker-J] Documentation about BDB licensing
[ https://issues.apache.org/jira/browse/QPID-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8622: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] Documentation about BDB licensing > > > Key: QPID-8622 > URL: https://issues.apache.org/jira/browse/QPID-8622 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, > qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, qpid-java-broker-7.1.0, > qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, qpid-java-broker-7.0.6, > qpid-java-broker-7.0.7, qpid-java-broker-8.0.0, qpid-java-broker-7.1.1, > qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, > qpid-java-broker-7.1.4, qpid-java-broker-7.0.9, qpid-java-broker-7.1.5, > qpid-java-broker-7.1.6, qpid-java-broker-7.1.7, qpid-java-broker-7.1.8, > qpid-java-broker-8.0.1, qpid-java-broker-7.1.9, qpid-java-broker-8.0.2, > qpid-java-broker-7.1.10, qpid-java-broker-8.0.3, qpid-java-broker-7.1.11, > qpid-java-broker-8.0.4, qpid-java-broker-7.1.12, qpid-java-broker-8.0.5, > qpid-java-broker-8.0.6, qpid-java-broker-9.0.0 >Reporter: Dan Langford >Priority: Trivial > Fix For: qpid-java-broker-9.1.0 > > > under section *9.11.3.4 Message Store* the broker book states > > Note that due to licensing concerns Qpid does not ship the BDB JE jar files. > [https://qpid.apache.org/releases/qpid-broker-j-9.0.0/book/Java-Broker-Runtime-Memory.html] > This is incorrect as of Broker-J 7.0.0 when Broker-J started shipping with > the BDB JE jar. > See QPID-7724 > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8649) [Broker-J] JUnit 5 tests refactoring for amqp-1-0-bdb-store and amqp-1-0-jdbc-store
[ https://issues.apache.org/jira/browse/QPID-8649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8649: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] JUnit 5 tests refactoring for amqp-1-0-bdb-store and > amqp-1-0-jdbc-store > --- > > Key: QPID-8649 > URL: https://issues.apache.org/jira/browse/QPID-8649 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses modules broker-plugins/amqp-1-0-bdb-store and > broker-plugins/amqp-1-0-jdbc-store -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8653) [Broker-J] Code cleanup: collection type arguments, collection factory methods, lambdas
[ https://issues.apache.org/jira/browse/QPID-8653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8653: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] Code cleanup: collection type arguments, collection factory > methods, lambdas > --- > > Key: QPID-8653 > URL: https://issues.apache.org/jira/browse/QPID-8653 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > Following issues are covered with this JIRA: > 1. Explicit collection type arguments can be replaced with diamond notation > to shorten the code and to make it more readable. > 2. Empty collection methods should be refactored using java 11 factory > methods where appropriate. > 3. Anonymous types should be replaced with lambdas or method references where > appropriate. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8651) [Broker-J] JUnit 5 tests refactoring for broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-1-0
[ https://issues.apache.org/jira/browse/QPID-8651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8651: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] JUnit 5 tests refactoring for > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-1-0 > > > Key: QPID-8651 > URL: https://issues.apache.org/jira/browse/QPID-8651 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses modules > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-1-0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8652) [Broker-J] JUnit 5 tests refactoring for broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-10-to-1-0
[ https://issues.apache.org/jira/browse/QPID-8652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8652: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] JUnit 5 tests refactoring for > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-10-to-1-0 > - > > Key: QPID-8652 > URL: https://issues.apache.org/jira/browse/QPID-8652 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses modules > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-10-to-1-0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8650) [Broker-J] JUnit 5 tests refactoring for broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-0-10
[ https://issues.apache.org/jira/browse/QPID-8650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8650: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] JUnit 5 tests refactoring for > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-0-10 > - > > Key: QPID-8650 > URL: https://issues.apache.org/jira/browse/QPID-8650 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses modules > broker-plugins/qpid-broker-plugins-amqp-msg-conv-0-8-to-0-10 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8646) [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-0-10-protocol
[ https://issues.apache.org/jira/browse/QPID-8646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8646: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-0-10-protocol > -- > > Key: QPID-8646 > URL: https://issues.apache.org/jira/browse/QPID-8646 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses module broker-plugins/amqp-0-10-protocol -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8647) [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-1-0-protocol
[ https://issues.apache.org/jira/browse/QPID-8647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8647: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-1-0-protocol > - > > Key: QPID-8647 > URL: https://issues.apache.org/jira/browse/QPID-8647 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses module broker-plugins/amqp-1-0-protocol -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8640) [Broker-J] Remove producer on link destruction
[
https://issues.apache.org/jira/browse/QPID-8640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8640:
-
Fix Version/s: qpid-java-broker-9.1.0
(was: qpid-java-broker-9.0.1)
> [Broker-J] Remove producer on link destruction
> --
>
> Key: QPID-8640
> URL: https://issues.apache.org/jira/browse/QPID-8640
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.1.0
>
>
> In some test scenarios following error is thrown on the client side:
> {code:java}
> proton._utils.LinkDetached: sender
> c83ab7c1-a1f4-4d3d-b7f9-527fabf9e9dd-broadcast to broadcast closed due to:
> Condition('amqp:internal-error', 'Child of type ProducerImpl already exists
> with name of c83ab7c1-a1f4-4d3d-b7f9-527fabf9e9dd-broadcast'){code}
> It seems, that producer is closed after calling sender.close() on the client
> side, but still remains to be a child of an appropriate AMQP session in
> closed state, preventing producer with the same name to be created.
> StandardReceivingLinkEndpoint#destroy() should be extended with the producer
> removal.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8644) [Broker-J] JUnit 5 tests refactoring for broker-plugins/access-control
[ https://issues.apache.org/jira/browse/QPID-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8644: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] JUnit 5 tests refactoring for broker-plugins/access-control > -- > > Key: QPID-8644 > URL: https://issues.apache.org/jira/browse/QPID-8644 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests > ([QPID-8615|https://issues.apache.org/jira/browse/QPID-8615]), code of > separate modules should be refactored to take advantage of JUnit 5 features. > This Jira addresses module broker-plugins/access-control -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8645) [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-0-8-protocol
[ https://issues.apache.org/jira/browse/QPID-8645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8645: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] JUnit 5 tests refactoring for broker-plugins/amqp-0-8-protocol > - > > Key: QPID-8645 > URL: https://issues.apache.org/jira/browse/QPID-8645 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > After migration of unit tests (QPID-8615), code of separate modules should be > refactored to take advantage of JUnit 5 features. > This Jira addresses module broker-plugins/amqp-0-8-protocol -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8626) [Broker-J] Dependency updates
[ https://issues.apache.org/jira/browse/QPID-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8626: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] Dependency updates > - > > Key: QPID-8626 > URL: https://issues.apache.org/jira/browse/QPID-8626 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > This Jira should serve for broker-j dependency updates for release 9.0.1 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8625) [Broker-J] ACL rules require full DN when using LDAP authentication
[
https://issues.apache.org/jira/browse/QPID-8625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8625:
-
Fix Version/s: qpid-java-broker-9.1.0
(was: qpid-java-broker-9.0.1)
> [Broker-J] ACL rules require full DN when using LDAP authentication
> ---
>
> Key: QPID-8625
> URL: https://issues.apache.org/jira/browse/QPID-8625
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Affects Versions: qpid-java-broker-9.0.0
>Reporter: Daniil Kirilyuk
>Priority: Minor
> Fix For: qpid-java-broker-9.1.0
>
>
> Currently a reference to a LDAP user in ACL rules requires full DN, e.g.:
> {code:java}
> ACL ALLOW "cn=danlangford,ou=000,ou=People,o=MyEnterprise" ALL {code}
> It would be beneficial to allow usage of a CN instead:
> {code:java}
> ACL ALLOW "cn=danlangford" ALL {code}
> or
> {code:java}
> ACL ALLOW danlangford ALL {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8621) [Broker-J] Add operation "resetStatistics" to Producer
[ https://issues.apache.org/jira/browse/QPID-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8621: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] Add operation "resetStatistics" to Producer > -- > > Key: QPID-8621 > URL: https://issues.apache.org/jira/browse/QPID-8621 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > QPID-8603 added functionality for resetting broker object statistics, > QPID-8602 added functionality to display producers in broker REST API. > There should be added functionality for resetting statistics for a producer > as well. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8620) [Broker-J] HTTP management plugin can reveal system data or debug information
[ https://issues.apache.org/jira/browse/QPID-8620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8620: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] HTTP management plugin can reveal system data or debug information > - > > Key: QPID-8620 > URL: https://issues.apache.org/jira/browse/QPID-8620 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > The function writeObjectToResponse() in AbstractServlet.java reveals system > data or debug information by calling writeValue(). AbstractServlet, > RestServlet and QueryServlet return error details on exceptions. The error > details should be logged instead and a generic error message should be return > in the HttpServletResponse. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8618) [Broker-J] ACL check on link stealing
[ https://issues.apache.org/jira/browse/QPID-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8618: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] ACL check on link stealing > - > > Key: QPID-8618 > URL: https://issues.apache.org/jira/browse/QPID-8618 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > [AMQP 1.0 > Standard|http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-complete-v1.0-os.pdf] > section *2.6.1 Naming A Link* describes how to name a link and its > "stealing" in case of connection loss. > Java broker does support link "stealing" but it seems like that broker does > not verify whether the client attempting to "steal" the link is authorized to > do so. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8616) [Broker-J] Privacy Violation: Heap Inspection in ManagedUser
[ https://issues.apache.org/jira/browse/QPID-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8616: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] Privacy Violation: Heap Inspection in ManagedUser > > > Key: QPID-8616 > URL: https://issues.apache.org/jira/browse/QPID-8616 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > Sensitive data (such as passwords) stored in memory can be leaked if memory > is not cleared after use. Often, Strings are used store sensitive data, > however, since String objects are immutable, removing the value of a String > from memory can only be done by the JVM garbage collector. The garbage > collector is not required to run unless the JVM is low on memory, so there is > no guarantee as to when garbage collection will take place. In the event of > an application crash, a memory dump of the application might reveal sensitive > data. > Approach used in QPID-8583 should be applied to class ManagedUser. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8617) [Broker-J] Jetty server dependencies update
[ https://issues.apache.org/jira/browse/QPID-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Vavricka updated QPID-8617: - Fix Version/s: qpid-java-broker-9.1.0 (was: qpid-java-broker-9.0.1) > [Broker-J] Jetty server dependencies update > --- > > Key: QPID-8617 > URL: https://issues.apache.org/jira/browse/QPID-8617 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-9.0.0 >Reporter: Daniil Kirilyuk >Priority: Minor > Fix For: qpid-java-broker-9.1.0 > > > Jetty Server 9.x has reached end of community support ([github > issue|https://github.com/eclipse/jetty.project/issues/7958]). Current Jetty > version should be updated either to 10.x or 11.x. Considering that Jetty 12.x > is currently in alpha version, it would be preferable to update it to the > latest version available (11.x) to make easier further updates. > Update will include > * dependencies update > * namespaces update (javax.servlet.* migrated to jakarta.servlet.*) > * code refactoring (in few cases it may be needed to refactor logic in favor > of more actual Jetty mechanisms) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
