Explanation | Java EE Context and Dependency Injection functionality is enabled on this server. |
Action | No action is required. |
Explanation | Message indicates when a custom property is set and recognized by JCDI. |
Action | No action is required. |
Explanation | A JCDI error has occurred that will prevent normal operation. |
Action | Review FFDC logs and exception text to identify the problem. |
Explanation | An unexpected error has occurred while processing the configuration that prevents normal operation. |
Action | Review FFDC logs and exception text to identify the problem. |
Explanation | An unexpected error has occurred while processing an EJB |
Action | Review FFDC logs and exception text to identify the problem. |
Explanation | The specified class was not visible to the available classloaders. |
Action | Review the classloader settings of the specified application class. |
Explanation | Java EE Context and Dependency Injection functionality is disabled on this server. |
Action | No action is required. |
Explanation | Java EE Context and Dependency Injection functionality is disabled for the specified application. |
Action | No action is required. |
Explanation | Please examine the manifest classpath of your application module. |
Action | No action is required. |
Explanation | JCDI runtime could NOT load classes resulting from a scan of the beans deployment archive. |
Action | Please fix the ClassNotFoundException during application start |
Explanation | An unexpected error has occurred while processing the configuration that prevents normal operation. |
Action | Please Review FFDC logs or exception text to identify the problem. |
Explanation | A CDI error has occurred that will prevent normal operation. |
Action | Review FFDC logs and exception text to identify the problem. |
Explanation | CDI found more than one beans.xml file. |
Action | Ensure the application archive contains only one beans.xml file. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | CDI found a resource producer field where the type of the field did not match the type of the Java EE resource injected into it. |
Action | Ensure that the correct Java EE resource is being injected into the resource producer field and that the type of the field matches the type of the resource injected into it. |
Explanation | The injection is not successful as the bean manager of the archive that the class belongs to is null. |
Action | Ensure that the archive the class belongs to is a bean archive. Refer to the CDI specification on how to make an archive a bean archive. |
Explanation | Annotation transactional cannot be used with EJB |
Action | The TransactionAttribute should be used instead of Transactional with EJB's |
Explanation | Lifecycle interceptors should avoid throwing checked exceptions |
Action | Check the logs to determine the problem |