This chapter describes messages for errors with a EJB prefix.
EJB5013 |
Problem occurred while deserializing stateful bean state.
Solution:Check the application classpath to ensure that all classes needed during deserialization are available.
EJB5017 |
An error occurred during the removal of an entity bean. One common cause is when the application throws a system exception from the ejbRemove method of an entity bean.
Solution:Check the exception stack trace to see if the exception originated from the entity bean implementation class.
EJB5031 |
An error occurred while looking up a Read Only Bean Notifier. The most common cause for this failure is that the string supplied to the getReadOnlyBeanNotifier method either does not refer to a read-only bean.
Solution:Check the application code that calls this method to make sure the string passed in refers to a valid read-only bean.
EJB5069 |
The bean's Home or LocalHome does not define a no-arg create method.
Solution:Check the Home or LocalHome interface for the appropriate create method signature. Running the verifier will help identify the error as well.
EJB5071 |
Some problem occurred during the beforeCompletionphase of the transaction lifecycle. This error often happens when application code throws a system exception from its ejbStore method or if the transaction manager encounters a system exception.
Solution:Check the stack trace to see if the exception originated from the application's ejbStore method. Also check the resource configuration to ensure that all resource managers involved in the transaction are configured properly and are healthy.
EJB5090 |
Problem during EJB container runtime initialization. See stack trace for more details. Some common causes are global JNDI name conflicts, classnotfound errors, and configuration errors for resources needed by the EJB.
Solution:If the EJB has a Remote view, check that its JNDIname does not clash with any other EJB's JNDI name or any other globalJNDI name. Check that all needed classes are available to the EJB. Also ensure that any resources needed by the EJB are available. If the EJB uses a data source make sure the corresponding database is running. If it uses a queue makes sure the physical queue has been created.
EJB5111 |
This error indicates a mismatch in the required method signature rules between a method defined on a [Home, Remote, LocalHome, Local] interface and the corresponding bean implementation class. E.g., this would happen if a create method in a Home interface did not have a matching ejbCreate method in the bean class.
Solution:Run the verifier tool to check that the methods defined on the bean class are correct with respect to the exposed interface.
EJB5117 |
Error while creating the persistent representation of an EJB timer. This typically means there is some configuration error or runtime problem with the EJB timer service data source.
Solution:Double-check the JDBC data source (and its associated connection pool) assigned to the timer-data source element in domain.xml. Common causes are that the database is not running, the timer table has not been created within that database, or that the connection pool's JDBC driver URL information is incorrect.
EJB5128 |
A problem occurred while the container was activating a stateful session bean. One possible cause is that the bean code threw a system exception from its ejbActivate method.
Solution:Check the stack trace to see whether the exception was thrown from the ejbActivate method and if so double-check the application code to determine what caused the exception.
EJB5129 |
An error occurred during the afterCompletion phase of the transaction lifecycle.
Solution:Check stack trace for details of error encountered by EJB container
EJB5014 |
Exception resolving object
Cause:TBD
Solution:TBD
EJB5015 |
Exception while adding method monitoring mbean
Cause:TBD
Solution:TBD
EJB5016 |
Exception creating BaseContainer : [{0}]
Cause:TBD
Solution:TBD
EJB5018 |
An exception was thrown during an ejb invocation on [{0}]
Cause:TBD
Solution:TBD
EJB5019 |
Some application or system exception occurred : [{0}]
Cause:TBD
Solution:TBD
EJB5020 |
Exception while unregistering monitormbean
Cause:TBD
Solution:TBD
EJB5021 |
Session bean transaction is incomplete : [{0}]
Cause:TBD
Solution:TBD
EJB5022 |
Messagedriven bean transaction is incomplete : [{0}]
Cause:TBD
Solution:TBD
EJB5023 |
Exception while registering monitormbean
Cause:TBD
Solution:TBD
EJB5024 |
Exception while registering child monitormbean
Cause:TBD
Solution:TBD
EJB5024 |
Exception while unregistering child monitormbean : [{0}]
Cause:TBD
Solution:TBD
EJB5025 |
Exception while releasing ejb context : [{0}]
Cause:TBD
Solution:TBD
EJB5026 |
Exception in removing ejb local object : [{0}]
Cause:TBD
Solution:TBD
EJB5027 |
Exception in removing ejb : [{0}]
Cause:TBD
Solution:TBD
EJB5028 |
Exception in getting ejb local object : [{0}]
Cause:TBD
Solution:TBD
EJB5029 |
Exception getting ejb context : [{0}]
Cause:TBD
Solution:TBD
EJB5030 |
Exception while comparing ejbs : [{0}]
Cause:TBD
Solution:TBD
EJB5032 |
Exception in creating new bean : [{0}]
Cause:TBD
Solution:TBD
EJB5033 |
Illegal state exception occurred : [{0}]
Cause:TBD
Solution:TBD
EJB5035 |
Some application or unchecked exception occurred : [{0}]
Cause:TBD
Solution:TBD
EJB5039 |
Some runtime exception occurred : [{0}]
Cause:TBD
Solution:TBD
EJB5041 |
Exception while running postinvoke : [{0}]
Cause:TBD
Solution:TBD
EJB5042 |
Exception setting bean context : [{0}]
Cause:TBD
Solution:TBD
EJB5043 |
Exception cleaning up ejb subclass : [{0}]
Cause:TBD
Solution:TBD
EJB5044 |
Name not found exception : [{0}]
Cause:TBD
Solution:TBD
EJB5045 |
Class cast exception : [{0}]
Cause:TBD
Solution:TBD
EJB5048 |
Exception creating new attribute
Cause:TBD
Solution:TBD
EJB5049 |
Exception obtaining attribute [{0}]
Cause:TBD
Solution:TBD
EJB5050 |
Exception in printStackTrace
Cause:TBD
Solution:TBD
EJB5051 |
Exception in printStackTrace of super
Cause:TBD
Solution:TBD
EJB5052 |
Exception closing session : [{0}]
Cause:TBD
Solution:TBD
EJB5053 |
Exception closing server session pool : [{0}]
Cause:TBD
Solution:TBD
EJB5054 |
Exception closing topic session: [{0}]
Cause:TBD
Solution:TBD
EJB5055 |
Exception in init of ejb : [{0}]
Cause:TBD
Solution:TBD
EJB5056 |
Exception in undeploying the bean : [{0}]
Cause:TBD
Solution:TBD
EJB5057 |
Exception creating session : [{0}]
Cause:TBD
Solution:TBD
EJB5058 |
Exception creating sessionfilecachestore
Cause:TBD
Solution:TBD
EJB5058 |
Exception while getting ejb stub : [{0}]
Cause:TBD
Solution:TBD
EJB5059 |
Exception creating ejb object : [{0}]
Cause:TBD
Solution:TBD
EJB5060 |
Exception creating ejb local object [{0}]
Cause:TBD
Solution:TBD
EJB5061 |
Exception removing ejb : [{0}]
Cause:TBD
Solution:TBD
EJB5062 |
Exception removing bean : [{0}]
Cause:TBD
Solution:TBD
EJB5063 |
Some exception removing bean : [{0}]
Cause:TBD
Solution:TBD
EJB5064 |
Exception in afterCompletion : [{0}]
Cause:TBD
Solution:TBD
EJB5065 |
Exception in deserializing [{0}]
Cause:TBD
Solution:TBD
EJB5066 |
Some generic ejb exception : [{0}]
Cause:TBD
Solution:TBD
EJB5067 |
Exception activating ejb : [{0}]
Cause:TBD
Solution:TBD
EJB5068 |
Exception in serializing : [{0}]
Cause:TBD
Solution:TBD
EJB5070 |
Exception creating stateless session bean : [{0}]
Cause:TBD
Solution:TBD
EJB5072 |
Error initializing home of container: [{0}]
Cause:TBD
Solution:TBD
EJB5083 |
Error -- invalid maxMsgs prop = [{0}]
Cause:TBD
Solution:TBD
EJB5085 |
Error -- invalid msg bean pool size = [{0}]
Cause:TBD
Solution:TBD
EJB5087 |
[{0}]: Invalid value [{1}] for [{2}] , use [{3}] instead
Cause:TBD
Solution:TBD
EJB5088 |
Number format exception
Cause:TBD
Solution:TBD
EJB5089 |
Error -- invalid cleanup interval prop = [{0}]
Cause:TBD
Solution:TBD
EJB5091 |
Exception occurred in postInvoke : [{0}]
Cause:TBD
Solution:TBD
EJB5092 |
Exception occurred in postInvokeTx : [{0}]
Cause:TBD
Solution:TBD
EJB5093 |
Exception occured in passiveIdleBeans
Cause:TBD
Solution:TBD
EJB5094 |
container.getClassLoader() returned null
Cause:TBD
Solution:TBD
EJB5095 |
Exception occured in selectVictims()
Cause:TBD
Solution:TBD
EJB5096 |
Unable to lookup UserTransaction
Cause:TBD
Solution:TBD
EJB5097 |
Exception during undeploy
Cause:TBD
Solution:TBD
EJB5098 |
Exception in preInvokeTx
Cause:TBD
Solution:TBD
EJB5099 |
Exception in checkUnfinishedTx
Cause:TBD
Solution:TBD
EJB5100 |
Exception in useClientTx
Cause:TBD
Solution:TBD
EJB5101 |
Transaction Aborted
Cause:TBD
Solution:TBD
EJB5102 |
Unable to complete container-managed transaction
Cause:TBD
Solution:TBD
EJB5103 |
Exception in releaseContext
Cause:TBD
Solution:TBD
EJB5104 |
Exception in callEJBStore
Cause:TBD
Solution:TBD
EJB5105 |
Exception in createContainer
Cause:TBD
Solution:TBD
EJB5106 |
Exception in EntityContainer
Cause:TBD
Solution:TBD
EJB5107 |
Exception while getting server session
Cause:TBD
Solution:TBD
EJB5108 |
Unable to initialize EJB Timer Service. The likely cause is the database has not been started or the timer database table has not been created.
Cause:TBD
Solution:TBD
EJB5109 |
EJB Timer Service started successfully for datasource [{0}]
Cause:TBD
Solution:TBD
EJB5110 |
Attempt to override reserved ejb interface method [{0}] in [{1}]. Override will be ignored.
Cause:TBD
Solution:TBD
EJB5112 |
Error cancelling timer with pkey [{0}]
Cause:TBD
Solution:TBD
EJB5113 |
Error cancelling timers for container [{0}] and pkey [{1}]
Cause:TBD
Solution:TBD
EJB5114 |
Error destroying timers for container [{0}]
Cause:TBD
Solution:TBD
EJB5115 |
Error destroying timer [{0}]
Cause:TBD
Solution:TBD
EJB5116 |
Delivering missed timer for timer id [{0}]. Timer should have fired at [{1}]
Cause:TBD
Solution:TBD
EJB5118 |
Failure removing timer bean [{0}]
Cause:TBD
Solution:TBD
EJB5119 |
Expunging timer [{0}] after [{1}] failed deliveries
Cause:TBD
Solution:TBD
EJB5120 |
EJB Timer Service last shutdown at [{0}]
Cause:TBD
Solution:TBD
EJB5121 |
EJB Timer Service shutdown info [{0}] not found. Shutdown time unknown.
Cause:TBD
Solution:TBD
EJB5122 |
EJB Timer Service shutdown at [{0}]
Cause:TBD
Solution:TBD
EJB5123 |
Rolling back timed out transaction [{0}] for [{1}]
Cause:TBD
Solution:TBD
EJB5124 |
Commit Option A is not currently supported. Using Commit Option B for [{0}]
Cause:TBD
Solution:TBD
EJB5125 |
Cannot add idle bean cleanup task
Cause:TBD
Solution:TBD
EJB5126 |
Cannot add asynchronous task
Cause:TBD
Solution:TBD
EJB5127 |
Error during passivation of [{0}]
Cause:TBD
Solution:TBD
EJB5130 |
Error while adding idle bean passivator task
Cause:TBD
Solution:TBD
EJB5131 |
Error while adding idle bean removal task
Cause:TBD
Solution:TBD
EJB5132 |
Could not determine passivation directory
Cause:TBD
Solution:TBD
EJB5133 |
Error while creating SFSBStore manager
Cause:TBD
Solution:TBD
EJB5134 |
Error while removing idle beans
Cause:TBD
Solution:TBD
EJB5135 |
Error while removing expired beans
Cause:TBD
Solution:TBD
EJB5136 |
Creation of passivation directory failed for {0}
Cause:TBD
Solution:TBD
EJB5137 |
Initialization of store manager failed. Directory: {0}
Cause:TBD
Solution:TBD
EJB5138 |
Initialization of store manager failed
Cause:TBD
Solution:TBD
EJB5139 |
Error while loading bean state from store. Key: {0}
Cause:TBD
Solution:TBD
EJB5140 |
Error while loading bean state from store
Cause:TBD
Solution:TBD
EJB5141 |
Error while removing bean state from store. Key: {0}
Cause:TBD
Solution:TBD
EJB5142 |
Error while removing bean state from store
Cause:TBD
Solution:TBD
EJB5143 |
Error while removing passivation directory: {0}
Cause:TBD
Solution:TBD
EJB5144 |
Error while removing passivation directory
Cause:TBD
Solution:TBD
EJB5145 |
Error while undeploying store manager
Cause:TBD
Solution:TBD
EJB5146 |
Error while undeploying store manager
Cause:TBD
Solution:TBD
EJB5147 |
Error while saving bean state to store. Key: {0}
Cause:TBD
Solution:TBD
EJB5148 |
Error while saving bean state to store
Cause:TBD
Solution:TBD
EJB5149 |
Error while initializing file store manager {0}
Cause:TBD
Solution:TBD
EJB5150 |
Error while initializing file store manager
Cause:TBD
Solution:TBD
EJB5151 |
Error while creating enterprise bean context for {0} during jacc callback
Cause:TBD
Solution:TBD
EJB5152 |
No methods registered yet for monitoring for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5153 |
Error while registering method {3} for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5154 |
Unexpected error while registering method {3} for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5155 |
Error while unregistering method {3} for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5156 |
Unexpected error while unregistering method {3} for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5157 |
Error while registering container stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5158 |
Unexpected error while registering container stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5159 |
Error while unregistering container stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5160 |
Unexpected error while unregistering container stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5161 |
Error while registering pool stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5162 |
Unexpected error while registering pool stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5163 |
Error while unregistering pool stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5164 |
Unexpected error while unregistering pool stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5165 |
Error while registering cache stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5166 |
Unexpected error while registering cache stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5167 |
Error while unregistering cache stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD
EJB5168 |
Unexpected error while unregistering cache stats for {0} ; {1} ; {2}
Cause:TBD
Solution:TBD