CWMFT

CWMFT0000E: A timeout occurred.

Explanation	An operation took too long to complete for the configured Timeout.
Action	Increase the maximum duration of the Timeout or ensure that the operation completes faster.

CWMFT0001E: No free capacity is available in the bulkhead for method {0}.

Explanation	A call to the method did not succeed because the bulkhead for the method is full.
Action	Increase availability in the bulkhead by increasing the capacity of the bulkhead or reducing the concurrent workload of this service.

CWMFT0002W: The {0} asynchronous method cannot complete because the application or component that called it stopped.

Explanation	Asynchronous methods run in the context of the component that started them. The application or component that called the asynchronous method stopped, which prevented the asynchronous method from completing.
Action	This warning usually occurs when an application, component, or server is shutting down. If all running asynchronous methods must complete, then the application or component must wait for the results before stopping.

CWMFT0003W: The asynchronous method {0} returned null.

Explanation	Methods annotated with @Asynchronous must not return a null value.
Action	Prevent a null value from being returned by the method.

CWMFT4998E: An internal error occurred. The exception is {0}.

Explanation	The application server experienced an internal error.
Action	Gather a set of traces and open a new issue against your application server.

CWMFT4999E: An internal error occurred.

Explanation	The application server experienced an internal error.
Action	Gather a set of traces and open a new issue against your application server.

CWMFT5000E: The asynchronous method {0} does not have a return type of Future.

Explanation	All methods in a class that is annotated with org.eclipse.microprofile.faulttolerance.Asynchronous must have a return type that is assignable from java.util.concurrent.Future.
Action	Update the return type.

CWMFT5001E: The asynchronous method {0} does not have a return type of Future.

Explanation	All methods that are annotated with org.eclipse.microprofile.faulttolerance.Asynchronous must have a return type that is assignable from java.util.concurrent.Future.
Action	Update the return type.

CWMFT5002E: The fallback method {0} has the wrong return type. The return type must match the return type of the method {1}.

Explanation	A fallback method must have the same return type as the method it handles.
Action	Update the return type.

CWMFT5003E: The fallback method {0} with parameter types matching method {1} was not found in class {2}.

Explanation	A fallback method was declared but it does not exist in the declaring class.
Action	Either remove the fallback annotation or add the missing method.

CWMFT5004E: A security exception occurred when the application server tried to process fallback annotations.

Explanation	To create a fallback policy, the application server requires permission to acquire and examine Java methods.
Action	Review the security policy of your application server and provide the permissions.

CWMFT5005E: A problem occurred while converting a system property {0} to type {1}. The raw string value is {2}. The exception is {3}.

Explanation	Any configuration values provided via system properties must be convertable to the appropriate type. e.g. using Long.valueOf(String)
Action	Check that the specified value is in the correct format for the type of the property it is overriding.

CWMFT5006E: A problem occurred while converting a system property to type {0}. The raw string value is {1}. The exception is {2}.

Explanation	Any configuration values provided via system properties must be convertable to the appropriate type. e.g. using Long.valueOf(String)
Action	Check that the specified value is in the correct format for the type of the property it is overriding.

CWMFT5007E: A problem occurred while converting a system property to type {0}. The raw string value is {1}.

Explanation	Any configuration values provided via system properties must be convertable to the appropriate type. e.g. using Long.valueOf(String)
Action	Check that the specified value is in the correct format for the type of the property it is overriding.

CWMFT5008E: The fallback policy for the method {0} is not valid because the type of the FallbackHandler implementation class {1} must be compatible with the return type {2} on the original method {3}.

Explanation	The type of the FallbackHandler implementation must be compatible with the return type of the original method.
Action	Update the type of the FallbackHandler implementation class to be compatible with the return type of the original method.

CWMFT5009E: The Fallback policy for the method {0} is not valid because both FallbackHandler class {1} and fallbackMethod {2} were specified. Specify only one of them.

Explanation	Either the fallbackMethod or the value should be set, not both.
Action	Remove either the fallbackMethod or the value from the Fallback annotation.

CWMFT5010E: The Retry policy parameter {0} value {1} for {2} is not valid because it must be greater than or equal to {3}.

Explanation	The specified value or the configured value, if configured for the Retry policy parameter, is not valid.
Action	Correct the value for the specified parameter.

CWMFT5011E: The Timeout value {0} specified on {1} is not valid, because the value must be greater than or equal to 0.

Explanation	The specified value or the configured value, if configured for the Timeout policy value parameter, is not valid.
Action	Correct the value for the specified parameter.

