GlassFish Wiki : Rar

Contents Previous Next

RAR Messages

----RAR5003
Error loading J2EE resource file

Cause:

TBD

Solution:

TBD

----RAR5004
JDBC driver threw an exception while recovery.

Cause:

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

Solution:

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

----RAR5005
The XA resource has been deleted before attempting recovery

Cause:

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

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

Solution:

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

----RAR5007
Exception while creating persistent manager resource.

Solution:

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

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

Cause:

The Naming provider is not up.

Solution:

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

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

Solution:

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

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

Solution:

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

----RAR5011
Could not create Initial Context.

Solution:

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

----RAR5012
Could not create Initial context factory.

Solution:

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

----RAR5013
Error in installing connection factories

Cause:

TBD

Solution:

TBD

----RAR5014
Cannot load class 0.

Cause:

TBD

Solution:

TBD

----RAR5015
Classpath is not properly set in domain.xml

Cause:

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

Solution:

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

----RAR5016
Error accessing configuration file.

Cause:

TBD

Solution:

TBD

----RAR5017
Cannot locate connection descriptor by name

Cause:

TBD

Solution:

TBD

----RAR5018
Cannot create connection factory

Cause:

TBD

Solution:

TBD

----RAR5019
Unexpected exception in creating new file

Cause:

TBD

Solution:

TBD

----RAR5020
Could not configure persistent manager resource properly.

Solution:

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

----RAR5021
Error in installing resource adapters

Cause:

TBD

Solution:

TBD

----RAR5022
Error in binding to JNDI namespace

Cause:

TBD

Solution:

TBD

----RAR5023
Error removing connection factory

Cause:

TBD

Solution:

TBD

----RAR5024
Error adding J2EE resource

Cause:

TBD

Solution:

TBD

----RAR5025
Error removing J2EE resource

Cause:

TBD

Solution:

TBD

----RAR5026
Failed to complete transaction.Error Message: 0.

Cause:

TBD

Solution:

TBD

----RAR5027
Unexpected exception in resource pooling

Cause:

TBD

Solution:

TBD

----RAR5029
Unexpected exception while registering component

Cause:

TBD

Solution:

TBD

----RAR5030
Unexpected exception while registering synchronization

Cause:

TBD

Solution:

TBD

----RAR5031
System Exception

Cause:

TBD

Solution:

TBD

----RAR5032
Unexpected exception while returning resource to pool

Cause:

TBD

Solution:

TBD

----RAR5033
ASSERT FAILED!!!

Cause:

TBD

Solution:

TBD

----RAR5034
Failed to resize pools

Cause:

TBD

Solution:

TBD

----RAR5035
Error while closing the physical connection.

Error while destroying the connector managed connection.

Solution:

Examine the exception stack trace for details.

----RAR5036
Resource reference is not defined for JNDI name 0

Cause:

TBD

Solution:

TBD

----RAR5037
Username/password not specified for resource reference 0. Defaulting to one in the pool.

Cause:

TBD

Solution:

TBD

----RAR5038
Could not create a physical connection.

Solution:

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

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

Cause:

The XA resource is not properly referenced because:

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

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

Solution:

----RAR5043
Exception while creating persistent manager resource.

Solution:

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

----RAR5044
Could not configure persistent manager resource properly.

Solution:

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

Cause:

The Naming provider is not up

Solution:

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

----RAR5046
Classpath is not properly set in domain.xml

Cause:

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

Solution:

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

----RAR5047
Could not create Initial Context.

Solution:

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

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

Cause:

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

----RAR5051
Jdbc pool monitoring bean registration failure

Cause:

TBD

Solution:

TBD

----RAR5052
Failed to look up connection pool resource name

Cause:

TBD

Solution:

TBD

----RAR5053
underlying connection not valid

Cause:

TBD

Solution:

TBD

----RAR5055
Missing parameter in properties file 0.

Cause:

TBD

Solution:

TBD

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

Solution:

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

----RAR5059
Binding JDBC DataSource Name: {0}, Pool Name: {1}

Cause:

TBD

Solution:

TBD

----RAR5060
Install JDBC Datasources ...

Cause:

TBD

Solution:

TBD

----RAR5061
Exception caught and ignored: {0}

Cause:

TBD

Solution:

TBD

----RAR5062
Exception caught while getting Local Transaction

Cause:

TBD

Solution:

TBD

----RAR5062
Exception while closing connection

Cause:

TBD

Solution:

TBD

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

Solution:

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

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

Solution:

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

----RAR5066
Exception while getting pooled connection.

Cause:

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

----RAR5067
Exception while getting XA Connection: {0}

Cause:

TBD

Solution:

TBD

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

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

Solution:

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

----RAR5069
The Connection object is now invalid due to database restart

Cause:

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

Solution:

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

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

Cause:

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

Solution:

