Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[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

  1. … 12 more files in changeset.
[WFLY-11493]: Core queues loaded at boot are not removable.

* Creating service for core queues created via ActiveMQServer

configuration in ServerAdd.

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

    • -0
    • +72
    ./CoreQueueMessagingTestCase.java
  1. … 4 more files in changeset.
[WFLY-9340] Unignore MessagingClientTestCase.testMessagingClientUsingMessagingPort

    • -58
    • +103
    ./MessagingClientTestCase.java
  1. … 2 more files in changeset.
JBEAP-8666 Fix tests to work with proper undertow model validation

  1. … 18 more files in changeset.
Reduce testsuite system.out messages.

  1. … 150 more files in changeset.
update tests that were using HornetQ API to Artemis

  1. … 4 more files in changeset.
[WFLY-4584] new messaging-activemq subsystem

* add Maven GAVs for ActiveMQ Artemis artifacts

* add new messaging-activemq subsystem based on the legacy messaging

subsystem and using Artemis code instead of HornetQ

* update test to use urn:jboss:domain:messaging-activemq:1.0 namespace

* add ActiveMQ Artemis client artifacts to jms client

* add org.jboss.activemq.artemis.integration:activemq-wildfly-integration artifact

* use service extension to bind with Artemis's transaction manager locator and recovery manager

* add (core) queues addition/removal to JMSOperations

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

  1. … 280 more files in changeset.
[WFLY-2730] HTTP upgrade multiplexing

When the HTTP upgrade handshake is performed, check whether

the http-upgrade-endpoint is defined and accepts the handshake

only if its value matches the acceptorName.

This http-upgrade-endpoint header is used by a http-connector to

specify which http-acceptor must be used in case there are multiple

http-acceptors registered on the server.

If the http-upgrade-endpoint header is not present, the 1st http-acceptor

encountered will be used. This is not deterministic and is suitable only

if there is a single http-acceptor.

* remove native messaging port for messaging subsystem.xml configuration

and use http-connector for JMS RemoteConnectionFactory

* add a http-connector-throughput to replace the corresponding

netty-throughput

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

  1. … 14 more files in changeset.
Upgrade netty-xnio-transport to 0.1.1.CR1

this version fixes intermittent failures in MessagingClientTestCase and

JmsClientTestCase

  1. … 1 more file in changeset.
[WFLY-2128] JMS one-port support

* add http-connector and http-acceptor resources to handle connections

from HTTP and upgrade to HornetQ protocol.

* use netty-xnio-transport to wrap the XNIO channel into a Netty channel

to hand it over to HornetQ server.

* component changes:

* add org.jboss.xnio.netty:netty-xnio-transport:0.1.0

  1. … 31 more files in changeset.
replace usages of deprecated junit.framework.*

  1. … 300 more files in changeset.
[AS7-203] MessagingClientTestCase fix

* the test was not checking whether a message was effectively consumed

=> set auto commit / auto ack to produce and consume as expected

* the core queue service was not removed properly because QueueRemove

was building a different service name that the one used to add the

queue

* fix Messaging services that were prepending twice HornetQ service name

to their own names

  1. … 3 more files in changeset.
WIP

  1. … 66 more files in changeset.
remove demo's and clean up smoke tests

  1. … 146 more files in changeset.
Change smoke tests to not be reliant on demo's

  1. … 309 more files in changeset.