| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server 3.1 Error Message Reference |
DPL5001 Class loader could not be made
Description: TBD
DPL5002 Cannot Add Icon
Description: TBD
DPL5003 SAX Parser cannot validate
Description: TBD
DPL5004 Cannot add jar to output stream
Description: TBD
DPL5005 Unexpected I/O Exception
Description: TBD
DPL5006 Error reading connector xml
Description: TBD
DPL5007 Error loading class [{0}]
Description: TBD
DPL5008 Error loading class
Description: TBD
DPL5009 Error loading the ejb class [{0}] in getFields on EjbDescriptor\n [{1}]
Description: TBD
DPL5010 Error loading ejb class in getFields on EjbDescriptor
Description: TBD
DPL5011 Error loading the ejb class in getFieldForName on EjbDescriptor [{0}]
Description: TBD
DPL5012 Error loading the ejb class in getFieldForName on EjbDescriptor [{0}]
Description: TBD
DPL5013 Mail Configuration Exception
Description: TBD
DPL5014 [{0}] not found in [{1}]
Description: TBD
DPL5015 Method not found
Description: TBD
DPL5016 Cannot instantiate implementation of [{0}]
Description: TBD
DPL5017 Cannot instantiate implementation
Description: TBD
DPL5018 Error while parsing
Description: TBD
DPL5019 Illegal Argument(s)
Description: TBD
DPL5020 SAX Parser cannot parse given stream
Description: TBD
DPL5021 No method found for XML query element
Description: TBD
DPL5022 Supplied External Descriptors are incorrect
Description: TBD
DPL5023 class not found
Description: TBD
DPL5024 Cannot expand jar archive
Description: TBD
DPL5025 Error in SAX parser configuration
Description: TBD
DPL5026 Exception in SAX parser
Description: TBD
DPL5027 Cannot create package
Description: TBD
DPL5028 Unexpected exception in MethodDescriptor.getMethod()
Description: TBD
DPL5029 Cannot read runtime descriptor nodes
Description: TBD
DPL5030 Cannot read EJB nodes
Description: TBD
DPL5031 Cannot read method descriptor nodes
Description: TBD
DPL5032 An authentication method was not defined in the web.xml descriptor. Using default BASIC for login configuration.
Description: TBD
DPL5033 Error parsing application.xml
Description: TBD
DPL5034 Rollback failed
Description: TBD
DPL5035 Error while running ejbc
Description: TBD
DPL5036 Duplicate entry in jar archive
Description: TBD
DPL5037 Error reading runtime descriptor nodes
Description: TBD
DPL5038 Verification Results: \n\tNumber of Failure(s): {0}\n\tNumber of Warning(s): {1}\n\tNumber of Error(s): {2}
Description: TBD
DPL5039 Caught a Throwable in POST_DEPLOY Event
Description: TBD
DPL5040 Caught a Throwable in PRE_UNDEPLOY Event
Description: TBD
DPL5041 Unknown port-component-name {0} port, all sub elements will be ignored"
Description: TBD
DPL5042 Construct a Dummy EJB Descriptor with name {0}
Description: TBD
DPL5043 Setting transaction type for dummy ejb {0}
Description: TBD
DPL5044 Setting type for dummy ejb {0}
Description: TBD
DPL5100 EJBC - Could not generate new source
Description: TBD
DPL5101 EJBC - Could not invoke rmic
Description: TBD
DPL5102 EJBC - rmic compilation failed
Description: TBD
DPL5103 EJBC - compilation failed
Description: TBD
DPL5104 EJBC - code gen required check error
Description: TBD
DPL5105 EJBC - Start of CMP section for [{0}]
Description: TBD
DPL5106 EJBC - End of CMP section for [{0}]
Description: TBD
DPL5107 EJBC - Generated code for EJBLocalHOme, EJBLocalObject implementations for [{0}]
Description: TBD
DPL5108 EJBC - Generated code for remote home and EJBObject implementations for [{0}]
Description: TBD
DPL5109 EJBC - START of EJBC for [{0}]
Description: TBD
DPL5110 EJBC - END of EJBC for [{0}]
Description: TBD
DPL5150 Run time exception during R/O bean notifier initialization
Description: TBD
DPL5200 Could not invoke rmic
Description: TBD
DPL5201 rmic compilation failed...
Description: TBD
DPL5202 Exception occurred compiling ejb
Description: TBD
DPL5203 Output jarfile [{0}] already exists
Description: TBD
DPL5204 Exception occurred while loading class [{0}]
Description: TBD
DPL5205 Exception occurred while generating ejb
Description: TBD
DPL5206 Class not found
Description: TBD
DPL5207 Some IO exception occurred
Description: TBD
DPL5208 Some exception occurred
Description: TBD
DPL5209 Adding to generated files: [{0}]
Description: TBD
DPL5210 Error generating code: [{0}]
Description: TBD
DPL5211 Error in setting message status
Description: TBD
DPL5212 Attempt to override reserved ejb interface method [{0}] in [{1}]. Override will be ignored.
Description: TBD
DPL5300 Interrupted while waiting for execution of [{0}]
Description: TBD
DPL5301 Timeout [{0}] milliseconds reached, Interrupting execution of command [{1}].
Description: TBD
DPL5302 Process creation failed.
Description: TBD
DPL5303 Execution of command in a sub-process interrupted.
Description: TBD
DPL5304 Execution of process failed
Description: TBD
DPL5305 Error reading from process output or error stream
Description: TBD
DPL5306 {0} Web Service Endpoint [{1}] listening at address [{2}]
Description: TBD
DPL5400 Exception occurred : {0}.\
Description: TBD
DPL5401 Optional package {0} does not exist or its Specification-Version does not match!! Unable to satisfy dependency for {1}
Description: TBD
DPL5402 Optional package dependency satisfied for {0}
Description: TBD
DPL5403 Either Extension-Name or Specification-Version for the optional package is not specified for {0}.\
Description: TBD
DPL5404 Specification-Version for the optional package [ {0} ] in the jarfile [ {1} ] is not specified. Please provide a valid specification version for this optional package
Description: TBD
DPL5405 Class {0} is not found
Description: TBD
DPL5406 Method {0} is not found
Description: TBD
DPL5407 Exception in populating default WebBundleDescriptor from default-web.xml {0}
Description: TBD
DPL5408 Ignore: {0}
Description: TBD
DPL5409 Exception in getting resources: {0}
Description: TBD
DPL5410 Skipping extension processing for {0} due to error: {1}
Description: TBD
DPL5411 Error in opening optional package file {0} due to exception: {1}.
Description: TBD
DPL5412 Bad format: checkpointed-methods [{0}]
Description: TBD
DPL8001 descriptor failure {0}
Cause: Archivist.setDescriptor() failed
Cause: The instance may not be of expected type
Solution: Ensure that the descriptor type is set as expected
Solution: Turn log level for deployment to see more details
DPL8002 file copy failure
Cause: Copying of files failed
Cause: May be because of lack of space or permission
Solution: Ensure that there is enough disk space
Solution: Ensure that the permissions are set as expected
DPL8003 archivist instantiation failure for {0}; type = {1}
Cause: ArchivistFactory.getArchivist() failed
Cause: the module type may not be as expected
Solution: Ensure that the module type is one of the supported types
Solution: Ensure that the module type is one of the supported types
DPL8004 file open failure; file = {0}
Cause: Opening of files failed
Cause: May be because of lack of permission or wrong file name
Solution: Ensure that the file name is correct
Solution: Ensure that the permissions are set as expected
DPL8005 Deployment Descriptor parsing failure : {0}
Cause: Error while parsing the deployment descriptor
Cause: May be because of malformed descriptor or absence of all required descriptor elements
Solution: Ensure that the descriptor is well formed and as per specification
Solution: Ensure that the SAX parser configuration is correct and the descriptor has right permissions
DPL8006 get/add descriptor failure : {0} TO {1}
Cause: Adding or getting a descriptor failed
Cause: May be because the node / information to be added is not valid; may be because of the descriptor was not registered
Solution: Ensure that the node to be added is valid
Solution: Ensure that the permissions are set as expected
DPL8007 Unsupported deployment descriptors element {0} value {1}
Cause: Failed to find the resource specified in the deployment descriptor
Cause: May be because of wrong specification in the descriptor
Solution: Ensure that the resource specified is present
Solution: Ensure that there is no typo in the resource specified in the descriptor
DPL8008 method/class loading failure : {0} \n method/class name - {1}
Cause: Failed to load the class / method
Cause: May be because of wrong class/method name
Solution: Ensure that the class / method specified is present
Solution: Ensure that the path info is correct
DPL8009 deployment manager load failure : unable to load - {0}
Cause: Failed to load the deployment manager
Cause: May be because of wrong uri specification or deployment factory not installed at all
Solution: Ensure that the resource specified is present
Solution: Ensure that there is no typo in the URI specified
DPL8010 autodeployment startup failure
Cause: Failed in autodeployment
Cause: May be because of failure in creating the autodeployer or while reading the autodeploy config info
Solution: Ensure that the autodeploy is enabled properly
Solution: Ensure that there autodeploy config info is set properly
DPL8011 autodeployment failure while deploying the application : {0}
Cause: Failed in autodeployment of applications
Cause: Mostly because of application specific failure
Solution: Ensure that the application can be deployed using CLI
Solution: Ensure that there autodeploy config info is set properly and the server is up and running
DPL8012 directory rename failure : {0} TO {1}
Cause: Failed to rename directory
Cause: May be because of lack of permissions
Solution: Ensure that the permissions are set as expected
Solution: Ensure that there is no directory name clash
DPL8013 JAR file creation failure : {0}
Cause: Failed to create JAR file
Cause: May be because of lack of permissions or lack of space
Solution: Ensure that the permissions are set as expected
Solution: Ensure that there is enough space
DPL8014 Application deployment failure
Cause: Failed to complete application deployment
Cause: May be because of lack of permissions or lack of space or wrong application
Solution: Ensure that the permissions are set as expected
Solution: Ensure that there is enough space
DPL8015 This application has no role mapper factory defined
Cause: Failed to find the resource specified in the deployment descriptor
Cause: May be because of wrong specification in the descriptor
Solution: Ensure that the resource specified is present
Solution: Ensure that there is no typo in the resource specified in the descriptor
DPL8017 Ejb-ref type mismatch for ejb reference {0}. Reference declares type {1} but target ejb {2} has {3} interface of type {4}.
Cause: Possible type mismatch in ejb-ref/ejb-local-ref/@EJB
Cause: May be because of wrong specification in the descriptor
Solution: Ensure that the type associated with the ejb reference is the correct one.
Solution: Ensure that there is no typo in the resource specified in the descriptor
DPL8018 Invalid spec version {0}, reset to value {1}
Description: TBD
DPL8019 The run-as principal {0} was assigned by the deployment system based on the specified role. Please consider defining an explicit run-as principal in the sun-specific deployment descriptor.
Description: TBD
DPL8020 The role-name is empty. The may not be what the developer had in mind. Please check this.
Description: TBD
DPL8021 Invalid URL {0} specified for WSDL location
Cause: Failed to create a URL from the wsdl location specified
Cause: May be because of wrong specification in the descriptor
Solution: Ensure that the resource specified is a valid URL
Solution: Ensure that there is no typo in the resource specified in the descriptor
DPL8022 Artifact {0} identified for inclusion in app clients after one or more app clients were generated.
Cause: The application might specify that modules are to be processed in the order they appear in the application and an app client module appears before a module that creates an artifact to be included in app clients.
Solution: Make sure, if the application specifies initialize-in-order as true, that the app clients appear after other modules which generated artifacts that should be accessible to app clients.
DPL8023 URL Pattern contains CR(#xD) or LF(#xA): [{0}]. Leading and trailing whitespace will be ignored.
Description: TBD
DPL8024 Artifact with relative path {0} expected at {1} but does not exist or cannot be read
Cause: The server is attempting to register an artifact to be included in the generated app client JAR but the artifact does not exist or cannot be read
Solution: This is an internal server error. Please file a bug report.
DPL8025 Artifact with relative path {0} from {1} collides with an existing artifact from file {2}
Cause: The server has created more than one artifact with the same relative path to be included in the generated app client JAR file
Solution: This is an internal server error. Please file a bug report.
DPL8026 Submodule {0} has been expanded from the EAR into the same relative location as the location where it would be copied for internal use, but is of the type {1} which is not the type the rest of deployment will expect.
Cause: A submodule in an EAR can have the same name as its expansion location but the submodule must be of the correct storage type (such as a directory, not a JAR) as well.
Solution: Rename the submodule JAR in the application so it is not the same name as the expansion directory the server uses, or keep the same name but package it in the EAR as a subdirectory and not as a JAR file.
DPL8027 Ignore {0} in archive {1}, as GlassFish counterpart runtime xml {2} is present in the same archive.
Description: TBD
DPL8028 [{0}] is not an allowed WebLogic module type. Allowed module types are JMS, JDBC and Interception.
Description: TBD
DPL8029 Ignore {0} in archive {1}, as Sun counterpart runtime xml {2} is present in the same archive.
Description: TBD
DPL8030 Sun specific deployment descriptor ({0} in archive {1}) is deprecating, please use GlassFish specific deployment descriptor {2} in the future.
Description: TBD
DPL8031 Ignoring {0} with time {1} because timestamp on containing archive {2}, {3}, is later
Cause: A file inside a file archive predates the archive and is therefore being hidden and will appear not to exist in the archive
Solution: The file might have been opened but never closed, for instance during an earlier deployment of an application, and incorrectly remains in the archive after an undeployment.
|