----RAR5071
Exception creating CciInteraction object

Cause:

TBD

Solution:

TBD

----RAR5072
Exception while clearing warnings from Statement object

Cause:

TBD

Solution:

TBD

----RAR5073
Exception while getting warnings from Statement object

Cause:

TBD

Solution:

TBD

----RAR5074
The Connection object is now invalid due to database restart

Cause:

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

Solution:

----RAR5075
Exception while setting up Statement according to Spec

Cause:

TBD

Solution:

TBD

----RAR5076
Exception while preparing statement

Cause:

TBD

Solution:

TBD

----RAR5077
Exception while closing statement

Cause:

TBD

Solution:

TBD

----RAR5078
Exception while beginning local transaction

Cause:

TBD

Solution:

TBD

----RAR5079
Exception while commiting local transaction

Cause:

TBD

Solution:

TBD

----RAR5080
Exception while commiting xa transaction

Cause:

TBD

Solution:

TBD

----RAR5081
Exception while rolling back local transaction

Cause:

TBD

Solution:

TBD

----RAR5082
Exception while creating CciManagedConnection

Cause:

TBD

Solution:

TBD

----RAR5083
Exception while destroying physical connection

Cause:

TBD

Solution:

TBD

----RAR5084
Exception while creating physical connection

Cause:

TBD

Solution:

TBD

----RAR5085
Exception while getting XA resource

Cause:

TBD

Solution:

TBD

----RAR5086
Exception creating CciManagedConnectionMetaData

Cause:

TBD

Solution:

TBD

----RAR5087
The Connection object is now invalid due to database restart

Cause:

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

Solution:

----RAR5088
Exception while checking if ResultSet can detect deletes

Cause:

TBD

Solution:

TBD

----RAR5089
Exception while checking if ResultSet can detect updates

Cause:

TBD

Solution:

TBD

----RAR5090
Exception while checking if ResultSet can detect other deletes

Cause:

TBD

Solution:

TBD

----RAR5091
Exception while checking if ResultSet can detect inserts

Cause:

TBD

Solution:

TBD

----RAR5092
Exception while checking if ResultSet can detect other updates

Cause:

TBD

Solution:

TBD

----RAR5093
Exception while checking if ResultSet can detect own updates

Cause:

TBD

Solution:

TBD

----RAR5094
Exception while checking if ResultSet can detect other inserts

Cause:

TBD

Solution:

TBD

----RAR5095
Exception while checking if ResultSet can detect own inserts

Cause:

TBD

Solution:

TBD

----RAR5096
Exception while checking if ResultSet can detect own deletes

Cause:

TBD

Solution:

TBD

----RAR5097
Exception while checking if RA supports concurrency in combo with give RS

Cause:

TBD

Solution:

TBD

----RAR5098
Exception while checking if RA supports a type of RS

Cause:

TBD

Solution:

TBD

----RAR5099
Classpath is not properly set in domain.xml

Cause:

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

Solution:

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

----RAR5100
Classpath is not properly set in domain.xml

Cause:

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

Solution:

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

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

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

Solution:

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

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

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

Solution:

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

----RAR5103
Error configuring the DataSource object.

Cause:

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

Solution:

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

----RAR5104
Error configuring the DataSource object.

Cause:

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

Solution:

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

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

Solution:

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

----RAR5106
The database connection is invalid.

Cause:

The cause can be either:

The database has been shutdown or restarted.

The network connection to the database has been lost.

Solution:

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

----RAR5107
The database connection is invalid.

Cause:

The cause can be either:

The database has been shutdown or restarted.

The network connection to the database has been lost.

Solution:

----RAR5108
The database connection is invalid.

Cause:

The cause can be either

The database has been shutdown or restarted.

The network connection to the database has been lost.

Solution:

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

Solution:

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

----RAR5110
The URL specified is incorrect.

The database server is not up and running.

Solution:

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

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

Solution:

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

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

Solution:

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

----RAR5113
Error creating a connection from the supplied information.

Cause:

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

Solution:

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

----RAR5114
Error creating a connection from the supplied info.

Cause:

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

Solution:

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

----RAR5115
Error cleaning up handles associated with this ManagedConnection

Cause:

TBD

Solution:

TBD

----RAR5116
Error creating a connection from the supplied info.

Cause:

Solution:

----RAR5117
Error while obtaining a connection from the pool.

Solution:

Check your connection pool configuration.

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

Solution:

Check whether the resource adapter has any specific security requirements.

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

Solution:

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

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

Solution:

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

----RAR6003
Could not access class: {0}

Cause:

TBD

Solution:

TBD

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

Solution:

Check whether the resource adapter has any specific security requirements.

----RAR6005
Error while creating ManagedConnectionFactory.

Solution:

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

----RAR6006
Failed to get ResourcesUtil object: {0}

