Chapter 1 Oracle GlassFish^TM Server 3.0.1 Error Messages

This chapter provides a compilation of error messages that you might encounter when using Sun GlassFish GlassFish Server 3.0.1.

This content is also available in wiki format on the GlassFish wiki: http://wiki.glassfish.java.net/Wiki.jsp?page=GlassFishV3ErrorMessageReference. The wiki version is an interactive, editable resource and may contain information that is not presented here. Consult that resource as well.

Error messages provide information about events that occur during GlassFish Server operation, such as configuration errors, security failures, or server malfunction. These messages often include diagnostic and troubleshooting information.

Error messages can also be viewed in the Administration Console Log Viewer. For more information about logging, see Chapter 7, Administering the Logging Service, in Oracle GlassFish Server 3.0.1 Administration Guide.

For additional troubleshooting information, see Oracle GlassFish Server 3.0.1 Troubleshooting Guide.

Message IDs and Diagnostic Information

Error messages in this chapter are listed in alphabetic and numeric order by message ID. The text is as it appears in the actual error message. Each message ID includes a prefix that represents a subsystem within the software.

Error messages for the following prefixes are provided:

• ACC

• ACDEPL

• ADM

• DIAG

• DPL

• DTX

• EJB

• JDO

• JTS

• MDB

• NAM

• RAR

• SEC

• WEB

ACC

ACC001 Using the only client {1} with main class {2} in {0} even though it does not match the specified main class name {3} or client name {4}

Cause:

The command line specified a main class or a client name different from the main class and name of the only client found.

Solution:

The error message lists the main classes and client names for the clients in the JAR. Make sure the command line specifies one of those.

ACC002 The application contains multiple app clients; please choose one using -mainclass {0} or -name {1}

Cause:

The command line did not specify a main class or a client name to run, and the JAR contains more than one client.

Solution:

Specify either -mainclass your-main-class-name or -name your-client-name on the appclient command.

ACC003 No app client in the app client group {0} matches the main class name "{1}" or the app client name "{2}";\nPlease choose one using -mainclass {3} or -name {4}

Cause:

The JAR file contains multiple app clients and none matches the -mainclass value or the -name value that was specified on the appclient command.

Solution:

Review the list of main classes and names in the original error message and make sure the appclient command specifies a main class or a name listed.

ACC004 No app clients are listed in the app client group {0}

Cause:

The deployment which generated the downloaded JAR file might have failed partially.

Solution:

Check the server.log file on the server for any deployment errors.

ACC005 The main method is either not public or not static

Cause:

The main method for the app client is not declared as "public."

Cause:

The main method for the app client is not declared as "static."

Solution:

Declare the main method as "public."

Solution:

Declare the main method as "static."

ACC006 The main method's return type is not void

Cause:

The main method does not have a return type of "void."

Solution:

Declare the main method so its return type is "void."

