|
|
1 |
ERROR: Unknown exception while handling request : val1 | |
|
Description |
The EJB Container encountered an unknown exception val1 while handling a request. |
Action |
Note the type of exception, including message and stack trace (if any). Contact BEA Customer Support. | |
2 |
WARN: Zombie stateless bean instance removed ... | |
|
Description |
The EJB Container found a zombie stateless object in its memory. |
Action |
Ignore. The EJB Container takes care of this event. | |
3 |
ERROR: Caught exception while rolling back bean managed transaction for stateless session bean val1:val2 | |
|
Description |
A stateless session bean instance of val1, using a Bean Managed Transaction, did not commit/rollback the transaction that it initiated. The EJB Container received an exception val2 while taking corrective action. |
Action |
Make sure that all methods of the stateless session bean commit/rollback the transaction before returning control back to the EJB Container. | |
4 |
WARN: Rolling back active transaction for stateless session bean val1 using bean managed transaction ... | |
|
Description |
A stateless session bean instance of val1, using the Bean Managed Transaction, did not commit/rollback the transaction that it initiated. The EJB Container took corrective action. |
Action |
None. | |
5 |
ERROR: Failed detaching bean val1 from global transaction. | |
|
Description |
The EJB Container received an error while disassociating stateless object val1 from global transaction. |
Action |
Contact BEA Customer Support. | |
6 |
ERROR: No such bean val1 exists or the bean is already removed. | |
|
Description |
An application tried to use a bean that does not exist, or that is already removed. |
Action |
This is an application error. Correct the application. Also, make sure beans are deployed in EJB Containers that have access to a persistence store of deployed beans. | |
7 |
ERROR: Failed to associate BMT StatefulSession Bean val1 in global aom. | |
|
Description |
This is an internal error. |
Action |
Contact BEA Customer Support. | |
8 |
ERROR: Caught exception on while making checks for BMT StatefulSession Bean : val1 in deactivate. val2 | |
|
Description |
This is an internal error. |
Action |
Contact BEA Customer Support with exception val2 trace. | |
9 |
ERROR: Method val1 of bean val2 implementing Mandatory transaction policy cannot be called without a transaction. | |
|
Description |
A method of a bean that implements the |
Action |
Make sure a method with a declarative transaction policy of | |
10 |
ERROR: Method val1 of bean val2 implementing Never transaction policy can not be called in a transaction. | |
|
Description |
A method of a bean that implements the |
Action |
Make sure a method with a declarative transaction policy of | |
11 |
ERROR: Stateless object val1 is still involved in transaction! Check deactivation logic for Stateless objects. | |
|
Description |
This is an internal error. An exceptional condition occurred after a method invocation on a stateless object (stateless bean or home) that was involved in a global transaction. The exceptional condition might have prevented the EJB Container from disassociating the stateless object from a global transaction. |
Action |
Contact BEA Customer Support. | |
12 |
ERROR: Problem detaching bean val1 from global transaction. | |
|
Description |
This is an internal error. |
Action |
Contact BEA Customer Support. | |
13 |
ERROR: Problem cleaning up val1 | |
|
Description |
This is an internal error that occurred while performing actions in transaction synchronization callbacks. |
Action |
Contact BEA Customer Support and provide val1. | |
14 |
ERROR: Unknown Tx policy for val1 | |
|
Description |
The EJB Container could not recognize the transaction policy of the bean identified by val1. |
Action |
Contact BEA Customer support and provide val1. | |
15 |
ERROR: Unknown exception in txInInvocation : val1 | |
|
Description |
The EJB Container received unknown exception val1 while performing actions in transaction synchronization callbacks. |
Action |
Contact BEA Customer support and provide val1. | |
16 |
ERROR: Problem synchronizing tx val1 with tuxedo for val2 | |
|
Description |
This is an internal error. |
Action |
Contact BEA Customer Support and provide val2. | |
17 |
ERROR: Context is still transactional after clearing it! | |
|
Description |
This is an internal error that occurred while cleaning up the transactional context of the thread. |
Action |
Contact BEA Customer Support. | |
18 |
ERROR: txClose failed in release! | |
|
Description |
This is an internal error. |
Action |
Contact BEA Customer Support. | |
19 |
ERROR: Received invalid primary key val1 while creating Remote Object val2 | |
|
Description |
The EJB Container encountered problems while creating a remote object val2. The primary key given by the bean or generated by the Container for Session beans is not in the proper format. |
Action |
If the bean is an entity bean, make sure the primary key can be serialized. If it is a session bean, contact BEA Customer Support. | |
20 |
ERROR: Unknown exception while creating Remote Object val1:val2 | |
|
Description |
An unknown exception occurred while creating a Remote Object. |
Action |
If the bean is an entity bean, make sure the primary key of the bean can be serialized. If the bean is a session bean, contact BEA Customer Support and provide val2. | |
21 |
ERROR: PersistenceStore:exist error: for bean val1 : val2 | |
|
Description |
The EJB Container received an exception while checking the existence of the state of bean val1 in persistence store. |
Action |
If bean val1 is an entity bean, make sure the correct schema is created in persistence store for a given bean. If bean val1 is a stateful session bean, read about the limitations of container-managed conversational state in BEA WebLogic Enterprise Getting Started. If this does not correct the problem, contact BEA Customer Support. | |
22 |
ERROR: PersistenceStore:read error: for bean val1 : val2 | |
|
Description |
The EJB Container received an error val2 while reading the state of bean val1 from persistence store. |
Action |
If bean val1 is an entity bean, make sure persistence store is set up correctly. If bean val1 is a stateful session bean, read about the limitations of container-managed conversational state in BEA WebLogic Enterprise Getting Started. If this does not correct the problem, contact BEA Customer Support. | |
23 |
ERROR: PersistenceStore:write error: for bean val1 : val2 | |
|
Description |
The EJB Container received an error val2 while writing the state of bean val1 in persistence store. |
Action |
If bean val1 is an entity bean, make sure persistence store is set up correctly. If bean val1 is a stateful session bean, read about the limitations of container-managed conversational state in BEA WebLogic Enterprise Getting Started. If this does not correct the problem, contact BEA Customer Support. | |
24 |
ERROR: PersistenceStore:remove error: for bean val1 : val2 | |
|
Description |
The EJB Container received an error val2 while removing the state of bean val1 from persistence store. |
Action |
Make sure bean val1 has not already been removed. If bean val1 is a stateful session bean, read about the limitations of container-managed conversational state in BEA WebLogic Enterprise Getting Started. If this does not correct the problem, contact BEA Customer Support. | |
27 |
ERROR: Unknown exception val1 while deploying jar val2 | |
|
Description |
An unexpected exception occurred while deploying a jar file. |
Action |
Correct the problem specified in the exception message and redeploy the jar file. | |
28 |
ERROR: While deploying bean val1 : val2 | |
|
Description |
Exception val2 occured while deploying bean val1. |
Action |
Make sure the deployable jar contains a compliant deployment descriptor. | |
29 |
ERROR: While deploying jar val1 : val2 | |
|
Description |
Exception val2 occured while deploying jar val1. |
Action |
Fix the problem specified in the exception message and redeploy the jar. | |
30 |
ERROR: Method val of bean val with Required/RequiresNew transaction policy was called without transaction but the bean is already involved in another transaction | |
|
Description |
If a method of a bean that implements the |
Action |
This is an application error. Notify the programmer. | |
31 |
ERROR: Method val of bean val with RequiresNew transaction policy was called while bean is already involved in another transaction | |
|
Description |
If a method of a bean that implements the |
Action |
This is an application error. Notify the programmer. | |
32 |
ERROR: Method val of bean val with NotSupported transaction policy was called when bean was already is involved in another transaction | |
|
Description |
|
Action |
| |
33 |
WARN: While undeploying jar val : val | |
|
Description |
|
Action |
| |
34 |
ERROR: Bean val is being deployed | |
|
Description |
|
Action |
| |
35 |
ERROR: Unknown exception while handling request : val1 | |
|
Description |
The EJB Container produced an unknown exception val1 while handling a request. |
Action |
Write down the type of Exception with the message and the stack trace, if any. Contact BEA Customer Support. | |
36 |
ERROR: Bean val is being deployed | |
|
Description |
|
Action |
|
|
Copyright © 1999 BEA Systems, Inc. All rights reserved.
|