Explanation | Operations cannot be performed on a Config instance that has been closed. |
Action | Obtain a new Config instance and attempt the operation again. |
Explanation | The ClassLoader used by a ConfigBuilder must not be null. |
Action | Set the ClassLoader to a non-null value. |
Explanation | A Config instance has already been set for the specified ClassLoader. |
Action | Use the 'releaseConfig' method to remove the previous instance and then retry the method. |
Explanation | An exception occurred while trying to close a Config instance. Its resources might not have been released. |
Action | Review the server message.log and FFDC logs to identify the problem. |
Explanation | No suitable Converter was found for the given type. |
Action | Add a suitable Converter or ensure the class has a public String constructor or a static valueOf(String) method. |
Explanation | A Converter threw an exception. |
Action | Review the server message.log and FFDC logs to identify the problem. |
Explanation | The input string was not a valid Boolean value. |
Action | Update the source input string and re-try the operation. |
Explanation | The Converter implementation class did not have a suitable generic type. |
Action | Ensure that the implementation class has a suitable generic type variable for the Converter interface. |
Explanation | The Java ServiceLoader created an exception. The most likely cause is that one of the named ConfigSource classes could not be found. |
Action | Check the classes named in the Java service files within your application. Review the server message.log and FFDC logs to further identify the problem. |
Explanation | The Java ServiceLoader created an exception. The most likely cause is that one of the named ConfigSourceProvider classes could not be found. |
Action | Check the classes named in the Java service files within your application. Review the server message.log and FFDC logs to further identify the problem. |
Explanation | The Java ServiceLoader created an exception. The most likely cause is that one of the named Converter classes could not be found. |
Action | Check the classes named in the Java service files within your application. Review the server message.log and FFDC logs to further identify the problem. |
Explanation | The attempt to cancel a future asynchronous update failed. Typically this is caused by a long running update call to a ConfigSource instance. |
Action | Review the server message.log and FFDC logs to identify the problem. |
Explanation | A Converter could not be found to convert the raw property String into the requested type. |
Action | Ensure that a suitable Converter class is available and listed in the Java service file. |
Explanation | The requested property did not exist in any of the configured sources. |
Action | Add the property to one of the existing sources or add a new source that contains the property. |
Explanation | The attempt to cancel a future asynchronous update failed. Typically this is caused by a long running update call to a ConfigSource instance. |
Action | Review the server message.log and FFDC logs to identify the problem. |
Explanation | No valid String constructor methods were found on the specified class. |
Action | Check that the specified class has a valid String constructor method. To determine which methods are valid, refer to the MicroProfile Config specification. |
Explanation | An attempt was made to convert using a Generic Type Variable, such as List<T>. This is not supported. |
Action | Instead, use a concrete argument type, such as List<String>. |
Explanation | The injection point annotated with the @ConfigProperty qualifier did not have a valid type. |
Action | Ensure that the injection point has a valid type for the property you wish to inject. |
Explanation | It is not possible to derive the default property name for the Constructors and Method parameters. The correct property name must be passed to the @ConfigProperty qualifier. |
Action | Set the correct property name using the @ConfigProperty qualifier. |
Explanation | An injected Config Property did not resolve. Either the named property could not be found or a Converter for the required type did not resolve. |
Action | Check the server message and ffdc logs to determine the cause. Ensure that the property exists in one of the Config Sources and that the required Converters have been configured. |
Explanation | The named property was not found in any of the configured sources. |
Action | Ensure that the property exists in one of the Config Sources. |
Explanation | A Config API error has occurred that prevents normal operation. |
Action | Review the server message.log and FFDC logs to identify the problem. |
Explanation | A Config API error has occurred that prevents normal operation. |
Action | Review the server message.log and FFDC logs to identify the problem. |