DPL Messages

DPL5001

Class loader could not be made

Cause:

TBD

Solution:

TBD

DPL5002

Cannot Add Icon

Cause:

TBD

Solution:

TBD

DPL5003

SAX Parser cannot validate

Cause:

TBD

Solution:

TBD

DPL5004

Cannot add jar to output stream

Cause:

TBD

Solution:

TBD

DPL5005

Unexpected I/O Exception

Cause:

TBD

Solution:

TBD

DPL5006

Error reading connector xml

Cause:

TBD

Solution:

TBD

DPL5007

Error loading class [{0}]

Cause:

TBD

Solution:

TBD

DPL5008

Error loading class

Cause:

TBD

Solution:

TBD

DPL5009

Error loading the ejb class [{0}] in getFields on EjbDescriptor\n [{1}]

Cause:

TBD

Solution:

TBD

DPL5010

Error loading ejb class in getFields on EjbDescriptor

Cause:

TBD

Solution:

TBD

DPL5011

Error loading the ejb class in getFieldForName on EjbDescriptor [{0}]

Cause:

TBD

Solution:

TBD

DPL5012

Error loading the ejb class in getFieldForName on EjbDescriptor [{0}]

Cause:

TBD

Solution:

TBD

DPL5013

Mail Configuration Exception

Cause:

TBD

Solution:

TBD

DPL5014

[{0}] not found in [{1}]

Cause:

TBD

Solution:

TBD

DPL5015

Method not found

Cause:

TBD

Solution:

TBD

DPL5016

Cannot instantiate implementation of [{0}]

Cause:

TBD

Solution:

TBD

DPL5017

Cannot instantiate implementation

Cause:

TBD

Solution:

TBD

DPL5018

Error while parsing

Cause:

TBD

Solution:

TBD

DPL5019

Illegal Argument(s)

Cause:

TBD

Solution:

TBD

DPL5020

SAX Parser cannot parse given stream

Cause:

TBD

Solution:

TBD

DPL5021

No method found for XML query element

Cause:

TBD

Solution:

TBD

DPL5022

Supplied External Descriptors are incorrect

Cause:

TBD

Solution:

TBD

DPL5023

class not found

Cause:

TBD

Solution:

TBD

DPL5024

Cannot expand jar archive

Cause:

TBD

Solution:

TBD

DPL5025

Error in SAX parser configuration

Cause:

TBD

Solution:

TBD

DPL5026

Exception in SAX parser

Cause:

TBD

Solution:

TBD

DPL5027

Cannot create package

Cause:

TBD

Solution:

TBD

DPL5028

Unexpected exception in MethodDescriptor.getMethod()

Cause:

TBD

Solution:

TBD

DPL5029

Cannot read runtime descriptor nodes

Cause:

TBD

Solution:

TBD

DPL5030

Cannot read EJB nodes

Cause:

TBD

Solution:

TBD

DPL5031

Cannot read method descriptor nodes

Cause:

TBD

Solution:

TBD

DPL5032

An authentication method was not defined in the web.xml descriptor. Using default BASIC for login configuration.

Cause:

TBD

Solution:

TBD

DPL5033

Error parsing application.xml

Cause:

TBD

Solution:

TBD

DPL5034

Rollback failed

Cause:

TBD

Solution:

TBD

DPL5035

Error while running ejbc

Cause:

TBD

Solution:

TBD

DPL5036

Duplicate entry in jar archive

Cause:

TBD

Solution:

TBD

DPL5037

Error reading runtime descriptor nodes

Cause:

TBD

Solution:

TBD

DPL5038

Verification Results: \n\tNumber of Failure(s): {0}\n\tNumber of Warning(s): {1}\n\tNumber of Error(s): {2}

Cause:

TBD

Solution:

TBD

DPL5039

Caught a Throwable in POST_DEPLOY Event

Cause:

TBD

Solution:

TBD

DPL5040

Caught a Throwable in PRE_UNDEPLOY Event

Cause:

TBD

Solution:

TBD

DPL5041

Unknown port-component-name {0} port, all sub elements will be ignored"

Cause:

