Clone Tools
  • last updated a few minutes ago
Constraints: committers
Constraints: files
Constraints: dates
WFLY-2772 Leverage JGroups FORK to consolidate EE channels

  1. … 213 more files in changeset.
Rename testsuite output directories to wildfly-*

  1. … 1 more file in changeset.
remove patching testsuite as it is moved to core

  1. … 25 more files in changeset.
[BZ1075971] Enabling picketlink tests to use different IP address than localhost. Conflicts: testsuite/integration/picketlink/pom.xml testsuite/integration/src/test/scripts/picketlink-build.xml

    • -0
    • +16
  1. … 5 more files in changeset.
Revert "Revert "Remove some deps leftovers & testsuite cleanup""

This reverts commit b05a7ff4d35cedc85d5ac82e611d44b5c7464f1e.

  1. … 95 more files in changeset.
Revert "Remove some deps leftovers & testsuite cleanup"

This reverts commit 005567fe438049426292e4ca270060eadd8c9b7b.

  1. … 96 more files in changeset.
WFLY-2159 Consolidate REPL and DIST cache configurations

  1. … 12 more files in changeset.
Fix clustering testsuite regression caused by The use of FILE_LOCK=NO in H2 causes database file corruption.

WFLY-2206 Don't copy the modules directory in the manualmode test suite

  1. … 1 more file in changeset.
Remove some deps leftovers & testsuite cleanup

- unify surefire configuration

- upgrade to newer surefire

- move most of surefire configuration to plugin definition section

- unify basic testsuite by removing full & web configs

- introduce -Phelp profile when you need to pring debug help for TS

- WFLY-2124 Revisit LDAP testing within the testsuite.

  1. … 96 more files in changeset.
[WFLY-456] Audit Logging - squashed the below commits since master has changed so much

[WFLY-456] Minor OperationContext impl cleanups

[WFLY-456] Bring in John Bailey's audit log classes

[WFLY-456] Add real audit loggers into the model controllers; integrate management handlers

[WFLY-456] Log the full set of information

[WFLY-456] Fix problems from rebase

[WFLY-456] Use SecurityContext when invoking JMX methods via remoting

[WFLY-456] Move core security classes into own module

[WFLY-456] Rework things and make the controller logger work

[WFLY-456] Include the access mechanism in the log, move some more classes to core-security

[WFLY-456] Make audit logger available to JMX

[WFLY-456] Pluggable MBeanServer delegate to audit logger, and loads of exception handling

[WFLY-456] Jmx audit log proxy

[WFLY-456] Separate the configuration for the core controller and jmx audit logs

[WFLY-456] Set the booting flag in the jmx layer

[WFLY-456] Integrate audit logging resource and ops into JMX extension so it can be configured there

[WFLY-456] Correct copyright notices in my new files

[WFLY-456] fix problems from rebase

[WFLY-456] Get rid of the original hashing implementation

[WFLY-456] Add missing originalResultTxControl from rebase

[WFLY-456] Add config for appenders

[WFLY-456] Basic file appender and json formatter. The output needs cleaning up and everything is currently hardcoded

[WFLY-456] Back up the previous log file. Basic syslog appender (awaiting the improved logmanager SyslogHandler)

[WFLY-456] Use the org.wildfly:wildfly-xxx names. Start configuring file appenders

[WFLY-456] Configure model for syslog appender

[WFLY-456] Log audit log records for ParallelBootOperationContext and ReadOnlyContext

[WFLY-456] Make whether to log on boot configurable

[WFLY-456] Be able to add/remove appender references at runtime and update the appenders at runtime

[WFLY-456] Add boot-log to jmx audit-log as well and update xsd's for both core and jmx

[WFLY-456] Make additive changes to appenders take effect right away, and delay changes/removals until the current audit record has been written

[WFLY-456] Add schema support and parsing for managed server path overrides, and clean up the handlers

[WFLY-456] Use 'handler' rather than 'appender'

[WFLY-456] Pass in audit log operations to managed servers on boot

[WFLY-456] Separate handler chains for host and managed server audit logs

[WFLY-456] i18n and get rid of code no longer needed

[WFLY-456] Fix problems from rebase, revisit security after moved WildFlySecurityManager

[WFLY-456] Flesh out the syslog handler, tried with UDP

[WFLY-456] Start testing the handlers and ops

[WFLY-456] Set up proper syslog host and app names

[WFLY-456] More tests

[WFLY-456] Complete renaming appender->handler. Really

[WFLY-456] Nicer separate configuration for JMX

[WFLY-456] Better testing for enabled and log-read-only audit log write attribute handlers