Cause:

TBD

Solution:

TBD

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

Solution:

Check whether the resource adapter configuration is proper.

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

Solution:

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

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

Solution:

Check whether the cascade option of undeploy is false.

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

Solution:

Check whether a previous resource adapter deployment is still available.

----RAR6011
Failed to obtain the classloader: {0}

Cause:

TBD

Solution:

TBD

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

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

----RAR6014
Incomplete or erroneous resource adapter deployment.

Solution:

Check whether the RA deployment is proper and complete.

----RAR6015
Connection pool is not created properly.

Solution:

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

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

Solution:

Check whether the deployment of the resource adapter is complete.

----RAR6017
Incomplete or erroneous connection pool creation.

Solution:

Check whether connection pool is created and is proper.

----RAR6018
Failed to add MCF to connector registry: {0}

Cause:

TBD

Solution:

TBD

----RAR6019
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}

Cause:

TBD

Solution:

TBD

----RAR6021
Error while creating ManagedConnectionFactory.

Solution:

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

----RAR6022
NullPointerException while creating ManagedConnectionFactory.

Solution:

Check whether resource adapter throws null pointer exception.

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

----RAR6024
Failed to bind connector resource in JNDI: {0}

Cause:

TBD

Solution:

TBD

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

Solution:

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

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

Solution:

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

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

Cause:

TBD

Solution:

TBD

----RAR6028
Resource Adapter does not contain resource adapter JavaBean.

Solution:

Make sure that the resource adapter is 1.5 compliant.

----RAR6029
Failed to delete admin object from jndi: {0}

Cause:

TBD

Solution:

TBD

----RAR6030
MCF cleanup in connector runtime failed.

Solution:

Check whether connection pool has already been deleted.

----RAR6031
Failed to unbind connectionPool from jndi: {0}

Cause:

TBD

Solution:

TBD

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

Solution:

Check whether the connection pool is created.

----RAR6033
Wrong connector connection pool entry in the domain.xml. No corresponding resource adapter
deployed. Resource Adapter Name:

Cause:

TBD

Solution:

TBD

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

Solution:

Check whether the resource adapter is deployed.

----RAR6035
Could not start the resource adapter instance.

Solution:

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

----RAR6036
Resource Adapter throws exception during ManagedConnectionFactory.setResourceAdapter().

Solution:

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

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

Solution:

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

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

Cause:

TBD

Solution:

TBD

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

Solution:

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

----RAR7002
MQ Resource adapter upgradation started.

Cause:

TBD

Solution:

TBD

----RAR7003
MQ Resource adapter upgradation completed.

Cause:

TBD

Solution:

TBD

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

Solution:

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

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

Solution:

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

----RAR7006
ActivationSpec validation failed.

Solution:

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

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

Solution:

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

----RAR7008
Initialized monitoring registry and listeners

Cause:

TBD

Solution:

TBD

----RAR7009
Cannot set autocommit mode for physical connection

Cause:

TBD

Solution:

TBD

----RAR7010
Could not find the connection pool specified.

Solution:

Try the following:

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

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

----RAR7011
Unexpected exception determining whether resource is referenced.

Cause:

TBD

Solution:

TBD

----RAR7012
J2EE Connector 1.5 specification compliant Resource Adapter stop() status

Cause:

TBD

Solution:

TBD

----RAR7013
Resource Adapter stop() call successful

Cause:

TBD

Solution:

TBD

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

Solution:

Make sure that domain.xml is configured correctly.

----RAR7015
Cannot register pool from monitoring registry

Solution:

TBD

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

Cause:

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

Solution:

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

----RAR7093
Error while cleaning up ManagedConnection

Cause:

TBD

Solution:

TBD

----RAR7094
{0} shutdown successful.

Cause:

TBD

Solution:

TBD

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

Cause:

TBD

Solution:

TBD

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

Solution:

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

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

Solution:

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

----RAR7099
Cannot unregister pool from monitoring registry: {0}

Cause:

TBD

Solution:

TBD

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

Cause:

TBD

Solution:

TBD

----RAR7100
Physical destination {0} is autocreated by application server.

Cause:

TBD

Solution:

TBD

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

Cause:

TBD

Solution:

TBD

----RAR7103
The physical destination {0} is already created.

Cause:

TBD

Solution:

TBD

----RAR7104
Exception while stopping Derby:

Cause:

TBD

Solution:

TBD

----RAR7105
Derby Embedded Driver not found:

Cause:

TBD

Solution:

TBD

----RAR7106
Invalid property combination (LazyConnectionEnlistment-false, LazyConnectionAssociation-true) for pool: {0}

Cause:

TBD

Solution:

TBD

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

Cause:

TBD

Solution:

TBD

----RAR8001
Error in executing the method: {0}

Cause:

TBD

Solution:

TBD

Contents Previous Next