GlassFish Wiki : AppServerErrorMessages

Please go to the Glassfish Application Server 9.1 Error Message Reference for the 9.1 version of this guide.

Application Server 9.0 Platform Edition Error Message Reference

Overview

About This Wiki

This Wiki is intended to be an interactive, editable version of the Sun Java System Application Server 9.0 Error Message Reference.

The most significant shortcoming of the current Error Message Reference is that it does not contain enough information – it pretty much contains just the error message IDs and message strings, with little or no explanatory text. The challenge is that it takes a lot of time to develop meaningful descriptions and solutions/workarounds for the problems indicated by the error messages, more time than either the developers or doc writers can currently afford. Moreover, meaningful solutions are really only available after the product has been in "the wild" for some time.

What follows here is the complete SEVERE error message catalog for Application Sever 9.0 Platform Edition. Please add your comments, descriptions, solutions and/or workarounds!

How This Wiki is Organized

The error messages in this Wiki are categorized according to their message ID prefix. For example, messages with a DPL prefix are in the section titled "DPL Error Messages." In addition, there is a general section at the beginning for "Unexpected Errors."

Preface

This guide describes error messages you may encounter when using the Sun Javaâ¢ System Application Server 9.0 Enterprise Edition and Platform Edition software. The error messages described here can also be viewed with the Application Server Log Viewer.

Who Should Use This Book

The Sun Java System Application Server Platform Edition 9.0 2006Q1 Error Message Reference is intended for developers and administrators who use the Sun Java System Application Server to assemble and deploy distributed and Web-based applications.

This guide assumes you are familiar with the following topics:

Java APIs as defined in the Javaâ¢ Servlet, JavaServer Pagesâ¢ (JSPâ¢), Enterprise JavaBeansâ¢ (EJBâ¢), and Java Database Connectivity (JDBCâ¢) specifications

The SQL structured database query languages

Relational database concepts

Before You Read This Book

Application Server can be purchased by itself or as a component of Sun Javaâ¢ Enterprise System (JavaÂ ES), a software infrastructure that supports enterprise applications distributed across a network or Internet environment. If you purchased ProductName as a component of JavaÂ ES, you should be familiar with the system documentation at http://docs.sun.com/coll/1286.1.

How This Book Is Organized

This guide is a compilation of messages that you may encounter while running the Application Server. Each message begins with a message ID, which has a format like the following:

SubsystemIntegerId:

The subsystem is identified by the initial characters in the message ID. For example, in JMS0001, the subsystem is JMS.

The error messages in this guide are divided into chapters based on the subsystem prefix:

ChapterÂ 1, Unexpected Errors describes unexpected errors you may encounter

ChapterÂ 2, DPL Error Messages lists DPL error messages

ChapterÂ 3, DTX Error Messages lists DTX error messages

ChapterÂ 4, EEADM Error Messages lists EEADM error messages

ChapterÂ 5, EJB Error Messages lists EJB error messages

ChapterÂ 6, JDO Error Messages lists JDO error messages

ChapterÂ 7, JTS Error Messages lists JTS error messages

ChapterÂ 8, MDB Error Messages lists MDB error messages

ChapterÂ 9, NAM Error Messages lists NAM error messages

ChapterÂ 10, RAR Error Messages lists RAR error messages

ChapterÂ 11, SYNC Error Messages lists SYNC error messages

ChapterÂ 12, WEB Error Messages lists WEB error messages

ChapterÂ 13, WSS Error Messages lists WSS error messages

The messages defined in this reference guide also include the following information:

Message: The brief text description accompanying the numeric message ID when viewed in the Application Server Log Viewer.

Cause: Meaning and likely cause of the message.

Solutions/Workarounds: Instructions on how to address the condition that caused the message to be generated.

Accessing Sun Resources Online

The docs.sun.com Web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. Books are available as online files in PDF and HTML formats. Both formats are readable by assistive technologies for users with disabilities.

To access the following Sun resources, go to http://www.sun.com:

Downloads of Sun products

Services and solutions

Support (including patches and updates)

Training

Research

Communities (for example, Sun Developer Network)

Unexpected Errors

Unexpected errors generally result from problems in the configuration (system configuration, JVM configuration, server configuration or application-level configuration). They can also occur when the system runs out of memory, or when there is a system crash, hardware failure, or power failure.

To find cases in which the error has been reported, search for occurrences of the error code (for example, HADB99999) at http://www.sunsolve.sun.com.

In the event of a general system failure, the error message can generally be ignored, because the error is unlikely to reoccur when the system is working properly.

If system memory is an issue, consult the Performance Tuning Guide for suggestions on optimizing your configuration. (Consider taking other actions to remedy the problem as well, such as adding memory or decreasing system load.)

When the system is not the cause, the problem may be due to the configuration settings. If you have recently made changes, consider backing them out.

When all else fails, you may need help analyzing your configuration. In that case, gather the following information and refer to the instructions in "Accessing Sun Resources Online," above:

Detailed information from the body of the message

Stack trace information

System logs

DPL Error Messages

This chapter describes messages for errors with a DPL prefix.

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.

DTX Error Messages

This chapter describes messages for errors with a DTX prefix.

DTX5001: Exception occurred while enlisting the resource.

Solution: Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.

DTX5002: Exception occurred while delisting the resource.

DTX5003: Trying to register the sync object while transaction is marked for rollback.

Solution: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

DTX5004: Exception occurred while enlisting the component resource.

DTX5005: Exception occurred while delisting the component resources.

DTX5006: Exception occurred while delisting the component resources.

DTX5008: Exception occurred while closing the connection.

Solution: Check if database is up and running.

DTX5009: Invalid integer passed to set the timeout.

Solution: Check the timeout that is being given in the server configuration file.

DTX5010: Could not register the JTA statistics for monitoring due to configuration problem.

Solution: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

DTX5011: Requested attribute is not monitorable.

Solution: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

DTX5012: JTAStats implementation class is not found.

Solution: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

EEADM Error Messages

This chapter describes messages for errors with an EEADM prefix.

EEADM0069: Error while sending event to remote instance.

Cause: Most likely an error in the connection layer. User name, password, host name or port number of the remote server instance may be incorrect.

Solution: Verify that user name, password, host name, or port number of the remote server instance is correct.

EJB Error Messages

This chapter describes messages for errors with a EJB prefix.

EJB5013: Problem occurred while deserializing stateful bean state.

Solution: Check the application classpath to ensure that all classes needed during deserialization are available.

EJB5017: An error occurred during the removal of an entity bean.

One common cause is when the application throws a system exception from the ejbRemove method of an entity bean.

Solution: Check the exception stack trace to see if the exception originated from the entity bean implementation class.

EJB5031: An error occurred while looking up a Read Only Bean Notifier.

The most common cause for this failure is that the string supplied to the getReadOnlyBeanNotifier method either does not refer to a read-only bean.

Solution: Check the application code that calls this method to make sure the string passed in refers to a valid read-only bean.

EJB5069: The `bean's` Home or `LocalHome` does not define a `no-arg` create method.

Solution: Check the Home or LocalHome interface for the appropriate create method signature. Running the verifier will help identify the error as well.

EJB5071: Some problem occurred during the `beforeCompletionphase` of the transaction lifecycle.

This error often happens when application code throws a system exception from its ejbStore method or if the transaction manager encounters a system exception.

Solution: Check the stack trace to see if the exception originated from the application's ejbStore method. Also check the resource configuration to ensure that all resource managers involved in the transaction are configured properly and are healthy.

EJB5090: Problem during EJB container runtime initialization.

See stack trace for more details. Some common causes are global JNDI name conflicts, classnotfound errors, and configuration errors for resources needed by the EJB.

Solution: If the EJB has a Remote view, check that its JNDIname does not clash with any other EJB's JNDI name or any other globalJNDI name. Check that all needed classes are available to the EJB. Also ensure that any resources needed by the EJB are available. If the EJB uses a data source make sure the corresponding database is running. If it uses a queue makes sure the physical queue has been created.

EJB5111: This error indicates a mismatch

This error indicates a mismatch in the required method signature rules between a method defined on a (Home, Remote, LocalHome, Local) interface and the corresponding bean implementation class. E.g., this would happen if a create method in a Home interface did not have a matching ejbCreate method in the bean class.

Solution: Run the verifier tool to check that the methods defined on the bean class are correct with respect to the exposed interface.

EJB5117: Error while creating the persistent representation of an EJB timer.

This typically means there is some configuration error or runtime problem with the EJB timer service data source.

Solution: Double-check the JDBC data source (and its associated connection pool) assigned to the timer-data source element in domain.xml. Common causes are that the database is not running, the timer table has not been created within that database, or that the connection pool's JDBC driver URL information is incorrect.

EJB5128: A problem occurred while the container was activating a stateful session bean.

One possible cause is that the bean code threw a system exception from its ejbActivate method.

Solution: Check the stack trace to see whether the exception was thrown from the ejbActivate method and if so double-check the application code to determine what caused the exception.

EJB5129: An error occurred during the `afterCompletion` phase of the transaction lifecycle.

Solution: Check stack trace for details of error encountered by EJB container

JDO Error Messages

This chapter describes messages for errors with a JDO prefix.

JDO7000: Error loading the default mapping policy which is used by database schema generation.

Solution: Check that the classpath settings are not corrupted.

JDO74003: Internal error in CMP module.

Solution: This is an Unexpected Internal Error. Please contact Sun with your application and the complete error log message.

JDO74005: CMR field is accessed in `ejbCreate`.

Solution: Change bean code to access CMR fields in ejbPostCreate.

JDO74006: Parameter passed to Collection CMR set method is null.

Solution: Use Collection.remove() method to remove all related beans from this Collection.

JDO74019: Possible error in EJB Container and CMR runtime life cycle.

Solution: This is an Unexpected Internal Error. Please turn on JDO and CMP logging and contact Sun with the complete error log message.

JDO74020: Possible error in EJB Container and CMR runtime life cycle.

