![]() |
![]() |
|
|
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. | |
8 |
ERROR: Caught exception 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 cannot 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 | |
13 |
ERROR: Problem clearing global aom entry val1 | |
|
Description |
This is an internal error that occurred while performing actions in transaction synchronization callbacks. |
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 the 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 the 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 the 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 the BEA WebLogic Enterprise Getting Started. If this does not correct the problem, contact BEA Customer Support. | |
28 |
ERROR: While deploying bean val1 : val2 | |
|
Description |
Exception val2 occurred 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 occurred 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 involved in another transaction | |
|
Description |
|
Action |
| |
33 |
WARN: While undeploying jar val1 : val2 | |
|
Description |
While undeploying the specified JAR module given by val1, the error given by val2 occurred. |
Action |
Because the error occurred during undeployment, the module might have been only partially undeployed and is probably no longer able to be used. A subsequent redeployment of this module may also fail. Contact BEA Customer Support. | |
34 |
ERROR: Bean val is being deployed | |
|
Description |
|
Action |
| |
35 |
ERROR: Unknown exception while handling request: val | |
|
Description |
The EJB container produced an unknown exception val while handling a request. |
Action |
Write down the type of exception along with the message and the stack trace, if any, and contact BEA Customer Support. | |
36 |
ERROR: Bean val is being deployed | |
|
Description |
|
Action |
| |
37 |
ERROR: Module val is already deployed | |
|
Description |
The module specified by val is already deployed and the deployment request has been rejected. The currently deployed module should be unaffected. |
Action |
If you wish to deploy this module, you should undeploy the other module first. Otherwise, make sure you entered the correct name for the module. If you entered the correct module name, choose a different name for the module you are deploying. | |
38 |
ERROR: Incompatible change of previously deployed module val | |
|
Description |
A module with this name already exists, but it is of a different type (for example, CORBA versus EJB), and the request has been rejected. The currently deployed module should be unaffected. |
Action |
Make sure that you entered the correct name for the module, or choose a different name for the module. | |
39 |
ERROR: No jarfile specified for module val | |
|
Description |
No |
Action |
Make sure that either the | |
40 |
ERROR: Problems opening jar file for module val1 val2 | |
|
Description |
An exception was encountered while trying to open the JAR file for module val1. The exception is given by val2. |
Action |
Check that the JAR file exists, that it is a valid JAR file, and that read permission has been granted. | |
41 |
ERROR: val descriptor was changed | |
|
Description |
A redeployment is being requested, and the EJB descriptor specified by val has changed. This is not allowed. The new module will not be deployed. |
Action |
To redeploy, the new EJB descriptor must match the original. Otherwise, you will have to shut down and restart the server to change the descriptor. | |
42 |
ERROR: Problems opening jar file for module val1 val2 | |
|
Description |
A val2 exception was thrown while trying to read some of the contents of the JAR file for module val1. |
Action |
Check that the JAR file exists, that it is a valid JAR file, and that read permission has been granted. | |
43 |
INFO: Module val successfully deployed | |
|
Description |
This is an informational message to inform you that the EJB module specified by val was successfully deployed by the JavaServer. |
Action |
None. | |
44 |
INFO: EJB module val successfully undeployed | |
|
Description |
This is an informational message to inform you that the EJB module specified by val was successfully undeployed by the JavaServer. |
Action |
None. | |
45 |
ERROR: Unknown exception val1 while deploying module val2 | |
|
Description |
A val1 exception was encountered while deploying the module val2. |
Action |
Depending on the exception, you should probably contact your local system administrator. If the problem persists, contact BEA Customer Support. | |
46 |
ERROR: Failed attaching bean val to global transaction | |
|
Description |
|
Action |
| |
47 |
WARN: Problem during val1 serializing field val2, field is not saved | |
|
Description |
There was a problem while writing to the persistence-store-file or while reading from the persistence-store-file. |
Action |
Check for the persistence-store-descriptor properties in the
| |
48 |
ERROR: Failed detaching bean val from global transaction | |
|
Description |
The EJB container received an error while disassociating a stateless object val from a global transaction. |
Action |
Contact BEA Customer Support. | |
49 |
ERROR: Problem clearing global aom entry val | |
|
Description |
This is an internal error that occurred while performing actions in transaction synchronization callbacks. |
Action |
Contact BEA Customer Support and provide val. | |
50 |
ERROR: discardInstance could not set aom flags to override | |
|
Description |
|
Action |
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|