Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
WFLY-7576 Don't use deprecated no-op OperationContext#stepCompleted()

    • -1
    • +0
    ./AlternativeAttributeCheckHandler.java
    • -1
    • +0
    ./HornetQServerResourceDefinition.java
  1. … 64 more files in changeset.
WFLY-7728 - Lazy load legacy messaging parsers

- don't use static instances

[WFLY-6504] Fix messaging migration warnings

Clarify migration warnings to emphasis whether something can not be

migrated *from* a legacy resource or *to* a new resource.

JIRA: https://issues.jboss.org/browse/WFLY-6504

Merge pull request #8659 from jmesnil/WFLY-6068_failback_delay_warning

[WFLY-6068] Migration warning for failback-delay

  1. … 1 more file in changeset.
[WFLY-6068] Migration warning for failback-delay

Discard the failback-delay from the server's add operation during

migration (and not from the ha-policy's add).

JIRA: https://issues.jboss.org/browse/WFLY-6068

  1. … 1 more file in changeset.
[WFLY-6125] Migration warning for remoting-interceptors

During migration, discard (deprecated) remoting-interceptors attribute

and a migration-warnings that these interceptors must be updated to use

the Artemis interceptor base class instead of the HornetQ one.

JIRA: https://issues.jboss.org/browse/WFLY-6125

  1. … 2 more files in changeset.
[WFLY-6068] Migration warning for failback-delay.

Warn that the failback-delay attribute is not migrated as Artemis

detects failback in a deterministic way.

JIRA: https://issues.jboss.org/browse/WFLY-6068

[WFLY-6027] Fix messaging migration warnings

Fix typos

JIRA: https://issues.jboss.org/browse/WFLY-6027

[WFLY-5678] Do not migrate attributes that no longer accept expressions

Reword migration warnings so that they are more helpful when displayed

in both :migrate and :describe-migration operations

JIRA: https://issues.jboss.org/browse/WFLY-5678

Add messaging subsystem transformers for EAP 6.4 and minimize deprecated api usage

  1. … 5 more files in changeset.
[WFLY-5709] Fix Messaging HA configuration

* the shared-store-colocated configuration creates replication

live/backup configuration instead of shared-store ones.

* live and backup configuration must always be created for colocated

configurations.

* remove failback-delay attribute that is ignored in Artemis since

1.0.0.wildfly-008

* add attribute initial-replication-sync-timeout to specify

deterministically how long to wait for the initial replication.

JIRA: https://issues.jboss.org/browse/WFLY-5709

  1. … 12 more files in changeset.
[WFLY-5667] Migration: do not migrate parameters ignored by new subsystem

During migration, do not migrate the use-nio parameter for remote/http

connector/acceptor resources in the new messaging-activemq subsystem and

add a warnings to the :migrate operation result.

JIRA: https://issues.jboss.org/browse/WFLY-5667

  1. … 2 more files in changeset.
[WFLY-5678] Do not migrate attributes that no longer accept expressions

The discovery-group and broadcast-group resources in the legacy

messaging subsystem accept expressions for their jgroups-stack and

jgroups-channel resources.

The same resources in the new messaging-activemq subsystem no longer

accepts expressions for them (as they are references to other model

resources).

During migration, these attributes are ignored and removed from the new

:add operations to create the messaging-activemq resources and warnings

are added to the migration-warnings.

This allows the :migrate operation to succeed and the user will have to

fix the model afterwards by specifying a correct value for these

attributes.

JIRA: https://issues.jboss.org/browse/WFLY-5678

  1. … 2 more files in changeset.
[WFLY-5548] Migrate backup-group-name attribute

If the legacy hornetq-server has defined a backup-group-name, migrate it

to the new ha-policy resource for replication-master and

replication-slave types.

JIRA: https://issues.jboss.org/browse/WFLY-5548

  1. … 2 more files in changeset.
Merge pull request #8287 from jmesnil/WFLY-5533_domain_migrate_with_legacy_entries

[WFLY-5533] Calling :migrate(add-legacy-entries=true) in domain fails

[WFLY-5533] Calling :migrate(add-legacy-entries=true) in domain fails

Read the server resource relative to the context's current address.

This address can can change whether we are in standalone or domain mode

but it always correspond to the messaging subsystem address.

JIRA: https://issues.jboss.org/browse/WFLY-5533

[WFLY-5526] Migrate forward-when-no-consumers attribute

Warn if the attribute is using an expression (and discard it).

Otherwise change it to the message-load-balancing-type according to

Artemis documentation at

http://activemq.apache.org/artemis/docs/1.1.0/clusters.html#configuring-cluster-connections

JIRA: https://issues.jboss.org/browse/WFLY-5526

  1. … 2 more files in changeset.
Merge pull request #8171 from jmesnil/WFLY-5384_validate_artemis_parameters

[WFLY-5384] Validate Artemis Parameters

[WFLY-5384] Validate Artemis Parameters

* map WildFly hyphen-separated names to Artemis CamelCase names for

acceptor/connectors parameters

* change http-upgrade-endpoint to be a required attribute for http-connector resource

JIRA: https://issues.jboss.org/browse/WFLY-5384

  1. … 10 more files in changeset.
[WFLY-5380] Do not create legacy connection factory using in-vm connector

Artemis in-vm connectors are not compatible with HornetQ ones.

Instead of creating legacy-connection-factory that would generate errors

during reload, discard it and add a warning.

JIRA: https://issues.jboss.org/browse/WFLY-5380

  1. … 1 more file in changeset.
WFLY-5306 Remove extensions in standalone mode when running migrate operations

  1. … 4 more files in changeset.
[WFLY-5241] Update messaging server path cardinality reporting

    • -24
    • +0
    ./HornetQServerResourceDefinition.java
  1. … 2 more files in changeset.
[WFCORE-5234] Avoid ModelNode.asPropertyList() in high level hornetq marshaling

[WFLY-5084] Warning for unmigrated discovery-group attributes

Add migration-warnings when discovery-group attributes can not be be

migrated.

JIRA: https://issues.jboss.org/browse/WFLY-5084

  1. … 1 more file in changeset.
[WFLY-5086] Messaging HA migration

* migrate the HA configuration of the legacy messaging servers when it

is possible to determine its state.

* if shared-store or backup attributes hold expressions, there is no way

to determine the actual HA configuration of the server in domain mode.

In that case, the HA configuration is discarded and the user is

warned.

* In other case, a ha-policy resource is created for the migrated server

of the new messaging-activemq subsystem.

JIRA: https://issues.jboss.org/browse/WFLY-5086

  1. … 2 more files in changeset.
[WFLY-5083] Warning for unmigrated broadcast-group attributes

Add migration-warnings when broadcast-group attributes can not be be

migrated.

JIRA: https://issues.jboss.org/browse/WFLY-5083

  1. … 2 more files in changeset.
Make MessagingExtension extends AbstractLegacyExtension

fix tests to run in ADMIN_ONLY_HC mode.

  1. … 11 more files in changeset.
Merge pull request #7947 from jmesnil/WFLY-5105_migration_cluster-connection

[WFLY-5105] Migrate discovery-group attribute in cluster-connection

[WFLY-5085][WFLY-5088] migrate generic messaging transport

If the (legacy) generic acceptor or connector are using the default

HornetQ-based Netty factory classes, migrate them to use instead the

Artemis-based classes.

Also fix the persistence of the generic connector resources (that must

marshall their socket-binding as a XML attribute).

JIRA: https://issues.jboss.org/browse/WFLY-5085

JIRA: https://issues.jboss.org/browse/WFLY-5088

[WFLY-5105] Migrate discovery-group attribute in cluster-connection

JIRA: https://issues.jboss.org/browse/WFLY-5105