Solution: This is an Unexpected Internal Error. Please turn on JDO and CMP logging and contact Sun with the complete error log message.

JDO74021: `ejbRemove` or `ejbStore` is called in an active transaction without bean being loaded in the same transaction.

Possible error in EJB Container and CMR runtime life cycle.

Solution: This is an Unexpected Internal Error. Please turn on JDO and CMP logging and contact Sun with the complete error log message.

JDO74043: Create, remove, or update is called on a read-only bean.

Solution: Do not attempt to update read-only beans. If update is required, the bean must be deployed as two different EJBs: as a read-only bean, and as an updateable bean. All updates must be done on the second bean.

JDO74045: State class is not generated properly for this CMP bean.

Solution: This is an Unexpected Internal Error. Please contact Sun with your application and the complete error log message.

JDO75007: Internal error in CMP module.

Solution: This is an Unexpected Internal Error. Please contact Sun with your application and the complete error log message.

JDO76604: JNDI name for the CMP resource is misspelled.

CMP resource with this JNDI name is not registered with this instance.
Solution: Check JNDI name for the resource you plan to use. Check JNDI name of the CMP resource specified in the module.

JDO7704: Cannot identify related field.

Cannot identify related class.
Solution: Verify that relationship definition is correct.

JDO82000: System was not able to create specified logger.

Error loading message bundle that corresponds to this logger.
Solution: Check that the classpath settings are not corrupted. Check error log for the detailed reason.

JTS Error Messages

This chapter describes messages for errors with a JTS prefix.

JTS5001: Servant is already active.

Servant is not active.
Solution: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

JTS5005: Recovery or resync process got interrupted.

Solution: See the server log for more details. This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

JTS5008: Transaction log directory is not accessible.

Solution: Make sure that the Transaction log directory (transaction-service.tx-log-dir in server configuration file) is proper and has the read, write permissions for the user of the application server.

JTS5015: ORB may not be running.

Solution: Make sure that ORB is running. If ORB is running, this is an Unexpected Internal Error. Please contact Sun with the complete error log message.

JTS5020: Configuration problem while giving the log path.

Solution: Check the Transaction log path in server configuration file (transaction-service.tx-log-dir).

JTS5028: `XAResource.recover` has thrown an exception during recovery.

Solution: See the exception Stack trace for more details.

JTS5032: Server could not communicate with the resource manager with in the retry limit.

Solution: Make sure that resource manager is up and running or increase the retry limit (transaction-service.retry-timeout-in-seconds in the server configuration file).

JTS5040: ORB may not be running.

Solution: See the server log for more details. This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

JTS5041: Database driver or Resource Adapter has thrown `XAException` with the error message

The resource manager is doing work outside a global transaction

Solution: Check if the application is using the same XA pool outside the transactional context as well as in the transactional context. Some drivers do not allow this scenario. Another scenario to verify is, two separate XA pools pointing to the same backend with the same credentials and the second connection is obtained with in the same transaction, without closing the first connection.

JTS5064: Unexpected exception thrown from `XAResource.end`.

Solution: See the server log for more details.

JTS5065: Transaction Log directory path is not valid or proper permissions are not there.

Solution: Make sure that transaction log directory is valid and files in that directory have read write permissions.

JTS5066: Possible cause is that transaction logs are corrupted.