TBD

Solution:

TBD

DPL5100

EJBC - Could not generate new source

Cause:

TBD

Solution:

TBD

DPL5101

EJBC - Could not invoke rmic

Cause:

TBD

Solution:

TBD

DPL5102

EJBC - rmic compilation failed

Cause:

TBD

Solution:

TBD

DPL5103

EJBC - compilation failed

Cause:

TBD

Solution:

TBD

DPL5104

EJBC - code gen required check error

Cause:

TBD

Solution:

TBD

DPL5105

EJBC - Start of CMP section for [{0}]

Cause:

TBD

Solution:

TBD

DPL5106

EJBC - End of CMP section for [{0}]

Cause:

TBD

Solution:

TBD

DPL5107

EJBC - Generated code for EJBLocalHOme, EJBLocalObject implementations for [{0}]

Cause:

TBD

Solution:

TBD

DPL5108

EJBC - Generated code for remote home and EJBObject implementations for [{0}]

Cause:

TBD

Solution:

TBD

DPL5109

EJBC - START of EJBC for [{0}]

Cause:

TBD

Solution:

TBD

DPL5110

EJBC - END of EJBC for [{0}]

Cause:

TBD

Solution:

TBD

DPL5150

Run time exception during R/O bean notifier initialization

Cause:

TBD

Solution:

TBD

DPL5200

Could not invoke rmic

Cause:

TBD

Solution:

TBD

DPL5201

rmic compilation failed...

Cause:

TBD

Solution:

TBD

DPL5202

Exception occurred compiling ejb

Cause:

TBD

Solution:

TBD

DPL5203

Output jarfile [{0}] already exists

Cause:

TBD

Solution:

TBD

DPL5204

Exception occurred while loading class [{0}]

Cause:

TBD

Solution:

TBD

DPL5205

Exception occurred while generating ejb

Cause:

TBD

Solution:

TBD

DPL5206

Class not found

Cause:

TBD

Solution:

TBD

DPL5207

Some IO exception occurred

Cause:

TBD

Solution:

TBD

DPL5208

Some exception occurred

Cause:

TBD

Solution:

TBD

DPL5209

Adding to generated files: [{0}]

Cause:

TBD

Solution:

TBD

DPL5210

Error generating code: [{0}]

Cause:

TBD

Solution:

TBD

DPL5211

Error in setting message status

Cause:

TBD

Solution:

TBD

DPL5212

Error in notification

Cause:

TBD

Solution:

TBD

DPL5212

Attempt to override reserved ejb interface method [{0}] in [{1}]. Override will be ignored.

Cause:

TBD

Solution:

TBD

DPL5300

Interrupted while waiting for execution of [{0}]

Cause:

TBD

Solution:

TBD

DPL5301

Timeout [{0}] milliseconds reached, Interrupting execution of command [{1}].

Cause:

TBD

Solution:

TBD

DPL5302

Process creation failed.

Cause:

TBD

Solution:

TBD

DPL5303

Error in closing process output or error stream.

Cause:

TBD

Solution:

TBD

DPL5303

Execution of command in a sub-process interrupted.

Cause:

TBD

Solution:

TBD

DPL5304

Execution of process failed

Cause:

TBD

Solution:

TBD

DPL5305

Error reading from process output or error stream

Cause:

TBD

Solution:

TBD

DPL5306

{0} Web Service Endpoint [{1}] listening at address [{2}]

Cause:

TBD

Solution:

TBD

DPL5400

Exception occurred : {0}.\

Cause:

TBD

Solution:

TBD

DPL5401

Optional package {0} does not exist or its Specification-Version doesnot match!! Unable to satisfy dependency for {1}

Cause:

TBD

Solution:

TBD

DPL5402

Optional package dependency satisfied for {0}

Cause:

TBD

Solution:

TBD

DPL5403

Either Extension-Name or Specification-Version for the optional package is not specified for {0}.\

Cause:

TBD

Solution:

TBD

DPL5404

Specification-Version for the optional package {0} is null!!! Please provide a valid specification version for this optional package

Cause:

TBD

Solution:

TBD

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.