Chapter 2 DPL Error Messages

This chapter describes messages for errors with a DPL prefix.

DPL Messages

DPL8001

Event subsystem does not recognize the new implementation of the server context found in runtime.

Cause:

The instance may not be of expected type

Solution:

Ensure that the descriptor type is set as expected. Set log level for deployment to view more details.

DPL8002

Copying of files failed.

Cause:

May be because of lack of space or permission.

Solution:

Ensure that the permissions are set as expected and that there is enough disk space.

DPL8003

ArchivistFactory.getArchivist() failed

Cause:

The module type may not be as expected.

Solution:

Ensure that the module type is one of the supported types.

DPL8004

Opening of files failed.

Cause:

May be because of lack of permission or wrong file name.

Solution:

Ensure that the file name is correct, and that the permissions are set as expected.

DPL8005

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. Also ensure that the SAX parser configuration is correct and the descriptor has right permissions.

DPL8006

Adding or getting a descriptor failed.

Cause:

May be because the node/information to be added is not valid; may also be because of the descriptor was not registered.

Solution:

Ensure that the node to be added is valid, and that the permissions are set as expected.

DPL8007

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, and that there is no typo in the resource specified in the descriptor.

DPL8008

Failed to load the class/method.

Cause:

May be because of wrong class/method name.

Solution:

Ensure that the class/method specified is present, and that the path information is correct.

DPL8009

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, and that there is no typo in the URI specified.

DPL8010

Failed in autodeployment.

Cause:

May be because of failure in creating the autodeployer or while reading the autodeploy configuration info.

Solution:

Ensure that the autodeploy is enabled properly, and that their autodeploy configuration is set properly.

DPL8011

Failed in autodeployment of applications.

Cause:

Mostly because of application specific failure.

Solution:

Ensure that the application can be deployed using CLI, and that there autodeploy configuration is set properly and the server is up and running.

DPL8012

Failed to rename directory.

Cause:

May be because of lack of permissions.

Solution:

Ensure that the permissions are set as expected, and that the there is no directory name clash.

DPL8013

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, and that the there is enough space.

DPL8014

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, and that the there is enough space.