Solution:* Please clean up the transaction-service.tx-log-dir/tx/* files and restart the server.

MDB Error Messages

This chapter describes messages for errors with a MDB prefix.

MDB00017: An error occurred during the message-driven `beancontainer` initialization at runtime.

Cause: The most common cause for this is that the physical resource (e.g. Queue) from which the message-driven bean is consuming either does not exist or has been configured incorrectly. Another common error is that the message-driven bean implementation class does not correctly implement the required javax.ejb.MessageBean or MessageListener interfaces.

Solution: Double-check that the JNDI name of the message-driven bean's resource in sun-ejb-jar.xml is correct. It is also useful to run the verifier to check that the code requirements for the message-driven bean class have been fulfilled.

MDB00048: An error occurred during the pre-invocation processing before a message-driven bean `MessageListener` method is called.

Cause: This is often caused by some transaction-related errors.

Solution: Double-check the transaction configuration for the message-driven bean and consult stack trace for additional details.

MDB00050: An error occurred during the lifecycle initialization of a message-driven bean instance.

Cause: This typically means a system exception was thrown from the bean code during the execution of the no-arg constructor, the setMessageDrivenContext method, or the ejbCreate method. Common causes are failed naming service lookups coding errors, or ClassNotFound errors.

Solution: Check the stack trace to see which method threw the exception. If the error was caused by a NamingException, double-check the environment configuration (ejb-refs, resource-refs, etc.) in the deployment descriptor against the coded names. It would also be useful to run the verifier.

MDB00051: An error occurred while the container was destroying an instance of a message-driven bean.

Cause: The most common cause is that a message-driven bean class threw a system exception from its ejbRemove method.

Solution: Check the message driven bean's ejbRemove implementation to determine what would result in an exception. Also consult the stack trace for more information.

MDB00052: An error occurred while the container was enabling the message flow into a message-driven bean.

Cause: This is an internal error that typically means there is a problem with the messaging system from which the message-driven bean is consuming.

Solution: Check the stack trace for more details.

NAM Error Messages

This chapter describes messages for errors with an NAM prefix.

NAM0002: Problem with serializing or deserializing of the object.

Solution: Check the class hierarchy to see if all the classes are Serializable.

NAM0003: Problem in creating a remote object for `SerialContextProvider`.

Cause: Problem during publishing SerialContextProvider in CosNaming Service.

Solution: Check if ORB CosNaming Service initialized. Check if ORB CosNaming Service initialized.

NAM0004: Application Server may not be running at port intended.

Cause: Possible Network Error.

Solution: Check to see if the Application Server is up and running on the port intended. The problem could be because of incorrect port. Check to see if you can access the host on which the Application Server is running.

NAM0005: The JMS Connection Factory may not be bound to a JNDI name.

Solution: Check the list of JNDI bindings by clicking on the JNDI tree on the Administrator's console. Check the JMS resource references bindings.

NAM0006: The JMS destination may not be bound to a JNDI name.

Solution: Check the list of JNDI bindings by clicking on the JNDI tree on the Administrator's console. Check the JMS resource references bindings.

NAM0007: Unresolved Message Destination Reference.

Solution: Check if the Message Destination has been linked to a Message Destination

NAM0008: Invalid Destination Name.

Solution: Check Destination Name

NAM1000: No endpoints selected.

Solution: Check system property com.sun.appserv.iiop.endpoints.

NAM1001: No endpoints selected.

Solution: Check system property com.sun.appserv.iiop.endpoints.

NAM1002: Bad JNDI provider URL.

Solution: Check system property java.naming.provider.url.

NAM1003: Bad `host:port` entry.

Solution: Check system property com.sun.appserv.iiop.endpoints.

NAM1004: Unknown host.

Solution: Check the host entry.

NAM1005: No endpoints selected.

Solution: Check system property com.sun.appserv.iiop.endpoints.

RAR Error Messages

This chapter describes messages for errors with a RAR prefix.

RAR5004: JDBC driver threw an exception while recovery.

Cause: Resource Adapter threw an exception during recovery in case of connectors.

Solution: Check database or EIS log for details. Check whether the connection pool configuration is proper. Check whether domain.xml is accessible.

RAR5005: The XA resource has been deleted before attempting recovery.

Cause: The XA resource is no longer referenced in domain.xml. The database server that the XA resource points to is no longer running.

The configuration information for the XA Resource has been changed before attempting recovery.

Solution: Check that the XA Resource and the pool it points to is still defined in domain.xml. Check that the XA Resource is present in the list of resource-refs in domain.xml. Check that the Database server is up and running. Check if the configuration info of the XA resource and the pool it points to is sane. In particular check that the datasourceclassname in the pool is correct and the XA resource points to the correct pool.

RAR5007: Exception while creating persistent manager resource.

Solution: Check whether the persistent manager factory class is configured properly and is available in the classpath. Check whether the JDBC resource name is correct and is configured properly.

RAR5008: Naming provider and port are not set in the initial context.

Cause: The Naming provider is not up.

Solution: Check the jndi.properties file has the naming provider host and port specified. Check if the naming provider is up and listening on the port specified in domain.xml

RAR5009: Could not create an instance of factory-class.

Solution: Make sure that factory-class name is configured correctly. Make sure that factory-class is available in the classpath of the application server

RAR5010: External JNDI resource has a wrong factory-class configuration.

Solution: Verify that factory class is an instance of javax.naming.spi.InitialContextFactory.

RAR5011: Could not create Initial Context.

Solution: Make sure that the external-jndi-resource configuration is sufficient to create an initial context.

RAR5012: Could not create Initial context factory.

Solution: Make sure that the external-jndi-resource configuration is sufficient to create an initial context factory.

RAR5015: Classpath is not properly set in `domain.xml`.

Cause: The application server process does not have read permissions on the directory that holds the classes/jar.

Solution: Check that the classpath attribute in the java-config includes a reference to the jar/package directory for the class. You do not have read permissions on the directory that holds the classes/jar.

RAR5020: Could not configure persistent manager resource properly.

Solution: Make sure that the JDBC resource name, you have configured is correct. Check whether the persistent manager factory class is proper. Check whether the persistent manager factory class has a setConnectionFactoryName method.

RAR5035: Error while closing the physical connection.

Error while destroying the connector managed connection.

Solution: Examine the exception stack trace for details.

RAR5038: Could not create a physical connection.

Solution: Connection pool is configured incorrectly. Check that database is running properly. Check that EIS (in case of connectors) is running properly. Check that SJS MQ (in case of JMS) is running properly. Verify that network connection to Database/EIS/MQ is properly configured.

RAR5042: The XA resource has been deleted before attempting recovery.

Cause: The XA resource is not properly referenced because:

The XA resource is no longer referenced in domain.xml. The database server that the XA resource points to is no longer running.

The configuration information for the XA Resource has been changed before attempting recovery.

RAR5043: Exception while creating persistent manager resource.

Solution: Check whether the persistent manager factory class is configured properly and is available in the classpath. Check whether the JDBC resource name is correct and is configured properly.

RAR5044: Could not configure persistent manager resource properly.

RAR5045: Naming provider and port are not set in the JNDI provider's property file.

Cause: The Naming provider is not up.

Solution: Check the jndi.properties file has the naming provider host and port specified. Check if the naming provider is up and listening on the port specified in domain.xml.

RAR5046: Classpath is not properly set in `domain.xml`.

Cause: You do not have read permissions on the directory that holds the classes/jar.

Solution: Check that the classpath attribute in the java-config includes a reference to the jar/package directory for the class. Check that the directory where the classes/jars reside have read permission for the application server process.

RAR5047: Could not create Initial Context.

Solution: Make sure that the external-jndi-resource configuration is sufficient to create an initial context.

RAR5048: The configuration for the JDBC resource could not be read from `domain.xml`.

Cause: This is an internal server error. Please contact Sun Microsystems with the complete error log

RAR5058: Could not create physical connection during connection pool resizing.

Solution: Check whether your network connection to the database or EIS is proper. Check your database/ EIS logs for possible connection creation errors.

RAR5063: The class specified in `datasourceclassname` attribute in the `jdbc-connection-pool` is not of type `javax.sql.XADataSource`.

Please consult your database vendor's documentation to identify the class that implements
the javax.sql.XADataSource

Solution: Check if the datasourceclass implements the javax.sql.XADataSource interface. Try using the javap tool for this purpose.

RAR5065: The class specified in `datasourceclassname` attribute in the `jdbc-connection-pool` is not of type `javax.sql.ConnectionPoolDataSource`.

Please consult your database vendor's documentation to identify the class that implements the javax.sql.ConnectionPoolDataSource.

Solution: Check if the datasourceclass implements the javax.sql.ConnectionPoolDataSource interface. Try using the javap tool for this purpose.

RAR5066: Exception while getting pooled connection.

Cause: The Database server is not up and running. The connection pool is full and cannot allocate more connections. The Database server threw some unexpected exception. Please study the exception message for more details

RAR5068: There are no managed connections in the connection pool at this time.

There is an internal server error. Please contact Sun Microsystems with the complete log message.

Solution: This is an internal server error. Please contact Sun Microsystems with the complete error log. This is an internal server error. Please contact Sun Microsystems with the complete error log.

RAR5069: The Connection object is now invalid due to database restart.

Cause: The connection object is now invalid since the database has either restarted or is not up and running. The JDBC driver cannot provide the required information.

Solution: Switch on the connection validation property of the connection pool and try again. If the database has restarted, restart the application server as well or set the connection validation property in the pool to avoid this in the future. If the database server is not up, please bring it up. Check the server log and please contact Sun Microsystems with the complete error log.

RAR5070: The Connection object is now invalid due to database restart.

Cause: The connection object is now invalid since the database has either restarted or is not up and running. The JDBC driver cannot provide the required information.

RAR5074: The Connection object is now invalid due to database restart.

Cause: The connection object is now invalid since the database has either restarted or is not up and running. The JDBC driver cannot provide the required information.

RAR5087: The Connection object is now invalid due to database restart.

Cause: The connection object is now invalid since the database has either restarted or is not up and running. The JDBC driver cannot provide the required information.

RAR5099: Classpath is not properly set in `domain.xml`.

Cause: The application server process does not have read permissions on the directory that holds the classes/jar.

Solution: Check if the server classpath specified in the java-config element in domain.xml has an entry for the jar containing this class. Check that the directory where the classes/jars reside have read permission for the application server process.

RAR5100: Classpath is not properly set in `domain.xml`.

Cause: The application server process does not have read permissions on the directory that holds the classes/jar.

Solution: Verify that the read permissions on the classes/jar directory are set properly.

RAR5101: The Application Server process does not have read access to the directory where this class resides.

The Application Server process does not have security permissions to access this code.

Solution: Check if the application server has read permissions on the directory where this class/jar containing this class resides. Check if your security manager policy is configured properly.

RAR5102: The application server process do not have permission to access the code base where the class resides.

This is an internal server/JVM error. Please contact Sun Microsystems with the complete error log.

Solution: See if the application server process has permission to read the directory where the class/jar resides. Check if all relevant JVM patches are installed on your machine. Please contact Sun Microsystems with the complete error log.

RAR5103: Error configuring the `DataSource` object.

Cause: The pool parameters in domain.xml are improper. The application server process does not have enough permissions to access the DataSource class.

Solution: Check that the pool parameters specified in domain.xml are correct. For example, check that parameters that expect numeric values are numerals. Check that the application server process has permissions to read the directory where the class resides.

RAR5104: Error configuring the `DataSource` object.

Cause: The pool parameters in domain.xml are improper. The application server process does not have enough permissions to access the DataSource class.

RAR5105: The connection validation method is incorrect, it should be one of `auto-commit`, `meta-data`, `table`.

The connection is no longer valid. It could have been rendered invalid due to database restart/shutdown.

Solution: Check if the connection validation is one of: auto-commit, meta-data, or table. If the method is table, check that the table name is correct. If the database has been restarted, restart the application server as well. If the database is down, start it up.

RAR5106: The database connection is invalid.

Cause: The cause can be either:

The database has been shutdown or restarted.

The network connection to the database has been lost.

Solution: If the database has been restarted, restart the application server as well. To avoid this in the future set the connection validation property in the pool. Check that the database is up and running and the network connection to the database is still alive.

RAR5107: The database connection is invalid.

Cause: The cause can be either:

The database has been shutdown or restarted.

The network connection to the database has been lost.

RAR5108: The database connection is invalid.

Cause: The cause can be either

The database has been shutdown or restarted.

The network connection to the database has been lost.

RAR5109: JDBC driver has thrown an `SQLException` while setting the isolation level.

Solution: Check your connection pool configuration and make sure that the isolation level is correct. Check whether your driver supports the isolation level you have specified in the connection pool.

RAR5110: The URL specified is incorrect.

The database server is not up and running.

Solution: Check if the URL specified in the getConnection call is correct. Consult the JDBC driver vendor's documentation for the correct URL format. Check that the Database server is up and running.

RAR5111: The class specified in `datasourceclassname` attribute in the `jdbc-connection-pool` is not of type `javax.sql.DataSource`.

Solution: Please consult your database vendor's documentation to identify the class that implements javax.sql.DataSource. Try using the javap tool for this purpose.

RAR5112: The class specified in `datasourceclassname` attribute in the `jdbc-connection-pool` is not of type `javax.sql.XADataSource`.

Solution: Please consult your database vendor's documentation to identify the class that implements the javax.sql.XADataSource. Try using the javap tool for this purpose.

RAR5113: Error creating a connection from the supplied information.

Cause: The connection pool is full and cannot allocate more connections. The Database server threw some unexpected exception. Please study the exception message for more details.

Solution: Check that the Database server is up and running. Check if the size of your connection pool is sufficiently large for serving all requests. Check the server log and please contact Sun Microsystems with the full error log.

RAR5114: Error creating a connection from the supplied info.

Cause: The Connection pool is full and incapable of serving more requests at this point. The database is down. Please try later. There is an internal server error. Please contact Sun Microsystems with the complete log message.

Solution: Check if the database server is correctly configured. Check if your pool size is sufficient to server all simultaneous connection requests. Check the server log and contact Sun Microsystems with the complete error message

RAR5116: Error creating a connection from the supplied info.

RAR5117: Error while obtaining a connection from the pool.

Solution: Check your connection pool configuration.

RAR6000: Illegal access Error while instantiating one of the resource adapter JavaBeans like `ManagedConnectionFactory` or `ResourceAdapter` JavaBean classes.

Solution: Check whether the resource adapter has any specific security requirements.

RAR6001: Error while locating one of the resource adapter JavaBeans like `ManagedConnectionFactory` or `ResourceAdapter` JavaBean classes.

Solution: Check if the resource adapter is bundled properly. Resource adapter jar file deployment descriptor specifies correct class names.

RAR6002: Error while instantiating one of the resource adapter JavaBeans like `ManagedConnectionFactory` or `ResourceAdapter` JavaBean.

Solution: Check if the resource adapter is bundled properly with all the classes.

RAR6004: Illegal access Error while instantiating one of the resource adapter JavaBeans like `ManagedConnectionFactory` or `ResourceAdapter` JavaBean classes.

Solution: Check whether the resource adapter has any specific security requirements.

RAR6005: Error while creating `ManagedConnectionFactory`.

Solution: Check if the resource adapter is bundled properly. Check whether connection pool configuration has correct properties for MCF. Check resource adapter documentation for configuring correct properties of MCF.

RAR6007: Runtime could not obtain list of resources of this resource adapter.

Solution: Check whether the resource adapter configuration is proper.

RAR6008: Resource Adapter threw an exception during `ResourceAdapter.stop()` method.

Solution: Check your resource adapter documentation about ResourceAdapter.stop() method.

RAR6009: A resource (connection pool, connector resource or admin object) pertaining to the resource adapter is existing.

Solution: Check whether the cascade option of undeploy is false.

RAR6010: Resource Adapter is already active in the connector runtime.

Solution: Check whether a previous resource adapter deployment is still available.

RAR6012

Solution: There is an internal server error. Please contact Sun Microsystems with the complete log message. Check whether resource adapter threw a null pointer exception.

RAR6013

Solution: There is an internal server error. Please contact Sun Microsystems with the complete log message.

RAR6014: Incomplete or erroneous resource adapter deployment.

Solution: Check whether the RA deployment is proper and complete.

RAR6015: Connection pool is not created properly.

Solution: Check your resource configuration, whether you are using correct connection pool name.

RAR6016: Resource Adapter is not yet initialized in the connector runtime.

Solution: Check whether the deployment of the resource adapter is complete.

RAR6017: Incomplete or erroneous connection pool creation.

Solution: Check whether connection pool is created and is proper.

RAR6019: Incomplete or erroneous resource adapter deployment.

Solution: Check whether the RA deployment is proper and complete.

RAR6021: Error while creating `ManagedConnectionFactory`.

Solution: Check if the resource adapter is bundled properly. Check whether connection pool configuration has correct properties for MCF. Check whether the resource adapter require security permissions to load the classes. Some adapters require getClassLoader() permission.

RAR6022: `NullPointerException` while creating `ManagedConnectionFactory`.

Solution: Check whether resource adapter throws null pointer exception.

RAR6023

Solution: There is an internal server error. Please contact Sun Microsystems with the complete log message.

RAR6025: Could not read the deployment descriptor of the resource adapter.

Solution: Check whether the resource adapter is packaged correctly. Check the correctness of deployment descriptor.

RAR6026: Could not parse the deployment descriptor of the resource adapter.

Solution: Check whether the resource adapter is packaged correctly. Check the correctness of deployment descriptor.

RAR6028: Resource Adapter does not contain resource adapter JavaBean.

Solution: Make sure that the resource adapter is 1.5 compliant.

RAR6030: MCF cleanup in connector runtime failed.

Solution: Check whether connection pool has already been deleted.

RAR6032: Connection Pool Name of the Resource configuration is wrong.

Solution: Check whether the connection pool is created.

RAR6034: Resource Adapter Name of the admin object configuration is wrong.

Solution: Check whether the resource adapter is deployed.

RAR6035: Could not start the resource adapter instance.

Solution: Check whether domain.xml is accessible. Check your resource adapter documentation for possible causes of failure during ResourceAdapter.start().

RAR6036: Resource Adapter throws exception during `ManagedConnectionFactory.setResourceAdapter()`.

Solution: If you are using third party resource adapter, contact resource adapter vendor. If you are a resource adapter developer, please check the resource adapter code.

RAR6037: Resource Adapter threw an exception during `ResourceAdapter.stop()` method.

Solution: Check your resource adapter documentation about ResourceAdapter.stop() method.

RAR7001: Could not unzip the MQ resource adapter archive from upgraded MQ.

Solution: Check whether new MQ resource adapter archive in imq_home/lib is accessible.

RAR7004: Resource Adapter is requesting endpoints to the MDB, before MDB deployment is complete.

Solution: There is an internal server error. Please contact Sun Microsystems with the complete log message.

RAR7005: Could not access the class loader specific to the MDB.

Solution: There is an internal server error. Please contact Sun Microsystems with the complete log message.

RAR7006: `ActivationSpec` validation failed.

Solution: Check your JMS related configuration in MDB deployment descriptor. Check your activation configuration in the MDB deployment descriptor.

RAR7007: Resource Adapter is trying to invoke an unknown method during message delivery.

Solution: Check your resource adapter documentation for possible issues during message delivery.

RAR7010: Could not find the connection pool specified.

Solution: Try the following:

Check whether the connection pool creation was successful. Check whether the pool name used is correct.

There is an internal server error. Please contact Sun Microsystems with the complete log message.

RAR7014: Could not read `shutdown-timeout-in-seconds` from `domain.xml` properly.

Solution: Make sure that domain.xml is configured correctly.

RAR7092: Wrong `transaction-support` connection pool attribute setting.

Cause: The connection pool specifies a transaction-support attribute value that is greater than the one specified in the pool according to this mathematical inequality: NoTransaction < LocalTransaction < XATransaction.

Solution: Change the transaction-attribute value in the pool to be less than or equal to the one specified in the resource adapter's ra.xml.

RAR7096: Error while trying to invoke the setter method for the specified property.

Solution: Check if the value and the property name specified are valid.

RAR7097: Error in finding a mutator method for the specified property.

Solution: Check if the property has been specified correctly and an appropriate public setter method method is available in the class.

SYNC Error Messages

This chapter describes messages for errors with a SYNC prefix.

SYNC002: User name, password, host name or port number may be incorrect.

Cause: DAS may be down or unreachable.

Solution: Check if User name, password, host name and port number are correct. Make sure DAS is running and can connect from the current instance(host).

SYNC006: Synchronization module subsystem's `meta-data.xml` file is corrupted.

Solution: There are several possible solutions:

Check synchronization-meta-data.xml and na-synchronization-meta-data.xml exist in appserv-se.jar and is a valid XML file.

Check if synchronization-meta-data.xml is not part of server classpath.

synchronization-meta-data.xml is not valid.

synchronization-meta-data.xml found in server classpath is not well formed.

SYNC029: This could be either a config Exception or `IOException`

Solution: Check domain.xml and das.properties. If the problem persists, you may backup and remove applications, generated, config, docroot and lib directories in the local repository and restart the server. The local repository will be synchronized again.

SYNC047: Connection problem during download.

File(s) could not be written to synchronization store.

Solution: Check if DAS is up. Check for connection errors during download. Check if synchronization repository has enough space and has permission. If the repository is on NFS, may be NFS is down.

SYNC049: File(s) could not be written to synchronization store.

Solution: Check if synchronization repository has enough space and has permission. If the repository is on NFS, may be NFS is down.

SYNC052: `domain.xml` is incorrect.

Solution: Make sure domain.xml errors are fixed. It may have been manually edited.

SYNC074: This could be a network communication error.

Solution: Please check domain.xml, das.properties and server log.

SYNC075: This could be a network communication error or Domain Administration Server is not running.

WEB Error Messages

This chapter describes messages for errors with a WEB prefix.

WEB0305: HTTP listener's proxy port is not a numeric string.

Solution: Check to see if the value of the HTTP listener's server-name attribute contains a colon, and if so, make sure the name component following the colon is a numeric string.

WEB0315: Two or more virtual servers associated with the same HTTP listener share the same host name.

Solution: Make sure that the sets of host names of all virtual servers associated with the same HTTP listener are disjunct.

WEB3004: The Application server could not initialize the native HTTP service. This could be cause by a misconfiguration, or a internal failure.

Cause: It is also possible that the native library has been found missing.

Solution: Check that the HttpService configuration is valid. Examine the message reported by the native HTTP service for clues. Verify that the following needed libraries are present in the Application Servers's lib directory. If the problem persists, contact Sun with the complete error log message.

WEB3005: The Application server could not start the native HTTP service. This could be cause by a misconfiguration, or a internal failure.

Cause: It is also possible that the native library has been found missing.

WEB3006: The file is missing.

Solution: Check that the file is present in the Application Server's lib directory, or if enabled in the Library Path. Please contact Sun with the complete error log message.

WEB3007: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

Solution: Please correct the format.

WSS Error Messages

This chapter describes messages for errors with a WSS prefix.

WSS0126: Unsupported algorithm type. Only RSA supported.

Solution: Check that the signature algorithm is RSA.

WSS0129: Malformed message `ds:Signature` element missing from the `wsse:Security` header block.

Solution: Check proper signature was generated while signing.

WSS0134: Unable to Initialize `XMLCipher` with the given Key.

Solution: Check that the XMLCipher was initialized properly.

WSS0137: An appropriate JCE provider is not configured in the JRE.

Solution: Look at root exception for more clues.

WSS0144: `Base64Decoding` exception is the root cause.

Solution: Check that the data is valid base64 encoded.

WSS0147: `TransformationConfiguration` exception while trying to use stylesheet to pretty print.

Solution: Make sure style sheet is valid.

WSS0148: Exception while trying to pretty print using transform.

Solution: Make sure the original SOAP Message and style sheet are both correct.

WSS0156: Error in certificate used for validation.

Solution: Check that the token contains a valid Certificate.

WSS0165: `XPath` does not correspond to a DOM element.

Solution: Check that the node represented by the XPath is a valid DOM element.

WSS0167: Invalid signature; verification failed.

Solution: Make sure the signature was not tampered with in transit.

WSS0168: Unable to generate a random symmetric key.

Solution: Verify that the KeyGenerator has been properly initialized.

WSS0169: Value of `FilterParameterConstants.BINARY_SEC_TOKEN` is not

set.

Solution: Check that direct referencestrategy is set before exporting the certificate.

WSS0181: Subject not authorized; validation failed.

Solution: Check that the user is authorized.

WSS0182: `FilterParameterConstants.REFERENCE_LIST` parameter has a null value.

Solution: The reference list that needs to be decrypted usually set by ImportEncryptedKeyFilter.

WSS0183: Could not locate a valid symmetric key needed for decryption.

Solution: Value of symmetric key seems to be null. Check its value.

WSS0184: Could not retrieve security domain from the Securable SOAP message.

Solution: Make sure the SecurityEnvironment factory has set the right security environment.

WSS0185: Could not find the certificate associated with the direct reference strategy.

Solution: Check that the URI is valid and subjectkeyidentifier parameter is set in configuration.

WSS0189: Data decryption algorithm has to be either `Triple-DES`, `AES128-CBC`, `AES256-CBC`.

Solution: Check that the encryption algorithm used is either 3DES, AES128_CBC, AES256_CBC.

WSS0190: The number of elements encrypted is less than required/allowed.

Solution: Check that the data references for encryption (in message) match the requirements.

WSS0191: A `SymmetricKey` was not generated earlier that is set on the calling thread.

KeyName specified could not locate a key in the security environment.

Solution: Check that ExportEncryptedKeyFilter is called before. Check that a valid KeyStore URL is used to instantiate the SecurityEnvironment and it contains a matching SecretKey.

WSS0192: At least one target needs to be specified for encryption.

Solution: Check that a non-null target list is used to instantiate the filter.

WSS0193: Target specified does not correspond to a valid message part.

Solution: Check that a valid XPath/QName/wsuId are specified.

WSS0194: `SOAP-ENV:Header` can not fully be encrypted.

SOAP-ENV:Body can not fully be encrypted.

Solution: Check that a valid XPath/QName/wsuId are specified complying to the spec.

WSS0195: `ReferenceListBlock` not set on the calling thread.

Solution: Check that ExportEncryptedKeyFilter is called before. Check that ExportReferenceListFilter is called before.

WSS0196: An instance of `SecurityEnvironment` class for the operating

environment was not set on SecurableSoapMessage.

Solution: Check that SetSecurityEnvironmentFilter processed the message before.

WSS0198: Only `RSA_SHA1` Signature algorithm is supported.

Solution: Check that RSA_SHA1 signature algorithm is specified.

WSS0199: Timestamp creation time can not be null.

Solution: Check that non-null creation time is used to instantiate the filter.

WSS0203: Header block corresponding to the desired requirement not found.

Solution: Check that the message meets the security requirements.

WSS0204: Illegal security header block found in the security header.

Solution: Check that the message is SOAP Security specification compliant.

WSS0205: Requirement for `wsu:Timestamp` has not been met.

Solution: Check that the message meets the security requirements.

WSS0206: Not all receiver requirements for security have been met.

Solution: Check that the message meets the security requirements.

WSS0208: Extra security than required by the receiver side policy found in the message.

Solution: Check that the message strictly meets the security requirements.

WSS0209: The message filter is incorrectly configured to process an inbound message.

Solution: Check that the filters are correctly configured to process inbound messages.

WSS0210: Only `RSAv1.5` Key Encryption Algorithm is supported.

Solution: Check that the Key Encryption Algorithm used in the inbound message is RSAv1.5.

WSS0212: Receiver requirement for digested password in `UsernameToken` not met.

Solution: Check that the message meets the security requirements.

WSS0213: Receiver requirement for nonce in `UsernameToken` not met.

Solution: Check that the message meets the security requirements.

WSS0215: `handle()` call for a `PropertyCallback` on the handler threw exception.

Solution: Check the handler implementation.

WSS0216: `handle()` call on the handler threw exception.

Solution: Check the handler implementation.

WSS0217: `handle()` call on the handler threw exception.

Solution: Check the handler implementation.

WSS0218: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for SignatureKeyCallback.DefaultPrivKeyCertRequest.

WSS0219: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for SignatureKeyCallback.DefaultPrivKeyCertRequest.

WSS0220: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for DecryptionKeyCallback.AliasSymmetricKeyRequest.

WSS0221: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for SignatureKeyCallback and/or EncryptionKeyCallback, check keystores and truststores.

WSS0222: `handle()` call on the handler failed to set the `Callback`.

Solution: Check keystore path and ensure that the right keys are present.

WSS0301: Data malformed. Base 64 decoding error.

Solution: Verify that data is base64 encoded.

WSS0302: Certificate parsing problem.

Solution: Data stream used to create the x509 certificate maybe corrupted.

WSS0303: Certificate encoding exception.

Solution: Check that the x509 data is valid. Could not extract raw bytes from it.

WSS0306: Invalid password type.

Solution: Password type must match that specified by the WSS specification.

WSS0307: Nonce encoding namespace check failed.

Solution: Nonce encoding type namespace seems invalid.

WSS0310: `NoSuchAlgorithmException`: Invalid algorithm.

Solution: Check that the algorithm passed to SecureRandom is valid.

WSS0311: Password digest could not be created.

Solution: Check that the algorithm passed to MessageDigest is valid.

WSS0316: `BinarySecurity` token's Encoding type is invalid.

Solution: Check that encoding value for BinarySecurity token is valid as per spec.

WSS0317: Could not find `X.509` certificate.

Solution: Ensure certificate path is not empty and certificate type is correct.

WSS0318: Error while parsing and creating the `KeyInfo` instance.

Solution: Check values passed to KeyInfo constructor.

WSS0319: Could not add key name to `KeyInfo` Header block.

Solution: Check KeyInfo and KeyName have been instantiated without exceptions.

WSS0320: Could not get `KeyName` from `KeyInfo`.

Solution: Make sure the KeyName exists in the KeyInfo.

WSS0321: Could not retrieve element from `KeyInfo` or could not import the node.

Solution: Check the element to be converted to SOAPElement.

WSS0322: Exception while parsing and creating the Signature element.

Solution: Check that a fully initialized XML Signature was passed.

WSS0323: Exception while trying to sign.

Solution: Check the key used to sign.

WSS0324: Exception while adding a Reference with URI, transforms and Digest algorithm URI to `SignedInfo`.

Solution: Verify the following:

Check getSignatureValue failure cause from underlying XML DSIG implementation.

Check that the message signed using corresponding private key, and has not been tampered with.

Check values passed to constructor of XMLSignature.addDocument passed to XML DSig implementation are correct.

WSS0327: Could not retrieve element from Signature or could not import the node.

Solution: Check the element to be converted to SOAPElement.

WSS0328: Error parsing date.

Solution: Check date format is in UTC. Check it is yyyy-MM-dd'T'HH:mm:ss'Z' or yyyy-MM-dd'T'HH:mm:ss'.'sss'Z'.

WSS0329: Expecting `UsernameToken` Element.

Solution: Check that the next element is UsernameToken.

WSS0330: Username not first child of `UsernameToken`.

WSS0331: Element may not be a proper `UsernameToken`.

Solution: Check that the UsernameToken matches the token schema.

WSS0332: `Username` was null.

Solution: Check UsernameToken contains a valid Username.

WSS0333: Keystore URL is null.

Solution: Check that the property javax.net.ssl.keyStore is set properly.

WSS0334: `KeyIdentifier` holds invalid `ValueType`.

Solution: Check KeyIdentifier ValueType's value.

WSS0335: `KeyReference` type not supported.

Solution: KeyReference type should be one of KeyIdentifier, Reference, X509Data.

WSS0336: Can't locate public key.

Solution: Check public key retrieved should not be null.

WSS0337: Could not resolve URI.

Solution: Check DirectReference's ValueType, it is not supported.

WSS0338: Key Reference Mechanism not supported.

Solution: Check reference is one of X509IssuerSerial, DirectReference, KeyIdentifier.

WSS0339: Support for processing information in the given `ds:KeyInfo` is

not present.

Solution: Check ds:KeyInfo matches schema.

WSS0340: Creation time cannot be ahead of current UTC time.

Solution: Check system time and ensure it is correct.

WSS0341: Creation time is very old.

Solution: Check system time and ensure it is correct.

WSS0342: `BinarySecurity` Token's Value type is invalid.

Solution: Check that valueType for BinarySecurity token is valid as per spec.

WSS0218: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for SignatureKeyCallback.DefaultPrivKeyCertRequest.

WSS0219: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for SignatureKeyCallback.DefaultPrivKeyCertRequest.

WSS0220: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for DecryptionKeyCallback.AliasSymmetricKeyRequest.

WSS0221: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for SignatureKeyCallback and/or EncryptionKeyCallback, check keystores and truststores.

WSS0222: `handle()` call on the handler failed to set the `Callback`.

Solution: Check keystore path and ensure that the right keys are present.

WSS0301: Data malformed. Base 64 decoding error.

Solution: Verify that data is base64 encoded.

WSS0302: Certificate parsing problem.

Solution: Data stream used to create the x509 certificate maybe corrupted.

WSS0303: Certificate encoding exception.

Solution: Check that the x509 data is valid. Could not extract raw bytes from it.

WSS0306: Invalid password type.

Solution: Password type must match that specified by the WSS specification.

WSS0307: Nonce encoding namespace check failed.

Solution: Nonce encoding type namespace seems invalid.

WSS0310: `NoSuchAlgorithmException`: Invalid algorithm.

Solution: Check that the algorithm passed to SecureRandom is valid.

WSS0311: Password digest could not be created.

Solution: Check that the algorithm passed to MessageDigest is valid.

WSS0316: `BinarySecurity` token's Encoding type is invalid.

Solution: Check that encoding value for BinarySecurity token is valid as per spec.

WSS0317: Could not find `X.509` certificate.

Solution: Ensure certificate path is not empty and certificate type is correct.

WSS0318: Error while parsing and creating the `KeyInfo` instance.

Solution: Check values passed to KeyInfo constructor.

WSS0319: Could not add key name to `KeyInfo` Header block.

Solution: Check KeyInfo and KeyName have been instantiated without exceptions.

WSS0320: Could not get `KeyName` from `KeyInfo`.

Solution: Make sure the KeyName exists in the KeyInfo.

WSS0321: Could not retrieve element from `KeyInfo` or could not import the node.

Solution: Check the element to be converted to SOAPElement.

WSS0322: Exception while parsing and creating the Signature element.

Solution: Check that a fully initialized XML Signature was passed.

WSS0323: Exception while trying to sign.

Solution: Check the key used to sign.

WSS0324: Exception while adding a Reference with URI, transforms and Digest algorithm URI to `SignedInfo`.

Solution: Verify the following:

Check getSignatureValue failure cause from underlying XML DSIG implementation.

Check that the message signed using corresponding private key, and has not been tampered with.

Check values passed to constructor of XMLSignature.addDocument passed to XML DSig implementation are correct.

WSS0327: Could not retrieve element from Signature or could not import the node.

Solution: Check the element to be converted to SOAPElement.

WSS0328: Error parsing date.

Solution: Check date format is in UTC. Check it is yyyy-MM-dd'T'HH:mm:ss'Z' or yyyy-MM-dd'T'HH:mm:ss'.'sss'Z'.

WSS0329: Expecting `UsernameToken` Element.

Solution: Check that the next element is UsernameToken.

WSS0330: Username not first child of `UsernameToken`.

WSS0331: Element may not be a proper `UsernameToken`.

Solution: Check that the UsernameToken matches the token schema.

WSS0332: `Username` was null.

Solution: Check UsernameToken contains a valid Username.

WSS0333: Keystore URL is null.

Solution: Check that the property javax.net.ssl.keyStore is set properly.

WSS0334: `KeyIdentifier` holds invalid `ValueType`.

Solution: Check KeyIdentifier ValueType's value.

WSS0335: `KeyReference` type not supported.

Solution: KeyReference type should be one of KeyIdentifier, Reference, X509Data.

WSS0336: Can't locate public key.

Solution: Check public key retrieved should not be null.

WSS0337: Could not resolve URI.

Solution: Check DirectReference's ValueType, it is not supported.

WSS0338: Key Reference Mechanism not supported.

Solution: Check reference is one of X509IssuerSerial, DirectReference, KeyIdentifier.

WSS0339: Support for processing information in the given `ds:KeyInfo` is

not present.

Solution: Check ds:KeyInfo matches schema.

WSS0340: Creation time cannot be ahead of current UTC time.

Solution: Check system time and ensure it is correct.

WSS0341: Creation time is very old.

Solution: Check system time and ensure it is correct.

WSS0342: `BinarySecurity` Token's Value type is invalid.

Solution: Check that valueType for BinarySecurity token is valid as per spec.

WSS0218: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for SignatureKeyCallback.DefaultPrivKeyCertRequest.

WSS0219: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for SignatureKeyCallback.DefaultPrivKeyCertRequest.

WSS0220: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for DecryptionKeyCallback.AliasSymmetricKeyRequest.

WSS0221: `handle()` call on the handler failed to set the `Callback`.

Solution: Check the handler implementation for SignatureKeyCallback and/or EncryptionKeyCallback, check keystores and truststores.

WSS0222: `handle()` call on the handler failed to set the `Callback`.

Solution: Check keystore path and ensure that the right keys are present.

WSS0301: Data malformed. Base 64 decoding error.

Solution: Verify that data is base64 encoded.

WSS0302: Certificate parsing problem.

Solution: Data stream used to create the x509 certificate maybe corrupted.

WSS0303: Certificate encoding exception.

Solution: Check that the x509 data is valid. Could not extract raw bytes from it.

WSS0306: Invalid password type.

Solution: Password type must match that specified by the WSS specification.

WSS0307: Nonce encoding namespace check failed.

Solution: Nonce encoding type namespace seems invalid.

WSS0310: `NoSuchAlgorithmException`: Invalid algorithm.

Solution: Check that the algorithm passed to SecureRandom is valid.

WSS0311: Password digest could not be created.

Solution: Check that the algorithm passed to MessageDigest is valid.

WSS0316: `BinarySecurity` token's Encoding type is invalid.

Solution: Check that encoding value for BinarySecurity token is valid as per spec.

WSS0317: Could not find `X.509` certificate.

Solution: Ensure certificate path is not empty and certificate type is correct.

WSS0318: Error while parsing and creating the `KeyInfo` instance.

Solution: Check values passed to KeyInfo constructor.

WSS0319: Could not add key name to `KeyInfo` Header block.

Solution: Check KeyInfo and KeyName have been instantiated without exceptions.

WSS0320: Could not get `KeyName` from `KeyInfo`.

Solution: Make sure the KeyName exists in the KeyInfo.

WSS0321: Could not retrieve element from `KeyInfo` or could not import the node.

Solution: Check the element to be converted to SOAPElement.

WSS0322: Exception while parsing and creating the Signature element.

Solution: Check that a fully initialized XML Signature was passed.

WSS0323: Exception while trying to sign.

Solution: Check the key used to sign.

WSS0324: Exception while adding a Reference with URI, transforms and Digest algorithm URI to `SignedInfo`.

Solution: Verify the following:

Check getSignatureValue failure cause from underlying XML DSIG implementation.

Check that the message signed using corresponding private key, and has not been tampered with.

Check values passed to constructor of XMLSignature.addDocument passed to XML DSig implementation are correct.

WSS0327: Could not retrieve element from Signature or could not import the node.

Solution: Check the element to be converted to SOAPElement.

WSS0328: Error parsing date.

Solution: Check date format is in UTC. Check it is yyyy-MM-dd'T'HH:mm:ss'Z' or yyyy-MM-dd'T'HH:mm:ss'.'sss'Z'.

WSS0329: Expecting `UsernameToken` Element.

Solution: Check that the next element is UsernameToken.

WSS0330: Username not first child of `UsernameToken`.

WSS0331: Element may not be a proper `UsernameToken`.

Solution: Check that the UsernameToken matches the token schema.

WSS0332: `Username` was null.

Solution: Check UsernameToken contains a valid Username.

WSS0333: Keystore URL is null.

Solution: Check that the property javax.net.ssl.keyStore is set properly.

WSS0334: `KeyIdentifier` holds invalid `ValueType`.

Solution: Check KeyIdentifier ValueType's value.

WSS0335: `KeyReference` type not supported.

Solution: KeyReference type should be one of KeyIdentifier, Reference, X509Data.

WSS0336: Can't locate public key.

Solution: Check public key retrieved should not be null.

WSS0337: Could not resolve URI.

Solution: Check DirectReference's ValueType, it is not supported.

WSS0338: Key Reference Mechanism not supported.

Solution: Check reference is one of X509IssuerSerial, DirectReference, KeyIdentifier.

WSS0339: Support for processing information in the given `ds:KeyInfo` is

not present.

Solution: Check ds:KeyInfo matches schema.

WSS0340: Creation time cannot be ahead of current UTC time.

Solution: Check system time and ensure it is correct.

WSS0341: Creation time is very old.

Solution: Check system time and ensure it is correct.

WSS0342: `BinarySecurity` Token's Value type is invalid.

Solution: Check that valueType for BinarySecurity token is valid as per spec.

WSS0343: Error in creating the BST due to
Unknown macro: {0}
.

Solution: Check that all required values are set on the Binary Security Token, including TextNode value.

WSS0344: The binary data in the Security Token can not be decoded, expected `Base64` encoding.

Solution: Check to see that the encoding format of the Binary Security Token is Base64Binary.

WSS0345: Error creating `SOAPElement` for `EncryptedDataHeaderBlock`.

Solution: If SOAPElement is used to create EncryptedData HeaderBlock, check to see that it is valid as per spec.

WSS0346: Invalid `SOAPElement` passed to `EncryptedDataHeaderBlock` constructor.

Solution: Check that the SOAPElement passed to EncryptedDataHeaderBlock is valid as per spec.

WSS0347: `SOAPElement` used to initialize `EncryptedType` may not have `CipherData` element.}}

CipherData may not have been set on the EncryptedType.

Solution: Check to see SOAPElement used to initialize EncryptedType has CipherData. Check to see setCipherData() is called on the EncryptedType.

WSS0348: Error creating `SOAPElement` for `EncryptedKeyHeaderBlock`.

Solution: If SOAPElement is used to create EncryptedKeyHeaderBlock, check to see that it is valid as per spec.

WSS0349: Invalid `SOAPElement` passed to `EncryptedKeyHeaderBlock()`.

Solution: Check that the SOAPElement passed to EncryptedKeyHeaderBlock() is valid as per spec.

WSS0350: Error creating/updating `CipherData` `SOAPElement` (in `EncryptedKeyHeaderBlock`).

Solution: Refer your SAAJ API Documentation.

WSS0351: Error creating `EncryptionMethod` `SOAPElement`.

Solution: Refer your SAAJ API Documentation.

WSS0352: Error creating `javax.xml.soap.Name` for `CipherValue`.

Solution: Refer your SAAJ API Documentation.

WSS0353: No `CipherValue` element(s) are present in `CipherData`.

Solution: Check to see if setCipherValue() is called on EncryptedType.

WSS0354: An error may have occurred creating `javax.xml.soap.Name` for `EncryptionMethod`.

Cause: An error may have occurred creating javax.xml.soap.Name for KeyInfo. An error may have occurred creating javax.xml.soap.Name for CipherData. An error may have occurred creating javax.xml.soap.Name for EncryptionProperties.

Solution: Refer your SAAJ API Documentation.

WSS0355: Error creating `com.sun.org.apache.xml.security.keys.content.keyvalues.DSAKeyValue`.}}

Error creating {{com.sun.org.apache.xml.security.keys.content.keyvalues.RSAKeyValue. Error creating com.sun.org.apache.xml.security.keys.content.KeyValue.
Solution: Check that a non-null SOAPElement is passed to addXXXKeyValue().

WSS0356: Error creating `com.sun.org.apache.xml.security.keys.content.X509Data`.

Solution: Check that a non-null SOAPElement is passed to addX509Data().

WSS0357: Error getting `KeyValue` from `KeyInfo` for

the given index.

Solution: Check that the ds:KeyInfo element has ds:KeyValue elements. Check that the index (beginning with 0) used to refer the ds:KeyValue element is valid.

WSS0358: Error getting `X509Data` from `KeyInfo` for

the given index.

Solution: Check that the ds:KeyInfo element has ds:X509Data elements. Check that the index (beginning with 0) used to refer the ds:X509Data element is valid.

WSS0359: Error adding `com.sun.org.apache.xml.security.keys.content.X509Data` to `KeyInfo`.

Solution: Check that a valid com.sun.org.apache.xml.security.keys.content.X509Data (as per specs.) is passed to addX509Data().

WSS0360: An error may have occurred creating `javax.xml.soap.Name` for `ReferenceList`.

Solution: Refer your SAAJ API Documentation.

WSS0361: An error may have occurred creating `org.w3c.dom.Element` for `ReferenceList`.

Cause: The org.w3c.dom.Document object passed ReferenceListHeaderBlock() may be null.

Solution: Check that the Namespace specified does not contain any illegal characters as per XML 1.0 specification. Check that the QName specified is not malformed (Refer to the J2SE Documentation for more information). Check that a non-Null Document is passed to the ReferenceListHeaderBlock().

WSS0362: Invalid `SOAPElement` passed to `ReferenceListHeaderBlock()`.

Solution: Check that the SOAPElement passed to ReferenceListHeaderBlock() is valid as per spec.

WSS0363: Error creating `javax.xml.soap.SOAPElement` for `xenc:DataReference`.

Cause: Error adding xenc:DataReference (SOAPElement) as child element of xenc:DataReference (SOAPElement). Error setting URI attribute on javax.xml.soap.SOAPElement for xenc:DataReference.

Solution: Refer your SAAJ API Documentation.

WSS0365: Error creating `javax.xml.soap.SOAPElement` for namespace node.

Solution: Refer your SAAJ API Documentation.

WSS0368: Error getting `SOAPEnvelope` from `SOAPPart`.

Solution: Refer your SAAJ API Documentation.

WSS0369: Error getting `SOAPHeader` from `SOAPEnvelope`.

Cause: Error creating SOAPHeader.

Solution: Refer to your SAAJ API Documentation.

WSS0371: Error in getting the `SOAPBody` from the `SOAPMessage`.}}

Error in creating {{javax.xml.soap.Name for setting the fault on SOAPBody. Error in adding fault to SOAPBody.
Solution: Refer your SAAJ API Documentation.

WSS0376: Error importing the `SOAPElement` representing the header block

to the document corresponding to the SOAPMessage to which the header
is being added.

Solution: Check that the SecurityHeaderBlock can be transformed to a valid SOAPElement. Refer to the J2SE Documentation for more.

WSS0377: Error creating `javax.xml.soap.SOAPElement` for `SecurityTokenReference`.

Solution: Refer your SAAJ API Documentation.

WSS0378: Error creating `javax.xml.soap.SOAPElement` for `SecurityTokenReference`.

Solution: Check that the org.w3c.dom.Document object passed to SecurityTokenReference() is non-null. Refer your SAAJ API Documentation.

WSS0379: `SOAPElement` passed to `SecurityTokenReference()` is not a valid `SecurityTokenReference` element as per spec.

Solution: Check that a valid SOAPElement as per spec. is passed to SecurityTokenReference().

WSS0380: The `ds:Reference` would already have been set using the constructors.

Solution: Check that a SOAPElement with ds:Reference (child element) is not used to instantiate SecurityTokenReference.

WSS0381: Error in setting the passed `ReferenceElement` on `SecurityTokenReference`.

Solution: Refer your SAAJ API Documentation.

WSS0382: Error appending `ds:Object` element to `ds:Signature`.

Solution: Check that a valid ds:Object SOAPElement (as per spec.) is passed to appendObject(). Check that a non-null SOAPElement is passed to appendObject().

WSS0383: Owner document of `ds:Signature` `SOAPElement` is null.

Solution: Check that the Document used to instantiate SignatureHeaderBlock() is not null.

WSS0384: Error creating `javax.xml.soap.Name` for Timestamp.

Solution: Refer your SAAJ API Documentation.

WSS0385: The `SOAPElement` used to instantiate `Timestamp()` is not valid (as per specification).

Solution: Check that the Localname and NamespaceURI of the SOAPElement used to create Timestamp() are correct as per spec.

WSS0386: Error creating `javax.xml.soap.SOAPElement` for `Timestamp`.}}

Error adding child {{SOAPElements to the Timestamp element.

Solution: Refer your SAAJ API Documentation.

WSS0387: `Username` is not set.

Solution: Check that a Username has been passed through the configuration file or through the callback handler.

WSS0388: Error creating `javax.xml.soap.SOAPElement` for `UsernameToken`.

Error adding child SOAPElements to the UsernameToken element.

Solution: Refer your SAAJ API Documentation.

WSS0389: `Base64` nonce encoding type has not been specified.

Solution: Check that the nonce encoding type used to create UsernameToken is Base64.

WSS0390: `UTF-8 Charset` is unsupported for byte-encoding (a string).

Solution: Refer your J2SE Documentation.

WSS0391: Invalid `Localname` and `NamespaceURI` of the `SOAPElement` used for creating the token.

Solution: Check that the Localname and NamespaceURI of the SOAPElement used to create X509SecurityToken are valid (as per specification).

WSS0393: The expiration time in Timestamp cannot be before current UTC time.

Solution: Check system time and ensure it is correct.

WSS0394: Error parsing date.

Solution: Check date format is in UTC. Check it is yyyy-MM-dd'T'HH:mm:ss'Z' or yyyy-MM-dd'T'HH:mm:ss'.'sss'Z'.

WSS0500: Classname not a recognized class name for a `MessageFilter`.

Solution: Check that the class implements MessageFilter.

WSS0502: Element encountered does not match element expected.

Solution: Check that the XML file follows schema for defining configuration.

WSS0503: Element encountered does not match valid element expected.

Solution: Check that the XML file follows schema for defining configuration.

WSS0508: Default settings can not be specified after custom settings are specified.

Solution: Check that no sender operations or receiver requirements are specified in a configuration. file. Check that no sender or receiver settings are programmatically added.

WSS0509: Custom settings can not be specified after default settings are specified.

Solution: Check that no default settings are programmatically added.

WSS0511: Non-permissible boolean value string - valid strings are true and false.

Solution: Check that the boolean value strings are either true or false.

WSS0512: Non-permissible attribute on a Security Configuration element.

Solution: Check that the configuration file is consistent with the security configuration schema.

WSS0513: Non-permissible element on `xwss:SecurityConfiguration`.

Solution: Check that the configuration file is consistent with the security configuration schema.

WSS0514: Non-permissible child element in a Security Configuration element.

Solution: Check that the configuration file is consistent with the security configuration schema.

WSS0515: Impermissible value for key reference string.

Solution: Check that the configuration file is consistent with the security configuration schema.

WSS0516: Non-permissible duplicate element on a Security Configuration Element.

Solution: Check that the configuration file is consistent with the security configuration schema.

WSS0517: Non-permissible duplicate element on a Security Configuration Element.

Solution: Check that the configuration file is consistent with the security configuration schema.

WSS0519: Non-permissible/missing attribute value.

Solution: Check that the configuration file is consistent with the security configuration schema.

WSS0520: `xwss:SymmetricKey` is not permitted along with `xwss:X509Token`.

Solution: Check that the configuration file is consistent with the security configuration schema.

WSS0600: A Key can not be located in `SecurityEnvironment` for the Token

Reference.

Solution: Check that the certificate referred to is valid and present in the Keystores.

WSS0601: A Key can not be located in `SecurityEnvironment` for the `KeyValue`.

Solution: Check that the certificate referred to is valid and present in the Keystores.

WSS0602: A Key can not be located in `SecurityEnvironment` for the `X509Data`.

Solution: Check that the certificate referred to is valid and present in the Keystores.

WSS0603: `XPathAPI` `TransformerException` in finding

element with matching wsu:Id/Id/SAMLAssertionID.

Solution: Refer your XPathAPI documentation.

WSS0606: Input Node Set to STR Transform is empty.

Solution: Check that the Referenced Node (to be STR transformed) in ds:SignedInfo is valid.

WSS0608: The Reference Mechanism in the `SecurityTokenReference` is

not supported.

Solution: Check that the Reference Mechanism is either Direct/KeyIdentifier/X509IssuerSerial.

WSS0609: The referenced security token is neither an XML token nor a raw binary token.

Solution: Check the referenced security token.

WSS0650: Username/Password data file not found.

Solution: Check that the system property com.sun.xml.wss.usersFile is set.

WSS0654: Error creating `javax.xml.soap.Name` for `wsu:Id`.

Solution: Try the following:

Refer your SAAJ API Documentation.

Check that the Class object corresponds to the header block identified by the SOAPElement.

WSS0656: The Keystore URL is not specified/invalid in `server.xml`.

A Keystore file does not exist in $user.home.
Solution: Check that the keystoreFile attribute is specified on SSL Coyote HTTP/1.1 Connector element in server.xml and is valid. Check that a keystore file exists in $user.home.

WSS0700: An instance of `SecurityEnvironment` is not set on `SecurableSoapMessage`.

Solution: Check that setSecurityEnvironment() is called on the SecurableSoapMessage. Check that SetSecurityEnvironmentFilter is applied on SecurableSoapMessage.

WSS0701: No X509v3 Certificate can be located for the alias in Keystore.

Cause: If no alias has been specified for signing, no default certificate is available.

Solution: Check that a default certificate is available and/or a valid alias is used.

WSS0702: The `X509v3` Certificate for the given alias does not contain

a subject key identifier.

Solution: Check that a valid X509v3 certificate is present in Keystores.

WSS0704: Agreement name: `SESSION-KEY-VALUE`, has not been set on the `SecurityEnvironment` instance.

Solution: Check that the agreement name SESSION-KEY-VALUE is set on SecurityEnvironment using setAgreementProperty().

WSS0750: Error creating `javax.xml.soap.SOAPElement`.

Solution: Refer your SAAJ API Documentation.

WSS0751: The `localname` of the `SOAPElement` passed

is not Reference.

The namespace URI of the SOAPElement passed does not conform to WSS Spec.

Solution: Check that a SOAPElement conformant to spec. is passed.

WSS0752: The `localname` of the `SOAPElement` passed is not Embedded.

The namespace URI of the SOAPElement passed does not conform to WSS Spec.

Solution: Check that a SOAPElement conformant to spec. is passed.

WSS0753: An embedded token in `wsse:Embedded` element is missing.

Solution: Check that the token element is conformant to the WSS specification.

WSS0754: Token on `EmbeddedReference` has already been set.

Cause: A SOAPElement representation of EmbeddedReference containing the Token is used to create the EmbeddedReference instance.

WSS0756: Error creating `SOAPElement` for `wsse:KeyIdentifier`.

Solution: Check your SAAJ API Documentation.

WSS0757: Error adding `KeyIdentifier` value to `wsse:KeyIdentifer`.

Solution: Check your SAAJ API Documentation.

WSS0758: Error creating `javax.xml.soap.Name`.

Solution: Refer your SAAJ API Documentation.

WSS0759: An `X509IssuerSerial` instance can not be created.

Solution: Check that the SOAPElement passed to the constructor is conformant to spec. (and has X509IssuerSerial child elements).

WSS0800: `ds:KeyInfo` in the message is not a valid one.

Solution: Check if the ds:KeyInfo in the message is valid.

WSS0753: An embedded token in `wsse:Embedded` element is missing.

Solution: Check that the token element is conformant to the WSS specification.

WSS0754: Token on `EmbeddedReference` has already been set.

Cause: A SOAPElement representation of EmbeddedReference containing the Token is used to create the EmbeddedReference instance.

WSS0756: Error creating `SOAPElement` for `wsse:KeyIdentifier`.

Solution: Check your SAAJ API Documentation.

WSS0757: Error adding `KeyIdentifier` value to `wsse:KeyIdentifer`.

Solution: Check your SAAJ API Documentation.

WSS0758: Error creating `javax.xml.soap.Name`.

Solution: Refer your SAAJ API Documentation.

WSS0759: An `X509IssuerSerial` instance can not be created.

Solution: Check that the SOAPElement passed to the constructor is conformant to spec. (and has X509IssuerSerial child elements).

WSS0800: `ds:KeyInfo` in the message is not a valid one.

Solution: Check if the ds:KeyInfo in the message is valid.

WSS0753: An embedded token in `wsse:Embedded` element is missing.

Solution: Check that the token element is conformant to the WSS specification.

WSS0754: Token on `EmbeddedReference` has already been set.

Cause: A SOAPElement representation of EmbeddedReference containing the Token is used to create the EmbeddedReference instance.

WSS0756: Error creating `SOAPElement` for `wsse:KeyIdentifier`.

Solution: Check your SAAJ API Documentation.

WSS0757: Error adding `KeyIdentifier` value to `wsse:KeyIdentifer`.

Solution: Check your SAAJ API Documentation.

WSS0758: Error creating `javax.xml.soap.Name`.

Solution: Refer your SAAJ API Documentation.

WSS0759: An `X509IssuerSerial` instance can not be created.

Solution: Check that the SOAPElement passed to the constructor is conformant to spec. (and has X509IssuerSerial child elements).

WSS0800: `ds:KeyInfo` in the message is not a valid one.

Solution: Check if the ds:KeyInfo in the message is valid.

WSS0753: An embedded token in `wsse:Embedded` element is missing.

Solution: Check that the token element is conformant to the WSS specification.

WSS0754: Token on `EmbeddedReference` has already been set.

Cause: A SOAPElement representation of EmbeddedReference containing the Token is used to create the EmbeddedReference instance.

WSS0756: Error creating `SOAPElement` for `wsse:KeyIdentifier`.

Solution: Check your SAAJ API Documentation.

WSS0757: Error adding `KeyIdentifier` value to `wsse:KeyIdentifer`.

Solution: Check your SAAJ API Documentation.

WSS0758: Error creating `javax.xml.soap.Name`.

Solution: Refer your SAAJ API Documentation.

WSS0759: An `X509IssuerSerial` instance can not be created.

Solution: Check that the SOAPElement passed to the constructor is conformant to spec. (and has X509IssuerSerial child elements).

WSS0800: `ds:KeyInfo` in the message is not a valid one.

Solution: Check if the ds:KeyInfo in the message is valid.

Application Server 9.0 Platform Edition Error Message Reference

Overview

About This Wiki

How This Wiki is Organized

Preface

Who Should Use This Book

Before You Read This Book

How This Book Is Organized

Accessing Sun Resources Online

Unexpected Errors

DPL Error Messages

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

DPL8002: Copying of files failed.

DPL8003: {ArchivistFactory.getArchivist()}} failed.

DPL8004: Opening of files failed.

DPL8005: Error while parsing the deployment descriptor.

DPL8006: Adding or getting a descriptor failed.

DPL8007: Failed to find the resource specified in the deployment descriptor.

DPL8008: Failed to load the class/method.

DPL8009: Failed to load the deployment manager.

DPL8010: Failed in autodeployment.

DPL8011: Failed in autodeployment of applications.

DPL8012: Failed to rename directory.

DPL8013: Failed to create JAR file.

DPL8014: Failed to complete application deployment.

DTX Error Messages

DTX5001: Exception occurred while enlisting the resource.

DTX5002: Exception occurred while delisting the resource.

DTX5003: Trying to register the sync object while transaction is marked for rollback.

DTX5004: Exception occurred while enlisting the component resource.

DTX5005: Exception occurred while delisting the component resources.

DTX5006: Exception occurred while delisting the component resources.

DTX5008: Exception occurred while closing the connection.

DTX5009: Invalid integer passed to set the timeout.

DTX5010: Could not register the JTA statistics for monitoring due to configuration problem.

DTX5011: Requested attribute is not monitorable.

DTX5012: JTAStats implementation class is not found.

EEADM Error Messages

EEADM0069: Error while sending event to remote instance.

EJB Error Messages

EJB5013: Problem occurred while deserializing stateful bean state.

EJB5017: An error occurred during the removal of an entity bean.

EJB5031: An error occurred while looking up a Read Only Bean Notifier.

EJB5069: The bean's Home or LocalHome does not define a no-arg create method.

EJB5071: Some problem occurred during the beforeCompletionphase of the transaction lifecycle.

EJB5090: Problem during EJB container runtime initialization.

EJB5111: This error indicates a mismatch

EJB5117: Error while creating the persistent representation of an EJB timer.

EJB5128: A problem occurred while the container was activating a stateful session bean.

EJB5129: An error occurred during the afterCompletion phase of the transaction lifecycle.

JDO Error Messages

JDO7000: Error loading the default mapping policy which is used by database schema generation.

JDO74003: Internal error in CMP module.

JDO74005: CMR field is accessed in ejbCreate.

JDO74006: Parameter passed to Collection CMR set method is null.

JDO74019: Possible error in EJB Container and CMR runtime life cycle.

JDO74020: Possible error in EJB Container and CMR runtime life cycle.

JDO74021: ejbRemove or ejbStore is called in an active transaction without bean being loaded in the same transaction.

JDO74043: Create, remove, or update is called on a read-only bean.

JDO74045: State class is not generated properly for this CMP bean.

JDO75007: Internal error in CMP module.

JDO76604: JNDI name for the CMP resource is misspelled.

JDO7704: Cannot identify related field.

JDO82000: System was not able to create specified logger.

JTS Error Messages

JTS5001: Servant is already active.

JTS5005: Recovery or resync process got interrupted.

JTS5008: Transaction log directory is not accessible.

JTS5015: ORB may not be running.

JTS5020: Configuration problem while giving the log path.

JTS5028: XAResource.recover has thrown an exception during recovery.

JTS5032: Server could not communicate with the resource manager with in the retry limit.

JTS5040: ORB may not be running.

JTS5041: Database driver or Resource Adapter has thrown XAException with the error message

JTS5064: Unexpected exception thrown from XAResource.end.

JTS5065: Transaction Log directory path is not valid or proper permissions are not there.

JTS5066: Possible cause is that transaction logs are corrupted.

MDB Error Messages

MDB00017: An error occurred during the message-driven beancontainer initialization at runtime.

MDB00048: An error occurred during the pre-invocation processing before a message-driven bean MessageListener method is called.

DPL8010: Failed in `autodeployment`.

EJB5069: The `bean's` Home or `LocalHome` does not define a `no-arg` create method.

EJB5071: Some problem occurred during the `beforeCompletionphase` of the transaction lifecycle.

EJB5129: An error occurred during the `afterCompletion` phase of the transaction lifecycle.

JDO74005: CMR field is accessed in `ejbCreate`.

JDO74021: `ejbRemove` or `ejbStore` is called in an active transaction without bean being loaded in the same transaction.

JTS5028: `XAResource.recover` has thrown an exception during recovery.

JTS5041: Database driver or Resource Adapter has thrown `XAException` with the error message

JTS5064: Unexpected exception thrown from `XAResource.end`.

MDB00017: An error occurred during the message-driven `beancontainer` initialization at runtime.

MDB00048: An error occurred during the pre-invocation processing before a message-driven bean `MessageListener` method is called.

NAM0003: Problem in creating a remote object for `SerialContextProvider`.

NAM1003: Bad `host:port` entry.

RAR5015: Classpath is not properly set in `domain.xml`.

RAR5046: Classpath is not properly set in `domain.xml`.

RAR5048: The configuration for the JDBC resource could not be read from `domain.xml`.

RAR5063: The class specified in `datasourceclassname` attribute in the `jdbc-connection-pool` is not of type `javax.sql.XADataSource`.

RAR5065: The class specified in `datasourceclassname` attribute in the `jdbc-connection-pool` is not of type `javax.sql.ConnectionPoolDataSource`.

RAR5099: Classpath is not properly set in `domain.xml`.

RAR5100: Classpath is not properly set in `domain.xml`.

RAR5103: Error configuring the `DataSource` object.

RAR5104: Error configuring the `DataSource` object.

RAR5105: The connection validation method is incorrect, it should be one of `auto-commit`, `meta-data`, `table`.

RAR5109: JDBC driver has thrown an `SQLException` while setting the isolation level.

RAR5111: The class specified in `datasourceclassname` attribute in the `jdbc-connection-pool` is not of type `javax.sql.DataSource`.

RAR5112: The class specified in `datasourceclassname` attribute in the `jdbc-connection-pool` is not of type `javax.sql.XADataSource`.

RAR6000: Illegal access Error while instantiating one of the resource adapter JavaBeans like `ManagedConnectionFactory` or `ResourceAdapter` JavaBean classes.

RAR6001: Error while locating one of the resource adapter JavaBeans like `ManagedConnectionFactory` or `ResourceAdapter` JavaBean classes.

RAR6002: Error while instantiating one of the resource adapter JavaBeans like `ManagedConnectionFactory` or `ResourceAdapter` JavaBean.

RAR6004: Illegal access Error while instantiating one of the resource adapter JavaBeans like `ManagedConnectionFactory` or `ResourceAdapter` JavaBean classes.

RAR6005: Error while creating `ManagedConnectionFactory`.