ACC007 The app client {0,choice,0#file|1#directory} {1} does not contain a manifest; the app client container cannot process it.

Cause:

The file might not be a valid app client JAR or undeployed EAR. It might be another kind of file or have become corrupted.

Solution:

Make sure to specify a valid app client JAR file or an EAR which contains at least one app client.

ACC008 The manifest in the app client facade {0} does not contain the expected entry for {1} or it is invalid; the app client container cannot process it.

Cause:

The app client facade JAR file might have generated incorrectly.

Cause:

The app client facade JAR file might have become corrupted.

Solution:

Check the server's server.log file for any errors during deployment of the application.

Solution:

Use the get-client-stubs command to retrieve the generated JAR files for the application again.

ACC009 \nThe credentials you provided (username and password) were not valid or do not\nallow access to the application. Please try again with a valid username and \npassword. If you are certain the username and password are correct please\ncontact your system administrator. The following information might be helpful:\n\n{0}

Cause:

The user supplied a username and password combination that are not valid.

Cause:

The user supplied a valid username and password but they are not authorized for access to the server-side resource requested.

Solution:

Make sure the username and password are correct.

Solution:

Make sure the username and password grant the desired access to the requested server-side resource.

ACC011 The expected client file {0} is missing. The deployment of the application or retrieval of the app client might have failed.

Cause:

The manifest of the generated facade JAR file refers to the specified app client JAR file but that file does not seem to exist.

Solution:

Make sure the deployment of the application succeeded and that the download of the app client files (using either "deploy --retrieve" or "get-client-stubs" succeeded.

ACDEPL

ACDEPL001 Directory URL {0} in the manifest Class-Path for {1} will not be honored; it does not end with a slash.

Cause:

Default class loaders will not include files from this directory at runtime; also, as a result, these files be not downloaded to clients.

Solution:

Please make sure all such directory URLs in the Class-Path entry of JAR manifests have a trailing slash.

ACDEPL101 Java Web Start services not started for the app client {0}; its developer has marked it as ineligible

Cause:

The developer's sun-application-client.xml file marks the app client as ineligible for Java Web Start support.

Solution:

If users should be able to launch this client using Java Web Start, change the <java-web-start-support> 'enabled' attribute.

ACDEPL102 Java Web Start services not started for the app client {0}; the administrator has disabled Java Web Start support for it

Cause:

The administrator disabled Java Web Start launches for the app client, either using '--properties java-web-start-enabled=false' during deployment or changing the properties afterwards.

Solution:

If users should be able to launch this client using Java Web Start, either deploy the application again without --properties or adjust the configuration using the admin console or the asadmin 'set' command

ACDEPL105 Error starting the adapter to serve static system-level content

Cause:

An unexpected internal system error occurred

Solution:

Please consult the exception stack trace

ACDEPL106 Attempt to replace existing static content for {0} with {1} which does not match the existing content {2}

Cause:

This is an internal error.

Solution:

Please file an issue with a reproducible test case.

ACDEPL107 Attempt to add or retrieve content with URI {0} to HTTP adapter with context root {1} and user-friendly context root {2} rejected; URIs must fall within the adapter context root

Cause:

This is an internal error.

Solution:

Please file an error with a reproducible test case.

ACDEPL108 Config file for client JNLP not found: {0}

Cause:

The config file does not exist.

Solution:

The file is part of the installation so this might be an internal error. Make sure you have not accidentally removed or renamed the config file. If not, please file an error with a reproducible test case.

ACDEPL109 The config file for client JNLP {0} exists but could not be read.

Cause:

The config file might be protected from reading.

Solution:

Make sure the config file protection settings permit the server to read it.

ACDEPL110 Error processing client JNLP config file {0}

Cause:

An error occurred attempting to process the config file's contents.

Solution:

The contents of the file might be invalid or incorrectly formatted. Check to make sure the file includes valid property settings.

ACDEPL111 Client JNLP document {0} refers to the static resource {1} that does not exist or is not readable.

Cause:

The developer-provided JNLP content refers to a file as if the file is in the application but the server could not find the file.

Solution:

Make sure the file is packaged in the application and that the reference to the file is correct. Then rebuild and redeploy the application.

ACDEPL112 Error attempting to process extensions from the manifest of JAR file {0}; ignoring it and continuing

Cause:

The exception listed in the log file was thrown as the server tried to open the JAR file or process the extensions listed in its manifest.

Solution:

Make sure the manifest of the JAR file correctly lists the extensions on which the JAR depends.

ADM

ADM1601 Received a request for registration of MBean, {0}, but it is already registered in the MBeanServer.

Cause:

Registration of the MBean was unsuccessful because it is already registered.

Solution:

Run 'asadmin list-mbeans' to see a list of registered MBeans

ADM1603 Unable to unregister the MBean, {0}. This MBean was never registered in the MBeanServer. In general, this should not be a problem.

Cause:

Unregistration of the MBean failed because it is not registered.

Solution:

Run 'asadmin list-mbeans' to see a list of registered MBeans

ADM1606 Can''t handle updating an MBean element itself ({0}). The MBean is updated in terms of its xml-attributes, none of which are dynamically reconfigurable.

Cause:

Can't handle updating an MBean element

Solution:

Note that none of the attributes of "mbean" element except 'enabled' and 'object-name' are modifiable dynamically. Only the properties in this element that are actually the attributes of the runtime mbean are modifiable dynamically.

ADM1607 Received an MBean change event, but the MBean, {0}, is disabled. Disabled MBeans can''t have their state changed.

Cause:

Disabled MBeans are not allowed to have their state changed

Solution:

Try enabling the MBean

ADM1608 An MBean with name: {0} could not be loaded. Continuing to load other MBeans";

Cause:

The MBeanServer refused to load the MBean

Solution:

Try redeploying the MBean

ADM1618 Can''t unregister MBean: {0}

Cause:

Can not unregister the MBean. This is a non-fatal error.

Solution:

Try restarting the AppServer

ADM5609 Unknown server context type [{0}]. Unable to set the config context from the event multicaster.

Cause:

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

DIAG

DIAG9049 No Diagnostic data has been collected

Solution:

Check whether the target [domain, node-agent, instance, cluster] is running.

DPL

DPL8001 descriptor failure {0}

Cause:

Archivist.setDescriptor() failed

Cause:

The instance may not be of expected type

Solution:

Ensure that the descriptor type is set as expected

Solution:

Turn log level for deployment to see more details

DPL8002 file copy failure

Cause:

Copying of files failed

Cause:

May be because of lack of space or permission

Solution:

Ensure that there is enough disk space

Solution:

Ensure that the permissions are set as expected

DPL8003 archivist instantiation failure for {0}; type = {1}

Cause:

ArchivistFactory.getArchivist() failed

Cause:

the module type may not be as expected

Solution:

Ensure that the module type is one of the supported types

Solution:

Ensure that the module type is one of the supported types

DPL8004 file open failure; file = {0}

Cause:

Opening of files failed

Cause:

May be because of lack of permission or wrong file name

Solution:

Ensure that the file name is correct

Solution:

Ensure that the permissions are set as expected

DPL8005 Deployment Descriptor parsing failure : {0}

Cause:

Error while parsing the deployment descriptor

Cause:

May be because of malformed descriptor or absence of all required descriptor elements

Solution:

Ensure that the descriptor is well formed and as per specification

Solution:

Ensure that the SAX parser configuration is correct and the descriptor has right permissions

DPL8006 get/add descriptor failure : {0} TO {1}

Cause:

Adding or getting a descriptor failed

Cause:

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

Solution:

Ensure that the node to be added is valid

Solution:

Ensure that the permissions are set as expected

DPL8007 Invalid Deployment Descriptors element {0} value {1}

Cause:

Failed to find the resource specified in the deployment descriptor

Cause:

May be because of wrong specification in the descriptor

Solution:

Ensure that the resource specified is present

Solution:

Ensure that there is no typo in the resource specified in the descriptor

DPL8008 method/class loading failure : method/class name - {0}

Cause:

Failed to load the class / method

Cause:

May be because of wrong class/method name

Solution:

Ensure that the class / method specified is present

Solution:

Ensure that the path info is correct

DPL8009 deployment manager load failure : unable to load - {0}

Cause:

Failed to load the deployment manager

Cause:

May be because of wrong uri specification or deployment factory not installed at all

Solution:

Ensure that the resource specified is present

Solution:

Ensure that there is no typo in the URI specified

DPL8010 autodeployment startup failure

Cause:

Failed in autodeployment

Cause:

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

Solution:

Ensure that the autodeploy is enabled properly

Solution:

Ensure that there autodeploy config info is set properly

DPL8011 autodeployment failure while deploying the application : {0}

Cause:

Failed in autodeployment of applications

Cause:

Mostly because of application specific failure

Solution:

Ensure that the application can be deployed using CLI

Solution:

Ensure that there autodeploy config info is set properly and the server is up and running

DPL8012 directory rename failure : {0} TO {1}

Cause:

Failed to rename directory

Cause:

May be because of lack of permissions

Solution:

Ensure that the permissions are set as expected

Solution:

Ensure that there is no directory name clash

DPL8013 JAR file creation failure : {0}

Cause:

Failed to create JAR file

Cause:

May be because of lack of permissions or lack of space

Solution:

Ensure that the permissions are set as expected

Solution:

Ensure that there is enough space

DPL8014 Application deployment failure

Cause:

Failed to complete application deployment

Cause:

May be because of lack of permissions or lack of space or wrong application

Solution:

Ensure that the permissions are set as expected

Solution:

Ensure that there is enough space

DPL8015 This application has no role mapper factory defined

Cause:

Failed to find the resource specified in the deployment descriptor

Cause:

May be because of wrong specification in the descriptor

Solution:

Ensure that the resource specified is present

Solution:

Ensure that there is no typo in the resource specified in the descriptor

DPL8017 Ejb-ref type mismatch for ejb reference {0}. Reference declares type {1} but target ejb {2} has {3} interface of type {4}.

Cause:

Possible type mismatch in ejb-ref/ejb-local-ref/@EJB

Cause:

May be because of wrong specification in the descriptor

Solution:

Ensure that the type associated with the ejb reference is the correct one.

Solution:

Ensure that there is no typo in the resource specified in the descriptor

DPL8021 Invalid URL {0} specified for WSDL location

Cause:

Failed to create a URL from the wsdl location specified

Cause:

May be because of wrong specification in the descriptor

Solution:

Ensure that the resource specified is a valid URL

Solution:

Ensure that there is no typo in the resource specified in the descriptor

DPL8022 Artifact {0} identified for inclusion in app clients after one or more app clients were generated.

Cause:

The application might specify that modules are to be processed in the order they appear in the application and an app client module appears before a module that creates an artifact to be included in app clients.

Solution:

Make sure, if the application specifies initialize-in-order as true, that the app clients appear after other modules which generated artifacts that should be accessible to app clients.

DPL8024 Artifact with relative path {0} expected at {1} but does not exist or cannot be read

Cause:

The server is attempting to register an artifact to be included in the generated app client JAR but the artifact does not exist or cannot be read

Solution:

This is an internal server error. Please file a bug report.

DPL8025 Artifact with relative path {0} from {1} collides with an existing artifact from file {2}

Cause:

The server has created more than one artifact with the same relative path to be included in the generated app client JAR file

Solution:

This is an internal server error. Please file a bug report.

DTX

DTX5001 Exception in enlistComponentResources.

Cause:

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 in delistComponentResources.

Cause:

Exception occurred while delisting 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.

DTX5003 RollbackException in registerSynchronization.

Cause:

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 RemoteException in UserTx.begin().

Cause:

Exception occurred while enlisting the component 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.

DTX5005 RemoteException in UserTx.commit().

Cause:

Exception occurred while delisting the component resources.

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.

DTX5006 RemoteException in UserTx.rollback().

Cause:

Exception occurred while delisting the component resources.

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.

DTX5008 Pooling Exception:

Cause:

Exception occurred while closing the connection.

Solution:

Check if DB is up and running.

DTX5009 Reconfiguration of transaction timeout failed

Cause:

Invalid integer passed to set the timeout.

Solution:

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

DTX5010 An exception occurred while JTAStats monitoring registration

Cause:

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 Error occurred while getting monitor attribute

Cause:

Requested attribute is not monitorable.

Solution:

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

DTX5012 ClassNotFoundException occurred while creating JTAStats

Cause:

JTAStats implementation class is not found.

Solution:

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

DTX5014 Caught exception in beforeCompletion() callback:

Cause:

Exception occurred while calling beforeCompletion() method of the registered synchronization

Solution:

Check exception message for the exact cause of the exception

DTX5015 Caught exception in afterCompletion() callback:

Cause:

Exception occurred while calling afterCompletion() method of the registered synchronization

Solution:

Check exception message for the exact cause of the exception

DTX5016 Error in XA recovery. See logs for more details

Cause:

Exceptions while trying to close connections of handlers.

Solution:

Individual resource handlers would have logged exceptions if any, check server.log for more details.

DTX5017 Cannot construct the probe. Transaction Manager is NULL!

Cause:

Transaction Manager is not set in the StatsProvider.

Solution:

This error shouldn't happen. Please file a bug with details about the setup.

DTX5018 TBEAN IS NULL FOR:

Cause:

TransactionAdminBean was not constructed properly

Solution:

This error shouldn't happen. Please file a bug with details about the setup.

EJB

EJB5013 Some EJB exception occurred : [{0}]

Cause:

Problem occurred while deserializing stateful bean state.

Solution:

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

EJB5017 Exception while running pre-invoke : ejbName = [{0}]

Cause:

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 Some remote exception occurred while refreshing rob : [{0}] : [{0}]

Cause:

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 Exception getting ejbcreate method : [{0}]

Cause:

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 remote or transactional roll back exception occurred

Cause:

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 healthy.

EJB5090 Exception in creating EJB container [{0}]

Cause:

Problem during ejb container runtime initialization. See stack trace for more details. Some common causes are global JNDI name conflicts, class-not-found 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 datasource make sure the corresponding database is running. If it uses a queue makes sure the physical queue has been created.

EJB5111 Bean class for ejb [{0}] does not define a method corresponding to [{1}] interface method [{2}]

Cause:

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 Timer creation failed for container [{0}] primary key [{1}] and info [{2}]

Cause:

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 datasource.

Solution:

Double-check the JDBC datasource (and its associated connection pool) assigned to the timer-datasource 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 Error during Stateful Session Bean activation for key [{0}]

Cause:

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 Error in ContainerSynchronization::afterCompletion

Cause:

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

Solution:

Check stack trace for details of error encountered by ejb container

EJB5169 Exception while running preinvoke

Cause:

An error occurred during the call to preInvoke of the EjbSecurityComponentInvocationHandler.

Solution:

Check the exception stack trace to see if the exception originated from EjbSecurityManager.

EJB5170 Exception while running postInvoke

Cause:

An error occurred during the call to postInvoke of the EjbSecurityComponentInvocationHandler.

Solution:

Check the exception stack trace to see if the exception originated from EjbSecurityManager.

EJB5173 No EJB modules found

Cause:

No EJB modules had been found on the classpath or specified via MODULE property.

Solution:

Check the classpath and the value(s) of the MODULE property.

EJB5174 Cannot determine server installation location

Cause:

Installation location is not specified, and cannot be determined relative to the implementation location.

Solution:

Check the classpath or specify server installation location using the org.glassfish.ejb.embedded.glassfish.installation.root property

EJB5175 Temporary file could not be created: {0}

Cause:

See output for details.

Solution:

See detailed exception at FINE log level.

JDO

JDO7000 Cannot get policy for {0}.

Cause:

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

Solution:

Check that the classpath settings are not corrupted.

JDO74003 Caught ModelException on setDeleteAction:

Cause:

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 Bean ''{0}'' is not persistent during call to {1}.

Cause:

CMR field is accessed in ejbCreate.

Solution:

Change bean code to access CMR fields in ejbPostCreate.

JDO74006 Bean ''{0}'' method {1}: Cannot set Collection value to null.

Cause:

Parameter passed to Collection CMR set method is null.

Solution:

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

JDO74019 Bean {0} is not loaded. Persistence manager in this instance is null.

Cause:

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 Cannot use bean {0} in more than one transaction. Persistence manager in this instance is not null.

Cause:

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 Bean {0} participates in a container transaction but persistence manager in this instance is null.

Cause:

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 Bean ''{0}'' method {1}: Update operations are not allowed for this bean type.

Cause:

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

Solution:

Do not attempt to update read-only beans.

Solution:

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 Cannot clone bean ''{0}'' instance with key {1}.

Cause:

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 Fatal internal exception while parsing EJBQL:\n\

Cause:

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 lookup for cmp-resource ''{0}'' failed.

Cause:

CMP resource with this JNDI name is not registered with this instance.

Cause:

JNDI name for the CMP resource is misspelled.

Solution:

Check JNDI name for the resource you plan to use.

Solution:

Check JNDI name of the CMP resource specified in the module.

JDO76605 JNDI lookup for cmp-resource ''{0}'' returned an instance of an unexpected type: {1}.

Cause:

CMP resource with this JNDI name does not reference jdbc-resource or persistence-manager-factory-resource.

JDO7704 This error (\

Cause:

Cannot identify related field.

Cause:

Cannot identify related class.

Solution:

Verify that relationship definition is correct.

JDO82000 Exception creating logger {0}

Cause:

System was not able to create specified logger.

Cause:

Error loading message bundle that corresponds to this logger.

Solution:

Check that the classpath settings are not corrupted.

Solution:

Check error log for the detailed reason.

JTS

JTS5001 Cannot create control object reference.

Cause:

Servant is already active.

Cause:

Servant is not active.

Solution:

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

JTS5002 Cannot locate [{0}] servant.

Solution:

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

JTS5003 Cannot destroy [{0}] object reference.

Solution:

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

JTS5004 Cannot create coordinator object reference

Solution:

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

JTS5005 Wait for resync complete interrupted

Cause:

Recovery or resync process got interrupted.

Solution:

See the server log for more details.

JTS5006 Unable to convert object reference to string in recovery.

Solution:

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

JTS5007 Cannot initialise log.

Solution:

See the server log for more details.

Solution:

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

JTS5008 Cannot open log file for server = [{0}].

Cause:

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

Solution:

Transaction log directory is not accessible.

JTS5009 Cannot create CoordinatorResource object reference

Solution:

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

JTS5010 Cannot create CoordinatorSynchronization object reference

Solution:

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

JTS5011 No coordinator available.

Solution:

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

JTS5012 Unexpected error occurred when trying to begin a new transaction.

Solution:

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

JTS5013 Unable to create a subordinate Coordinator.

Solution:

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

JTS5015 Unexpected error occurred when creating portable object adaptors

Cause:

ORB may not be running.

Solution:

Make sure that ORB is running.

Solution:

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

JTS5016 Unexpected error occurred when creating current object

Solution:

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

JTS5018 Cannot register [{0}] instance with the ORB.

Solution:

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

JTS5020 Invalid log path. Using [{0}].

Cause:

Configuration problem while giving the log path.

Solution:

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

JTS5022 Unexpected exception [{0}] from log.

Solution:

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

JTS5024 Cannot create RecoveryCoordinator object reference.

Solution:

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

JTS5026 Exception [{0}] recovering an in-doubt Coordinator.

Solution:

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

JTS5027 Exception [{0}] on [{1}] operation during resync.

Solution:

See the server log for more details.

JTS5028 XAException occurred during recovery of XAResource objects; XA Error Code : [{0}]

Cause:

XAResource.recover has thrown an exception during recovery.

Solution:

See the exception Stack trace for more details.

JTS5029 Exception [{0}] on [{1}] operation during resync.

Solution:

See the server log for more details.

JTS5030 Unable to write restart record.

Solution:

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

JTS5031 Exception [{0}] on Resource [{1}] operation.

Solution:

See the server log for more details.

JTS5032 Retry limit of [{0}] [{1}] operations exceeded.

Cause:

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).

JTS5033 Exception [{0}] on [{1}] synchronization operation.

Solution:

See the server log for more details.

JTS5034 Already identified to communications manager.

Solution:

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

JTS5035 Unable to identify to communications manager.

Solution:

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

JTS5036 Transaction in the wrong state for [{0}] operation.

Solution:

See the server log for more details.

Solution:

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

JTS5037 Cannot create Terminator object reference.

Solution:

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

JTS5040 Cannot create TransactionFactory object reference.

Cause:

ORB may not be running.

Solution:

See the server log for more details.

Solution:

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

JTS5041 The resource manager is doing work outside a global transaction

Cause:

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.

JTS5042 Unexpected error occurred while getting the status of the transaction

Solution:

See the server log for more details.

Solution:

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

JTS5043 Unexpected error occurred while creating transaction manager instance

Solution:

See the server log for more details.

Solution:

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

JTS5048 Assert condition not satisfied

Solution:

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

JTS5049 Cannot create XAResource object reference.

Solution:

See the server log for more details.

Solution:

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

JTS5051 Invalid transaction state change

Solution:

See the server log for more details.

Solution:

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

JTS5053 Invalid log record data in section [{0}].

Solution:

See the server log for more details.

Solution:

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

JTS5054 Unexpected error occurred in after completion

Cause:

One or more SynchronizationImpls beforeCompletion or afterCompletion methods have thrown unexpected exception.

JTS5055 Unexpected error occurred in getCORBAReference

Solution:

See the server log for more details.

Solution:

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

JTS5056 Invalid wait point

Solution:

Make sure to call FailureInducer.setWaitPoint() with a valid WaitPoint.

JTS5058 Invalid crash point

Solution:

Make sure to call FailureInducer.setWaitPoint() with a valid WaitPoint.

JTS5059 Exception recovering an in-doubt Coordinator

Solution:

See the server log for more details.

Solution:

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

JTS5062 Exception occurred while setting XAResource timeout

Solution:

See the server log for more details. XAResource.setTransactionTimeout() might not be supported for this XAResource.

JTS5064 Unexpected exception occurred while delisting the resource

Cause:

Unexpected exception thrown from XAResource.end.

Solution:

See the server log for more details.

JTS5065 An IO Exception occurred while handling recovery file

Cause:

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 Unexpected error occurred in recovery process. Possible cause is that transaction logs are corrupted. Please clean up the transaction-service.tx-log-dir/tx/* files and restart the server.

Cause:

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

MDB00017 [{0}]: Exception in creating message-driven bean container: [{1}]

Cause:

An error occurred during the message-driven bean container initialization at runtime. 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 Message-driven bean [{0}]: Exception in preinvoke : [{1}]

Cause:

An error occurred during the pre-invocation processing before a message-driven bean MessageListener method is called. 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 Message-driven bean [{0}]: Exception in creating message-driven ejb : [{1}]

Cause:

An error occurred during the lifecycle initialization of a message-driven bean instance. 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 Message-driven bean [{0}] preinvoke exception in destroy message-driven ejb: [{1}]

Cause:

An error occurred while the container was destroying an instance of a message-driven bean. 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 Message-driven bean [{0}]: start message delivery exception: [{1}]

Cause:

An error occurred while the container was enabling the message flow into a message-driven bean. 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

NAM0002 Exception in NamingManagerImpl copyMutableObject().

Cause:

Problem with serialising or deserialising of the object

Solution:

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

NAM0003 Exception in SerialContextProviderImpl InsertSerialContextProvider() : {0}.

Cause:

Problem in creating a remote object for SerialContextProvider.

Cause:

Problem during publishing SerialContextProvider in CosNaming Service.

Solution:

Check if ORB CosNaming Service initialised.

NAM0004 Exception during name lookup : {0}

Cause:

App Server may not be running at port intended.

Cause:

Possible Network Error.

Solution:

Check to see if the AppServer is up and running on the port intended. The problem could be because of incorrect port.

Solution:

Check to see if you can access the host on which the AppServer running.

NAM0005 JMS Connection Factory resource not found: {0}

Cause:

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 Admnistrator's console. Check the JMS resource references bindings.

NAM0006 JMS Destination object not found: {0}

Cause:

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 Admnistrator's console. Check the JMS resource references bindings.

NAM0007 Message Destination Reference {0} has not been linked to a Message Destination

Cause:

Unresolved Message Destination Reference

Solution:

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

NAM0008 Invalid Destination: {0} for {1}

Cause:

Invalid Destination Name

Solution:

Check Destination Name

NAM1000 No Endpoints selected in com.sun.appserv.iiop.endpoints property. Using {0}:{1} instead

Cause:

No endpoints selected.

Solution:

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

NAM1001 No Endpoints selected in com.sun.appserv.iiop.endpoints property. Using JNDI Provider URL {0} instead

Cause:

No endpoints selected.

Solution:

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

NAM1002 Exception : (0) thrown for bad provider URL String: {1}

Cause:

Bad JNDI provider URL

Solution:

Check system property java.naming.provider.url

NAM1003 Bad host:port entry: {0} Exception thrown : {1}

Cause:

Bad host:port entry

Solution:

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

NAM1004 Unknown host: {0} Exception thrown : {1}

Cause:

Unknown host

Solution:

Check the host entry

NAM1005 No Endpoints selected. Please specify using system property com.sun.appserv.iiop.endpoints.

Cause:

No endpoints selected.

Solution:

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

RAR

RAR2001 Unsupported callback {0} during credential mapping

Cause:

Resource adapter has used a callback that is not supported by application server

Solution:

Check whether the callback in question is supported by application server

RAR2002 Work is an WorkContextProvider and ExecutionContext [ {0} ] is not null

Cause:

submitted work has execution-context as well it is a work-context-provider which is specification violation

Solution:

Make sure that either execution-context or work-context-provider with transaction-context is passed, but not both

RAR2003 duplicate work context for type [ {0} ]

Cause:

multiple work contexts of same type submitted

Solution:

Make sure that same context type is not submitted multiple times in the work-context

RAR2004 Application server cannot handle the following work context : {0}

Cause:

Work Context in question is not supported by application server

Solution:

Check the application server documentation for supported work contexts

RAR2005 setting custom workcontext for WorkContext [ {0} ] using most specific support Work Context [ {1} ]

Cause:

Requested work context is not supported, but a super type of the context is supported

RAR2006 most specific work context for [ {0} ] supported by container is [ {1} ]

Cause:

Requested work context is not supported, but a super type of the context is supported

RAR2007 Unable to load work context class {0} due to the following exception {1}

Cause:

Work Context class is not available to application server

Solution:

Make sure that the work context class is available to server

RAR2008 Unable to set security context

Cause:

Unable to set security context

Solution:

Check the server.log for exceptions

RAR5004 Error in XA recovery. See logs for more details.

Cause:

Jdbc driver threw an exception while recovery.

Cause:

Resource Adapter threw an exception while recovery in case of connectors.

Solution:

Check database or EIS log for details.

Solution:

Check whether the connection pool configuration is proper.

Solution:

Check whether domain.xml is accessible.

RAR5005 Error in accessing XA resource with JNDI name [{0}] for recovery

Cause:

The XA resource has been deleted before attempting recovery

Cause:

The XA resource is no longer referenced in the domain.xml

Cause:

The database server that the XA resource points to is no longer running

Cause:

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 the domain.xml

Solution:

Check that the XA Resource is present in the list of resource-refs in the domain.xml

Solution:

Check that the Database server is up and running

Solution:

Check if the config 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 Error in creating data source object: [{0}]

Cause:

Exception while creating persistent manager resource.

Solution:

Check whether the persistent manager factory class is configured properly and is available in the classpath.

Solution:

Check whether the jdbc resource name is correct and is configured properly.

RAR5008 Error in creating a naming Reference for custom resource [{0}]

Cause:

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

Solution:

Check if the naming provider is up and listening on the port specified in the domain.xml

RAR5009 Cannot load external-jndi-resource factory-class ''[{0}]''

Cause:

Could not create an instance of factory-class.

Solution:

Make sure that factory-class name is configured correctly.

Solution:

Make sure that factory-class is available in the classpath of the application server

RAR5010 external-jndi-resource factory-class ''[{0}]'' must be of type javax.naming.spi.InitialContextFactory

Cause:

External JNDI resource has a wrong factory-class configuration

Solution:

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

RAR5011 Exception thrown creating initial context for external JNDI factory ''[{0}]''

Cause:

Could not create Initial Context.

Solution:

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

RAR5012 Cannot create external-jndi-resource factory-class ''[{0}]''

Cause:

Could not create Initial context factory.

Solution:

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

RAR5015 Unexpected exception in loading class [{0}] by classloader

Cause:

Classpath is not properly set in the domain.xml

Cause:

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

Solution:

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

RAR5020 Error in Persistence Manager Settings [{0}]

Cause:

Could not configure persistence manager resource properly.

Solution:

Make sure that the Jdbc resource name, you have configured is correct

Solution:

Check whether the persistence manager factory class is proper.

Solution:

Check whether the persistence manager factory class has a setConnectionFactoryName method.

RAR5026 Failed to complete transaction.Error Message: [{0}].

Cause:

Internal error while completing the transaction.

RAR5027 Unexpected exception in resource pooling

Cause:

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

RAR5029 Unexpected exception while registering component

Cause:

Internal error while registering the resource to the transaction.

RAR5030 Unexpected exception while registering synchronization

Cause:

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

RAR5031 System Exception

Cause:

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

RAR5035 Unexpected exception while destroying resource from pool {0}. Exception message: {1}

Cause:

Error while closing the physical connection.

Cause:

Error while destroying the connector managed connection.

Solution:

Refer to the manual of the resource that is pooled (JDBC driver or Resource Adapter).

Solution:

To get exception stack, please change log level to FINE. Examine this exception stack trace for details.

RAR5038 Unexpected exception while creating resource for pool {0}. Exception : {1}

Cause:

Could not create a physical connection.

Solution:

Connection pool is configured incorrectly.

Solution:

Database is running properly.

Solution:

EIS (in case of connectors) is running properly.

Solution:

SJS MQ (in case of JMS) is running properly.

Solution:

Network connection to Database/EIS/MQ is proper.

Solution:

Check linked exception (if there was a linked exception it is logged after this message).

RAR5042 Error in accessing XA resource for recovery

Cause:

The XA resource has been deleted before attempting recovery

Cause:

The XA resource is no longer referenced in the domain.xml

Cause:

The database server that the XA resource points to is no longer running

Cause:

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 the domain.xml

Solution:

Check that the XA Resource is present in the list of resource-refs in the domain.xml

Solution:

Check that the Database server is up and running

Solution:

Check if the config info of the XA resource and the pool it points to is sane. In particular check that the data source class name in the pool is correct and the XA resource points to the correct pool

RAR5043 Error in creating data source object:

Cause:

Exception while creating persistent manager resource.

Solution:

Check whether the persistent manager factory class is configured properly and is available in the classpath.

Solution:

Check whether the jdbc resource name is correct and is configured properly.

RAR5044 Error in Persistence Manager Settings

Cause:

Could not configure persistence manager resource properly.

Solution:

Make sure that the Jdbc resource name, you have configured is correct

Solution:

Check whether the persistence manager factory class is proper.

Solution:

Check whether the persistence manager factory class has a setConnectionFactoryName method.

RAR5045 Error in creating a naming Reference for custom resource

Cause:

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

Solution:

Check if the naming provider is up and listening on the port specified in the domain.xml

RAR5046 Unexpected exception in loading class by classloader [{0}]

Cause:

Classpath is not properly set in the 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

Solution:

Check that the directory where the classes/jars reside have read permission for the application server process

RAR5047 Exception thrown creating initial context for external JNDI factory [{0}]

Cause:

Could not create Initial Context.

Solution:

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

RAR5048 Error in configuring JDBC resource

Cause:

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

Cause:

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

RAR5058 Error while Resizing pool {0}. Exception : {1}

Cause:

Could not create physical connection during connection pool resizing.

Solution:

Check your database/ EIS logs for possible connection creation errors.

Solution:

Check whether your network connection to the database or EIS is proper.

RAR5063 Exception while creating XADataSource :{0}

Cause:

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 Exception while creating DataSource Object :{0}

Cause:

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 :{0}

Cause:

The Database server is not up and running

Cause:

The connection pool is full and cannot allocate more connections

Cause:

The Database server threw some unexpected exception. Please study the exception message for more details

RAR5068 No such element in connection set

Cause:

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

Cause:

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

RAR5069 Exception while fetching EIS Product name :{0}

Cause:

The Connection object is now invalid due to database restart

Cause:

The connection object is now invalid since the database is not up and running

Cause:

The JDBC driver cannot provide the required information due to internal error

Solution:

Switch on the connection validation property of the connection pool and try again

Solution:

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

Solution:

Check the server log and please contact Sun Microsystems with the complete error log

RAR5070 Exception while fetching EIS Product version :{0}

Cause:

The Connection object is now invalid due to database restart

Cause:

The connection object is now invalid since the database is not up and running

Cause:

The JDBC driver cannot provide the required information due to internal error

Solution:

Switch on the connection validation property of the connection pool and try again

Solution:

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

Solution:

Check the server log and please contact Sun Microsystems with the complete error log

RAR5074 Table based validation detected invalid connection. Querying the table {0} failed. Set resource-adapter log-level to FINE for exception stack trace.

Cause:

The Connection object is now invalid due to database restart

Cause:

The connection object is now invalid since the database is not up and running

Cause:

The JDBC driver cannot execute the statement due to internal error

Solution:

Switch on the connection validation property of the connection pool and try again

Solution:

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

Solution:

Check the server log and please contact Sun Microsystems with the complete error log

RAR5087 Exception while querying the EIS for max connections

Cause:

The Connection object is now invalid due to database restart

Cause:

The connection object is now invalid since the database is not up and running

Cause:

The JDBC driver cannot provide the required information due to internal error

Solution:

Switch on the connection validation property of the connection pool and try again

Solution:

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

Solution:

Check the server log and please contact Sun Microsystems with the complete error log

RAR5099 Wrong class name or classpath for Datasource Object

Cause:

Classpath is not properly set in the 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 the domain.xml has an entry for the jar containing this class

Solution:

Check that the directory where the classes/jars reside have read permission for the application server process

RAR5100 Wrong class name or classpath for {0}

Cause:

Classpath is not properly set in the 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 the domain.xml has an entry for the jar containing this class

Solution:

Check that the directory where the classes/jars reside have read permission for the application server process

RAR5101 Exception while instantiating {0}

Cause:

The appserver process does not have read access to the directory where this class resides

Cause:

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

Solution:

Check if your security manager policy is configured properly

RAR5102 Access error while instantiating {0}

Cause:

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

Cause:

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

Solution:

Check if all relevant JVM patches are installed on your machine. Please contact Sun Microsystems with the complete error log

RAR5103 Error setting java bean value : {0}

Cause:

The pool parameters in the domain.xml are improper.

Cause:

The application server process does not have enough permissions to access the DataSource class

Solution:

Check that the pool parameters specified in the domain.xml are correct. For example check that parameters that expect numeric values are numerals

Solution:

Check that the application server process has permissions to read the directory where the class resides

RAR5104 Not a valid type for this method : {0}

Cause:

The pool parameters in the domain.xml are improper.

Solution:

Check that the pool parameters specified in the domain.xml are correct. For example check that parameters that expect numeric values are numerals

RAR5105 Connection Error occurred : {0}

Cause:

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

Cause:

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.

Solution:

If the database has been restarted, restart the application server as well. If the database is down, start it up

RAR5106 AutoCommit based validation detected invalid connection. Set resource-adapter log-level to FINE for exception stack trace

Cause:

Database server is not up thus rendering the connection invalid

Cause:

The JDBC driver is unable to provide the auto-commit status of the connection due to an internal error

Solution:

Check if the database server is up and running

Solution:

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

RAR5107 Meta-Data based validation detected invalid connection. Set resource-adapter log-level to FINE for exception stack trace

Cause:

The connection is invalid due to a database restart

Cause:

The connection is invalid due to a database shutdown

Cause:

The JDBC driver cannot provide the connection's metadata information due to an internal error

Solution:

If the database has been restarted, restart the appserver as well. To avoid this in the future set the connection validation property in the pool

Solution:

Check that the database is up and running

RAR5108 Error while getting transaction isolation level :{0}

Cause:

The connection is invalid due to database restart/shutdown

Cause:

The JDBC driver cannot provide the transaction isolation level due to an internal error

Solution:

Please bring up the database if not up already. Check if the connection validation pool property is set, else set this property if the database server will be restarted in the future.

RAR5109 Error while setting transaction isolation level

Cause:

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

Solution:

Check whether your driver supports the isolation level you have specified in the connection pool.

RAR5110 Error creating managed Connection with user and password : {0}

Cause:

The URL specified is incorrect

Cause:

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.

Solution:

Check that the Database server is up and running

RAR5111 Error casting to javax.sql.Datasource

Cause:

The class specified in datasourceclassname attribute in the jdbc-connection-pool is not of type javax.sql.DataSource. Please consult your database vendor's documentation to identify the class that implements the javax.sql.DataSource

Solution:

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

RAR5112 Error casting to javax.sql.XADatasource

Cause:

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

RAR5113 Error creating connection from supplied information: Reason - {0}

Cause:

The Database server is not up and running

Cause:

The connection pool is full and cannot allocate more connections

Cause:

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

Solution:

Check if the size of your connection pool is sufficiently large for serving all requests

Solution:

Check the server log and please contact Sun Microsystems with the full error log

RAR5114 Error allocating connection : [{0}]

Cause:

There was an SQLException while acquiring connection from the Database. Please see the detailed exception message for more information

Cause:

The Connection pool is full and incapable of serving more requests at this point. Please try later.

Cause:

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

Solution:

Check if the database server is correctly configured

Solution:

Check if your pool size is sufficient to server all simultaneous connection requests

Solution:

Check the server log and contact Sun Microsystems with the complete error message

RAR5116 The XA connection could not be allocated: {0}

Cause:

The Database server is not up and running

Cause:

The connection pool is full and cannot allocate more connections

Cause:

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

Solution:

Check if the size of your connection pool is sufficiently large for serving all requests

Solution:

Check the server log and please contact Sun Microsystems with the full error log

RAR5117 Failed to obtain/create connection from connection pool [ {0} ]. Reason : {1}

Cause:

Error while obtaining a connection from the pool.

Solution:

Check your connection pool configuration.

RAR6000 Invalid deployment descriptor, no connection-definition found either via ra.xml or annotations for the resource-adapter [ {0} ]

Cause:

Illegal access Error while instantiating one of the resource adapter java beans like ManagedConnectionFactory or ResourceAdapter Javabean classes.

Solution:

Check whether the resource adapter have any specific security requirements..

RAR6001 Class Not found : {0}

Cause:

Error while locating one of the resource adapter java beans like ManagedConnectionFactory or ResourceAdapter Javabean classes.

Solution:

Resource adapter is bundled properly.

Solution:

Resource adapter jar file deployment descriptor specifies correct class names.

RAR6002 Could not instantiate class : {0}

Cause:

Error while instantiating one of the resource adapter java beans like ManagedConnectionFactory or ResourceAdapter Javabean.

Solution:

Resource adapter is bundled properly with all the classes.

RAR6004 Privileged action error : {0}

Cause:

Illegal access Error while instantiating one of the resource adapter java beans like ManagedConnectionFactory or ResourceAdapter Javabean classes.

Solution:

Check whether the resource adapter have any specific security requirements..

RAR6005 Could not create mcf : {0}

Cause:

Error while creating ManagedConnectionFactory.

Solution:

Resource adapter is bundled properly.

Solution:

Check whether connection pool configuration has correct properties for MCF.

Solution:

Check resource adapter documentation for configuring correct properties of MCF.

RAR6006 Failed to get ResourcesUtil object : {0}

Solution:

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

RAR6007 Failed to get Resources list from domain.xml

Cause:

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

Solution:

Check whether the resource adapter configuration is proper.

RAR6008 Failed to remove Active Resource Adapter from registry {0}

Cause:

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

Solution:

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

RAR6009 Connector Connection Pools/resources still exist. Remove all the connector connection pools and resources before undeploying rar : {0}

Cause:

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 started/deployed : {0}

Cause:

Resource Adapter is already active in the connector runtime.

Solution:

Check whether a previous resource adapter deployment is still available.

RAR6011 Failed to obtain the classloader : {0}

Solution:

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

RAR6012 Null pointer Exception : {0}

Solution:

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

Solution:

Check whether resource adapter threw a null pointer exception.

RAR6013 Could not publish connector descriptor in JNDI : {0}

Solution:

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

RAR6014 Could not find the connector descriptor in the rar : {0}

Cause:

Incomplete or erroneous resource adapter deployment.

Solution:

Check whether the RA deployment is proper and complete.

RAR6015 Obtained Null connection pool object from jndi : {0}

Cause:

Connection pool is not created properly.

Solution:

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

RAR6016 Active resource adapter not initialized.Rar Name : {0}

Cause:

Resource Adapter is not yet initialized in the connector runtime.

Solution:

Check whether the deployment of the resource adapter is complete.

RAR6017 Failed to get connection pool object via JNDI lookup : {0}

Cause:

Incomplete or erroneous connection pool creation.

Solution:

Check whether connection pool is created and is proper.

RAR6019 Failed to get connector descriptor from registry. RarName : {0}

Cause:

Incomplete or erroneous resource adapter deployment.

Solution:

Check whether the RA deployment is proper and complete.

RAR6020 Failed to publish connection pool object in JNDI : {0}

Solution:

Check whether the connection pool is existing.

RAR6021 Failed to create MCF : {0}

Cause:

Error while creating ManagedConnectionFactory.

Solution:

Resource adapter is bundled properly.

Solution:

Check whether connection pool configuration has correct properties for MCF.

Solution:

Check whether the resource adapter require security permissions to load the classes. Some adapters require getClassLoader() permission.

RAR6022 Failed to register MCF in connector registry : {0}

Cause:

NullPointerException while creating ManagedConnectionFactory.

Solution:

Check whether resource adapter throws null pointer exception.

RAR6023 Null connector descriptor in registry. Module Name is : {0}

Solution:

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

RAR6025 Failed to read the connector deployment descriptors : {0}

Cause:

Could not read the deployment descriptor of the resource adapter.

Solution:

Check whether the resource adapter is packaged correctly.

Solution:

Check the correctness of deployment descriptor.

RAR6026 Failed to parse the connector deployment descriptors : {0}

Cause:

Could not parse the deployment descriptor of the resource adapter.

Solution:

Check whether the resource adapter is packaged correctly.

Solution:

Check the correctness of deployment descriptor.

RAR6027 Malformed URL to add to path of classloader : {0}

Solution:

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

RAR6028 This adapter is not 1.5 compliant : {0}

Cause:

Resource Adapter doesnt contain resource adapter java bean.

Solution:

Make sure that the resource adapter is 1.5 compliant.

RAR6030 Failed to remove the MCF : {0}

Cause:

MCF cleanup in connector runtime failed.

Solution:

Check whether connection pool has already been deleted.

Solution:

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

RAR6031 Failed to unbind connectionPool from jndi : {0}

Solution:

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

RAR6032 Wrong connector resource entry in the domain.xml. No corresponding connection pool created. Pool Name:

Cause:

Connection Pool Name of the Resource configuration is wrong.

Solution:

Check whether the connection pool is created.

RAR6034 Wrong admin object entry in the domain.xml. No corresponding resource adapter deployed. Resource Adapter Name :

Cause:

Resource Adapter Name of the admin object configuration is wrong

Solution:

Check whether the resource adapter is deployed.

RAR6035 Resource adapter start failed : {0}

Cause:

Could not start the resource adapter instance.

Cause:

ResourceAdpater threw an exception during ResourceAdapter.start()

Solution:

Check whether the domain.xml is accessible.

Solution:

Check your resource adapter documentation for possible causes of failure during ResourceAdapter.start()

RAR6036 Resource adapter association failed : {0}

Cause:

Resource Adapter throws exception during ManagedConnectionFactory.setResourceAdapter()

Solution:

If you are using third party resource adapter, contact resource adapter vendor.

Solution:

If you are a resource adapter developer, please check the resource adapter code.

RAR6037 Resource adapter threw an exception while stopping

Cause:

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

Solution:

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

RAR7000 Check for a new version of MQ installation failed : {0}

Cause:

MQ resource adapter in the upgraded MQ is not accessible.

Cause:

Could not read the manifest of New MQ resource adapter file.

RAR7001 Upgrading a MQ resource adapter failed : {0}

Cause:

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 MDB deployment is still happening. Cannot create end point now.

Cause:

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

RAR7005 Class loader not found : [{0}]

Cause:

Could not access the class loader specific to the MDB.

RAR7006 ActivationSpec validation failed : [{0}]

Cause:

ActivationSpec validation failed.

Solution:

Check your JMS related configuration in MDB deployment descriptor.

Solution:

Check your activation configuration in the MDB deployment descriptor.

RAR7007 The method is not defined : [{0}]

Cause:

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

Solution:

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

RAR7008 Initialized monitoring registry and listeners

Solution:

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

RAR7010 Pool not reachable.

Cause:

Could not find the connection pool specified.

Solution:

Check whether the connection pool creation was successful.

Solution:

Check whether the pool name used is correct.

RAR7011 Unexpected exception determining whether resource is referenced.

Solution:

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

RAR7014 Error reading Connector Service Element from domain.xml while trying to get shutdown-timeout-in-seconds value. Continuing with the default shutdown timeout value

Cause:

Could not read shutdown-timeout-in-seconds from the domain.xml properly.

Solution:

Make sure that domain.xml is configured correctly.

RAR7092 Incorrect transaction support level. This RAR has a lower tx support level in its ra.xml transaction-support attribute : {0}

Cause:

The ra.xml specifies LocalTransaction as the transaction-support and connection-pool is configured with XATransaction support.

Cause:

The ra.xml specifies NoTransaction as the transaction-support and connection-pool is configured with XATransaction or LocalTransaction support.

RAR7093 Error while cleaning up ManagedConnection

Solution:

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

RAR7095 {0} shutdown unsuccessful. Please refer the server and/or resource adapter logs for more information.

Cause:

The resource adapter failed to shutdown within the specified shutdown timeout.

Solution:

Check the resource adapter and server logs for any exceptions during resource adapter stop.

Solution:

Increase the shutdown-timeout-in-seconds attribute of connector-service if the resource adapter requires a longer time to shutdown.

RAR7096 Exception {2} while trying to set the value {1} on property {0}

Cause:

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 No setter method present for the property {0} in the class {1}

Cause:

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.

RAR7099 The mcf being used to allocate the connection and the MCF in the pool are not equal.

Cause:

The configuration parameters like username/password for the Pool being accessed are changed and the application has not been redeployed

Cause:

The MCF equals method is improperly implemented

Solution:

Ensure that your resource adapter properly implements the equals method

RAR7101 Autocreation of physical destination {0} failed.

Cause:

Creation of physical destination in SJS MQ failed. Please look at SJS MQ log for more details.

Cause:

You haven't configured jms-service properly. Make sure that default-jms-host of jms-service points to a valid SJS MQ location.

RAR7102 Default-jms-host of jms-service is not configured properly. Using the first jms-host as the default-jms-host.

Cause:

You haven't configured default-jms-host in the jms-service.

Cause:

The jms-host configured as default-jms-host is not not available.

RAR7104 Exception while stopping Derby :

Cause:

Embedded Derby will always throw this exception when the database is shutdown

RAR7105 Derby Embedded Driver not found :

Cause:

Derby embedded driver class is not found in classpath

RAR7106 LazyConnectionEnlistment need to be true for LazyConnectionAssociation to work, for pool: {0}

Cause:

Connection Pool properties, LazyConnectionAssociation is true and LazyConnectionEnlistment is false which is not allowed.

RAR7107 Unable to retrieve password from alias

Cause:

Alias may not exist. Ensure that alias exists.

RAR7108 Error while loading jms resources during recovery : {0}

Cause:

Error getting jms resource configs.

Cause:

Lookup failed for the jms resource. Not found in jndi.

Solution:

See server log for more information

RAR7109 Error while loading jdbc resources during recovery : {0}

Cause:

Error getting jdbc resource configs.

Cause:

Lookup failed for the jdbc resource. Not found in jndi.

Solution:

See server log for more information

RAR7110 Error while loading connector resources during recovery : {0}

Cause:

Error getting connector resource configs.

Cause:

Lookup failed for the connector resource. Not found in jndi.

Cause:

Error loading the embedded RAR.

Solution:

See server log for more information

RAR8000 The method {0} is not present in the class : {1}

Solution:

Check the error message to see which class doesnt have the method.

Solution:

Check the connection pool configuration property names.

Solution:

Check the jms resource configuration property names.

Solution:

Check the admin object resource configuration property names.

Solution:

Check the resource adapter configuration property names.

RAR8001 Error in executing the method : {0}

Solution:

Check the error message to see which class has failed to execute the method.

Solution:

Check the connection pool configuration property names and values.

Solution:

Check the jms resource configuration property names. and values

Solution:

Check the admin object resource configuration property names and values.

Solution:

Check the resource adapter configuration property names and values.

RAR8002 Class Not Found : {0}

Solution:

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

RAR8003 Cannot register pool from monitoring registry: {0}

Solution:

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

RAR8004 Cannot unregister pool from monitoring registry: {0}

Solution:

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

RAR8007 Error registering MonitoringLevelListener in monitoring registry. The Exception is: {0}

Solution:

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

RAR8012 Exception while scheduling timer : {0}

Cause:

Timer could have already been cancelled because of any unchecked exception

RAR8013 Unable to destroy a jdbc resource during transaction recovery

Solution:

Check server.log for any resource specific exceptions

RAR8014 Associate with thread need to be false for Pooling disable to work, for pool: {0}

Cause:

Connection Pool properties, Associate with thread is true and Pooling is disabled which is not allowed.

RAR8015 Connection validation is set to true and Pooling is disable, for pool: {0}

Cause:

Connection validation is useful only in a pooled environment.

RAR8016 Validate Atmost once period is set when Pooling is disabled, for pool : {0}

Cause:

Validate atmost once period is useful only in a pooled environment.

RAR8017 Match Connections is set to true when Pooling is disabled, for pool : {0}

Cause:

Match Connections is useful only in a pooled environment.

RAR8018 Max Connection usage is set when Pooling is disabled, for pool : {0}

Cause:

Max Connection Usage is useful only in a pooled environment.

RAR8019 Idle Timeout is specified when Pooling is disabled, for pool : {0}

Cause:

Idle Timeout is useful only in a pooled environment.

RAR8021 Following validation constraints violated for Java Bean of type [ {0} ] of resource-adapter [ {1} ] : Message = {2})

Cause:

There could be erraneous values (not acceptable according to the constraints) specified in the bean

RAR8022 Failed to get invalid connections from Managed Connection Factory {0}. Exception = {1}; Message = {2}

Cause:

Resource Adapter threw a ResourceException.

Solution:

Check the resource adapter's documentation.

RAR8023 Flush Connection Pool did not happen as pool - {0} is not initialized

Cause:

Flush Connection Pool is a NO-OP as the pool has not been initialized till now.

Solution:

Check if pool has been initialized

RAR8024 Get Validation Table Names failed. Reason - {0}

Cause:

Database server is not up and admin GUI tries to get connection validation table names

Solution:

Make sure database server is up and running.

RAR8025 Flush Connection Pool failed for pool - {0}. Reason - {1}

Cause:

Database server is not up and Flush tries to access the pool.

Solution:

Make sure database server is up and running.

RAR8030 Exception while getting validation table names. Set resource-adapter log-level to FINE for exception stack trace.

Cause:

Database access error

Solution:

Check is database server is up and running

RAR8031 Exception while pinging tableName : {0}.

Cause:

Database access error

Solution:

Check is database server is up and running

RAR8033 Deletion of pool failed. PoolName not specified.

Cause:

PoolName specified could be null

RAR8034 Exception while reconfiguring pool [ {0} ] : , {1}

Cause:

Unable to reconfigure connection pool.

Solution:

Review the new modifications to pool properties and attributes

RAR8035 Exception while creating jdbc connection pool [ {0} ] : , {1}

Cause:

unable to create jdbc connection pool

Solution:

check whether database is up and running, use ping-connection-pool to \

RAR8036 Exception while redeploying jdbc-connection-pool [ {0} ], {1}

Cause:

unable to redeploy jdbc connection pool

Solution:

check whether database is up and running, use ping-connection-pool to \

RAR8037 exception while getting transaction-support for RAR [ {0} ] , {1}

Cause:

Unable to get connector descriptor

Solution:

check whether rar is property deployed, ra.xml or annotations equivalent are correct.

RAR8038 unable to load the resource-adapter [ {0} ], {1}

Cause:

Possible exception while bootstrapping RAR or validating RAR

Solution:

Check server.log for exact cause of failure which may be due to one of the steps in \

RAR8039 unable to unload the resource-adapter [ {0} ], {1}

Cause:

Possible exception while destroying pools

Cause:

Possible exception while deactivating end-points

Cause:

Possible exception while stopping RA

Solution:

Check server.log for exact cause of failure which may be due failure while destroying pools

Solution:

Check server.log for exact cause of failure which may be due failure in de-activating end-points

Solution:

Check server.log for exact cause of failure which may be due failure while stopping RA

RAR8040 Unable to delete resource-adapter-config for RAR [ {0} ]

Cause:

Possible exception while deleting resource-adapter-config

Solution:

Check server.log for exact cause of failure that happened while deleting resource-adapter-config

RAR8041 Unable to delete resource-adapter-config for RAR [ {0} ], {1}

Cause:

Possible exception while deleting resource-adapter-config

Solution:

Check the exception message while deleting the configuration of resource-adapter-config

RAR8042 Unable to delete work-security-map(s) for RAR [ {0} ]

Cause:

Possible exception while deleting work-security-map configuration

Solution:

Check server.log for exact cause of failure that happened while deleting work-security-map configuration

RAR8043 Unable to delete work-security-map(s) for RAR [ {0} ], {1}

Cause:

Possible exception while deleting work-security-map configuration

Solution:

Check the exception message while deleting the configuration of work-security-map

RAR8044 Unable to admin-object-resource(s) for RAR [ {0} ]

Cause:

Possible exception while deleting admin-object-resource configuration

Solution:

Check server.log for exact cause of failure that happened while deleting admin-object-resource configuration

RAR8045 Unable to delete admin-object-resource(s) for RAR [ {0} ], {1}

Cause:

Possible exception while deleting admin-object-resource configuration

Solution:

Check the exception message while deleting the configuration of admin-object-resource

RAR8046 Unable to connector-resource(s) for RAR [ {0} ]

Cause:

Possible exception while deleting connector-resource configuration

Solution:

Check server.log for exact cause of failure that happened while deleting connector-resource configuration

RAR8047 Unable to delete connector-resource(s) for RAR [ {0} ], {1}

Cause:

Possible exception while deleting connector-resource configuration

Solution:

Check the exception message while deleting the configuration of connector-resource

RAR8048 Unable to connector-connection-pool(s) for RAR [ {0} ]

Cause:

Possible exception while deleting connector-connection-pool configuration

Solution:

Check server.log for exact cause of failure that happened while deleting connector-connection-pool configuration

RAR8049 Unable to delete connector-connection-pool(s) for RAR [ {0} ], {1}

Cause:

Possible exception while deleting connector-connection-pool configuration

Solution:

Check the exception message while deleting the configuration of connector-connection-pool

RAR8050 Exception while processing xml files for detecting bean-validation-mapping\

Cause:

Possible invalid entries in mapping xml files

Solution:

Check whether all the constraints defined in the validation mapping xml files are valid

RAR8051 unable to stop resource adapter [ {0} ] due to exception {1}, set FINEST log level\

Cause:

unable to destroy pools or stop RA or deactivating end-points

Solution:

Check server.log for exceptions due to failure in destroying pools or stopping RA or deactivating end-points

RAR8052 RA [ {0} ] stop timeout occured, {1}

Cause:

unable to stop RA in specified time, timeout occurred

Solution:

Check whether ra.destroy() has happened successfully or any exceptions in server.log

RAR8053 RA [ {0} ] stop failed, {1}

Cause:

RA stop failed

Solution:

Check server.log for any exceptions

RAR8054 Exception while creating an unpooled [test] connection for pool [ {0} ], {1}

Cause:

Unable to create a new connection

Solution:

Check whether connection parameters are correct

RAR8055 Exception while getting connector descriptor for RAR [ {0} ], {1}

Cause:

Possible exception while parsing ra.xml or RA is not deployed

Solution:

Check whether RA name is correct, RA is already deployed, server.log for exceptions while parsing ra.xml

RAR8056 unable to load Connection Pool [ {0} ], {1}

Cause:

Exception while loading RAR or resource-adapter-config or connection pool

Solution:

Check the exception, server.log for status of RAR, resource-adapter-config, exceptions while loading connection pool

RAR8057 one or more resources of resource-adapter [ {0} ] exist, use '--cascade=true' to delete them during undeploy

Cause:

resources of RAR exist during RAR undeployment

Solution:

Check whether resources of RAR exist, delete them before RAR undeployment or use '--casecade=true' \

RAR8058 Unsupported work context [ {0} ] for RAR [ {1} ]

Cause:

Required work context is not supported by the container

Solution:

Check the application server documentation for supported work context types in addition to\

RAR8059 Exception while trying to find properties of class [ {0} ], set log-level to\

Cause:

Possible exception due to access permission or class is not available

Solution:

Check whether the class is available to the server, appropriate permissions are provided to load the class

RAR8060 Unable to lookup pool [ {0} ], {1}

Cause:

Possible exception during pool initialization

Solution:

Check any exceptions in server.log related to pool creation

RAR8061 failed to load resource-adapter-config or RA [ {0} ], {1}

Cause:

Unable to load RA or resource-adapter-config

Solution:

Possible failure to load RA or resource-adapter-config. Check server.log for exceptions

RAR8062 failed to load resources for RA[ {0} ], {1}

Cause:

Unable to load resources

Solution:

Possible failure to load resources. Check server.log for exceptions

RAR8502 Error creating ActivationSpec : {0} , set FINEST log level to get complete\

Cause:

Error while creating activation-spec object

Solution:

Check whether activation configuration is correct

RAR8503 Exception while creating ActivationSpec and getting inbound resources for recovery

Cause:

Possible exception while creating instance of ActivationSpec

Cause:

Possible exception while acquiring inbound resource for recovery

Solution:

Check the server.log for ActivationSpec instantiation related exceptions

Solution:

Check the server.log for inbound XA Resource acquisition related exceptions

RAR8504 Exception during inbound recovery

Cause:

Possible exception while creating instance of ActivationSpec

Cause:

Possible exception while acquiring inbound resource for recovery

Cause:

Possible exception while bootstrapping RAR

Solution:

Check the server.log for ActivationSpec instantiation related exceptions

Solution:

Check the server.log for inbound XA Resource acquisition related exceptions

Solution:

Check the server.log for RAR bootstrap related exceptions

RAR8701 Exception while extracting RAR [ {0} ] from archive : {1}

Cause:

RAR is not available in the bundle

Solution:

check whether the RAR is bundled in the archive

RAR8702 Port Number provided is not a number [ {0} ] : {1}

Cause:

Not a number provided for the property 'port'

Solution:

Provide a valid number for the property 'port'

RAR8703 failed to create libraries classloader

Cause:

Failed to create libraries classloader due to insufficient security privileges

Solution:

Check whether sufficient privilege is provided to create libraries classloader

RAR8704 failed to create connector classloader

Cause:

Failed to create connector classloader due to insufficient security privileges

Solution:

Check whether sufficient privilege is provided to create connector classloader

RAR9000 Custom validation detected invalid connection. Executing the isValid() of {0} class failed. Set resource-adapter log-level to FINE for exception stack trace.

Cause:

The Connection object is now invalid due to database restart

Cause:

The connection object is now invalid since the database is not up and running

Cause:

The JDBC driver cannot execute the statement due to internal error

Solution:

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

Solution:

Check the server log and please contact Sun Microsystems with the complete error log

RAR9001 Custom validation class name is invalid

Cause:

Custom validation class name is invalid as it does not implement interface org.glassfish.jdbc.api.ConnectionValidation

Cause:

Custom validation class name could not be loaded

Cause:

Custom validation class name is not in the classpath.

RAR9002 Exception while getting Proxied Connection during SQL tracing : {0}

Cause:

Connection object could be null

Cause:

Initialization provoked by method could have failed.

Cause:

Underlying method inaccessible.

RAR9003 Sql tracing : ClassNotFoundException while trying to load class : {0}

Cause:

Sql trace listener class name is not in the classpath.

RAR9004 Exception while introspecting SQL trace listeners : {0}

Cause:

Constructor of the sql trace listener provided does not have enough access.

Cause:

Sql trace listener does not implement org.glassfish.api.jdbc.SQLTraceListener.

Cause:

Error while instantiating sql trace listener class provided.

RAR9005 Error while executing Init SQL : {0}

Cause:

Database access error

Solution:

Check is database server is up and running

RAR9601 Unable to undeploy resource : {0}. Following exception occurred : {1}

Cause:

Error while creating ManagedConnectionFactory.

Cause:

Unable to unbind resource from JNDI.

Solution:

Resource adapter is bundled properly.

Solution:

Check whether connection pool configuration has correct properties for MCF.

Solution:

Check whether the resource adapter require security permissions to load the classes. Some adapters require getClassLoader() permission.

RAR9604 Exception while pinging pool during creation for pool {0}. Following exception occurred {1}

Cause:

The specified jdbc connection pool is unusable.

RAR9605 Ping pool during creation failed for pool : {0} . Pool has been created successfully but ping failed.

Cause:

There could be some erroneous values specified in jdbc connection pool configuration.

Cause:

Caused by unsupported/incorrect values for database connectivity properties.

SEC

SEC1000 Caught exception.

Cause:

A Security Exception has been thrown

Solution:

A Security Exception has been thrown

SEC1003 Could not override SecurityManager.

Cause:

Could not override SecurityManager.

Solution:

Could not override SecurityManager.

SEC1102 Incomplete configuration, login module not specified.

Cause:

Error during SolarisRealm initialization. LoginModule not specified

Solution:

Please provide the jaas-context in the SolarisRealm configuration

SEC1103 No AuthenticationHandler available for this realm.

Cause:

The Realm configured is not an instance of CertificateRealm, Certificate authentication requires certificate realm.

Cause:

No AuthenticationHandler available for this realm.

Solution:

Please check if the realm class is an instance of CertificateRealm

Solution:

Check of the Realm has been configured correctly. This is the base class method that has to be overridden

SEC1104 Error while obtaining private subject credentials.

Cause:

Private Credentials of Subject not available

Solution:

Please check if the private credentials are available

SEC1105 A PasswordCredential was required but not provided.

Cause:

PasswordCredential was required, but not supplied.

Solution:

Please check if the password is provided

SEC1106 Error during LDAP search with filter [{0}].

Cause:

Error during LDAP search

Solution:

Please check the LDAP configuration

SEC1109 Error reading file realm data.

Cause:

Error reading keyfile of filerealm

Solution:

Please check if the keyfile for the filerealm is configured correctly and is in place.

SEC1110 JAAS context requested from certificate realm. Configuration error is likely.

Cause:

JAAS context requested from certificate realm.

Solution:

Certificate Realm does not have a JAAS context. Please check the configuration

SEC1111 Cannot load group for JDBC realm user [{0}].

Cause:

Exception while obtaining groups for the users.

Solution:

Please check the JDBC configuration, encoding algorithm and the groups for the user.

SEC1112 Cannot validate user [{0}] for JDBC realm.

Cause:

Cannot obtain the password for the user provided.

Solution:

Please check the JDBC configuration, encoding algorithm and the password for the user.

SEC1130 Code does not have permission to invoke programmatic login mechanism.

Cause:

Code does not have permission to invoke programmatic login mechanism.

Solution:

Code does not have permission to invoke programmatic login mechanism.

SEC1140 Policy provider configuration overridden by property {0} with value {1}

Cause:

Policy Provider Configuration Property is overridden by property javax.security.jacc.auth.policy.provider.

Solution:

Policy Provider Configuration Property is overridden by property javax.security.jacc.auth.policy.provider.

SEC1141 Requested jacc-provider [{0}] is not configured in domain.xml.

Cause:

JaccProvider class not found for name defined.

Solution:

Please check if the name of the Jacc provider is defined correctly.

SEC1142 Error while reading policy-provider in domain.xml.

Cause:

Error while reading policy-provider in domain.xml.

Solution:

Please check if the policy provider defined is correct.

SEC1145 No policy provider defined. Will use the default JDK Policy implementation.

Cause:

No policy provider defined. Will use the default JDK Policy implementation.

Solution:

No policy provider defined. Will use the default JDK Policy implementation.

SEC1146 Policy configuration factory overridden by property {0} with value {1}

Cause:

Policy Configuration Factory overridden

Solution:

Please check if the system property javax.security.jacc.PolicyConfigurationFactory.provider has not been set.

SEC1147 Policy configuration factory not defined.

Cause:

Policy Configuration Factory not defined

Solution:

Please check if the Policy Configuration Factory has been defined.

SEC1203 GFAuthConfigFactory unable to load Provider: {0}, reason: {1}

Cause:

Error while loading ConfigProvider.

Solution:

Please check if the configprovider has been configured correctly.

SEC1204 GFAuthConfigFactory loader failure

Cause:

Error while loading the persisted entries of GFAuthConfigFactory

Solution:

Error while loading the persisted entries of GFAuthConfigFactory

SEC1205 Cannot write to file {0}. Updated provider list will not be persisted.

Cause:

Cannot write to file. Updated provider list will not be persisted.

Solution:

Cannot write to file. Updated provider list will not be persisted.

SEC1206 Could not persist updated provider list due to {0}. Will use default providers when reloaded.

Cause:

Could not persist updated provider list due to {0}. Will use default providers when reloaded.

Solution:

Could not persist updated provider list due to {0}. Will use default providers when reloaded.

SEC1207 Could not read auth configuration file due to {0} Will use default providers.

Cause:

Could not read auth configuration file. The default provider will be used.

Solution:

Could not read auth configuration file. The default provider will be used.

SEC5028 Exception loading keystore

Cause:

There was an exception while loading keystore

Solution:

Please check the if the file path and password are correct

SEC5029 Exception storing keystore

Cause:

There was an exception while storing the keystore

Solution:

Please check the if the file path and password are correct

SEC5030 Exception loading security provider

Cause:

There was an exception while loading the security provider

Solution:

Please check the if the Provider classname is correct.

SEC5031 Exception getting security provider name

Cause:

There was an exception while obtaining the name of the Provider.

Solution:

Please check the if the Provider name is correct.

SEC5036 Exception in getting security context

Cause:

There was an exception obtaining the default security context.

Solution:

There was an exception obtaining the default security context.

SEC5038 Default user login exception.

Cause:

There was an exception while authenticating the default caller principal

Solution:

There was an exception while authenticating the default caller principal

SEC5039 Exception entering name and password for security

Cause:

An exception occurred while processing username and password for security

Solution:

An exception occurred while processing username and password for security

SEC5043 Exception in security accesscontroller action

Cause:

Exception while extracting username and realm from the subject post login

Solution:

Exception while extracting username and realm from the subject post login

SEC5048 doAsPrivileged AuthPermission required to set SecurityContext.

Cause:

AuthPermission required to set SecurityContext,

Solution:

AuthPermission required to set SecurityContext,

SEC5049 Unexpected exception while attempting to set SecurityContext.

Cause:

There was an unexpected exception while setting the security context

Solution:

There was an unexpected exception while setting the security context

SEC5051 Cannot setRemoteHost.

Cause:

null Subject used in SecurityContext construction.

Solution:

null Subject used in SecurityContext construction.

SEC5054 Certificate has expired: {0}

Cause:

Certificate expired

Solution:

Please check the validity date of the certificate

SEC5055 Role mapping conflicts found in application {0}. Some roles may not be mapped.

Cause:

Principal-Group-Role Mapping conflicts in the application

Solution:

Please check if the roles have been mapped to the same principals/groups consistently in all the descriptors.

WEB

WEB0121 Enabled session ID reuse for web module [{0}] deployed on virtual server [{1}]

Cause:

Use caution before enabling this feature, because it puts the burden of creating unpredictable session ids on the client, which may not be trusted

Solution:

Check your sun-web.xml for a property with name reuseSessionID, and set it to false if you do not want to enable this feature

WEB0126 Failed to parse sun-web.xml singleThreadedServletPoolSize property value ({0}) of web module deployed at {1}, using default ({2})

Cause:

The value of the singleThreadedServletPoolSize property in the sun-web.xml deployment descriptor cannot be parsed as an Integer

Solution:

Make sure to specify an Integer as the value of the singleThreadedServletPoolSize property

WEB0137 Invalid redirect property value [{0}] for virtual server [{1}]: More than one [{2}] component

Cause:

The value of the redirect property of the virtual server specifies more than one component of the same name

Solution:

Check the redirect property of the virtual server and make sure it does not specify more than one component of the same name

WEB0138 Invalid redirect property value [{0}] for virtual server [{1}]: Missing from component

Cause:

The redirect property value of the virtual server is missing a from component

Solution:

Make sure to specify a from component for the redirect property of the virtual server

WEB0139 Invalid redirect property value [{0}] for virtual server [{1}]: Missing url or url-prefix component

Cause:

The redirect property value of the virtual server is missing an url or url-prefix component

Solution:

Make sure that the value of the redirect property of the virtual server specifies an url or url-prefix component, but not both

WEB0140 Invalid redirect property value [{0}] for virtual server [{1}]: Both url and url-prefix specified

Cause:

The value of the redirect property of the virtual server specifies both an url and an url-prefix component

Solution:

Make sure that the value of the redirect property of the virtual server specifies an url or url-prefix component, but not both

WEB0141 Invalid redirect property value [{0}] for virtual server [{1}]: escape must be equal to yes or no

Cause:

The value of the escape component is invalid

Solution:

Make sure to specify either yes or no (case-insensitive) as the value of the escape component for the redirect property of the virtual server

WEB0142 Invalid send-error property value [{0}] for virtual server [{1}]: More than one [{2}] component

Cause:

The value of the send-error property of the virtual server specifies more than component of the same name

Solution:

Check the send-error property of the virtual server and make sure it does not specify more than one component of the same name

WEB0143 Invalid send-error property value [{0}] for virtual server [{1}]: Missing path component

Cause:

The value of the send-error property of the virtual server is missing a path component

Solution:

Make sure to specify a path component for the send-error property of the virtual server

WEB0145 Unable to deploy web module [{0}] at root context of virtual server [{1}], because this virtual server declares a default-web-module

Cause:

There can be at most one web module occupying a virtual server's root context at any time

Solution:

You must first undeclare a virtual server's default-web-module in order to be able to deploy to the virtual server's root context

WEB0147 Unable to add listener of type [{0}] to virtual server [{1}]

Cause:

Declared listener is neither of type org.apache.catalina.ContainerListener nor org.apache.catalina.LifecycleListener

Solution:

Make sure the declared listener implements org.apache.catalina.ContainerListener or org.apache.catalina.LifecycleListener

WEB0152 Unable to load web module [{0}] at context root [{1}], because it is not correctly encoded

Cause:

The specified context root contains one or more '%' characters and therefore is assumed to have been encoded using some multibyte encoding scheme, but it fails to be decoded using UTF-8 which is assumed as the default multibyte encoding

Solution:

When deploying to a multibyte context root, make sure it is encoded according to UTF-8

WEB0203 Error looking up the configuration information of the default-web-module [{0}] for virtual server [{1}]

Cause:

The web module that has been designated as the default-web-module may not exist

Solution:

Make sure that the web module that has been designated as the default-web-module for the virtual server has been deployed

WEB0207 Invalid sso-cookie-secure configuration [{0}] for virtual server [{1}]

Cause:

The sso-cookie-secure attribute of the virtual server has an unsupported value

Solution:

Make sure the value of the sso-cookie-secure attribute of the virtual server is set to 'true', 'false', or 'dynamic'

WEB0305 Unable to parse proxy port component ({0}) of server-name attribute of network-listener {1}

Cause:

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 The host name {0} is shared by virtual servers {1} and {2}, which are both associated with the same HTTP listener ({3})

Cause:

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

WEB0324 Missing end delimiter in access log pattern: {0}

Cause:

The given access log pattern is missing a trailing '%'

Solution:

Make sure that any access log pattern element is bounded by a leading and trailing '%'

WEB0354 Unable to parse max-history-files access log configuration [{0}]

Cause:

max-history-files not specified as an integer

Solution:

Make sure the value of the com.sun.enterprise.server.logging.max_history_files system property or max-history-files attribute of access-log is given as an integer

WEB0356 Web module [{0}] not loaded to any virtual servers

Cause:

No virtual servers specified on which to load the web module

WEB0358 Invalid attribute [{0}] in thread-pool configuration

Cause:

The specified attribute value cannot be parsed as an Integer

Solution:

Make sure to specify an Integer as the attribute value

WEB0400 Unable to set request encoding [{0}] determined from sun-web.xml deployment descriptor of web application [{1}]

Cause:

The sun-web.xml deployment descriptor specifies an invalid request encoding

Solution:

Check the form-hint-field, default-charset, and locale-charset-map configuration in the sun-web.xml deployment descriptor and make sure it specifies a valid request encoding

WEB0500 default-locale attribute of locale-charset-info element is being ignored

Cause:

This attribute has been deprecated

Solution:

Use default-charset attribute of parameter-encoding element instead

WEB0509 Unable to add valve to web module [{0}]

Cause:

Valve declaration is missing a name attribute

Solution:

You must specify a name attribute with your valve declaration

WEB0510 Unable to add valve with name [{0}] to web module [{1}]

Cause:

Valve declaration is missing a class-name attribute

Solution:

You must specify a class-name attribute with your valve declaration

WEB0512 Object of type {0} is not a valve

Cause:

Declared custom valve does not implement any of the required valve interfaces

Solution:

Make sure the declared custom valve implements org.apache.catalina.Valve or org.glassfish.web.valve.GlassFishValve

WEB0513 Unable to add listener of type [{0}] to web module [{1}]

Cause:

Declared listener does not implement any of the required interfaces

Solution:

Make sure the declared listener implements org.apache.catalina.ContainerListener, org.apache.catalina.LifecycleListener, or org.apache.catalina.InstanceListener

WEB0516 Unable to save sessions for web module [{0}] during redeployment

Cause:

An HTTP session that was supposed to survive the redeployment of the web module failed to be serialized. This kind of error can occur only if the keepSessions property of the redeploy command has been set to true

Solution:

Make sure that all HTTP sessions of the web module are serializable, or disable the feature that preserves HTTP sessions across redeployments

WEB0517 Unable to restore sessions for web module [{0}] from previous deployment

Cause:

An HTTP session that was supposed to survive the redeployment of the web module failed to be restored (deserialized). This can happen if an application class that was used as a session attribute has changed incompatibly

Solution:

Make sure that any application classes that are being used as session attributes change only in a compatible way during redeployments

WEB9002 Illegal value ([{0}]) for scope attribute of cache tag

Cause:

Only 'request', 'session', and 'application' scopes are supported for caching purposes

Solution:

If the scope attribute of the cache tag is specified, make sure its value is set to 'request', 'session', or 'application'

WEB9031 WebappClassLoader unable to load resource [{0}], because it has not yet been started, or was already stopped

Cause:

This problem usually indicates that the classloader of a web application was cached, and an attempt is being made to have it load resources even though the web application with which the classloader used to be associated has already been undeployed

Solution:

Make sure that the classloader associated with your web application is not cached and used beyond the lifetime of your web application

WEB9032 Class {0} has unsupported major or minor version numbers, which are greater than those found in the Java Runtime Environment version {1}

Cause:

This error indicates that a web application contains class files that were compiled with a version of the Java programming language compiler that is greater than the version of the Java Runtime Environment with which the GlassFish application server process was launched

Solution:

Make sure that the classes of your web application have been compiled with a version of the Java programming language compiler that is less than or equal to the version of the Java Runtime Environment with which the GlassFish application server process was launched