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

> ## Chapter 7
> Deployment

> This chapter lists error messages that originate from the Deployment subsystem.

> ##

> DPL

> ##### DPL5001

> Severity | SEVERE
> Description | An error occurred while loading all the classes within the JAR.
> Action | See the stack trace for more information and make sure the corresponding JAR file exists.

> ##### DPL5002

> Severity | SEVERE
> Description | Unable to add an icon.
> Action | See the stack trace for more information and make sure the icon file is available in the JAR file.

> ##### DPL5003

> Severity | WARNING
> Description | SAX Parser cannot validate. This error or warning message is sent either from the XML parser or the application.
> Action | See the stack trace for more information. If it is an XML parser error, Analyze the System, as described on (more...) . If the error is from the application, make sure the XML file is valid.

> ##### DPL5004

> Severity | WARNING
> Description | Cannot add JAR to output stream.
> Action | Make sure the user has appropriate access permission to the temporary directory, tmp, and there is sufficient space in the tmp directory.

> ##### DPL5005

> Severity | WARNING
> Description | An IO exception occurred. This error occurs when deployment backend tries to create a file in the specified directory.
> Action | Make sure the user has appropriate access permission to the temporary directory, tmp, and there is sufficient space in the tmp directory.

> ##### DPL5006

> Severity | WARNING
> Description | An error occurred while reading the connector.xml file. This error occurs while converting the XML subtree representing connector information into a connector descriptor object.
> Action | See the stack trace for more information and see if the supplied connector.xml file exists and is valid.

> ##### DPL5007

> Severity | SEVERE
> Description | An error occurred while loading the class, EjbDescriptor.getMethods().
> Action | See the stack trace for more information and see if the class exists in the classpath.

> ##### DPL5008

> Severity | SEVERE
> Description | An error occurred while loading the class.
> Action | See the stack trace for more information and see if the class exists in the classpath.

> ##### DPL5009

> Severity | SEVERE
> Description | An error occurred while loading the EJB class, in getFields on EjbDescriptor.
> Action | See the stack trace for more information and see if the EJB class is available.

> ##### DPL5010

> Severity | SEVERE
> Description | An error occurred while loading the EJB class in getFields on EjbDescriptor.
> Action | See the stack trace for more information and see if the EJB class is available.

> ##### DPL5011

> Severity | SEVERE
> Description | An error occurred while loading the EJB class in getFieldForName on EjbDescriptor.
> Action | See the stack trace for more information and see if the EJB class is available.

> ##### DPL5012

> Severity | SEVERE
> Description | An error occurred while loading the EJB class in getFieldForName on EjbDescriptor.
> Action | See the stack trace for more information and see if the EJB class is available.

> ##### DPL5013

> Severity | SEVERE
> Description | A mail configuration exception occurred while loading the configuration information from the mail resource node in server.xml for the JavaMail session object.
> Action | See the stack trace for more information.

> ##### DPL5014

> Severity | SEVERE
> Description | A method not found in ejbDescriptor.
> Action | See the stack trace for more information and make sure the EJB bean contains this method.

> ##### DPL5015

> Severity | SEVERE
> Description | The method was not found.
> Action | See the stack trace for more information and make sure the EJB bean contains this method.

> ##### DPL5016

> Severity | WARNING
> Description | Unable to instantiate implementation of interface. This is a configuration error.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5017

> Severity | WARNING
> Description | Unable to instantiate implementation. This is a configuration error.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5018

> Severity | WARNING
> Description | An error occurred while parsing. This error occurs while translating an input stream containing the XML document into the implementation object for Taglib.
> Action | See the stack trace for more information and make sure the XML file is valid.

> ##### DPL5019

> Severity | WARNING
> Description | Illegal argument(s). This warning occurs while constructing the application object from the XML tree (application.xml).
> Action | Make sure the application.xml of a particular EAR file is valid.

> ##### DPL5020

> Severity | SEVERE
> Description | SAX Parser cannot parse given stream. This message is sent from the XML parser or the application.
> Action | Make sure the application.xml file is valid. If the error occurred from the XML Parser, Analyze the System, as described on (more...) .

> ##### DPL5021

> Severity | SEVERE
> Description | No method found for XML query element. This error occurs when the tags in the ejb-jar.xml file does not have respective query methods.
> Action | Make sure the ejb-jar.xml file tags are valid.

> ##### DPL5022

> Severity | WARNING
> Description | Supplied external descriptors are incorrect. This error occurs while adding the EJB JAR file into the application using the given descriptor entry name.
> Action | See the stack trace and make sure the specified descriptor entry name (ejb-jar.xml) is available.

> ##### DPL5023

> Severity | WARNING
> Description | Unable to find the class.
> Action | See the stack trace for more information.

> ##### DPL5024

> Severity | WARNING
> Description | Unable to expand JAR archive.
> Action | Make sure there is sufficient disk space and that the user has access permission to the directory.

> ##### DPL5025

> Severity | WARNING
> Description | An error occurred in the SAX parser configuration.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5026

> Severity | WARNING
> Description | An exception occurred in the SAX parser. This warning message is sent from either the XML parser or the application.
> Action | Make sure the archive (ear/jar) XML files are valid. See the stack trace for more information. If the problem persists, Analyze the System, as described on (more...) .

> ##### DPL5028

