DPL

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 Invalid 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 : method/class name - {0}

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

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.

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.