ERROR: Unknown exception while handling request: val1
説明
The EJB container encountered an unknown exception val1 while handling a request.
アクション
Note the type of exception, including message and stack trace (ifany). Contact BEA Customer Support.
2
WARN: Zombie stateless bean instance removed ...
説明
The EJB container found a zombie stateless object in its memory.
アクション
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
説明
A stateless session bean instance of val1, using a Bean Managed Transaction, did notcommit/rollback the transaction that it initiated. The EJB Containerreceived an exception val2 while taking corrective action.
アクション
Make sure that all methods of the stateless session bean commit/rollbackthe transaction before returning control back to the EJB container.
4
WARN: Rolling back active transaction for stateless session bean val1 using bean managed transaction ...
説明
A stateless session bean instance of val1, using the Bean Managed Transaction, did notcommit/rollback the transaction that it initiated. The EJB containertook corrective action.
アクション
None.
5
ERROR: Failed detaching bean val1 from global transaction
説明
The EJB container received an error while disassociating stateless objectval1 from global transaction.
アクション
Contact BEA Customer Support.
6
ERROR: No such bean val1 exists or the bean is already removed
説明
An application tried to use a bean that does not exist, or that is already removed.
アクション
This is an application error. Correct the application. Also, make sure beans are deployed in EJB containersthat have access to a persistence store of deployed beans.
8
ERROR: Caught exception while making checks for BMT StatefulSession Bean: val1 in deactivate val2
説明
This is an internal error.
アクション
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
説明
A method of a bean that implements the Mandatory transaction policy must becalled within a transaction.
アクション
Make sure a method with a declarative transaction policy of Mandatory isnot called without a global transaction.
10
ERROR: Method val1 of bean val2 implementing Never transaction policy cannot be called in a transaction
説明
A method of a bean that implements the Never transaction policy must not becalled within a transaction.
アクション
Make sure a method with a declarative transaction policy of Never isnot called within a global transaction.
13
ERROR: Problem clearing global aom entry val1
説明
This is an internal error that occurred while performing actions in transactionsynchronization callbacks.
アクション
Contact BEA Customer Support and provide val1.
15
ERROR: Unknown exception in txInInvocation: val1
説明
The EJB container received unknown exception val1 while performingactions in transaction synchronization callbacks.
アクション
Contact BEA Customer support and provide val1.
16
ERROR: Problem synchronizing tx val1 with tuxedo for val2
説明
This is an internal error.
アクション
Contact BEA Customer Support and provide val2.
17
ERROR: Context is still transactional after clearing it!
説明
This is an internal error that occurred while cleaning up the transactional context ofthe thread.
アクション
Contact BEA Customer Support.
18
ERROR: txClose failed in release!
説明
This is an internal error.
アクション
Contact BEA Customer Support.
19
ERROR: Received invalid primary key val1 while creating Remote Object val2
説明
The EJB container encountered problems while creating a remote objectval2. The primary key given by the bean or generated by the containerfor session beans is not in the proper format.
アクション
If the bean is an entity bean, make sure the primary key can beserialized. If it is a session bean, contact BEA Customer Support.
20
ERROR: Unknown exception while creating Remote Object val1 : val2
説明
An unknown exception occurred while creating a Remote Object.
アクション
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 Supportand provide val2.
21
ERROR: PersistenceStore:exist error: for bean val1 : val2
説明
The EJB container received an exception while checking the existence ofthe state of bean val1 in persistence store.
アクション
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 ofcontainer-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
説明
The EJB container received an error val2 while reading the state of bean val1from persistence store.
アクション
If bean val1 is anentity bean, make sure persistence store is set up correctly. If bean val1 is a stateful session bean, read about the limitations ofcontainer-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
説明
The EJB container received an error val2 while writing the state of bean val1in persistence store.
アクション
If bean val1 is anentity bean, make sure persistence store is set up correctly. If bean val1 is a stateful session bean, read about the limitations ofcontainer-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
説明
The EJB container received an error val2 while removing the state of beanval1 from persistence store.
アクション
Make sure bean val1 has not already been removed. If bean val1 is a statefulsession bean, read about the limitations of container-managed conversationalstate 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
説明
Exception val2 occurred while deploying bean val1.
アクション
Make sure the deployable JAR contains a compliant deployment descriptor.
29
ERROR: While deploying jar val1 : val2
説明
Exception val2 occurred while deploying JAR val1.
アクション
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
説明
If a method of a bean that implements the Required or RequiresNewtransaction policy is called without a transaction, the container is supposed to automaticallystart a new transaction; however, the container was unable to start thenew transaction because the bean was already involved in another transaction.
アクション
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
説明
If a method of a bean that implements the RequiresNewtransaction policy is called within a transaction, the container is supposedto automaticallystart a new transaction; however, the container was unable to start thenew transaction because the bean was already involved in another transaction.
アクション
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
説明
アクション
関連項目
33[TAG]WLE51
WARN: While undeploying jar val1 : val2
説明
While undeploying the specified JAR module given by val1, the error given by val2 occurred.
アクション
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
説明
アクション
関連項目
35
ERROR: Unknown exception while handling request: val
説明
The EJB container produced an unknown exception val while handling arequest.
アクション
Write down the type of exception along with the message and the stack trace, ifany, and contact BEA Customer Support.
36
ERROR: Bean val is being deployed
説明
アクション
関連項目
37[TAG]WLE51
ERROR: Module val is already deployed
説明
The module specified by val is already deployed and the deployment request has been rejected. The currently deployed module should be unaffected.
アクション
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 correctmodule name, choose a different name for the module you are deploying.
関連項目
38[TAG]WLE51
ERROR: Incompatible change of previously deployed module val
説明
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.
アクション
Make sure that you entered the correct name for the module, or choose a different name for the module.
関連項目
39[TAG]WLE51
ERROR: No jarfile specified for module val
説明
No .jar file was found for the module specified by val. The deployment request has been rejected.
アクション
Make sure that either the UBBCONFIG file or the tmadmin command used to deploy this module has a .jar file specified.
関連項目
40[TAG]WLE51
ERROR: Problems opening jar file for module val1val2
説明
An exception was encountered while trying to open the JAR file for module val1. The exception is given by val2.
アクション
Check that the JAR file exists, that it is a valid JAR file, and that read permission has been granted.
関連項目
41[TAG]WLE51
ERROR: val descriptor was changed
説明
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.
アクション
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[TAG]WLE51
ERROR: Problems opening jar file for module val1val2
説明
A val2 exception was thrown while trying to read some of the contents of the JAR file for module val1.
アクション
Check that the JAR file exists, that it is a valid JAR file, and that read permission has been granted.
関連項目
43[TAG]WLE51
INFO: Module val successfully deployed
説明
This is an informational message to inform you that the EJB module specified by val was successfully deployed by the JavaServer.
アクション
None.
関連項目
44[TAG]WLE51
INFO: EJB module val successfully undeployed
説明
This is an informational message to inform you that the EJB module specified by val was successfully undeployed by the JavaServer.
アクション
None.
関連項目
45[TAG]WLE51
ERROR: Unknown exception val1 while deploying module val2
説明
A val1 exception was encountered while deploying the module val2.
アクション
Depending on the exception, you should probably contact your local system administrator. If the problem persists, contact BEA Customer Support.
関連項目
46[TAG]WLE51
ERROR: Failed attaching bean val to global transaction
説明
アクション
関連項目
47[TAG]WLE51
WARN: Problem during val1 serializing field val2, field is not saved
説明
There was a problem while writing to the persistence-store-file or while reading from the persistence-store-file.
アクション
Check for the persistence-store-descriptor properties in theweblogic-ejb-extensions.xmlfile, and make sure the directories have the right permission and that the disk is not full.If the problem persists, contact BEA Customer Support.
48
ERROR: Failed detaching bean val from global transaction
説明
The EJB container received an error while disassociating a stateless objectval from a global transaction.
アクション
Contact BEA Customer Support.
49
ERROR: Problem clearing global aom entry val
説明
This is an internal error that occurred while performing actions in transactionsynchronization callbacks.
アクション
Contact BEA Customer Support and provide val.
50[TAG]WLE51
ERROR: discardInstance could not set aom flags to override