> Severity | SEVERE
> Description | An exception occurred in MethodDescriptor.getMethod(). This error occurs while getting the method from EjbDescriptor which contains the meta-information describing EJBs.
> Action | See the stack trace for more information. Make sure the method name exists in the EJB.

> ##### DPL5029

> Severity | WARNING
> Description | Unable to read runtime descriptor nodes (XML file for runtime bindings for a J2EE application) from the input stream.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5030

> Severity | WARNING
> Description | Unable to read EJB nodes from the input stream (containing the ejb-jar.xml file).
> Action | Make sure the ejb-jar.xml content is valid.

> ##### DPL5031

> Severity | WARNING
> Description | Unable to read the method descriptor nodes (XML format of a method element) from the input stream representing XML.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5032

> Severity | WARNING
> Description | An authentication method was not defined in the web.xml descriptor and is therefore using the default, BASIC, for login configuration.
> Action | Make sure the web.xml file, login-config element contains the value for auth-method.

> ##### DPL5034

> Severity | WARNING
> Description | An error in the deployment and consequently Rollback failed.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5035

> Severity | WARNING
> Description | An error occurred while deploying the EJB module and generating clientStubs.
> Action | See the stack trace for more information.

> ##### DPL5036

> Severity | WARNING
> Description | A duplicate entry exists in the JAR archive. This error occurs when two files with the same name are added into the JAR archive while creating the client JAR archive.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5100

> Severity | SEVERE
> Description | Unable to generate new source. This error occurs while generating the Java files (EJBHome/EJBObject).
> Action | See the stack trace for more information. If you are unable to fix the error, Analyze the System, as described on (more...) .

> ##### DPL5101

> Severity | SEVERE
> Description | Unable to invoke rmic.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5102

> Severity | SEVERE
> Description | This error is sent by the rmic compiler while generating stub or skeletons from EJBHome/EJBRemote.
> Action | See the stack trace for more information. Analyze the System, as described on (more...) .

> ##### DPL5103

> Severity | SEVERE
> Description | EJBC compilation failed. This error occurs during the compilation of generated Java files (EJBHome/Remot/stub/skeletons).
> Action | See the stack trace for more information. Analyze the System, as described on (more...) .

> ##### DPL5104

> Severity | WARNING
> Description | The EJBC code gen required check error. This error occurs when EAR or JAR files are redeployed. The deployment backend checks if the EAR/JAR file and the new EAR/JAR file to be deployed are similar, to determine if deployment backend must regenerate Home/Remote implementation code for an EJB.
> Action | Make sure both the new and old ear/jar file exists.

> ##### DPL5200

> Severity | SEVERE
> Description | Unable to invoke rmic. This error occurs when the deployment backend is not able to invoke the rmic.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5201

> Severity | SEVERE
> Description | The rmic compilation failed. This error occurs when the generated Java files (EJBHome/Remote) are sent to the rmic for generating stubs/skeletons.
> Action | See the stack trace for more information. Analyze the System, as described on (more...) .

> ##### DPL5202

> Severity | SEVERE
> Description | An exception occurred while compiling the EJB. This error occurs when compiling the generated Java files (EJBHome/EJBRemote).
> Action | Analyze the System, as described on (more...) .

> ##### DPL5203

> Severity | WARNING
> Description | The output JAR file already exists. This error occurs while generating the jar for this application and the JAR file with the same name exists.
> Action | Check if the application Cooked.jar exists where the GeneratorDriver is running.

> ##### DPL5204

> Severity | WARNING
> Description | An exception occurred while loading the class. This exception occurs while loading the stubs/skeletons of home/interface classes in EAR.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5205

> Severity | SEVERE
> Description | An exception occurred while generating EJB. This error occurs while running rmic on generated Java (EJBHome/Remote)files.
> Action | See the stack trace for more information.

> ##### DPL5206

> Severity | SEVERE
> Description | This error occurs either while loading the bean implementation class or while loading the stubs for all the EJBHome/EJBRemote classes in the JAR.
> Action | Make sure the bean implementation class is present in the JAR. If the problem persists, Analyze the System, as described on (more...) .

> ##### DPL5207

> Severity | SEVERE
> Description | An IO exception occurred. This error occurs when the deployment backend (GeneratorDriver) tries to get an application object representing the EAR file.
> Action | Make sure the application.xml file is present in ear file.

> ##### DPL5208

> Severity | SEVERE
> Description | An exception occurred.
> Action | See the stack trace for more information.

> ##### DPL5209

> Severity | WARNING
> Description | This exception occurs when the deployment backend adds generated files (EJBHome/EJBObject) to the generated file list.
> Action | See the stack trace for more information.

> ##### DPL5210

> Severity | SEVERE
> Description | An error occurred while generating code. This error occurs when the deployment backend runs the generator to generates files for EJBHome/EJBObject.
> Action | See the stack trace for more information.

> ##### DPL5211

> Severity | SEVERE
> Description | An error occurred while setting the message status. This error occurs when the deployment client (remote/local) sends a request to the deployment backend and the backend sends a message to the client requesting the status. This is a communication related exception that occurs during the execution of remote method call.
> Action | Analyze the System, as described on (more...) .

> ##### DPL5212

> Severity | WARNING
> Description | This error occurs when the deployment client (remote/local) sends a request to the deployment backend and the backend sends a notification event to the client. This is a communication related exception that occurs during the execution of remote method call.
> Action | Analyze the System, as described on (more...) .

> Previous Contents Index Next

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