Chapter 11 RAR Error Messages

Previous Contents Next
Sun Java System Application Server 8.1 Enterprise Edition 2005Q1 Error Message Reference

Chapter 11
RAR Error Messages

This chapter describes messages for errors with a RAR prefix.

RAR5004

Message

Jdbc driver threw an exception while recovery.

Cause

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

Solutions/Workarounds

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

RAR5005

Message

The XA resource has been deleted before attempting recovery

Cause

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

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

Solutions/Workarounds

Check that the XA Resource and the pool it points to is still defined in domain.xml. Check that the XA Resource is present in the list of resource-refs in domain.xml. Check that the Database server is up and running. Check if the 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

Message

Exception while creating persistent manager resource.

Solutions/Workarounds

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

RAR5008

Message

Naming provider and port are not set in the initial context

Cause

The Naming provider is not up

Solutions/Workarounds

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

RAR5009

Message

Could not create an instance of factory-class.

Solutions/Workarounds

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

RAR5010

Message

External JNDI resource has a wrong factory-class configuration

Solutions/Workarounds

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

RAR5011

Message

Could not create Initial Context.

Solutions/Workarounds

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

RAR5012

Message

Could not create Initial context factory.

Solutions/Workarounds

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

RAR5015

Message

Classpath is not properly set in domain.xml

Cause

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

Solutions/Workarounds

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

RAR5020

Message

Could not configure persistent manager resource properly.

Solutions/Workarounds

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

RAR5035

Message

Error while closing the physical connection.

Error while destroying the connector managed connection.

Solutions/Workarounds

Examine the exception stack trace for details.

RAR5038

Message

Could not create a physical connection.

Solutions/Workarounds

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

RAR5042

Message

The XA resource has been deleted before attempting recovery

Cause

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

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

Solutions/Workarounds

Check that the XA Resource and the pool it points to is still defined in domain.xml. Check that the XA Resource is present in the list of resource-refs in domain.xml. Check that the Database server is up and running. Check if the 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

RAR5043

Message

Exception while creating persistent manager resource.

Solutions/Workarounds

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

RAR5044

Message

Could not configure persistent manager resource properly.

Solutions/Workarounds

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

RAR5045

Message

Naming provider and port are not set in the jndi provider's property file

Cause

The Naming provider is not up

Solutions/Workarounds

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

RAR5046

Message

Classpath is not properly set in domain.xml

Cause

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

Solutions/Workarounds

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

RAR5047

Message

Could not create Initial Context.

Solutions/Workarounds

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

RAR5048

Message

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

Cause

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

RAR5058

Message

Could not create physical connection during connection pool resizing.

Solutions/Workarounds

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

RAR5063

Message

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

Solutions/Workarounds

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

RAR5065

Message

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

Solutions/Workarounds

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

RAR5066

Message

Exception while getting pooled connection

Cause

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

RAR5068

Message

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

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

Solutions/Workarounds

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

RAR5069

Message

The Connection object is now invalid due to database restart

Cause

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

Solutions/Workarounds

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

RAR5070

Message

The Connection object is now invalid due to database restart

Cause

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

Solutions/Workarounds

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

RAR5074

Message

The Connection object is now invalid due to database restart

Cause

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

Solutions/Workarounds

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

RAR5087

Message

The Connection object is now invalid due to database restart

Cause

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

Solutions/Workarounds

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

RAR5099

Message

Classpath is not properly set in domain.xml

Cause

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

Solutions/Workarounds

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

RAR5100

Message

Classpath is not properly set in domain.xml

Cause

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

Solution

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

RAR5101

Message

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

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

Solutions/Workarounds

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

RAR5102

Message

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

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

Solutions/Workarounds

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

RAR5103

Message

Error configuring the DataSource object

Cause

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

Solutions/Workarounds

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

RAR5104

Message

Error configuring the DataSource object

Cause

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

Solutions/Workarounds

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

RAR5105

Message

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

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

Solutions/Workarounds

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

RAR5106

Message

The database connection is invalid.

Cause

The database has been shutdown or restarted.

The network connection to the database has been lost.

Solutions/Workarounds

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. Check that the database is up and running and the network connection to the database is still alive.

RAR5107

Message

The database connection is invalid.

Cause

The database has been shutdown or restarted.

The network connection to the database has been lost.

Solutions/Workarounds

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. Check that the database is up and running and the network connection to the database is still alive.

RAR5108

Message

The database connection is invalid.

Cause

The database has been shutdown or restarted.

The network connection to the database has been lost.

Solutions/Workarounds

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. Check that the database is up and running and the network connection to the database is still alive.

RAR5109

Message

Jdbc driver has thrown an SQLException while setting the isolation level.

