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.i18n Localization package.
|
BEA-190000
|
Info: Initializing J2EE Connector Service
|
|
BEA-190001
|
Info: J2EE Connector Service initialized successfully
|
|
BEA-190002
|
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
|
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 of ex on createManagedConnection.
|
Description
| The connector service was unable to obtain a managed connection from the resource adapter because of the specified exception. |
|
Cause
| The cause should be evident from the exception. |
|
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
|
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
|
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
|
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
|
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
|
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 resurce adaptors configuration file. |
|
Action
| Ensure that a legal value for is specified. |
|
|
BEA-190072
|
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
|
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
|
Error: An error occurred while decrypting the EIS password for the poolName resource adapter.
|
Description
| An exception was thrown by the encyption 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
|
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
|
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 enlistement 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
|
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
|
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
|
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
|
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
|
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
|
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-199999
|
Debug: Stack trace for message id
|
Description
| Stack trace for previously logged message |
|
