Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[WFCORE-4000] Refactoring org.jboss.as.process.jdk.JdkType -> org.jboss.as.host.controller.jvm.JvmType

  1. … 9 more files in changeset.
[WFCORE-3481] Stop using deprecated OFE constructor

  1. … 2 more files in changeset.
[WFCORE-3145] Comment out unused logger methods

    • -216
    • +215
    ./HostControllerLogger.java
  1. … 19 more files in changeset.
[WFCORE-2964] Use the default-server-logging.properties file on initial boot of domain servers. Ignore the logging.configuration system property which should always be set to the incorrect file by the domain startup scripts.

  1. … 2 more files in changeset.
WFCORE-2331 - log warning a reconnected slave if reload-required or restart-required triggered

  1. … 1 more file in changeset.
[WFCORE-2203]: Outcome from /host=x/server-config=y:remove() operation in managed domain with multiple hosts lists out all the steps in result

The synchronization model operation after an operation between the HC and the DC shouldn't use the current operation's response.

  1. … 8 more files in changeset.
[WFCORE-2223] Drop pointless validation of jboss.modules.dir

  1. … 3 more files in changeset.
WFCORE-2933 add support for empty host.xml & domain.xml when starting an embedded-HC (--empty-domain-config, --remove-existing-domain-config, --empty-host-config, --remove-existing-host-config) add support for adding a host controller with /host=foo:add() replace HostRegistrationHandler with HostAddHandler allow localhostname to be overridden when using /host=foo:add() DMCS unrefactor from Brian

  1. … 33 more files in changeset.
[WFCORE-2094] Propagate server instability notifications to the DC

  1. … 8 more files in changeset.
[WFCORE-2094] Propagate server instability notifications to the DC

  1. … 8 more files in changeset.
[WFCORE-2094] Log server suspected messages if proxied domain rollout request times out

  1. … 6 more files in changeset.
[WFCORE-2094] Log server suspected messages if proxied domain rollout request times out

  1. … 6 more files in changeset.
[WFCORE-2094] Domain server notifies HC upon controller instability

This commit introduces a notification mechanism via which a listener for "controller instability" notifications can be created and wired into the ModelController.

In a domain server, such a listener is registered. In this case it's an additional function of HostControllerClient, which responds to notifications by asynchronously sending a message back to the managing HC.

Currently the managing HC simply logs a WARN when receiving such a message. In the future it could also do something else with the data, e.g. expose it over the management API for use by the admin console.

Notifications are currently sent in two cases:

1) An OperationContext is interrupted or times out waiting for MSC stability during operation finalization. This means MSC was not stable at the time of finalization and the state of the system is no longer knowable.

2) An Error is thrown during operation execution. Again in such a situation the state of the system is no longer knowable.

In the latter case, there is no guarantee that the listener will be able to send the message to the HC. For example if the Error is an OOME sending a message may not be possible. So this is not a foolproof means of ensuring the HC is aware of server instability. Possible future work to cover that kind of scenario could be to have the HC send some sort of health check request to the server when it detects that an operation has timed out.

This also doesn't send a notification if the server fails to shut down properly, e.g. from problems with the MSC ServiceContainer not stopping. That would be detected by the bootstrap shutdown hook, which has no relationship to this logic.

  1. … 14 more files in changeset.
[WFCORE-2094] Domain server notifies HC upon controller instability

This commit introduces a notification mechanism via which a listener for "controller instability" notifications can be created and wired into the ModelController.

In a domain server, such a listener is registered. In this case it's an additional function of HostControllerClient, which responds to notifications by asynchronously sending a message back to the managing HC.

Currently the managing HC simply logs a WARN when receiving such a message. In the future it could also do something else with the data, e.g. expose it over the management API for use by the admin console.

Notifications are currently sent in two cases:

1) An OperationContext is interrupted or times out waiting for MSC stability during operation finalization. This means MSC was not stable at the time of finalization and the state of the system is no longer knowable.

2) An Error is thrown during operation execution. Again in such a situation the state of the system is no longer knowable.

In the latter case, there is no guarantee that the listener will be able to send the message to the HC. For example if the Error is an OOME sending a message may not be possible. So this is not a foolproof means of ensuring the HC is aware of server instability. Possible future work to cover that kind of scenario could be to have the HC send some sort of health check request to the server when it detects that an operation has timed out.

This also doesn't send a notification if the server fails to shut down properly, e.g. from problems with the MSC ServiceContainer not stopping. That would be detected by the bootstrap shutdown hook, which has no relationship to this logic.

  1. … 14 more files in changeset.
Merge pull request #1957 from baranowb/WFCORE-311_v2

[WFCORE-311] use @Cause instead of toString()

[WFCORE-2009] Correct attribute validation to reflect that SSL configuration can now come from either an ssl-context or a security-realm.

  1. … 10 more files in changeset.
Merge remote-tracking branch 'upstream' into remoting5_integration

  1. … 21 more files in changeset.
Merge branch 'WFCORE-1763_WFCORE-1764' into remoting5_integration

  1. … 17 more files in changeset.
[WFCORE-1780] Clean up log messages in case of failure to connect to DC

  1. … 1 more file in changeset.
Merge remote-tracking branch 'upstream/master' into remoting5_integration

  1. … 32 more files in changeset.
[WFCORE-952] Use standard null checks

  1. … 6 more files in changeset.
WFCORE-316: --cached-dc additional fixes - keep the remote file repository so it's available when the DC becomes available again - load domain.cached-remote.xml as a temporary file until boot is successful to prevent any boot errors leaving it in a clobbered state - if any remote content is unavailable from an offline DC during boot, and not present in the local repository, abort the boot.

  1. … 4 more files in changeset.
[WFCORE-311] use @Cause instead of toString()

Merge branch 'WFCORE-1700'

  1. … 12 more files in changeset.
Merge remote-tracking branch 'upstream' into elytron_integration

  1. … 2 more files in changeset.
Merge remote-tracking branch 'upstream/master' into elytron_integration

  1. … 12 more files in changeset.
  1. … 14 more files in changeset.
WFCORE-1535 Adapted ManagedServer#resume() to avoid the potential forever block

  1. … 7 more files in changeset.
[WFCORE-1498] Log different messages in different shutdown scenarios

  1. … 12 more files in changeset.
[JBEAP-6101] [WFCORE-1498] Log different messages in different shutdown scenarios

Backported from

https://github.com/wildfly/wildfly-core/pull/1515/commits/f4cd933c3245ddc52e057cbcb69f35121a4d0454

# Conflicts:

# host-controller/src/main/java/org/jboss/as/host/controller/logging/HostControllerLogger.java

# server/src/main/java/org/jboss/as/server/logging/ServerLogger.java

  1. … 12 more files in changeset.