|
The Connector1.0 catalog contains messages in the range
BEA190000 - BEA199999. Messages in this catalog are part of the
weblogic.connector
Internationalization package and the weblogic.connector Localization package.
|
BEA-190000
|
Info: Initializing J2EE Connector Service
|
|
BEA-190001
|
Info: J2EE Connector Service initialized successfully
|
|
BEA-190002(retired)
|
Debug: < poolName > : msgText
|
Cause
| Debug output requested.
|
|
Action
| No Action Required.
|
|
|
BEA-190003(retired)
|
Info: J2EE Connector Service, Component license validation failed, ex.
|
Cause
| The license file does not indicate that the J2EE Connector feature is available.
|
|
Action
| Check or refresh the license file WebLogicLicense.xml and reboot the system.
|
|
|
BEA-190004
|
Warning: ConnectionFactory not found for jndiName jndiName.
|
Description
| Unable to locate the ConnectionFactory for a resource adapter with the name jndiName in the JNDI tree.
|
|
Cause
| This warning can occur upon viewing the JNDI tree for the managed server on the console. The other likely cause for this error is that the user has specified an incorrect JNDI name for the desired resource adapter or that the resource adapter is not deployed.
|
|
Action
| Ignore the warning if it occurs while viewing the JNDI tree of a managed server. Otherwise, check the deployed connectors in the console and verify the name used to access it.
|
|
|
BEA-190005
|
Error: An error occurred while creating a connection factory for ManagedConnectionFactory with jndiName jndiName.
|
Description
| The resource adapter threw a ResourceException when WebLogic Server tried to create a connection factory.
|
|
Cause
| The cause is unknown. Consult the resource adapter vendor documentation.
|
|
Action
| Examine the exception in the log for more information about how to correct the problem. You may need to refer to the resource adapter vendor documentation to determine an appropriate course of action.
|
|
|
BEA-190006(retired)
|
Error: An error occurred while granting a connection request.
|
|
BEA-190007(retired)
|
Error: An error occurred while obtaining a connection instance for transType resource adapter.
|
|
BEA-190008
|
Error: An error occurred while cleaning up or destroying the connection instance for transType resource adapter.
|
Description
| A ResourceException was thrown by the resource adapter when attempting to destroy() or cleanup() the ManagedConnection.
|
|
Cause
| This error occurs as the result of an attempt to call cleanup() or destroy() on a resource adapter managed connection. The resource adapter can throw a ResourceException if the operation fails. It can also throw an IllegalStateException if, for example, an attempt was made to cleanup a connection when a transaction was in progress. A ResourceAdapterInternalException may be thrown if an internal error condition is detected in the resource adapter.
|
|
Action
| Examine the log for the exact type of exception thrown. In the case of an IllegalStateException, you should report the error to BEA support. In the case of a ResourceAdapterInternalException, report the error the resource adapter vendor.
|
|
|
BEA-190009
|
Info: No ConnectionRequestInfo was provided for Application Managed Security Context.
|
|
BEA-190010
|
Info: Unable to determine resource principal for the container-managed security context.
|
Cause
| Improper security principal map configuration for resource adapter.
|
|
Action
| Check the resource adapter configuration.
|
|
|
BEA-190011(retired)
|
Info: Unable to locate context: java:/comp/env/wls-connector-resref.
|
Cause
| The client invoker does not have a proper res-ref entry in the client deployment descriptor, or an invalid JNDI lookup of ConnectionFactory occurred.
|
|
Action
| Check the client res-ref configuration.
|
|
|
BEA-190012
|
Info: Component using JNDIName: jndiName has security managed security.
|
|
BEA-190013
|
Error: An error occurred while processing context: java:/comp/env/wls-connector-resref.
|
Description
| Unable to locate the resource reference for the resource adapter from the application component information in the JNDI tree.
|
|
Cause
| This is an internal WebLogic Server error.
|
|
Action
| Report this error to BEA support.
|
|
|
BEA-190014(retired)
|
Info: Initializing connection pool for resource adapter poolName.
|
|
BEA-190016(retired)
|
Error: < poolName > Unknown error occurred while loading class className.
|
Cause
| The specified resource adapter class could not be loaded.
|
|
Action
| Check the resource adapter configuration and/or contents of resource adapter archive.
|
|
|
BEA-190017(retired)
|
Warning: < poolName > capacity-increment is less than 1.
|
Description
| < poolName > capacity-increment is less than 1. Setting capacity-increment since shrinking-enabled is true and initial-capacity is less than max-capacity.
|
|
Cause
| Incorrect configuration of resource adapter pool parameters.
|
|
Action
| Check the resource adapter configuration.
|
|
|
BEA-190018(retired)
|
Warning: < poolName > shrink-period-minutes is less than 1.
|
Description
| < poolName > shrink-period-minutes is less than 1. Setting shrink-period-minutes to 1 since shrinking-enabled is true and shrink-period-minutes is set.
|
|
Cause
| Incorrect configuration of resource adapter pool parameters.
|
|
Action
| Check the resource adapter configuration.
|
|
|
BEA-190019
|
Error: < poolName > An error occurred when opening the log file logFile for the resource adapter.
|
Description
| The log file specified for resource adapter logging could not be opened.
|
|
Cause
| The log file is either a directory rather than a regular file, or it could not be opened for some other reason.
|
|
Action
| Check the log-filename configuration parameter in weblogic-ra.xml.
|
|
|
BEA-190020
|
Error: < poolName > An error occurred while setting the log file to the resource adapter.
|
Description
| The resource adapter log file was opened successfully but a problem occurred when setting it to the ManagedConnectionFactory object of the resource adapter.
|
|
Cause
| An error occurred when WebLogic Server called the resource adapter's ManagedConnectionFactory.setLogWriter() method.
|
|
Action
| Contact your resource adapter supplier about the ManagedConnectionFactory.setLogWriter() method.
|
|
|
BEA-190021(retired)
|
Warning: < poolName > Changing config value configName as specified in map-config-property.
|
|
BEA-190022(retired)
|
Error: < poolName > Error locating method methodName.
|
Cause
| The method required to set configuration properties is not present. Either the method is not defined or the config-property is incorrectly specified.
|
|
Action
| Check the config-property specifications in the ra.xml file of the resource adapter.
|
|
|
BEA-190023
|
Error: < poolName > Error invoking the ManagedConnectionFactory "set" method for the configuration property "configName". Reason: reason.
|
Description
| WebLogic Server attempted to invoke a method to set the value of the specified property of the resource adapter ManagedConnectionFactory. However either an IllegalAccessException, InvocationTargetException or some other exception occurred.
|
|
Cause
| The method required for setting the config-property could not be properly invoked.
|
|
Action
| Check the config-property of the ra.xml file in the resource adapter and make sure that the property indicated is specified correctly.
|
|
|
BEA-190024
|
Warning: < poolName > Error making initial connections for pool. Reason: reason
|
Description
| Failed to create one or more of the initial connections for the resource adapter upon deployment
|
|
Cause
| The backend to which the Resource Adapter connects may be down, or the resource adapter may be misconfigured
|
|
Action
| Check the availability of the backend system, then confirm the correct configuration of the resource adapter.
|
|
|
BEA-190025(retired)
|
Warning: < poolName > Connection Pool has been initialized with no connections.
|
|
BEA-190026(retired)
|
Info: < poolName > Connection Pool initialization has completed successfully.
|
|
BEA-190027(retired)
|
Info: < poolName > Shutting down connections.
|
|
BEA-190028(retired)
|
Info: < poolName > Connections shutdown successfully.
|
|
BEA-190029(retired)
|
Warning: < poolName > No connections could be created.
|
|
BEA-190030(retired)
|
Error: < poolName > Error making initial connections for pool -- No Default Resource Principal.
|
Cause
| The resource adapter configuration parameters requested that an initial connection pool be populated. There was no 'default' resource principal defined for the creation of these initial connections.
|
|
Action
| Check the security configuration for this resource adapter.
|
|
|
BEA-190031(retired)
|
Error: < poolName > Error making capacityIncrement - 1 connections for pool -- No Default Resource Principal.
|
|
BEA-190032
|
Warning: < poolName > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "ex "
|
Description
| The connector service was unable to obtain a managed connection from the resource adapter because of the specified exception thrown by the resource adapter's ManagedConnectionFactory.
|
|
Cause
| The cause should be evident from the exception. One likely cause is a misconfigured weblogic-ra.xml or ra.xml. The property(ies) specifying the connection information may not be correct.
|
|
Action
| Check the exception to determine the cause and attempt to remedy the indicated problem. You may need to consult the configuration for the resource adapter or documentation. You might also consult the resource adapter vendor support information/organization.
|
|
|
BEA-190033
|
Error: < poolName > createManagedConnection returned a null ManagedConnection.
|
Description
| < poolName > createManagedConnection returned a null ManagedConnection.
|
|
Cause
| This generally is a resource adapter error. A resource adapter should never return a null managed connection.
|
|
Action
| Check the exception to determine the cause and attempt to remedy the indicated problem. You may need to consult the configuration for the resource adapter or documentation. You might also consult the resource adapter vendor support information/organization
|
|
|
BEA-190034(retired)
|
Warning: < poolName > Max Connections have been allocated. No additional connections will be created.
|
|
BEA-190035(retired)
|
Info: numConn physical connection(s) were created with the following Meta Data: Product name of EIS instance: prodName Product version of EIS instance: prodVer Maximum number of connections supported from different processes: maxConns User name for connection: uName
|
|
BEA-190036(retired)
|
Error: < poolName > Error destroying ManagedConnection.
|
|
BEA-190037(retired)
|
Error: < poolName > Error shrinking pool.
|
|
BEA-190038(retired)
|
Error: < poolName > Undeployment of Resource Adapter has been requested. No new connections are allowed.
|
|
BEA-190039(retired)
|
Error: < poolName > Could not create any new ManagedConnections during a connection request.
|
|
BEA-190040(retired)
|
Error: < poolName > The maximum number of connections have been allocated and are in use.
|
Cause
| A connection request was made but cannot be granted. There are no connections in the free pool to be matched. The max number of connections have been allocated, and free ones can not be recycled because the free pool is empty. All allocated connections must be busy.
|
|
Action
| Retry theconnection request later.
|
|
|
BEA-190041(retired)
|
Error: < poolName > The returned ManagedConnection instance is null.
|
Description
| There is a problem with the ManagedConnection that was supposed to be used for a connection request. It is null. We are returning null from the connection request.
|
|
|
BEA-190042(retired)
|
Error: < poolName > Error loading class className. Reason: reason.
|
Cause
| The specified resource adapter class could not be loaded.
|
|
Action
| Check the resource adapter configuration and/or contents of the resource adapter archive.
|
|
|
BEA-190043(retired)
|
Error: < poolName > Error introspecting the managed connection factory: mcfClassName. Reason: reason.
|
Description
| < poolName > Error introspecting the managed connection factory: mcfClassName. Reason: reason.
|
|
Cause
| Could not get the BeanInfo class from the ManagedConnectionFactory.
|
|
Action
| Check the validity of the ManagedConnectionFactory class specified in the ra.xml file.
|
|
|
BEA-190044(retired)
|
Error: < poolName > Error canceling pool shrinking scheduler. Reason: reason
|
Description
| Problem occurred while canceling the pool shrinking scheduler.
|
|
|
BEA-190045(retired)
|
Error: < poolName > Error starting pool shrinking timer. Reason: reason.
|
Description
| Error starting the connection pool shrinker.
|
|
|
BEA-190046(retired)
|
Error: < poolName > Pool shrinking error. Unable to shrink pool from curSize size to newSize.
|
Description
| Error shrinking connection pool.
|
|
Cause
| Error calling the ManagedConnection destroy method.
|
|
Action
| Determine a possible problem with ManagedConnection.destroy()
|
|
|
BEA-190047(retired)
|
Error: < poolName > Error calling matchManagedConnectionFactory. Error: reason. Creating new connections instead.
|
Cause
| Error calling the matchManagedConnections method on the ManagedConnectionFactory.
|
|
Action
| Troubleshoot the matchManagedConnections method.
|
|
|
BEA-190048(retired)
|
Error: Failure adding ManagedConnectionFactory. Null raMBean error.
|
Cause
| WebLogic Server tried to pass a null argument while adding a ManagedConnectionFactory.
|
|
Action
| Check the reason for a null MBean when adding a ManagedConnectionFactory.
|
|
|
BEA-190049
|
Error: The connector service failed to initialize. ServiceMBean initialization error: error..
|
Description
| An error occurred in connector service initialization.
|
|
Cause
| This error should not occur under normal operations. Possible causes of this error could be low memory, file corruption, or machine instability.
|
|
Action
| Try rebooting the machine and restart the server again. If the problem persists, please take a note of the error details and contact BEA support.
|
|
|
BEA-190050
|
Error: An error occurred in the connector service shutdown.\n Error: error
|
Description
| An error occurred while shutting down the connector service. error: error.
|
|
Cause
| The error occurred as a result of shutting down a connection pool or unregistering the ServiceMBean. error: error
|
|
Action
| Report the error to BEA support.
|
|
|
BEA-190051
|
Error: An error occurred while shutting down the connection pool with pool name: poolName. Reason: reason
|
Description
| An error occurred while shutting down the connection pool with pool name: poolName. Reason: reason
|
|
Cause
| An error occurred while shutting down the connection pool. The error occurred while unregistering the ConnectionPoolRuntimeMBean. pool name:poolName. Reason: reason
|
|
Action
| Report to BEA support.
|
|
|
BEA-190052
|
Error: An error occurred while creating a connection pool with pool name: poolName. Reason: reason
|
Description
| An error occurred while creating a connection pool with pool name: poolName. Reason: reason.
|
|
Cause
| An error occurred while creating a connection pool. The error occurred while initializing the ConnectionPoolRuntimeMBean. pool name:poolName. Reason: reason
|
|
Action
| Report the error to BEA support.
|
|
|
BEA-190053
|
Error: An error occurred while creating a resource for a connection pool poolName. Reason: reason
|
Description
| An error occurred while creating a resource for a connection pool with pool name: poolName.
|
|
Cause
| Error occurred while instantiating a ConnectionRuntimeMBean for the connection being created. Pool name: poolName. Reason: reason
|
|
Action
| Report the error to BEA support.
|
|
|
BEA-190054
|
Error: An error occurred while destroying a resource for a connection pool poolName. Reason: reason
|
Description
| An error occurred while destroying a resource for a connection pool with pool name: poolName.
|
|
Cause
| An error occurred while unregistering a ConnectionRuntimeMBean for the connection being destroyed. Pool name: poolName. Reason: reason
|
|
Action
| Report the error to BEA support.
|
|
|
BEA-190055(retired)
|
Error: An error occurred when sleeping the leak detection thread. Reason: reason
|
Action
| Report the error to BEA support.
|
|
|
BEA-190056
|
Error: An error occurred while reserving a resource from a connection pool poolName. Reason: reason
|
Description
| An error occurred while reserving a resource from a connection pool with pool name: poolName.
|
|
Cause
| An error occurred while registering an XAResource for the connection being reserved with the transaction manager. Pool name:poolName. Reason: reason
|
|
Action
| Report the error to BEA support.
|
|
|
BEA-190057(retired)
|
Error: An error occurred while unregistering XAResource with pool name:poolName. Reason: reason
|
|
BEA-190058(retired)
|
Error: The J2EE connector service license validation failed. The resource adapter cannot be deployed.
|
Cause
| The license file does not indicate that the J2EE connector feature is available.
|
|
Action
| Check or refresh the license file WebLogicLicense.xml and reboot the system.
|
|
|
BEA-190059(retired)
|
Error: Application deployment failed. You have attempted to deploy an application that uses J2EE 1.3 features while running WebLogic Server in J2EE 1.2 mode. You can configure WebLogic Server to run in J2EE 1.3 mode using the Administration Console.
|
|
BEA-190060(retired)
|
Warning: Connection leak detected
|
Description
| A connection leak has been detected and will now be automatically closed by the server.
|
|
Cause
| This occurs when an application component obtains a connection to a resource adapter, then releases the connection without closing it as it should.
|
|
Action
| Make sure that all the components in your application properly close connections to resource adapters. You can use the Administration Console to see how many leaks have been detected for the connection pool of each connector. Also, if the property is set to true for a configured resource adapter pool, then you can use the Administration Console to see the call stacks of all leaked connections for the pool, which can help you find out which component has caused a leak.
|
|
|
BEA-190061(retired)
|
Warning: Idle connection detected.
|
Description
| An idle connection has been detected and will now be automatically closed by the server.
|
|
Cause
| Some component has held a connection to a resource adapter and was not used in a time greater than the property configured in the weblogic-ra.xml file for that resource adapter.
|
Action
| Make sure that the components in your application do not hold open connections much longer than they need to. If necessary, increase the configured property in the resource adapter weblogic-ra.xml file.
| |
|
|
BEA-190062(retired)
|
Error: ConnectionPoolManager is not yet available.
|
|
BEA-190063(retired)
|
Error: Remote access to a resource adapter is not supported.
|
|
BEA-190064
|
Warning: Access has been denied to poolName - Application: appName, Module: modName, EIS Type: eisName. while reserving a connection.
|
Description
| Access has been denied to poolName - Application: appName, Module: modName, EIS Type: eisName. while reserving a connection.
|
|
Cause
| Entitlement check did not pass for the connection request to the connection pool with name: poolName.
|
|
Action
| Check your entitlement configuration in the console.
|
|
|
BEA-190065(retired)
|
Warning: A deprecated element security-principal-map is being used for poolName - Application: appName, Module: modName, EIS Type: eisName.
|
Description
| A deprecated element security-principal-map is being used for poolName - Application: appName, Module: modName, EIS Type: eisName.
|
|
Cause
| A deprecated element security-principal-map is being used for poolName - Application: appName, Module: modName, EIS Type: eisName.
|
|
Action
| Remove the security-principal-map element from the weblogic-ra.xml in the resource adaptor. The user entries and their security mappings can be made using the console.
|
|
|
BEA-190066(retired)
|
Error: Failed to import security-principal-map entry for resource-username=eisPrincipal while deploying poolName - Application: appName, Module: modName, EIS Type: eisName.
|
Description
| Failed to import security-principal-map entry for resource-username=eisPrincipal while deploying poolName - Application: appName, Module: modName, EIS Type: eisName.
|
|
|
BEA-190067(retired)
|
Error: An error occurred while deploying a resource adaptor for pool name poolName\n Application name: appName, Module name: modName, EIS Type: eisType.
|
Description
| An error occurred while deploying a resource adaptor. for pool name: poolName.
|
|
Cause
| Failed to import security-principal-map into the embedded LDAP server while deploying poolName - Application: appName, Module: modName, EIS Type: eisType.
|
|
Action
| Report this error to BEA support.
|
|
|
BEA-190068(retired)
|
Warning: Failed to delete the pre-existing credential map and resource map entries from the embedded LDAP server while deploying poolName - Application: appName, Module: modName, EIS Type: EISType.
|
|
BEA-190069(retired)
|
Error: Cannot map a ManagedConnectionFactory to a connection pool. Ensure that the MCF hashCode() and equals() methods are implemented properly. For details, see the Troubleshooting section in the "Programming WebLogic Server J2EE Connectors" guide.
|
|
BEA-190070(retired)
|
Error: < poolName > Cannot find a "set" method in the ManagedConnectionFactory for the configuration property "configPropName".
|
Description
| < poolName > Cannot find a "set" method in the ManagedConnectionFactory for the configuration property "configPropName".
|
|
Cause
| < poolName > Cannot find a "set" method in the ManagedConnectionFactory for the configuration property "configPropName".
|
|
Action
| Ensure that the MCF contains "get" and "set" methods for each of the ra.xml configuration properties. Ensure that the data types associated with these methods match the data type specified in the element.
|
|
|
BEA-190071(retired)
|
Error: < poolName > A ClassNotFoundException was caught when the server attempted to find the of "configType" that was specified for the configuration property "configPropName".
|
Description
| < poolName > A ClassNotFoundException was caught when the server attempted to find the of "configType" that was specified for the configuration property "configPropName".
|
Cause
| An incorrect config-property-type element was defined in the resource adaptors configuration file.
|
|
Action
| Ensure that a legal value for is specified.
| |
|
BEA-190072(retired)
|
Error: An error occurred while initializing the managed connection factory. < poolName > A value must be specified for the configuration property "configPropName".
|
Description
| An error occurred while initializing the managed connection factory. < poolName > A value must be specified for the configuration property "configPropName".
|
|
Cause
| < poolName > A value must be specified for the configuration property "configPropName".
|
|
Action
| Ensure that a or a element is specified for "configPropName".
|
|
|
BEA-190073(retired)
|
Warning: Cannot find "part" in resource adapter "name".
|
|
BEA-190074(retired)
|
Error: An exception occurred when processing the deployment descriptor "dd" for: "name": exMsg
|
Description
| An exception occurred when processing the deployment descriptor "dd" for: "name": exMsg
|
|
Cause
| An exception error occurred with error : exMsg
|
|
Action
| Report the error to BEA support, if you are unable to resolve the exception.
|
|
|
BEA-190075
|
Error: The resource adapter returned a null connection factory when createConnectionFactory was called for "jndiName".
|
Description
| The resource adapter returned a null connection factory when createConnectionFactory was called for "jndiName".
|
|
Cause
| The resource adapter is not functioning according to the specification.
|
|
Action
| Contact the resource adapter vendor.
|
|
|
BEA-190077(retired)
|
Error: An error occurred while decrypting the EIS password for the poolName resource adapter.
|
Description
| An exception was thrown by the inception service while attempting to decrypt the EIS password while importing the security principal map.
|
|
Cause
| This error likely means a resource adapter archive has been migrated where the passwords in the security principal map were encrypted on a different server using the encryption tool.
|
|
Action
| Replace the encrypted text in the weblogic-ra.xml file with a clear text password. You can either leave it there unencrypted, or reencrypt it with the encryption tool for the new server.
|
|
|
BEA-190078(retired)
|
Error: An error occurred while removing the pre-existing entries from the embedded LDAP server while deploying a resource adaptor for pool name poolName\n Application name: appName, Module name: modName, EIS Type: eisType.
|
Description
| An error occurred while deploying a resource adapto for pool name: poolName.
|
|
Cause
| Unknown.
|
|
Action
| Report this error to BEA support.
|
|
|
BEA-190079
|
Warning: The descriptor element oldElement has been replaced by newElement.
|
Description
| The value of oldElement has been converted to the value of newElement and will be used internally within WebLogic Server. Specifying newElement explicitly will override this converted oldElement value.
|
|
Cause
| A deprecated descriptor element has been detected.
|
|
Action
| Convert the old descriptor element to the replacement element.
|
|
|
BEA-190080
|
Warning: An inactive deprecated descriptor element oldElement has been detected.
|
Description
| There is no direct replacement descriptor element for oldElement. This descriptor value will not be used internally within WebLogic Server.
|
|
Cause
| An inactive deprecated descriptor element has been detected.
|
|
Action
| Refer to the connector documentation for more information.
|
|
|
BEA-190081
|
Info: Testing resource adapter "jndiName" for viability of connection proxies.
|
|
BEA-190082
|
Info: Proxy test passed. WLS will use connection proxies for resource adapter "jndiName".
|
|
BEA-190083(retired)
|
Warning: Proxy test failed. WLS will not use connection proxies for resource adapter "jndiName".
|
Description
| Proxy test failed. WLS will not use connection proxies for resource adapter "jndiName".
|
|
Cause
| The "jndiName" The resource adapter attempted to cast the WLS connection proxy to a class or an interface not implemented by the proxy and got a java.lang.ClassCastException (java.lang.ClassCastException). Late transaction enlistment and leak and idle detection will be turned off for this resource adapter.
|
|
Action
| No action required.
|
|
|
BEA-190084
|
Error: Unable to complete connection proxy test for "jndiName" due to the following exception. WLS will attempt to use connection proxies for resource adapter "jndiName" as usual.
|
Description
| Unable to complete connection proxy test for "jndiName" due to the following exception. WLS will attempt to use connection proxies for resource adapter "jndiName" as usual.
|
|
Cause
| WebLogic Server attempted to pose as an application component to determine whether a generated proxy class is compatible with a resource adapter (to support late transaction enlistment and leak and idle detection of connections). The connection proxy test failed.
|
|
Action
| None required.
|
|
|
BEA-190085
|
Info: The linkref RAR name has been marked for late deployment since its base has not been deployed.
|
Description
| The linkref RAR name has been marked for late deployment since its base has not been deployed. The RAR cannot be used until its base has been deployed. Once the base has been deployed, the linkref will automatically deploy.
|
|
Cause
| The base RAR that the linkref points to has not been deployed yet.
|
|
Action
| Do not use the linkref until its base has been deployed.
|
|
|
BEA-190086(retired)
|
Info: The dependent linkref RAR name has been deployed.
|
Description
| The dependent linkref RAR name has been deployed.
|
|
Cause
| The base RAR that the linkref links to has been deployed.
|
|
Action
| No action required.
|
|
|
BEA-190087(retired)
|
Error: An error occurred while deploying the dependent linkref name.
|
Description
| An error occurred while deploying the dependent linkref name with exception ex.
|
|
Cause
| The deployment of the linkref failed with the following exception: ex.
|
|
Action
| Check the configuration of the linkref.
|
|
|
BEA-190088
|
Error: Trying to deploy a connector with a JNDI name that already exists name.
|
Description
| Trying to deploy a connector with a JNDI name that already exists name.
|
|
Cause
| Trying to deploy a connector with a JNDI name that already exists name.
|
|
Action
| Use a unique JNDI name while deploying the connector.
|
|
|
BEA-190089
|
Error: Unexpected error occurred while processing a resource adapter jar file.
|
Description
| Unexpected error occurred while processing a resource adapter jar file.
|
|
Cause
| Unknown
|
|
Action
| Examine stack trace for cause and action.
|
|
|
BEA-190090
|
Error: Call to implementation of ManagedConnection.getLocalTransaction in resource adapter with jndiName = jndiName failed: msg
|
Description
| Failed to get local transaction instance for the resource adapter
|
|
Cause
| Refer to the error message for more information.
|
|
Action
| See the error message for more information. If it is still unclear, contact the resource adapter vendor or BEA support.
|
|
|
BEA-190091
|
Error: Call to implementation of ManagedConnection.getXAResource in resource adapter with jndiName = jndiName failed: msg
|
Description
| Failed to obtain the XAResource instance for the resource adapter.
|
|
Cause
| Refer to the error message for more information.
|
|
Action
| Refer to the error message for more information. If still unclear, contact the resource adapter vendor or BEA support.
|
|
|
BEA-190092
|
Error: An error occurred while reserving a resource from a connection pool poolName. Reason: msg
|
Description
| An error occurred while reserving a resource from a connection pool with pool name: poolName.
|
|
Cause
| An error occurred while registering a Non-XAResource for the connection being reserved with the transaction manager. pool name:poolName. Reason: msg
|
|
Action
| Report this error to BEA support.
|
|
|
BEA-190093(retired)
|
Error: Failed to prepare a connection pool while deploying a resource adapter: msg
|
Description
| Preparing a connection pool failed for a resource adapter.
|
|
Cause
| The backend EIS may not be available, or the configuration for initial connections may be invalid. See error details for more specific information.
|
|
Action
| Check the backend EIS availability, and validate the resource adapter configuration including the credentials.
|
|
|
BEA-190094(retired)
|
Error: Failed to perform a dynamic update on the connection pool: jndiName.
|
Description
| Failed to perform a dynamic update on the connection pool : jndiName. Unable to find the connection pool for the specified JNDI name.
|
|
Cause
| It is possible that a dynamic update is being performed on a linkref whose base has not been deployed yet.
|
|
Action
| If this is a linkref with a base that has not been deployed, make sure that the base is deployed. Otherwise, contact BEA support for help.
|
|
|
BEA-190095(retired)
|
Error: An application has attempted to use a resource adapter connection in multiple transactions simultaneously: poolName
|
Description
| WebLogic Server does not support using a resource adapter connection in multiple transactions simultaneously.
|
|
Cause
| An application is using a resource adapter connection in multiple transactions.
|
|
Action
| Before using a connection in a transaction, ensure that all transactions using the same connection are complete.
|
|
|
BEA-190096(retired)
|
Error: A shared connection was obtained but could not be re-enlisted: poolName, msg
|
Description
| Failed to re-enlist the shared connection for the resource adapter.
|
|
Cause
| See the error description in the message body.
|
|
Action
| Contact the resource adapter vendor or BEA support for help.
|
|
|
BEA-190097
|
Info: Unable to complete the connection proxy test for "jndiName" due to an exception. WebLogic Server will attempt to use connection proxies for resource adapter "jndiName" as usual. Exception: ex.
|
Description
| Unable to complete connection proxy test for "jndiName" due to an exception. WebLogic Server will attempt to use connection proxies for resource adapter "jndiName" as usual. Exception: ex.
|
|
Cause
| WebLogic Server attempted to pose as an application component to determine whether a generated proxy class is compatible with a resource adapter (to support late transaction enlistment and leak and idle detection of connections). The connection proxy test failed.
|
|
Action
| No action required.
|
|
|
BEA-190098
|
Warning: Trying to release a resource that has already been released for name.
|
Description
| Trying to release a resource that has already been released for name.
|
|
Cause
| Trying to release a resource that has already been released for name. It is possible that the connection was already released due to an error that occurred with the connection.
|
|
Action
| No Action required.
|
|
|
BEA-190099
|
Warning: Attempting to close a connection that has already been closed for name.
|
Description
| Attempting to close a connection that has already been closed for name.
|
|
Cause
| Attempting to close a connection that has already been closed for name.
|
|
Action
| No Action required.
|
|
|
BEA-190100
|
Error: A close() method was not found on the connection handle while testing for the viability for connection proxies : poolName
|
Description
| A close() method was not found on the connection handle while testing for the viability for connection proxies : poolName. As per the 1.0 specification a close() method is required on the connection handle.
|
|
Cause
| A close() method was not found on the connection handle while testing for the viability for connection proxies : poolName. As per the 1.0 specification a close() method is required on the connection handle.
|
|
Action
| Implement a close() method for the connection handle.
|
|
|
BEA-190101
|
Warning: Linkrefs are deprecated for 1.0 resource adapters : raName
|
Description
| Linkrefs are deprecated for 1.0 resource adapters.
|
|
Cause
| Linkrefs are deprecated for 1.0 resource adapters.
|
|
Action
| None
|
|
|
BEA-199999
|
Debug: Stack trace for message id
|
Description
| Stack trace for previously logged message
|
|
|
BEA-199998
|
Debug: Stack trace for message id\nstackTrace
|
Description
| Stack trace for previously logged message\n stackTrace
|
|
|
BEA-190102
|
Error: Failed to unregister the Diagnostic Image for the Connector Service
|
Description
| Failed to unregister the Diagnostic Image for the Connector Service
|
|
Cause
| WLS internal error.
|
|
Action
| See stack trace & report to BEA
|
|
|
BEA-190103
|
Error: Failed to register the Diagnostic Image for the Connector Service
|
Description
| Failed to register the Diagnostic Image for the Connector Service
|
|
Cause
| Internal WLS error
|
|
Action
| See stack trace and report to BEA.
|
|
|
BEA-190104
|
Warning: While configuring an object of type: className of Resource Adapter raName, the following errors/omissions were found:\nerrors
|
Description
| While configuring an object of type: className of Resource Adapter raName, the following errors/omissions were found:\nerrors
|
|
Cause
| Properties have been specified in a resource adapter deployment descriptor which are inconsistent with those defined by the resource adapter code. There may be properties specified in the descriptor that do no exist in the object are of the wrong type.
|
|
Action
| Check that the properties specified are spelled properly. Check with the resource adapter documentation or the vendor to determine whether these warnings can be ignored or not.
|
|
|
BEA-190105
|
Error: Failed to initialize the AnonymousSubject
|
Description
| Failed to initialize the AnonymousSubject for calling into adapter code
|
|
Cause
| Internal WLS Error
|
|
Action
| See stack trace and report to BEA.
|
|
|
BEA-190106
|
Error: Failed to find the RuntimeMBean for the module: message
|
Description
| Failed to find the RuntimeMBean for the module: message
|
|
Cause
| Internal WLS Error
|
|
Action
| See stack trace and report to BEA.
|
|
|
BEA-190107
|
Error: Failed to unregister the RuntimeMBean for the module: ex
|
Description
| Failed to unregister the RuntimeMBean for the module: ex
|
|
Cause
| Internal WLS Error
|
|
Action
| See stack trace and report to BEA.
|
|
|
BEA-190108
|
Error: Failed to initialize the Jndi Subcontexts for the adapter: appId = appId, ex
|
Description
| Failed to initialize the Jndi Subcontexts for the adapter: appId = appId, ex
|
|
Cause
| Internal WLS Error
|
|
Action
| See stack trace and report to BEA.
|
|
|
BEA-190109
|
Info: Extracting file fileName to nativeLibDir
|
Description
| Extracting file fileName to nativeLibDir
|
|
|
BEA-190110
|
Warning: Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.
|
Description
| Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.
|
|
Cause
| See the message body for information.
|
|
Action
| Please contact the Resource Adapter vendor and notify them of this warning condition.
|
|
|
BEA-190111
|
Error: InvalidDyeException was thrown: Module Name = moduleName, ex
|
Description
| InvalidDyeException was thrown: Module Name = moduleName, ex
|
|
Cause
| Internal WLS Error
|
|
Action
| See stack trace and report to BEA.
|
|
|
BEA-190112
|
Error: Failed to register the XAResource to be used for recovery: ex
|
Description
| Failed to register the XAResource to be used for recovery: ex
|
|
Cause
| See the error description in the message body.
|
|
Action
| See stack trace and report to BEA.
|
|
|
BEA-190113
|
Error: Failed to Unregister the XAResource used for recovery: ex
|
Description
| Failed to Unregister the XAResource used for recovery: ex
|
|
Cause
| See the error description in the message body.
|
|
Action
| See stack trace and report to BEA.
|
|
|
BEA-190114
|
Error: Failed to apply dynamic pool changes: ex
|
Description
| Failed to apply dynamic pool changes: ex
|
|
Cause
| See the error description in the message body.
|
|
Action
| See the error description in the message body.
|
|
|
BEA-190115
|
Error: The ManagedConnectionFactory class does not implement the ResourceAdapterAssociation interface: mcf
|
Description
| The ManagedConnectionFactory class does not implement the ResourceAdapterAssociation interface: mcf
|
|
Cause
| See the message body for information.
|
|
Action
| Please contact the Resource Adapter vendor and notify them of this error condition.
|
|
|
BEA-190116
|
Error: An invalid event was triggered on the XAResource used for recovery: msg
|
Description
| An invalid event was triggered on the XAResource used for recovery: msg
|
|
Cause
| Internal WLS error.
|
|
Action
| Report this error to BEA.
|
|
|
BEA-190117
|
Error: Invocation of ManagedConnection.cleanup() failed: ex
|
Description
| Invocation of ManagedConnection.cleanup() failed: ex
|
|
Cause
| See the message body for information.
|
|
Action
| Examine the stack trace and error message for more information.
|
|
|
BEA-190118
|
Error: ConnectionErrorOccurred event was triggered: error
|
Description
| ConnectionErrorOccurred event was triggered: error
|
|
Cause
| Adapter has indicated an error occurred on the exception.
|
|
Action
| Examine the stack trace and error message for more information.
|
|
|
BEA-190119
|
Error: Invocation of ManagedConnection.destroy() failed: ex
|
Description
| Invocation of ManagedConnection.destroy() failed: ex
|
|
Cause
| The implementation of the Resource Adapter's cleanup() method threw an exception.
|
|
Action
| Examine the stack trace and error message for more information.
|
|
|
BEA-190120
|
Error: Invocation of ManagedConnection.getXAResource() returned null
|
Description
| Invocation of ManagedConnection.getXAResource() returned null
|
|
Cause
| The implementation of the Resource Adapter''s getXAResource() returned null.
|
|
Action
| Please contact the adapter vendor to determine why getXAResource() returned null.
|
|
|
BEA-190121
|
Error: Failed to dissociate the Connection Handles from a ManagedConnection: Adapter JndiName = raJndiName, ex
|
Description
| Failed to dissociate the Connection Handles from a ManagedConnection: Adapter JndiName = raJndiName, ex
|
|
Cause
| See the message body and stack trace for more details.
|
|
Action
| See the message body and stack trace for more details.
|
|
|
BEA-190122
|
Error: The Resource Adapter passed a null ManagedConnection into WebLogic Server''s implementation of ConnectionManager.lazyEnlist()
|
Description
| The Resource Adapter passed a null ManagedConnection into WebLogic Server''s implementation of ConnectionManager.lazyEnlist()
|
|
Cause
| The Resource Adapter''s implementation passed a null ManagedConnection into the lazyEnlist() method.
|
|
Action
| Please notify the Resource Adapter''s vendor about this error.
|
|
|
BEA-190123
|
Info: Outbound adapter for jndiName = jndiName, is using sharing scope = sharingScope
|
Description
| Outbound adapter for jndiName = jndiName, is using sharing scope = sharingScope
|
|
|
BEA-190124
|
Error: Failed to deploy LinkRef Adapter, moduleName = moduleName, baseRA = baseName, Exception: ex
|
Description
| Failed to deploy LinkRef Adapter, moduleName = moduleName, baseRA = baseName, Exception: ex
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-190125
|
Error: Internal Error occurred, Assertion Failed: msg
|
Description
| Internal Error occurred, Assertion Failed: msg
|
|
Cause
| An internal consistency check failed indicating a software defect.
|
|
Action
| Please note the circumstances of the error as well as any related log messages and contact BEA Support.
|
|
|
BEA-190126
|
Error: anonymous
|
Description
| anonymous
|
|
Cause
| anonymous
|
|
Action
| anonymous
|
|
|
BEA-190127
|
Error: CloseCount
|
Description
| CloseCount
|
|
Cause
| CloseCount
|
|
Action
| CloseCount
|
|
|
BEA-190128
|
Error: CreateCount
|
Description
| CreateCount
|
|
Cause
| CreateCount
|
|
Action
| CreateCount
|
|
|
BEA-190129
|
Error: FreePoolSize
|
Description
| FreePoolSize
|
|
Cause
| FreePoolSize
|
|
Action
| FreePoolSize
|
|
|
BEA-190130
|
Error: PoolSize
|
Description
| PoolSize
|
|
Cause
| PoolSize
|
|
Action
| PoolSize
|
|
|
BEA-190131
|
Error: WaitingThreadCount
|
Description
| WaitingThreadCount
|
|
Cause
| WaitingThreadCount
|
|
Action
| WaitingThreadCount
|
|
|
BEA-190132(retired)
|
Error: Number of times close was called on the connection pool
|
Description
| Number of times close was called on the connection pool
|
|
Cause
| Number of times close was called on the connection pool
|
|
Action
| Number of times close was called on the connection pool
|
|
|
BEA-190133
|
Error: Number of times create was called on the connection pool
|
Description
| Number of times create was called on the connection pool
|
|
Cause
| Number of times create was called on the connection pool
|
|
Action
| Number of times create was called on the connection pool
|
|
|
BEA-190134
|
Error: Number of connections in the pool that are free for use
|
Description
| Number of connections in the pool that are free for use
|
|
Cause
| Number of connections in the pool that are free for use
|
|
Action
| Number of connections in the pool that are free for use
|
|
|
BEA-190135
|
Error: Size of the connection pool
|
Description
| Size of the connection pool
|
|
Cause
| Size of the connection pool
|
|
Action
| Size of the connection pool
|
|
|
BEA-190136
|
Error: Number of threads in the waiting state
|
Description
| Number of threads in the waiting state
|
|
Cause
| Number of threads in the waiting state
|
|
Action
| Number of threads in the waiting state
|
|
|
BEA-190137
|
Error: Never
|
Description
| Never
|
|
Cause
| Never
|
|
Action
| Never
|
|
|
BEA-190138
|
Error:
|
BEA-190139
|
Error: Running
|
Description
| Running
|
|
Cause
| Running
|
|
Action
| Running
|
|
|
BEA-190140
|
Error: Suspended
|
Description
| Suspended
|
|
Cause
| Suspended
|
|
Action
| Suspended
|
|
|
BEA-190141
|
Error: New
|
Description
| New
|
|
Cause
| New
|
|
Action
| New
|
|
|
BEA-190142
|
Error: Initialized
|
Description
| Initialized
|
|
Cause
| Initialized
|
|
Action
| Initialized
|
|
|
BEA-190143
|
Error: Prepared
|
Description
| Prepared
|
|
Cause
| Prepared
|
|
Action
| Prepared
|
|
|
BEA-190144
|
Error: Activated
|
Description
| Activated
|
|
Cause
| Activated
|
|
Action
| Activated
|
|
|
BEA-190145
|
Error: Unknown
|
Description
| Unknown
|
|
Cause
| Unknown
|
|
Action
| Unknown
|
|
|
BEA-190146
|
Error: An error occurred while setting the log file to the resource adapter's ManagedConnectionFactory: poolName. The exception was 'exMessage' with cause 'cause'.
|
Description
| The resource adapter log file was opened successfully but a problem occurred when setting it to the ManagedConnectionFactory object of the resource adapter.
|
|
Cause
| An error occurred when WebLogic Server called the resource adapter''s ManagedConnectionFactory.setLogWriter() method.
|
|
Action
| Examine the message & cause and/or contact the resource adapter provider
|
|
|
BEA-190147
|
Info: Profiling Record for Pool: PoolName = 'poolName', Type = 'type', Timestamp = 'timestamp', Properties : props
|
Description
| Profiling Record for Harvester has been logged
|
|
Cause
| The Harvester has logged this Profiling Record for debug purposes.
|
|
Action
| No action is necessary. This message is for information only.
|
|
|
BEA-199000
|
Error: Only positive values allowed for initial-capacity unless initial and max capacity are equal.
|
Description
| Only positive values allowed for initial-capacity unless initial and max capacity are equal.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-190148
|
Warning: The attempt to set the property "propName" of type "propType" of object "object" to value "propVal" failed with a PropertyVetoException thrown by the resource adapter. The veto message was "vetoMsg".
|
Description
| The attempt to set the property "propName" of type "propType" of object "object" to value "propVal" failed with a PropertyVetoException thrown by the resource adapter. The veto message was "vetoMsg".
|
|
Cause
| See the veto message for more info.
|
|
Action
| See the veto message for more info. Contact the resource adapter provider if more assistance is needed.
|
|
|
BEA-190149
|
Warning: No JNDI Name has been specified for the resource adapter in module moduleName of application appName. Since this is an inbound resource adapter, must also be specified in weblogic-ra.xml for endpoint activation by a message endpoint MDB to work.
|
Description
| No JNDI Name has been specified for the resource adapter in module moduleName of application appName. Since this is an inbound resource adapter, must also be specified in weblogic-ra.xml for endpoint activation by a message endpoint MDB to work.
|
Cause
| Missing element in weblogic-ra.xml
|
Action
| Specify the in weblogic-ra.xml that corresponds to the JNDI name expected by the MDB that is using this inbound resource adapter.
| | |
|
BEA-190150
|
Warning: The process of creating the Connector Diagnostic Image has been timedout by the Diagnostic Framework. The resulting image may be incomplete.
|
Description
| The process of creating the Connector Diagnostic Image has been timedout by the Diagnostic Framework. The resulting image may be incomplete.
|
|
Cause
| The process of creating the Connector Diagnostic Image has been timedout by the Diagnostic Framework.
|
|
Action
| Please investigate the contents of the log and diagnostic images for more information.
|
|
|
BEA-190151
|
Error: Parsing error, buildOutboundResourceAdapter() Error in parsing ra.xml. While looking for connectionfactory-interface failed to find: "xpath"
|
Description
| Parsing error, buildOutboundResourceAdapter() Error in parsing ra.xml. While looking for connectionfactory-interface failed to find: "xpath"
|
|
Cause
| There is an error in the xml configuration for this adapter.
|
|
Action
| Please contact the vendor to obtain a Resource Adapter with a valid configuration.
|
|
|
BEA-190152
|
Error: Failed to create a new ConnectorInboundRuntimeMBeanImpl for "name", err
|
Description
| Failed to create a new ConnectorInboundRuntimeMBeanImpl for "name", err
|
|
Cause
| See the error in the logged message for more information.
|
|
Action
| See the error in the logged message for more information.
|
|
|
BEA-190153
|
Warning: Failed to close the logging stream for pool: "poolName", err
|
Description
| Failed to close the logging stream for pool: "poolName", err
|
|
Cause
| See the error in the logged message for more information.
|
|
Action
| See the error in the logged message for more information.
|
|
|
BEA-190154
|
Warning: Failed to create the logging stream for pool: "poolName", err
|
Description
| Failed to create the logging stream for pool: "poolName", err
|
|
Cause
| See the error in the logged message for more information.
|
|
Action
| See the error in the logged message for more information.
|
|
|
BEA-190155
|
Warning: Compliance checking/validation of the resource adapter raName resulted in the following warnings:\nwarnings
|
Description
| Compliance checking/validation of the resource adapter raName resulted in the following warnings:\nwarnings
|
|
Cause
| The specified resource adapter failed to pass compliance/validity checking as indicated by the warnings and/errors listed.
|
|
Action
| Correct the ra.xml, weblogic-ra.xml or the resource adapter archive.
|
|
|
BEA-190156
|
Info: There were no compliance/validation errors found in the resource adapter raName
|
Description
| There were no compliance/validation errors found in the resource adapter raName
|
|
|
BEA-190157
|
Info: There were numErrors compliance/validation error(s) and numWarnings warning(s) found in the resource adapter raName
|
Description
| There were numErrors compliance/validation error(s) and numWarnings warning(s) found in the resource adapter raName
|
|
|
BEA-190158
|
Info: This is a link ref resource adapter for linkRefName. No validation can be done at this time.
|
Description
| This is a link ref resource adapter for linkRefName. No validation can be done at this time.
|
|
Cause
| Since there is no ra.xml in this resource adapter, validation of the adapter cannot be performed until it and the base adapter are deployed
|
|
Action
| None required.
|
|
|
BEA-199001
|
Error: Zero value for max-capacity is allowed only for link-ref adapters.
|
Description
| Zero value for max-capacity is allowed only for link-ref adapters.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199002
|
Error: Negative values are not allowed for max-capacity.
|
Description
| Negative values are not allowed for max-capacity.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199003
|
Error: max-capacity should be greater than or equal to initial-capacity. jndiName
|
Description
| max-capacity should be greater than or equal to initial-capacity. jndiName
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199004
|
Error: Only positive values allowed for capacity-increment.
|
Description
| Only positive values allowed for capacity-increment.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199005
|
Error: capacity-increment should be less than or equal to ( max_capacity-initial_capacity ). jndiName
|
Description
| capacity-increment should be less than or equal to ( max_capacity-initial_capacity). jndiName
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199006
|
Error: Only positive values allowed for shrink-frequency-seconds.
|
Description
| Only positive values allowed for shrink-frequency-seconds.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199007
|
Error: Only values greater than or equal to 0 allowed for inactive-connection-timeout-seconds.
|
Description
| Only values greater than or equal to 0 allowed for inactive-connection-timeout-seconds.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199010
|
Error: There is no ra.xml or weblogic-ra.xml specified. The rar is null and there is no alternate descriptor.
|
Description
| There is no ra.xml or weblogic-ra.xml specified. The rar is null and there is no alternate descriptor.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199011
|
Error: There is no ra.xml or weblogic-ra.xml specified.
|
Description
| There is no ra.xml or weblogic-ra.xml specified.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199012
|
Error: Unable to find the schema.
|
Description
| Unable to find the schema.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199013
|
Error: Application displayName does not have any Components in it.
|
Description
| Application displayName does not have any Components in it.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199014
|
Error: Application displayName is a RAR file, but it contains more than 1 component.
|
Description
| Application displayName is a RAR file, but it contains more than 1 component.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199015
|
Error: Error occurred while trying to rollback the module: msg
|
Description
| Error occurred while trying to rollback the module: msg
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199016
|
Error: Unable to create runtime MBean for connector: Module 'moduleName', msg
|
Description
| Unable to create runtime MBean for connector: Module 'moduleName', msg
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199017
|
Error: Error closing virtual jar file for jarFile, msg
|
Description
| Error closing virtual jar file for jarFile, msg
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199018
|
Error: Error creating virtual jar file for uri, msg
|
Description
| Error creating virtual jar file for uri, msg
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199019
|
Error: Failed to initialize the Connector-specific Jndi sub-contexts for the application, appId, msg
|
Description
| Failed to initialize the Connector-specific Jndi sub-contexts for the application, appId, msg
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199020
|
Error: Failed to prepare changes for dynamic update, uri, msg
|
Description
| Failed to prepare changes for dynamic update, uri, msg
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199021
|
Error: Jndi Name is null or empty.
|
Description
| Jndi Name is null or empty.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199022
|
Error: Unable to get InitialContext while attempting to verify JNDI name of a resource adapter object.
|
Description
| Unable to get InitialContext while attempting to verify JNDI name of a resource adapter object.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199023
|
Error: ResourceLink is null or empty.
|
Description
| ResourceLink is null or empty.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199024
|
Error: Unable to get InitialContext while attempting to verify resource link of resource adapter.
|
Description
| Unable to get InitialContext while attempting to verify resource link of resource adapter.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199028
|
Error: Resource Adapter with JNDIName: jndiName already deployed
|
Description
| Resource Adapter with JNDIName: jndiName already deployed
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199029
|
Error: Bind operation failed: jndiName, msg
|
Description
| Bind operation failed: jndiName, msg
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199031
|
Error: Failed to unbind the ConnectionFactory, jndiName, msg
|
Description
| Failed to unbind the ConnectionFactory, jndiName, msg
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199032
|
Error: Unable to getInitialContext() during unbindConnectionFactory, msg
|
Description
| Unable to getInitialContext() during unbindConnectionFactory, msg
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199036
|
Error: ResourceLink: resourceLink already bound into App-Scoped JNDI tree.
|
Description
| ResourceLink: resourceLink already bound into App-Scoped JNDI tree.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199037
|
Error: Unable to bind to the app-scoped jndi tree: moduleName#resourceLink : msg
|
Description
| ResourceLink: moduleName already bound into App-Scoped JNDI tree.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199038
|
Error: NamingException while trying to unbind references during unbindAdminObject of resource adapter, msg
|
Description
| NamingException while trying to unbind references during unbindAdminObject of resource adapter, msg
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199039
|
Error: Unable to get the connection factory for key. Please check that if the resource adapter has been deployed.
|
Description
| Unable to get the connection factory for key. Please check that if the resource adapter has been deployed.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199040(retired)
|
Error: JNDI Name: jndiName already bound in JNDI tree.
|
Description
| JNDI Name: jndiName already bound in JNDI tree.
|
|
Cause
| Refer to the message body and exception information for more information.
|
|
Action
| Refer to the message body and exception information for more information.
|
|
|
BEA-199041
|
Error: An exception occurred while calling newInstance in the Resource Adapter, classname = cls, Exception = ex
|
Description
| An exception occurred while calling newInstance in the Resource Adapter, classname = cls, Exception = ex
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199042
|
Error: An exception occurred while trying to create the Connector Diagnostic Image, Exception = ex
|
Description
| An exception occurred while trying to create the Connector Diagnostic Image, Exception = ex
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199043
|
Error: Trying to prepare an RA that has not been initialized
|
Description
| Trying to prepare an RA that has not been initialized
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199044
|
Error: Trying to activate an RA that has not been prepared. Current state : state
|
Description
| Trying to activate an RA that has not been prepared. Current state : state
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199045
|
Error: Trying to rollback an RA that is in the ACTIVATED state
|
Description
| Trying to rollback an RA that is in the ACTIVATED state
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199046
|
Error: Unable to create the native lib directory
|
Description
| Unable to create the native lib directory
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199047
|
Error: Bad resource adapter class specification for class 'raClassName' : raErrors
|
Description
| Bad resource adapter class specification for class 'raClassName' : raErrors
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199048
|
Error: Trying to version a resource adapter that is not versionable
|
Description
| Trying to version a resource adapter that is not versionable
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199049
|
Error: Unable to populate the Work Manager during RA initialize
|
Description
| Unable to populate the Work Manager during RA initialize
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199050
|
Error: Caught exception while starting the resource adapter : moduleName, msg
|
Description
| Caught exception while starting the resource adapter : moduleName, msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199051
|
Error: Caught exception while creating the BootstrapContext : moduleName, msg
|
Description
| Caught exception while creating the BootstrapContext : moduleName, msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199052
|
Error: Unable to version the resource adapter
|
Description
| Unable to version the resource adapter
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199053
|
Error: Unable to set up work runtimer
|
Description
| Unable to set up work runtimer
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199054
|
Error: Unable to introspect the object that was passed in. obj
|
Description
| Unable to introspect the object that was passed in. obj
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199055
|
Error: Unable to get the setter method for the key : keyName
|
Description
| Unable to get the setter method for the key : keyName
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199056
|
Error: \tUnable to invoke the setter method for the key : keyName
|
Description
| Unable to invoke the setter method for the key : keyName
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199057(retired)
|
Error: \tConfiguration Properties Error: errorMessage, KeyName = "keyName", KeyType = "keyType", KeyValue = "keyValue"
|
Description
| Configuration Properties Error: errorMessage, KeyName = "keyName", KeyType = "keyType", KeyValue = "keyValue"
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199058(retired)
|
Error: Property value has not been defined
|
Description
| Property value has not been defined
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199059(retired)
|
Error: \tProperty type has not been defined
|
Description
| Property type has not been defined
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199060(retired)
|
Error: Property name has not been defined
|
Description
| Property name has not been defined
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199061(retired)
|
Error: \tFor property "keyName of type "keyType" and value "keyValue", the type in the descriptor does not match the type in the object: "propertyType" and conversion yields the following exception: "ex".
|
Description
| For property "keyName of type "keyType" and value "keyValue", the type in the descriptor does not match the type in the object: "propertyType".
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199062(retired)
|
Error: \tUnable to get the property type for the property name = 'keyName'.
|
Description
| Unable to get the property type for the property name = 'keyName'.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199063(retired)
|
Error: \tAn invalid property type type has been defined for property name name
|
Description
| An invalid property type type has been defined for property name name
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199064(retired)
|
Error: \tFor property "name of type "type", unable to find the set method
|
Description
| For property "name of type "type", unable to find the set method
|
|
Cause
| The resource adapter object being configured does not have a set method corresponding to the property name/type in the descriptor.
|
|
Action
| Edit the deployment descriptor and change the name and/or type of the property element.
|
|
|
BEA-199065
|
Error: \tAn invalid type type has been specified for a key
|
Description
| An invalid type type has been specified for a key
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199066
|
Error: \tFor property "propName", the type and value do not match. Type = propType, Value = propValue, Exception: ex
|
Description
| For property "propName", the type and value do not match. Type = propType, Value = propValue, Exception: ex
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199067
|
Error: LoginException while trying to establish security identity for user 'username' in weblogic-ra.xml element elementName: ex
|
Description
| LoginException while trying to establish security identity for user 'username' in weblogic-ra.xml element elementName: ex
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199068
|
Error: No deployed ResourceAdapter with adapter JNDI name = 'jndiName' was found.
|
Description
| No deployed ResourceAdapter with adapter JNDI name = 'jndiName' was found.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199071
|
Error: Unable to initialize ActivationSpec clsName. Cause unknown.
|
Description
| Unable to initialize ActivationSpec clsName. Cause unknown.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199072
|
Error: Failed to instantiate class clsName, msg
|
Description
| Failed to instantiate class clsName, msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199073
|
Error: methodName passed argName of 'argValue'
|
Description
| methodName passed argName of 'argValue'
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199074
|
Error: Required Configuration Properties Missing in ActivationSpec: missing
|
Description
| Required Configuration Properties Missing in ActivationSpec: missing
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199075
|
Error: Located a resource adapter with JNDI name = 'jndiName', but that adapter is not yet fully deployed and active.
|
Description
| Located a resource adapter with JNDI name = 'jndiName', but that adapter is not yet fully deployed and active.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199076
|
Error: Could not locate a resource adapter with JNDI name = 'jndiName'.
|
Description
| Could not locate a resource adapter with JNDI name = 'jndiName'.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199077
|
Error: The resource adapter with JNDI name = 'jndiName' does not have a element with a of 'messageListenerType'
|
Description
| The resource adapter with JNDI name = 'jndiName' does not have a element with a of 'messageListenerType'
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
| |
|
BEA-199089
|
Error: The resource adapter does not have a element in ra.xml.
|
Description
| The resource adapter does not have a element in ra.xml.
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
| |
|
BEA-199090
|
Error: The resource adapter does not have a element in ra.xml.
|
Description
| The resource adapter does not have a element in ra.xml.
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
| |
|
BEA-199091
|
Error: The resource adapter does not have any elements in ra.xml.
|
Description
| The resource adapter does not have any elements in ra.xml.
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
| |
|
BEA-199092
|
Error: Internal Error occurred, Assertion Failed: msg
|
Description
| Internal Error occurred, Assertion Failed: msg
|
|
Cause
| An internal consistency check failed indicating a software defect.
|
|
Action
| Please note the circumstances of the error as well as any related log messages and contact BEA Support.
|
|
|
BEA-199093
|
Error: setDyeBits failed because Diagnostic Contexts are not enabled.
|
Description
| setDyeBits failed because Diagnostic Contexts are not enabled.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199094
|
Error: Invalid dye value specified, bits. Value must be between 0 and 15 in order to fit within a 4-bit space.
|
Description
| Invalid dye value specified, bits. Value must be between 0 and 15 in order to fit within a 4-bit space.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199095
|
Error: getDyeBits failed, moduleName = moduleName: msg
|
Description
| getDyeBits failed, moduleName = moduleName: msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199096
|
Error: setDyeBits failed: Failed to obtain Diagnostic Context. ModuleName = moduleName.
|
Description
| setDyeBits failed: Failed to obtain Diagnostic Context. ModuleName = moduleName.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199097
|
Error: getDyeBits failed because Diagnostic Contexts are not enabled.
|
Description
| getDyeBits failed because Diagnostic Contexts are not enabled.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199098
|
Error: This connection does not meet the criteria for manual deletion.
|
Description
| This connection does not meet the criteria for manual deletion.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199099
|
Error: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'key', msg.
|
Description
| Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'key', msg.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199100
|
Error: Resource Adapter threw Non-ResourceException from its implementation of ManagedConnection.getLocalTransaction(), Pool = 'key', msg.
|
Description
| Resource Adapter threw Non-ResourceException from its implementation of ManagedConnection.getLocalTransaction(), Pool = 'key', msg.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199101
|
Error: Resource Adapter returned null from its implementation of ManagedConnection.getLocalTransaction(), Pool = 'key'.
|
Description
| Resource Adapter returned null from its implementation of ManagedConnection.getLocalTransaction(), Pool = 'key'.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199102
|
Error: Unable to register NonXAResource, msg.
|
Description
| Unable to register NonXAResource, msg.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199103
|
Error: Commit Failed: msg, Stack Trace: stack
|
Description
| Commit Failed: msg, Stack Trace: stack
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199104
|
Error: Rollback Failed: msg, Stack Trace: stack
|
Description
| Rollback Failed: msg, Stack Trace: stack
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199105
|
Error: Resource Adapter returned null from ManagedConnection.getXAResource() while trying to obtain XAResource for recovery.
|
Description
| Resource Adapter returned null from ManagedConnection.getXAResource() while trying to obtain XAResource for recovery.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199106
|
Error: Resource Adapter threw non-ResourceException in call to ManagedConnection.getXAResource(): msg
|
Description
| Resource Adapter threw non-ResourceException in call to ManagedConnection.getXAResource(): msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199107
|
Error: Resource Adapter returned null from ManagedConnectionFactory.createManagedConnection() while trying to create ManagedConnection for recovery.
|
Description
| Resource Adapter returned null from ManagedConnectionFactory.createManagedConnection() while trying to create ManagedConnection for recovery.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199108
|
Error: Failed to initialize ManagedConnection for recovery: msg
|
Description
| Failed to initialize ManagedConnection for recovery: msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199109
|
Error: Connector Internal Error: Illegal type found during enlistResource.
|
Description
| Connector Internal Error: Illegal type found during enlistResource.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199110
|
Error: Connector Internal Error: Invalid type found in registerResource: clsName.
|
Description
| Connector Internal Error: Invalid type found in registerResource: clsName.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199111
|
Error: Attempt to start an XA Transaction inside a Resource Adapter''s Local Transaction is illegal.
|
Description
| Attempt to start an XA Transaction inside a Resource Adapter''s Local Transaction is illegal.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199112
|
Error: Failed to create managed connection: msg
|
Description
| Failed to create managed connection: msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199113
|
Error: Failed to setup the ManagedConnection with WLS after successfully getting it from a call to the Resource Adapter''s ManagedConnectionFactory.createManagedConnection method.
|
Description
| Failed to setup the ManagedConnection with WLS after successfully getting it from a call to the Resource Adapter''s ManagedConnectionFactory.createManagedConnection method.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199114
|
Error: Internal WLS Connector Error: Object Id is null.
|
Description
| Internal WLS Connector Error: Object Id is null.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Please contact BEA Support.
|
|
|
BEA-199116
|
Error: Resource Adapter Error: getConnection method returned null from the adapter's ManagedConnection implementation in class 'mcCls'
|
Description
| Resource Adapter Error: getConnection method returned null from the adapter's ManagedConnection implementation in class 'mcCls'
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199117
|
Error: The resource adaptor has returned the same connection handle that was returned on a prior call to getConnection(...). A new connection handle must be returned with every call to getConnection(...) as per the JCA specification.
|
Description
| The resource adaptor has returned the same connection handle that was returned on a prior call to getConnection(...). A new connection handle must be returned with every call to getConnection(...) as per the JCA specification.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199118
|
Error: While testing connection, the adapter's implementation of getInvalidConnections() threw ResourceException: msg
|
Description
| While testing connection, the adapter's implementation of getInvalidConnections() threw ResourceException: msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199119
|
Error: While testing connection, the adapter's implementation of getInvalidConnections() threw non-ResourceException: msg
|
Description
| While testing connection, the adapter's implementation of getInvalidConnections() threw non-ResourceException: msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199120
|
Error: Connections should not be tested for a ManagedConnectionFactory that does not implement ValidatingManagedConnectionFactory.
|
Description
| Connections should not be tested for a ManagedConnectionFactory that does not implement ValidatingManagedConnectionFactory.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199121
|
Error: The ResourceAdapter with pool = 'pool' passed a null value to the Application Server's implementation of the lazyEnlist method for the ConnectionManager class.
|
Description
| The ResourceAdapter with pool = 'pool' passed a null value to the Application Server's implementation of the lazyEnlist method for the ConnectionManager class.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199122
|
Error: Access to resource adapter, with pool = 'pool', has been denied.
|
Description
| Access to resource adapter, with pool = 'pool', has been denied.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199123
|
Error: Unable to get a connection for pool = 'pool', msg
|
Description
| Unable to get a connection for pool = 'pool', msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199124
|
Error: Pool 'poolName' is disabled, cannot allocate resources to applications.
|
Description
| Pool 'poolName' is disabled, cannot allocate resources to applications.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199125
|
Error: The resource adapter''s implementation of ManagedConnectionFactory returned null from the createConnectionFactory() method.
|
Description
| The resource adapter''s implementation of ManagedConnectionFactory returned null from the createConnectionFactory() method.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199126
|
Error: Stack trace at connection create:
|
Description
| Stack trace at connection create:
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199127
|
Error: Local Transaction not supported for this Resource Adapter.
|
Description
| Local Transaction not supported for this Resource Adapter.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199128
|
Error: The connection handle has not been set for the connection closed event as per the JCA specification.
|
Description
| The connection handle has not been set for the connection closed event as per the JCA specification.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199129
|
Error: Error preparing the pool with key : 'pool', msg
|
Description
| Error preparing the pool with key : 'pool', msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199130
|
Error: Unable to resume the pool, msg
|
Description
| Unable to resume the pool, msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199131
|
Error: Unable to bind to the jndi tree : 'pool' , msg
|
Description
| Unable to bind to the jndi tree : 'pool' , msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199132
|
Error: Key = poolKey, Message = msg, Exception = exMsg
|
Description
| Key = poolKey, Message = msg, Exception = exMsg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199133
|
Error: Unable to shutdown the pool : Key = 'poolKey', Message = msg, Exception = exMsg
|
Description
| Unable to shutdown the pool : Key = 'poolKey', Message = msg, Exception = exMsg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199134
|
Error: Attempting to create a connection factory with a JNDI name that already exists: 'jndiName'.
|
Description
| Attempting to create a connection factory with a JNDI name that already exists: 'jndiName'.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199135
|
Error: Attempting to create a connection factory with a Resource Link that already exists: 'resourceLink'.
|
Description
| Attempting to create a connection factory with a Resource Link that already exists: 'resourceLink'.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199136
|
Error: There was a problem verifying the JNDI name of the outbound connection: jndiName, msg
|
Description
| There was a problem verifying the JNDI name of the outbound connection: jndiName, msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199137
|
Error: The ManagedConnectionFactory class implementation 'mcfClassName' does not implement the ResourceAdapterAssociation interface and does not implement setResourceAdapter() and/or getResourceAdapter().
|
Description
| The ManagedConnectionFactory class implementation 'mcfClassName' does not implement the ResourceAdapterAssociation interface and does not implement setResourceAdapter() and/or getResourceAdapter().
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199138
|
Error: Unable to set the ResourceAdapter class for the mcf 'mcfClassName', msg
|
Description
| Unable to set the ResourceAdapter class for the mcf 'mcfClassName', msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199139
|
Error: Unexpected exception thrown by resource adapter's ManagedConnectionFactory implementation 'mcfClassName', msg
|
Description
| Unexpected exception thrown by resource adapter's ManagedConnectionFactory implementation 'mcfClassName', msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199140
|
Error: Could not find the managed connection factory class 'mcfClassName', msg
|
Description
| Could not find the managed connection factory class 'mcfClassName', msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199141
|
Error: Failed to instantiate the Resource Adapter's implementation of the ManagedConnectionFactory class 'mcfClassName, msg
|
Description
| Failed to instantiate the Resource Adapter's implementation of the ManagedConnectionFactory class 'mcfClassName, msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199142
|
Error: Unable to access the Resource Adapter's implementation of the ManagedConnectionFactoryClass 'mcfClassName', msg
|
Description
| Unable to access the Resource Adapter's implementation for the ManagedConnectionFactoryClass 'mcfClassName', msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199143
|
Error: Internal WebLogic Server Connector Error: Failed to get the connection pool for jndiName: 'jndiName'.
|
Description
| Internal WebLogic Server Connector Error: Failed to get the connection pool for jndiName: 'jndiName'.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Please contact BEA support.
|
|
|
BEA-199144
|
Error: A Resource Adapter may only be accessed from within the same application from which it was deployed.
|
Description
| A Resource Adapter may only be accessed from within the same application from which it was deployed.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199145
|
Error: Operation is not supported, raName, msg
|
Description
| Operation is not supported, raName, msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199146
|
Error: If only a weblogic-ra.xml has been specified for the resource adapter, it must be a linkref.
|
Description
| If only a weblogic-ra.xml has been specified for the resource adapter, it must be a linkref.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199147
|
Error: The resource adapter only has a weblogic-ra.xml specified. It also needs the ra.xml.
|
Description
| The resource adapter only has a weblogic-ra.xml specified. It also needs the ra.xml.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199148
|
Error: Error Creating Native Lib Directory: path
|
Description
| Error Creating Native Lib Directory: path
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199149
|
Error: FileNotFoundException when creating native lib dir for displayName
|
Description
| FileNotFoundException when creating native lib dir for displayName
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199150
|
Error: Failure while creating native library directory for displayName, msg
|
Description
| Failure while creating native library directory for displayName, msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199151
|
Error: There was an error starting the pool: msg
|
Description
| There was an error starting the pool: msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199152
|
Error: test-frequency-seconds is set to non-zero
|
Description
| test-frequency-seconds is set to non-zero
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199153
|
Error: Connection Testing cannot be enabled for a pool when the ManagedConnectionFactory does not implement ValidatingManagedConnectionFactory. The following invalid settings have been detected:
|
Description
| Connection Testing cannot be enabled for a pool when the ManagedConnectionFactory does not implement ValidatingManagedConnectionFactory. The following invalid settings have been detected:
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199154
|
Error: Work instance passed in to the WorkManager is null.
|
Description
| Work instance passed in to the WorkManager is null.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199155
|
Error: The Work Manager is currently not accepting doWork() calls.
|
Description
| The Work Manager is currently not accepting doWork() calls.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199156
|
Error: The Work Manager is currently suspended. New Work is not being accepted.
|
Description
| The Work Manager is currently suspended. New Work is not being accepted.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199157
|
Error: Unable to establish Execution Context and/or enlist Work in imported transaction, msg
|
Description
| Unable to establish Execution Context and/or enlist Work in imported transaction, msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199158
|
Error: Global tx id 'gid' not associated with specified Work instance
|
Description
| Global tx id 'gid' not associated with specified Work instance
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199159
|
Error: Global tx id 'gid' not registered with the Work Manager
|
Description
| Global tx id 'gid' not registered with the Work Manager
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199160
|
Error: The element was deprecated in WebLogic Server 7.0 and is no longer supported. Please remove the element from the weblogic-ra.xml for the Resource Adapter.
|
Description
| The element was deprecated in WebLogic Server 7.0 and is no longer supported. Please remove the element from the weblogic-ra.xml for the Resource Adapter.
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
| |
|
BEA-199161
|
Error: Work instance with global tx id 'gid' already active; conncurrent work disallowed.
|
Description
| Work instance with global tx id 'gid' already active; conncurrent work disallowed.
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199162
|
Error: Bad ManagedConnectionFactory class specification for class 'mcfClassName' : mcfErrors
|
Description
| Bad ManagedConnectionFactory class specification for class 'mcfClassName' : mcfErrors
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199163(retired)
|
Error: For property "propName" of type "propType" and value "propValue", a duplicate property was found in the descriptor and was set again.
|
Description
| For property "propName" of type "propType" and value "propValue", a duplicate property was found in the descriptor and was set again.
|
|
Cause
| The deployment descriptor for the resource adapter contains a duplicate property for the object being configured.
|
|
Action
| Edit the deployment descriptor to remove the duplicate entry if necessary.
|
|
|
BEA-199164
|
Error: Unable to activate the pool, msg
|
Description
| Unable to activate the pool, msg
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199165
|
Error: test-connections-on-create is set to true
|
Description
| test-connections-on-create is set to true
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199166
|
Error: test-connections-on-release is set to true
|
Description
| test-connections-on-release is set to true
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199167
|
Error: test-connections-on-reserve is set to true
|
Description
| test-connections-on-reserve is set to true
|
|
Cause
| Check the logs for the cause of this exception.
|
|
Action
| Inspect the cause and take action accordingly.
|
|
|
BEA-199168
|
Error: Unable to force log rotation: The connection pool for "poolKey" is configured to use the server log.
|
Description
| Unable to force log rotation: The connection pool for "poolKey" is configured to use the server log.
|
|
Cause
| Log rotation cannot be forced for pools which are configured to use the server log.
|
|
Action
| Change the pools logging parameters to use a different log other than the server log.
|
|
|
BEA-199169
|
Error: Failed to get the Connection Factory for the pool "key", err
|
Description
| Failed to get the Connection Factory for the pool "key", err
|
|
Cause
| See the details of the error message for more information.
|
|
Action
| See the details of the error message for more information.
|
|
|
BEA-199170
|
Error: For the setting action: "configuredUser" has higher privileges than the deployment user: "currentUser".
|
Description
| For the setting action: "configuredUser" has higher privileges than the deployment user: "currentUser".
|
|
Cause
| The deployment user does not have the privileges to perform the current deployment action.
|
|
Action
| Try the deployment action with admin privileged user.
|
|
|
BEA-199171
|
Error: The security-principal-map is not a valid element.
|
Description
| The security-principal-map is not a valid element. You will need to define the mapping using the console.
|
|
Cause
| The security-principal-map is not a valid element. You will need to define the mapping using the console.
|
|
Action
| Define the mapping using the console.
|
|
|
BEA-199172
|
Error: The following error occurred in the ra.xml: msg
|
Description
| While doing doing validation on the resource adapter, the following error occurred in the ra.xml: msg
|
|
Cause
| Refer to the text of the message for the description of the problem and the likely cause.
|
|
Action
| Correct the problem in the ra.xml file
|
|
|
BEA-199173
|
Error: The following error occurred in the weblogic-ra.xml: msg
|
Description
| While doing doing validation on the resource adapter, the following error occurred in the weblogic-ra.xml: msg
|
|
Cause
| Refer to the text of the message for the description of the problem and the likely cause.
|
|
Action
| Correct the problem in the weblogic-ra.xml file
|
| | | | | | | | |
|