[WFLY-456] Separate handlers for JMX subsystem audit logging, and tests

[WFLY-456] Maintan a failure count per appender

[WFLY-456] Configure the json formatter and reference from the audit log handlers

Expose 'max-length' and 'truncate' for the syslog handler

[WFLY-456] Make audit logging work in admin-only mode

Fix bug not enabling the appender in domain mode

[WFLY-456] Fixes to tls syslog handler having tried it out against rsyslog

[WFLY-456] don't enable log by default

[WFLY-456] Test jmx audit log transformation

[WFLY-456] Test audit logging in testsuite

[WFLY-456] Move new i18n bits into domain-management, rather than using the ones from controller

[WFLY-456] Recycle handler operation, make max-failure-count configurable per handler, expose runtime attributes for handler failure counts

[WFLY-456] Use strings instead of byte[] for the formatters for now. We can revisit the byte[] part if more tamper detecting formatters are used in the future

[WFLY-456] Use platform independent line terminator

[WFLY-456] Changes to work with latest logmanager following a squash

  1. … 208 more files in changeset.
[WFLY-490] Set up some integration tests

    • -0
    • +34
  1. … 19 more files in changeset.
generate configuration files suitable for use inside the amazon EC2 compute cloud disable mcast for NAKACK protocol for more efficient processing; see add validation tests for the ec2 config files

  1. … 7 more files in changeset.
[WFLY-405] use a lighter standalone configuration for patching tests

  1. … 2 more files in changeset.
Revert "Revert "Initial HTTP Upgrade support for remoting naming and EJB invocations""

This reverts commit 8fedd0f07ee2bfe8fd526e09daa84e62e0b036ce.

  1. … 105 more files in changeset.
Revert "Initial HTTP Upgrade support for remoting naming and EJB invocations"

This reverts commit e44b2ae0f1354eb82766f15b0ae06906b00ae0b4.

  1. … 104 more files in changeset.
[WFLY-245] Add test case for xsite backupFor option to Infinispan subsystem.

  1. … 4 more files in changeset.
[WFLY-405] patching testsuite

    • -0
    • +39
  1. … 7 more files in changeset.
JBQA-6578 session DB persistence tests

  1. … 6 more files in changeset.
[WFLY-245] Fix up XSLT scripts for adding backups.

  1. … 2 more files in changeset.
[WFLY-245] Make test case variables more self-expalanatory.

  1. … 3 more files in changeset.
Initial HTTP Upgrade support for remoting naming and EJB invocations

  1. … 104 more files in changeset.
[WFLY-245] Basic x-site testcase implementation.

  1. … 15 more files in changeset.
delete manualmode's jbossas-messaging-failover before copy

HornetQ failover is depending on the file system to lock a file.

I have seen PRs be aborted because HornetQ live server can not lock this

file to start (there is no timeout on this lock operation).

Deleting the directory ensures that the file system's lock (from previous

runs) is removed.

[WFLY-245] Update XSLT operations for creating x-site configurations.

  1. … 2 more files in changeset.
[WFLY-245] Disable execution of x-site tests; update server instance names to use wildfly base name.

  1. … 1 more file in changeset.
[WFLY-245] Add ant target and maven execution to build xsite configurations.

  1. … 1 more file in changeset.
[WFLY-245] Fix a few typos.

  1. … 1 more file in changeset.
[WFLY-245] Add in XSLT transforms for x-site.

    • -0
    • +263
  1. … 4 more files in changeset.
[AS7-6699] HornetQ backup mode

When HornetQ is configured to be a backup, it will start and remain

passive (its resources are not deployed, it does not accept any

connections, etc.)

For AS7 hornetq-server's children resources, that means that:

* read-attribute on runtime attributes is a no-op (returns undefined)

* execute an operation on a queue will throw an exception warning the

user that HornetQ is in backup mode

* add active runtime r/o attribute to hornetq-server

For AS7 services, there are some substantial changes too.

HornetQService default does *not* start the HornetQ server. This is done

by JMSService. This means that any service must not depend on

HornetQService but JMSService to make sure that the server is

effectively started.

JMSService is started asynchronously and the server start is completed


* the HornetQ server has been activated (immediately when it is a live

node, or after failover if it is a backup)

* and the JMSServerManager is started (and can deploy JMS resources)

It is important for other services depending on messaging services

(queue, jms-queue, topic, connection-factory &

pooled-connection-factory) that these services must NOT be started

until a backup hornetq-server fails over.

* refactor messaging's SecurityActions (based on ExtensionAddHandler


  1. … 34 more files in changeset.