Skip navigation.

EJB Messages 0-99

  Previous

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 Mandatory transaction policy must be called within a transaction.

Action

Make sure a method with a declarative transaction policy of Mandatory is not called without a global transaction.

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 Never transaction policy must not be called within a transaction.

Action

Make sure a method with a declarative transaction policy of Never is not called within a global transaction.

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 Required or RequiresNew transaction policy is called without a transaction, the container is supposed to automatically start a new transaction; however, the container was unable to start the new transaction because the bean was already involved in another transaction.

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 RequiresNew transaction policy is called within a transaction, the container is supposed to automatically start a new transaction; however, the container was unable to start the new transaction because the bean was already involved in another transaction.

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


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


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.

 

Skip footer navigation  Back to Top Previous