Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix for WFCORE-3575, CLI, failed connect side effect

  1. … 1 more file in changeset.
Fix for WFCORE-3447 CLI SSL security commands

  1. … 32 more files in changeset.
[WFCORE-2235] Fixing race condition that appears when the following scenario happens:

Module A depends on module B (optional dependency).

Both modules are dynamic (they're not present on the file system

but dynamically deployed at runtime). The following scenario exposes

race condition for this kind of dynamic modules:

1] Module A is starting and module B is not available yet

2] Module A during its initialization phase calls

ModuleLoader.loadModuleLocal() to resolve its optional module B dependency

3] Module A initialization thread registers "newFuture" with "moduleMap"

4] Module A initialization thread fails to find ModuleSpec of module B

5] ModuleLoadService representing Module B appears and is starting

(such service knows all its preconditions are met - its ModuleSpec is available)

6] MSC thread executing ModuleLoadService.start() (of module B)

is calling moduleLoader.loadModule(moduleB_Id)

7] MSC thread executing ModuleLoadService.start() (of module B)

enters ModuleLoader.loadModuleLocal() to find the module

8] MSC thread requests "moduleMap" and receives "newFuture" created in step [3]

9] MSC thread enters "newFuture" wait set and blocks (waiting for Module A

initialization thread to complete)

10] Module A initialization thread wakes up and identifies that (moduleSpec == null)

MOduleLoader.loadModuleLocal() will return null

11] Before method return "finally" sections is executed, where:

a) newFuture.setModule(null) is called

b) "newFuture" is removed from "moduleMap"

12] MSC thread wakes up and throws ModuleNotFoundException

This fix ensures proper ordering of resolution process for dynamic modules

and fixes aforementioned race condition.

  1. … 1 more file in changeset.
[WFCORE-3073] Ignore tests on Windows if taskkill without /f param doesn't stop the server.

See also https://stackoverflow.com/questions/14952948/kill-jvm-not-forcibly-from-command-line-in-windows-7

Mitigate intermittent WFCORE-2235 failures by reducing loop count to 1, temporarily making InterdependentDeploymentTestCase a test only for critical regressions

[WFCORE-3311] Initialize the log manager early for the CLIEmbededServerTestCase to ensure early initialization doesn't break replacing stdout.

Revert "Work around the WFCORE-2235 problem to avoid intermittent failures fo…"

WFCORE-3266 Change default configuration to utilize a single simple mapper

  1. … 1 more file in changeset.
JBEAP-12933 Change default configuration to utilize a single simple mapper

  1. … 1 more file in changeset.
WFCORE-3266 Change default configuration to utilize a single simple mapper

  1. … 1 more file in changeset.
Work around the WFCORE-2235 problem to avoid intermittent failures for the known issue

[WFCORE-3218] Upgrade jboss-logmanager from 2.0.7.Final to 2.1.0.Alpha4.

  1. … 4 more files in changeset.
Fix for WFCORE-3236, iteration of collections for CLI

  1. … 8 more files in changeset.
WFCORE-3199 Make sure the permissions deployment unit processors are registered before the deployment chain gets created and finalized

  1. … 1 more file in changeset.
[WFCORE-3182] Set the name of the server to ensure the size of the syslog headers is predictable.

[WFCORE-3174] Ensure tests will pass once internationalized message bundles are added.

  1. … 4 more files in changeset.
[WFCORE-3073] Invoke the SuspendController if the BootstrapImpl shutdown hook runs when the server is in ControlledProcessState.State.RUNNING

  1. … 4 more files in changeset.
[WFCORE-3109]: Only one AuditLogItem is written

The queue should be cleared out of the loop.

  1. … 1 more file in changeset.
[WFCORE-3078]: Intermittent failure in AuditLogBootingSyslogTest shows that WFCORE-2923 doesn't cover every case

Changing the AuditLogger in the ResultHandler of AuditLogLoggerAddHandler instead of as a RUNTIME step.

Clearing the queue when writting log entries after the ManagedAuditLogger change status to LOGGING.

  1. … 4 more files in changeset.
[WFCORE-2997] Be more aggressive in skipping the unregisterMBean log record

[WFCORE-2997] Loop before failing AuditLogBootingSyslogTest

[WFCORE-2997] Remove the occasional extra jmx entries that happen when the ServiceLoader WeakReference is cleared resulting in audit-logged calls to unregisterMBean

Also improve error output for AuditLogBootingSyslogTest

[WFCORE-2978]: Verify that WFCORE-2923 fix is valid.

* Adding tests.

* Adding capability dependencies to ensure that the credential store is defined.

* Adding a dummy service to associate to the credential store.

  1. … 8 more files in changeset.
Fix for WFCORE-2883. Un-ignore failing test

[WFCORE-2917] Switch to using sasl-mechanism-selector attribute.

    • -1
    • +1
    ./test/resources/test-wildfly-config.xml
  1. … 3 more files in changeset.
WFCORE-2483 Extend HTTPSManagementInterfaceTestCase tests with usage of credential reference

  1. … 4 more files in changeset.
[WFCORE-2876]: Runtime-failure-causes-rollback does not seem to have effect when configured in model

The runtime-failure-causes-rollback wasn't properly propagated to the boot scanner.

If runtime-failure-causes-rollback is set to 'false' then failed deployments added at boot shouldn't be undeployed.

  1. … 2 more files in changeset.
Fix for WFCORE-2679. CLI, ignore failing test

[WFLY-8835] add test for custom-credential-security-factory integration

  1. … 1 more file in changeset.
[WFCORE-2528] Try reenabling the test