Explanation | An attempt to load the class file as a resource for an application did not succeed. |
Action | Ensure the class is available to the application. |
Explanation | An attempt to read the class file as a resource for an application did not succeed. |
Action | Check the file system integrity. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/ |
Explanation | The system tried to create an application class loader, but the server does not provide the required Java packages. |
Action | Check that the server is configured with all the features needed to support this application. |
Explanation | To define a shared library in the server configuration, you must specify an ID attribute. |
Action | Edit the server configuration and add an ID attribute to the library element. |
Explanation | To reference a library in the server configuration, you must specify the ID of an existing library. |
Action | Edit the server configuration and ensure the referenced library has been defined and that the ID is correct. |
Explanation | To specify the ID for a shared library in the server configuration, you must follow attribute naming conventions. |
Action | Edit the server configuration and modify the ID attribute of the library element. |
Explanation | To reference a fileset from a shared library in the server configuration, you must specify the ID of an existing fileset. |
Action | Check the server configuration for the library element, and ensure that the referenced fileset exists. |
Explanation | An application references a library through a common class loader and will therefore need to share class instances; however, they have been configured to see different API sets. The application and the library must be configured to see exactly the same set of APIs in order to ensure consistent application behavior. |
Action | Either update the configuration so the application and the library can see the same API set, or configure the application to use the library privately. |
Explanation | Applications can be configured to specify which API types they intend to access. |
Action | Ensure that the configuration lists only valid types. |
Explanation | To reference a class loader in the server configuration, you must specify the ID of an existing class loader. |
Action | Check the server configuration to ensure that the class loader has been defined and that the ID is correct. |
Explanation | A shared library is in use but one of the associated filesets could not be retrieved in time. |
Action | Check for and redress any errors or warnings associated with the fileset. |
Explanation | To add a file to a library in the server configuration, you must specify the fully qualified name of an existing file. |
Action | Edit the server configuration and modify the file attribute of the library element. |
Explanation | To add a file to a library in the server configuration, you must specify the fully qualified path to an existing folder. |
Action | Edit the server configuration and modify the folder attribute of the library element. |
Explanation | To add a file to a classpath it must be a valid container of classes and resources such as a jar file. |
Action | Edit the server configuration and ensure any file or fileset attributes are referencing valid class and resource containers. |
Explanation | A library has become available, for example as a result of processing the server configuration. |
Action | No user action is required. |
Explanation | The server was unable to prevent locking of the JAR files within installed applications. The JAR files may remain locked until the server stops. |
Action | To delete JAR files within an installed application the server must be stopped prior to deletion. |
Explanation | Only archive files such as jar or zip files can be added to the classpath. |
Action | Edit the server configuration and ensure any files referenced from the classloader element are archive files. |
Explanation | A library has become unavailable, for example because it was removed from the server configuration. |
Action | If the library is still required, ensure that it is still configured correctly. |
Explanation | A class loader has been configured to delegate to a class provider but could not retrieve the appropriate class provider. The class loader will work but will not be able to retrieve any classes or resources from the specified class provider. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | A class loader has been configured to delegate to a class provider but the class provider has not provided a compatible class loader and cannot be used. The class loader will work, but will not be able to retrieve any classes or resources from the specified class provider. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support or check with the class provider service vendor. |
Explanation | A class loader has been configured to delegate to a class provider but the class provider has not provided a compatible class loader and cannot be used. The class loader will work, but will not be able to retrieve any classes or resources from the specified class provider. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support or check with the class provider service vendor. |
Explanation | A class loader has been configured to delegate to a specified class provider and will share class instances. However, they have been configured to see different API sets. The delegating class loader and the class provider must be configured to see the same set of APIs in order to have consistent application behavior. |
Action | Update the configuration so the delegating class loader and the class provider can see the same API set. |
Explanation | The service was declared in the META-INF/services directory and the service was registered to the server. |
Action | No user action is required. |
Explanation | The implementation of the service was not found. |
Action | Make sure that the name that is specified in the service declaration is correct. |
Explanation | A class that is required for the initialization of the service was not found. |
Action | Make sure that the name that is specified in the service declaration is correct. |
Explanation | The system cannot create an instance of the service implementation because there is no access to the class definition, or the class is missing a no argument constructor. |
Action | Ensure that there is access to the class definition and the constructor. |
Explanation | The system cannot access the class declaration or the constructor. |
Action | Ensure that that the class and constructor are defined and accessible. |
Explanation | There were no services declared in the META-INF/services folder. |
Action | Ensure that the Basic Extensions using Liberty Libraries (BELL) is configured with the correct library that has the expected META-INF/services folder |
Explanation | The service declaration file is not readable. |
Action | Ensure that the file is readable by the system. |
Explanation | The system received an unexpected exception error during the creation of the instance. This error can occur as a result of an exception from the constructor of the class. |
Action | If an exception occurred in the constructor, review and verify the behavior of the class constructor. |
Explanation | There is no matching service declared in the META-INF/services folder. |
Action | No user action is required. |
Explanation | To prevent applications and resources from seeing SPI packages, the BELL references the library through a unique class loader that is not shared with applications that reference the same library. |
Action | Disable SPI visibility in the BELL configuration whenever the BELL must reference a library through a class loader that is shared with applications that reference the same library. Otherwise, no action is required. |
Explanation | BELL SPI visibility cannot be enabled for the Liberty global shared library. |
Action | Modify the BELL configuration to reference a library other than the Liberty global shared library. |
Explanation | The system cannot access a method required for BELL property injection. The service implementation class must define a public constructor, or a public method named updateBell, with one parameter of type java.util.Map<string,String> in order to support BELL property injection. |
Action | Ensure that the class defines a public constructor, or a public method named updateBell, with a single parameter of type java.util.Map<String, String>. |
Explanation | The system was not able to create a folder on the disk. |
Action | Make sure that the drive is has the correct write permissions and that there is enough space on disk |
Explanation | The ArtifactContainerFactory object must not be null when the server is running. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support or check with the class provider service vendor. |
Explanation | The system failed to delete the cache file. Because the file still exists in the system, this might cause corruption in nested archives. |
Action | Verify that the cache file is not in a locked state, which can cause the file deletion to fail. |
Explanation | Each API type can be specified a maximum of one time. |
Action | Check the server configuration for duplicate API type to ensure that the API type are correct. |
Explanation | All default API types are added, remove duplicates. |
Action | Check the server configuration and remove default API type to ensure that the API type are correct. |
Explanation | Change the invalid API type to a valid API type. |
Action | Check the server configuration for invalid API type to ensure that the API type are correct. |
Explanation | Change the invalid API type to a valid API type with + or -. |
Action | Check the server configuration for invalid API type to ensure that the API type are correct. |
Explanation | A class that is typically provided by one or more server features could not be loaded. |
Action | Try enabling the specified feature or a newer version of the feature in the server.xml file. |
Explanation | Work was submitted to an unmanaged thread that does not support setting the ClassLoader. |
Action | Ensure that work runs on a thread that is managed by the server or allows the setContextClassLoader operation. |