|
169800
|
Error: A PooledConnectionFactory object with an invalid external version of version was found
|
Description
| A PooledConnectionFactory could not be read from JNDI because the version of WebLogic Server that stored it is not compatible with the version that is retrieving it. |
|
Cause
| The version of WebLogic Server that stored it is not compatible with the version that is retrieving it. |
|
Action
| Contact BEA support. |
|
|
169801
|
Error: The JMS method methodName may not be called inside an EJB or servlet
|
Description
| The application code attempted to call a method on the JMS API that is not allowed by the J2EE specifications. Certain methods are restricted for use by the application server so that it can maintain a pool of JMS objects. |
|
Cause
| The application code has violated the J2EE specifications. |
|
Action
| Change the code to avoid calling the specified method. |
|
|
169802
|
Error: Cannot create a wrapped JMS connection using a username and password when the res-auth element is set to Container
|
Description
| An EJB or servlet was deployed using a JMS connection factory resource that has a res-auth setting of Container, but the application code attempted to open a JMS connection using a username and password. In this case, the username and password are supplied by WebLogic Server. |
|
Cause
| The application code is not using the J2EE APIs properly. |
|
Action
| Either remove the username and password, or set the res-auth element to Application. |
|
|
169803
|
Error: JNDI lookup of the JMS connection factory name failed
|
Description
| The server attempted to look up a JMS connection factory at the specified location, but the lookup failed. |
|
Cause
| The remote JNDI server or JMS server is not available, or the name was incorrectly specified. |
|
Action
| Check that the server is running, and check the name in the deployment descriptor XML files. |
|
|
169804
|
Error: Cannot use a JMS connection factory because the object is of the wrong type
|
Description
| A JMS connection factory that was retrieved from JNDI is either a QueueConnectionFactory when a TopicConnectionFactory was expected, or vice versa, or the object is of neither type. |
|
Cause
| Either the name of the connection factory in the deployment descriptor XML files is wrong, or the wrong object was bound into JNDI. |
|
Action
| Check the name in the XML files against what is actually registered in JNDI. |
|
|
169805
|
Error: A pooled JMS connection is being closed because an error was detected on the connection: msg
|
Description
| There was a problem with a JMS connection that was being used in a servlet or EJB. The connection has been closed, and will be re-opened the next time it is used if possible. |
|
Cause
| The JMS server is unavailable, or there is some other problem with it that makes it impossible to send or receive messages. |
|
Action
| Check the configuration parameters for the JMS server, and check that it is available on the network. |
|
|
169806
|
Error: Cannot use a JMS destination because the object is of the wrong type
|
Description
| A JMS destination is either a Queue when a Topic was expected, or vice versa, or the object is of neither type. |
|
Cause
| Change the application to use a valid destination type. |
|
Action
| Change the application to use a valid destination type. |
|
|
169807
|
Warning: There was an error while making the initial connection to the JMS resource named poolName from within an EJB or a servlet. The server will attempt the connection again later. The error was errorMsg
|
Description
| When an EJB, JSP, or servlet that uses a JMS connection factory as a resource-reference is first deployed, the server tries to connect to the JMS provider. The server will attempt the connection again later when the JMS resource is actually used. |
|
Cause
| See the error message from the JMS provider. |
|
Action
| No action necessary. |
|
|
169808
|
Warning: There was an error while making the initial connection to the JMS resource named poolName from the EJB "ejbName" inside application "appName". The server will attempt the connection again later. The error was errorMsg
|
Description
| When an EJB, that uses a JMS connection factory as a resource-reference is first deployed, the server tries to connect to the JMS provider. The server will attempt the connection again later when the JMS resource is actually used. |
|
Cause
| See the error message from the JMS provider. |
|
Action
| No action necessary. |
|
|
169809
|
Error: An error occurred while registering the JMS connection with JTA
|
Description
| An error occurred while attempting to register a JMS session resource with the transaction system. |
|
Cause
| The JMS connection factory specified does not properly support XA, or something is wrong with the transaction system. |
|
Action
| Check the linked exception, and verify that the JMS provider properly supports XA. |
|
|
169810
|
Error: An error occurred while committing or rolling back a JTA transaction used for a JMS operation by the J2EE container
|
Description
| The transaction system was unable to commit or rollback a transaction that the J2EE container started in order to handle a JMS operation. |
|
Cause
| There was a problem with the transaction system. |
|
Action
| See the linked exception for more information. |
|
|
169811
|
Error: The JMS object may not be used because it has been closed
|
Description
| The "close" method has been closed on a JMS object, so it is no longer possible to invoke methods on the object. |
|
Cause
| The object has been closed. |
|
Action
| This is a programming error and should be fixed on the users's part. |
|
|
169812
|
Error: The pooled JMS session is enlisted in another transaction and may not be used elsewhere
|
Description
| A pooled JMS session is enlisted in a transaction, and it either may not be used in another transaction, or it may not be used outside a transaction. |
|
Cause
| Check the application code to ensure that a pooled JMS session (retrieved from the JNDI java:comp/env/jms context) is not kept between transactions. It should be closed so that it is returned to the pool. |
|
Action
| Check the application code. |
|
|
169813
|
Warning: There was an error while closing a JMS session pool or a pooled JMS connection: errorMsg The pool or object was forcibly closed.
|
Description
| The session pool or pooled connection object encountered an error while closing, but it was closed anyway. |
|
Cause
| See the linked exception for more information. |
|
Action
| No action required. |
|
|
169814
|
Error: The JMS session pool has been disabled
|
Description
| The resource pool subsystem has disabled the JMS session pool, so it may not be used. |
|
Cause
| An administrative action was taken. |
|
Action
| Re-enable the session pool. |
|
|
169815
|
Error: A JMS session pool could not be created because the propName property was not specified
|
Description
| A JMS session pool was either created directly by the user or by internal container code, and it did not properly specify a property. |
|
Cause
| If the JMSSessionPool class is not being used directly by the user, then this is an internal error. |
|
Action
| Contact BEA support. |
|
|
169816
|
Error: The JMS session pool is shutting down
|
Description
| An operation was attempted against a JMS session pool, but the pool is in the middle of shutting down. |
|
Cause
| The pool is being shut down, possibly because of an error. |
|
Action
| Check for other errors that indicate why the pool is being shut down, and retry the operation. |
|
|
169817
|
Warning: The JMS connection factory resource resName declared in the EJB "ejbName" as part of application "appName" does not support XA. It cannot be used inside a transaction context.
|
Description
| The a JMS connection factory was defined as a resource-reference for the specified EJB. Since the connection factory does not support XA, it may not be used inside a transaction context, or an exception will be thrown. |
|
Cause
| If the specified JMS connection factory is intended to be used inside a transaction context, then the EJB was configured improperly. |
|
Action
| If the specified JMS connection factory is intended for use inside a transaction context, then the connection factory used by the EJB must be changed so that it supports XA, or the EJB descriptor must be changed to point to a different connection factory. However, if the connection factory will never be used inside a transaction context, then no action is necessary. |
|
|
169818
|
Warning: The JMS connection pool named "poolName" has a configured connection factory JNDI name of "jndiName". However, an object that is not a javax.jms.ConnectionFactory is bound to that JNDI name. The object bound to that JNDI name has type "clazz".
|
Description
| The JMS connection pool named "poolName" has a configured connection factory JNDI name of "jndiName". However, an object that is not a javax.jms.ConnectionFactory is bound to that JNDI name. The object bound to that JNDI name has type "clazz". |
|
Cause
| An object other than a ConnectionFactory is bound to the configured JNDI name of the connection pool. |
|
Action
| Either change the JNDI name of the JMS connection pool property or change the JNDI name of the object that is currently bound into JNDI. |
|
|
169819
|
Error: There was an error with a resource pool used to pool JMS sessions
|
Description
| The resource pool subsystem detected an error which makes the JMS session pool unusable. |
|
Cause
| There is a problem with the resource pool. |
|
Action
| See the linked exception for details. |
|
|
169820
|
Error: A JMS message consumer could not be created using a temporary queue or topic that was created using another connection
|
Description
| TemporaryQueue and TemporaryTopic objects, once created, may only be used to create message consumers when the consumers were created using the same connection that was used to create the temporary destination. |
|
Cause
| Application programming error. |
|
Action
| Change application code. |
|
|
169821
|
Error: Error creating or instantiating a wrapper for class name
|
Description
| The server was not able to create a wrapper for the specified class. The wrapper is used to intercept certain methods from the JMS provider to provide WebLogic Server-specific behavior. |
|
Cause
| There may be an error with the classpath, or with the underlying JMS providers code. |
|
Action
| Check the classpath. If this does not fix the problem, contact BEA support. |
|
|
169822
|
Error: Unable to use a wrapped JMS session in the transaction because two-phase commit is not available
|
Description
| An EJB or servlet attempted to use a wrapped JMS session that it acquired from a resource-ref inside a transaction context, but the JMS session cannot participate in the transaction because two-phase commit is not available from the connection factory. |
|
Cause
| The JMS connection factory specified does not support two-phase commit. |
|
Action
| For WebLogic JMS, two-phase commit may be enabled by setting the "UserTransactionsEnabled" flag on the JMS connection factory. For other JMS providers, you must specify a JMS connection factory that supports XA. |
|
|
169823
|
Error: Failure occured on createQueueConnection. Unexpected return type.
|
Description
| User call to createQueueConnection() returned an unexpected type class. |
|
Cause
| Probable cause is the JMS 1.1 ConnectionFactory with the JMS 1.0.2 createQueueConnection() API. Some JMS providers do NOT support backward compatibility. |
|
Action
| Either change the API call to createConnection() or change the connection factory type to QueueConnectionFactory. |
|
|
169824
|
Error: Failure occured on createTopicConnection. Unexpected return type.
|
Description
| User call to createTopicConnection() returned an unexpected type class. |
|
Cause
| Probable cause is the JMS 1.1 ConnectionFactory with the JMS 1.0.2 createTopicConnection() API. Some JMS providers do NOT support backward compatibility. |
|
Action
| Either change the API call to createConnection() or change the connection factory type to TopicConnectionFactory. |
|