CWMFT5012E: The CircuitBreaker policy parameter {0} value {1} for the {2} is not valid, because the parameter value must not be a negative number.

Explanation	The specified value or the configured value, if configured for the delay CircuitBreaker policy parameter, is not valid.
Action	Correct the value for the specified parameter.

CWMFT5013E: The CircuitBreaker policy parameter {0} value {1} for the {2} is not valid, because the value must be between 0 and 1, inclusively.

Explanation	The specified value or the configured value, if configured for the failureRatio CircuitBreaker policy parameter, is not valid.
Action	Correct the value for the specified parameter.

CWMFT5014E: The CircuitBreaker policy parameter {0} value {1} for the {2} is not valid, because the parameter must not be a negative number.

Explanation	The specified value or the configured value, if configured for the requestVolumeThreshold CircuitBreaker policy parameter, is not valid.
Action	Correct the value for the specified parameter.

CWMFT5015E: The CircuitBreaker policy parameter {0} value {1} for the {2} is not valid, because the parameter must not be a negative number.

Explanation	The specified value or the configured value, if configured for the successThreshold CircuitBreaker policy parameter, is not valid.
Action	Correct the value for the specified parameter.

CWMFT5016E: The Bulkhead policy parameter {0} value {1} for the {2} is not valid, because the parameter must be greater than or equal to 1.

Explanation	The specified value or the configured value, if configured for the Bulkhead policy parameter, is not valid.
Action	Correct the value for the specified parameter.

CWMFT5017E: The Retry policy maximum duration of {0} {1} for the {2} target is not valid as it must be greater than the delay duration of {3} {4}.

Explanation	The maximum duration must be greater than the delay. The maximum duration consists of the maxDuration parameter and the durationUnit parameter. The delay consists of the delay parameter and the delayUnit parameter.
Action	Correct the value of one or more of the parameters.

CWMFT5018E: The CircuitBreaker policy {0} parameter for {1} is not valid because its value is empty.

Explanation	The specified value or the value that is configured for the CircuitBreaker policy failOn parameter is not valid.
Action	Correct the value for the specified parameter.

CWMFT5019W: The Retry policy jitter delay of {0} {1} for the {2} target is not valid because the jitter delay must be less than the delay duration of {3} {4}.

Explanation	The jitter delay must be less than the delay. The jitter delay consists of the jitter parameter and the jitterDelayUnit parameter. The delay consists of the delay parameter and the delayUnit parameter.
Action	Correct the value of one or more of the parameters so that the duration for the jitter delay is less than the duration of the delay.

CWMFT5020E: The {0} asynchronous method does not have a return type of either java.util.concurrent.Future or java.util.concurrent.CompletionStage.

Explanation	All methods that are annotated with org.eclipse.microprofile.faulttolerance.Asynchronous must have a return type of either java.util.concurrent.Future or java.util.concurrent.CompletionStage.
Action	Update the return type.

CWMFT5021E: The fallback method {0} with parameter and return types matching method {1} was not found in the class hierarchy of {2}.

Explanation	A fallback method was declared but it does not exist in the declaring class, its superclasses, or the interfaces it implements.
Action	Either remove the fallback annotation or add the missing method. If the fallback method exists but is still not being found, check that the parameter types and return type of the two methods match and that the fallback method is visible to the class which declares the annotated method.

CWMFT5022E: MicroProfile Fault Tolerance annotations cannot be used in combination with the {0} annotation.

Explanation	Intermixing MicroProfile Fault Tolerance annotations with the specified annotation is not supported.
Action	Remove the MicroProfile Fault Tolerance annotations or the conflicting annotation.

CWMFT5997E: An internal error occurred. The exception is {0}.

Explanation	The application server experienced an internal error.
Action	Gather a set of traces and open a new issue against your application server.

CWMFT5998E: An internal error occurred.

Explanation	The application server experienced an internal error.
Action	Gather a set of traces and open a new issue against your application server.

CWMFT9999E: A Fault Tolerance API error has occurred: {0}

Explanation	A Fault Tolerance API error has occurred that prevents normal operation.
Action	Review the FFDC logs and exception text to identify the problem.

CWMFT9999E: A Fault Tolerance API error has occurred: {0}

Explanation	A Fault Tolerance API error has occurred that prevents normal operation.
Action	Review the FFDC logs and exception text to identify the problem.

CWMFT9999E: A Fault Tolerance API error has occurred: {0}

Explanation	A Fault Tolerance API error has occurred that prevents normal operation.
Action	Review the FFDC logs and exception text to identify the problem.