BEA-420000
|
Warning: The message interception service cannot bind "jndiName" to the local JNDI.
Description
| The JNDI name has been used already. |
Cause
| The JNDI name has been used already. |
Action
| Application should not use JNDI name starting with weblogic. Please correct this problem then try again. |
|
BEA-420001(retired)
|
Error: The addAssociation method encouters some internal error due to "msg".
Description
| The addAssociation method cannot create association runtime mbean. |
Cause
| Unknown cause. |
Action
| Contact customer support. |
|
BEA-420002
|
Error: The addAssociation method encounters some input error due to "msg".
Description
| The addAssociation method encounters some input error due to "msg". |
Cause
| Illegal usage of addAssociation API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420003
|
Error: The addAssociation method encounters some usage error due to "msg".
Description
| The addAssociation method encounters some usage error due to "msg". |
Cause
| The interception point type is unknown either due to typo or the registerInterceptionPointNameDescription method didnt register the expected interception point type first. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420004
|
Error: The removeAssociation method encounters some input error due to "msg".
Description
| The removeAssociation method encounters some input error due to "msg". |
Cause
| Illegal usage of removeAssociation API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420005
|
Error: The registerInterceptionPointNameDescription method encounters some input error due to "msg".
Description
| The registerInterceptionPointNameDescription method encounters some input error due to "msg". |
Cause
| Illegal usage of registerInterceptionPointNameDescription API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420006
|
Error: The registerInterceptionPoint method encounters some input error due to "msg".
Description
| The registerInterceptionPoint method encounters some input error due to "msg". |
Cause
| Illegal usage of registerInterceptionPoint API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420007
|
Error: The registerInterceptionPoint method encounters some usage error due to "msg".
Description
| The registerInterceptionPoint method encounters some usage error due to "msg". |
Cause
| The interception point type is unknown either due to typo or the registerInterceptionPointNameDescription method didnt register the expected interception point type first. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420008
|
Error: The unRegisterInterceptionPoint method encounters some input error due to "msg".
Description
| The unRegisterInterceptionPoint method encounters some input error due to "msg". |
Cause
| Illegal usage of unRegisterInterceptionPoint API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420009
|
Error: The registerProcessorType method encounters some input error due to "msg".
Description
| The registerProcessorType method encounters some input error due to "msg". |
Cause
| Illegal usage of registerProcessorType API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420010
|
Error: The addProcessor method encounters some input error due to "msg".
Description
| The addProcessor method encounters some input error due to "msg". |
Cause
| Illegal usage of addProcessor API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420011
|
Error: The addProcessor method encounters some usage error due to "msg".
Description
| The addProcessor method encounters some usage error due to "msg". |
Cause
| The processor type is unknown either due to typo or the registerProcessorType method didnt register the expected processor type first. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420012
|
Error: The removeProcessor method encounters some input error due to "msg".
Description
| The removeProcessor method encounters some input error due to "msg". |
Cause
| Illegal usage of removeProcessor API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420013
|
Error: The getAssociationHandle method encounters some input error due to "msg".
Description
| The getAssociationHandle method encounters some input error due to "msg". |
Cause
| Illegal usage of getAssociationHandle API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420014
|
Error: The getProcessorHandles method encounters some input error due to "msg".
Description
| The getProcessorHandles method encounters some input error due to "msg". |
Cause
| Illegal usage of getProcessorHandles API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420015
|
Error: The getProcessorHandle method encounters some input error due to "msg".
Description
| The getProcessorHandle method encounters some input error due to "msg". |
Cause
| Illegal usage of getProcessorHandle API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420016
|
Error: The registerInterceptionPointNameDescriptionListener method encounters some input error due to "msg".
Description
| The registerInterceptionPointNameDescriptionListener method encounters some input error due to "msg". |
Cause
| Illegal usage of registerInterceptionPointNameDescriptionListener API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420017
|
Error: The removeAssociation method encounters some input error due to "msg".
Description
| The removeAssociation method encounters some input error due to "msg". |
Cause
| Illegal usage of removeAssociation API. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420018(retired)
|
Error: The removeAssociation method encounters some usage error due to "msg".
Description
| The removeAssociation method encounters some usage error due to "msg". |
Cause
| Unknown cause. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420019
|
Error: The process method encounters some usage error due to "msg".
Description
| The process method encounters some usage error due to "msg". |
Cause
| The required processor for the given association is not created at the time. To send message to a target that has association defined the processor specified in the association needs to be added beforehand. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420020
|
Error: The process method encounters some usage error due to "msg".
Description
| The process method encounters some usage error due to "msg". |
Cause
| The processor throws illegal error. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420021
|
Error: The process method encounters some usage error due to "msg".
Description
| The process method encounters some usage error due to "msg". |
Cause
| The processor throws illegal runtime exception. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420022(retired)
|
Error: The processOnly method encounters some usage error due to "msg".
Description
| The processOnly method encounters some usage error due to "msg". |
Cause
| The required processor for the given association is not created at the time. To send message to a target that has association defined the processor specified in the association needs to be added beforehand. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420023(retired)
|
Error: The processOnly method encounters some usage error due to "msg".
Description
| The processOnly method encounters some usage error due to "msg". |
Cause
| The processor throws illegal error. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420024(retired)
|
Error: The processOnly method encounters some usage error due to "msg".
Description
| The processOnly method encounters some usage error due to "msg". |
Cause
| The processor throws illegal runtime exception. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420025
|
Error: The addAssociation method encounters some usage error due to "msg".
Description
| The addAssociation method encounters some usage error due to "msg". |
Cause
| The added association exists already. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420026
|
Error: The unregisterInterceptionPoint method encounters some usage error due to "msg".
Description
| The unregisterInterceptionPoint method encounters some usage error due to "msg". |
Cause
| The Interception Point has been removed already. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420027
|
Error: The interception point name argument is invalid due to "msg".
Description
| The interception point name argument is invalid due to "msg". |
Cause
| The interception point name argument is invalid for several reasons. For instance the total number of name element is different than what is being registered with the interception service or any name element is invalid by itself. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420028
|
Error: The removeProcessor method encounters some usage error due to "msg".
Description
| The removeProcessor method encounters some usage error due to "msg". |
Cause
| The processor has been removed. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420029
|
Error: The registerProcessorType method encounters some usage error due to "msg".
Description
| The registerProcessorType method encounters some usage error due to "msg". |
Cause
| The processor factory class cannot be instantiated. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420030
|
Error: The registerProcessorType method encounters some usage error due to "msg".
Description
| The registerProcessorType method encounters some usage error due to "msg". |
Cause
| The processor factory class cannot be instantiated. |
Action
| If this is caused by an external application then fix the related code. Otherwise, contact the customer support. |
|
BEA-420031
|
Error: The process method encounters some usage error due to "msg".
Description
| The process method encounters some usage error due to "msg". |
Cause
| The processor currently is processing more intercepted message than that is allowed by the associations depth. |
Action
| User can increase the depth on the association via the association handle object. |
|
BEA-420032(retired)
|
Error: The processOnly method encounters some usage error due to "msg".
Description
| The processOnly method encounters some usage error due to "msg". |
Cause
| The processor currently is processing more intercepted message than that is allowed by the associations depth. |
Action
| User can increase the depth on the association via the association handle object. |
|