Emmanuel Hugonnet

[WFCORE-4603]: Replace Deployment --runtime-name option not working.

* Taking the runtime-name into account when replacing 2 deployments.

Jira: https://issues.jboss.org/browse/WFCORE-4603

[WFLY-12326]: Messaging subsystem model version bump.

* Updating Model Version to 8.0.0

Jira: https://issues.jboss.org/browse/WFLY-12326

[WFLY-12326]: Messaging subsystem model version bump.

* Updating Model Version to 8.0.0

Jira: https://issues.jboss.org/browse/WFLY-12326

[WFLY-5286]: Provide CLI operation which returns used journal type - NIOxASYNCIO

Adding a new runtime-journal-type attribute to define the effective

journal type being used.

Jira: https://issues.jboss.org/browse/WFLY-5286

[WFLY-12252]: Add metric type flags on messaging subsytem metrics.

* Adding the missing flags

Jira: https://issues.jboss.org/browse/WFLY-12252

[WFLY-12105]: Upgrade Apache Artemis from 2.8.0.Final to 2.8.1.Final.

* Upgrading Apache Artemis to 2.8.1

Jira: https://issues.jboss.org/browse/WFLY-12105

[WFLY-12174]: Configure internal broker not to check for configuration changes.

* Setting the configurationFileRefreshPeriod to -1 to avoid reloading of

logging.properties

Jira: https://issues.jboss.org/browse/WFLY-12174

[WFLY-11727]: QPid Proton-J version is lagging behind.

* Aligning with Apache Artemis 2.8.0 version pof proton-j

Jira: https://issues.jboss.org/browse/WFLY-11727

[WFLY-11727]: QPid Proton-J version is lagging behind.

* Aligning with Apache Artemis 2.8.0 version pof proton-j

Jira: https://issues.jboss.org/browse/WFLY-11727

[WFLY-12038]: Expose the enable1Prefixes configuration on external (pooled) connection factories.

* Adding a new attribute 'enable-amq1-prefix' on external connection

factories to override the use of those compatibility prefixes when

connecting to a remote artemis broker.

Jira: https://issues.jboss.org/browse/WFLY-12038

[WFLY-11876]: Upgrade Artemis to 2.8.0

* updating to Apache Artemis 2.8.0

* taking new artemis native packaging into account

Jira: https://issues.jboss.org/browse/WFLY-11876

[WFLY-11876]: Upgrade Artemis to 2.8.0

* updating to Apache Artemis 2.8.0

* taking new artemis native packaging into account

Jira: https://issues.jboss.org/browse/WFLY-11876

[WFLY-11851]: Adding a system property to define the default routing type of core queues.

Adding 'org.wildfly.messaging.core.queue.default.routing-type' so that

we can define the default routing type of core queues.

Jira: https://issues.jboss.org/browse/WFLY-11851

[WFLY-11789]: Intermittent failures in NotClosingInjectedContextTestCase.

Ensuring that we get the destination before sending to it.

Jira: https://issues.jboss.org/browse/WFLY-11789

[WFLY-11789]: Intermittent failures in NotClosingInjectedContextTestCase.

Ensuring that we get the destination before sending to it.

Jira: https://issues.jboss.org/browse/WFLY-11789

[WFLY-11829]: Support messaging clusters (Artemis Clusters) behind http load balancers. * Disabling automatic topology updates on client via a new attribute.

Jira: https://issues.jboss.org/browse/WFLY-11829

[WFLY-11828]: Bump messaging schema version to 7.0

Bumping version to 7.0

Jira: https://issues.jboss.org/browse/WFLY-11828

    • -0
    • +1018
    /messaging-activemq/src/main/resources/schema/wildfly-messaging-activemq_7_0.xsd
[WFLY-11741]: Upgrade Jboss Metadata to 13.0.0.Final.

* Upgrading JBoss Metadata to deprecate ReplicationConfig.

Jira: https://issues.jboss.org/browse/WFLY-11741

[WFLY-11741]: Upgrade Jboss Metadata to 13.0.0.Final.

* Upgrading JBoss Metadata to deprecate ReplicationConfig.

Jira: https://issues.jboss.org/browse/WFLY-11741

[WFLY-11700] Adding test for EAP 7.2 transformers

[WFLY-11668-fix]:Issue in WFLY-11668 transformer registration.

* Fixing wrong transformer registration.

Jira: https://issues.jboss.org/browse/WFLY-11668

[WFLY-11668]: Core queue creation is missing a routing type attribute.

* Adding a routing-type attribute to allow for core-queue creation.

Jira: https://issues.jboss.org/browse/WFLY-11668

[WFLY-10212]: Deploying of jms bridge requires a lot of mandatory parameters.

* Defining default values for:

- quality-of-service

- failure-retry-interval

- max-retries

- max-batch-size

- max-batch-time

Jira: https://issues.jboss.org/browse/WFLY-10212

[WFLY-10212]: Deploying of jms bridge requires a lot of mandatory parameters.

* Defining default values for:

- quality-of-service

- failure-retry-interval

- max-retries

- max-batch-size

- max-batch-time

Jira: https://issues.jboss.org/browse/WFLY-10212

[WFLY-10212]: Deploying of jms bridge requires a lot of mandatory parameters.

* Defining default values for:

- quality-of-service

- failure-retry-interval

- max-retries

- max-batch-size

- max-batch-time

Jira: https://issues.jboss.org/browse/WFLY-10212

[WFLY-11142]: Regression in SOAP over JMS when WF13 and WF14 are communicating.

* Adding missing dependency for the wildfly-client-properties artifact

Jira: https://issues.jboss.org/browse/WFLY-11142

    • -0
    • +4
    /webservices/tests-integration/pom.xml
[WFLY-6684]: JMS Bridge should display statistics about messages that have been processed.

* Adding message-count and aborted-message-count metrics on JMS Bridge

Jira: https://issues.jboss.org/browse/WFLY-6684

[WFLY-11579]: Description of transaction timeout is misleading.

* Fixig description

Jira: https://issues.jboss.org/browse/WFLY-11579

[WFLY-11586]: Missing runtime reference to external destinations.

* Fixing the missing reference to rcternal JMS destinations in deployments.

Jira: https://issues.jboss.org/browse/WFLY-11586

[WFLY-11561]: org.jboss.as.test.integration.messaging.jms.context.notClosingInjectedContext.NotClosingInjectedContextTestCase.

* Fixing missing permissions for NotClosingInjectedContextTestCase.

Jira: https://issues.jboss.org/browse/WFLY-11561