Solutions/Workarounds

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

RAR5110

Message

The URL specified is incorrect

The database server is not up and running

Solutions/Workarounds

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

RAR5111

Message

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

Solutions/Workarounds

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

RAR5112

Message

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

Solutions/Workarounds

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

RAR5113

Message

Error creating a connection from the supplied information.

Cause

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

Solutions/Workarounds

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

RAR5114

Message

Error creating a connection from the supplied info.

Cause

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

Solutions/Workarounds

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

RAR5116

Message

Error creating a connection from the supplied info.

Cause

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

Solutions/Workarounds

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

RAR5117

Message

Error while obtaining a connection from the pool.

Solutions/Workarounds

Check your connection pool configuration.

RAR6000

Message

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

Solutions/Workarounds

Check whether the resource adapter has any specific security requirements.

RAR6001

Message

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

Solutions/Workarounds

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

RAR6002

Message

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

Solutions/Workarounds

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

RAR6004

Message

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

Solutions/Workarounds

Check whether the resource adapter has any specific security requirements.

RAR6005

Message

Error while creating ManagedConnectionFactory.

Solutions/Workarounds

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

RAR6007

Message

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

Solutions/Workarounds

Check whether the resource adapter configuration is proper.

RAR6008

Message

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

Solutions/Workarounds

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

RAR6009

Message

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

Solutions/Workarounds

Check whether the cascade option of undeploy is false.

RAR6010

Message

Resource Adapter is already active in the connector runtime.

Solutions/Workarounds

Check whether a previous resource adapter deployment is still available.

RAR6012

Solutions/Workarounds

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

RAR6013

Solutions/Workarounds

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

RAR6014

Message

Incomplete or erroneous resource adapter deployment.

Solutions/Workarounds

Check whether the RA deployment is proper and complete.

RAR6015

Message

Connection pool is not created properly.

Solutions/Workarounds

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

RAR6016

Message

Resource Adapter is not yet initialized in the connector runtime.

Solutions/Workarounds

Check whether the deployment of the resource adapter is complete.

RAR6017

Message

Incomplete or erroneous connection pool creation.

Solutions/Workarounds

Check whether connection pool is created and is proper.

RAR6019

Message

Incomplete or erroneous resource adapter deployment.

Solutions/Workarounds

Check whether the RA deployment is proper and complete.

RAR6021

Message

Error while creating ManagedConnectionFactory.

Solutions/Workarounds

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

RAR6022

Message

NullPointerException while creating ManagedConnectionFactory.

Solutions/Workarounds

Check whether resource adapter throws null pointer exception.

RAR6023

Solutions/Workarounds

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

RAR6025

Message

Could not read the deployment descriptor of the resource adapter.

Solutions/Workarounds

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

RAR6026

Message

Could not parse the deployment descriptor of the resource adapter.

Solutions/Workarounds

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

RAR6028

Message

Resource Adapter does not contain resource adapter java bean.

Solutions/Workarounds

Make sure that the resource adapter is 1.5 compliant.

RAR6030

Message

MCF cleanup in connector runtime failed.

Solutions/Workarounds

Check whether connection pool has already been deleted.

RAR6032

Message

Connection Pool Name of the Resource configuration is wrong.

Solutions/Workarounds

Check whether the connection pool is created.

RAR6034

Message

Resource Adapter Name of the admin object configuration is wrong

Solutions/Workarounds

Check whether the resource adapter is deployed.

RAR6035

Message

Could not start the resource adapter instance.

Solutions/Workarounds

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

RAR6036

Message

Resource Adapter throws exception during ManagedConnectionFactory.setResourceAdapter()

Solutions/Workarounds

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

RAR6037

Message

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

Solutions/Workarounds

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

RAR7001

Message

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

Solutions/Workarounds

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

RAR7004

Message

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

Solutions/Workarounds

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

RAR7005

Message

Could not access the class loader specific to the MDB.

Solutions/Workarounds

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

RAR7006

Message

ActivationSpec validation failed.

Solutions/Workarounds

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

RAR7007

Message

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

Solutions/Workarounds

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

RAR7010

Message

Could not find the connection pool specified.

Solutions/Workarounds

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

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

RAR7014

Message

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

Solutions/Workarounds

Make sure that domain.xml is configured correctly.

RAR7092

Message

Wrong transaction-support connection pool attribute setting.

Cause

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

Solutions/Workarounds

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

RAR7096

Message

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

Solutions/Workarounds

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

RAR7097

Message

Error in finding a mutator method for the specified property

Solutions/Workarounds

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

Previous Contents Next

Part No: 819-0791. Copyright 2004-2005 Sun Microsystems, Inc. All rights reserved.