Previous Contents Index Next |
Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Error Messages Reference

> ## Chapter 19
> Class Loader

> This chapter lists error messages that originate from the class loader.

> ##

> LDR

> A class loader is a Java component responsible for loading Java classes according to specific rules.

> ##### LDR5001

> Severity | WARNING
> Description | The classloader failed to convert the path (as indicated in the error message) into a URL.
> Action | Verify if the specified file path is valid and exists, and retry.

> ##### LDR5002

> Severity | WARNING
> Description | An error occurred while undeploying an EJB.
> Action | Refer to the exception data for more information.

> ##### LDR5003

> Severity | SEVERE
> Description | The unique ID specified in the EJB descriptor is automatically generated and updated during deployment or redeployment. The error occurs when it conflicts with an ID assigned to another EJB.
> Action | Redploy the EJB, thereby forcing the unique ID to be regenerated.

> ##### LDR5004

> Severity | SEVERE
> Description | An error occurred while creating the EJB container.
> Action | Refer to the exception data for information on how to fix this error.

> ##### LDR5005

> Severity | WARNING
> Description | An error occurred while unloading a Resource Adapter Reference (RAR).
> Action | Refer to the exception data for information on how to fix this error.

> ##### LDR5006

> Severity | SEVERE
> Description | An exception occurred while loading the application’s deployment descriptor.
> Action | Refer to the exception data for information on how to fix this error.

> ##### LDR5007

> Severity | WARNING
> Description | This error is caused by LDR5001.
> Action | Verify that the specified file path is valid and exists.

> ##### LDR5008

> Severity | WARNING
> Description | An error occurred while getting the deployment location of the deployed connector module.
> Action | Refer to the exception data for details.

> ##### LDR5009

> Severity | WARNING
> Description | An error occurred while creating the URL.
> Action | Make sure the filename and path is correct.

> ##### LDR5011

> Severity | WARNING
> Description | The class specified under the <ejb-class> element of the EJB deployment descriptor could not be found.
> Action | Make sure the class exists in the deployment directory or the generated directory of the server instance.

> ##### LDR5012

> Severity | SEVERE
> Description | The JNDI name you assigned to the bean is already in use by another bean.
> Action | Assign a different JNDI name to the bean.

> ##### LDR5013

> Severity | SEVERE
> Description | This is the actual exception caused by LDR5012.
> Action | Assign a different JNDI name to the bean.

> ##### LDR5100

> Severity | SEVERE
> Description | A configuration exception occurred.
> Action | Analyze the System, as described on (more...) .

> ##### LDR5101

> Severity | SEVERE
> Description | The META-INF/application.xml file could not be read, parsed or loaded.
> Action | Verify that the META-INF/application.xml exists in the application's deployment directory and is formatted correctly.

> ##### LDR5200

> Severity | SEVERE
> Description | An exception, java.io.IOException occurred while trying to access the application deployment directory.
> Action | Ensure that the application deployment directory exists.

> ##### LDR5201

> Severity | WARNING
> Description | The environment property, com.sun.aas.installRoot is not set. Therefore, the location of the EJB class loader’s CodeSource is set to the current working directory.
> Action | This system property is set internally. Analyze the System, as described on (more...) .

> ##### LDR5202

> Severity | WARNING
> Description | An exception java.io.IOException occurred while trying to read the resource file from disk.
> Action | Refer to the exception data for details.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.