|
BEA-045001(retired)
|
Warning: The foreign JMS server MBean "mBeanName" has already been deployed.
|
Description
| The specified MBean has been deployed more than once, and it will not be deployed again. |
|
Cause
| This is an internal error. |
|
Action
| Undeploy and re-reploy the MBean that caused the error. If this does not solve the problem, restart the server. |
|
|
BEA-045002
|
Error: Error occurred while binding the remote JNDI object to the local JNDI name "localName".
|
Description
| An error occurred while binding an object from a foreign JNDI provider, such as a foreign JMS server, into the local JNDI tree. |
|
Cause
| The local JNDI name you are attempting to bind to may not be valid. |
|
Action
| Check the name to see if its syntax is correct. |
|
|
BEA-045003(retired)
|
Error: Error occurred while unbinding a remote JNDI object from local JNDI name "localName"
|
Description
| An error occurred while removing an object from the local JNDI tree. |
|
Cause
| There may be an error in the JNDI subsystem. |
|
Action
| Check the nested exception message for more detail. |
|
|
BEA-045004(retired)
|
Error: The JNDI object used to perform foreign lookup is not a reference.
|
Description
| The server attempted to perform a lookup of an object from a foreign JNDI provider, such as a foreign JMS server, and the object it found internally cannot be used to perform the remote lookup. |
|
Cause
| This is an internal error. |
|
Action
| If the lookup continually fails, restart the server. |
|
|
BEA-045005(retired)
|
Error: The configuration MBean "mBeanName" cannot be found, or it is of the wrong type.
|
Description
| A configuration MBean, such as a ForeignJMSServer, ForeignJMSDestination, or ForeignJMSConnectionFactory MBean, cannot be found, and a JNDI lookup cannot proceed. |
|
Cause
| There may be something wrong with the name of the MBean. |
|
Action
| Un-deploy and re-deploy the MBean. If this does not fix the problem, restart the server. |
|
|
BEA-045006(retired)
|
Error: A lookup of the foreign JNDI object "name" failed.
|
Description
| The server was unable to complete the lookup of the specified JNDI object from a foreign JNDI server, such as a foreign JMS server. |
|
Cause
| The foreign server may not be responding, or there may be a problem with the configuration parameters for the ForeignJMSServer MBean. |
|
Action
| Make sure the foreign JNDI provider is working, and check the configuration parameters for the ForeignJMSServer MBean. |
|
|
BEA-045025(retired)
|
Error: Unable to deploy JMS module: uriName from appName.
|
Description
| Unable to deploy JMS module: uriName from appName. |
|
Cause
| Invalid configuration of the JMS resource in the JMS module descriptor. |
|
Action
| Fix the entity JMS resource configuration/conflict. |
|
|
BEA-045026(retired)
|
Error: Error occurred while binding the imported destination to the local JNDI name "localName".
|
Description
| An error occurred while binding an imported destination into the local JNDI tree. |
|
Cause
| The local JNDI name you are attempting to bind to may not be valid. |
|
Action
| Check the name to see if its syntax is correct. |
|
|
BEA-045027(retired)
|
Error: Error occurred while unbinding an improted destination from local JNDI name "localName"
|
Description
| An error occurred while removing an imported destination from the local JNDI tree. |
|
Cause
| There may be an error in the JNDI subsystem. |
|
Action
| Check the nested exception message for more detail. |
|
|
BEA-045028
|
Warning: The messages threshold for the JMS server serverName has been exceeded for more than one hour
|
Description
| The messages threshold on a JMS server has been exceeded. This message is only generated when the "health state" of a JMS server is queried. |
|
Cause
| The threshold was exceeded |
|
Action
| Verify that messages are being consumed and sufficient memory is available |
|
|
BEA-045029
|
Warning: The messages threshold for the JMS server serverName has been exceeded for more than 90 percent of the running time of the server
|
Description
| The messages threshold on a JMS server has been exceeded. This message is only generated when the "health state" of a JMS server is queried. |
|
Cause
| The threshold was exceeded |
|
Action
| Verify that messages are being consumed and sufficient memory is available |
|
|
BEA-045030
|
Warning: The bytes threshold for the JMS server serverName has been exceeded for more than one hour
|
Description
| The bytes threshold on a JMS server has been exceeded. This message is only generated when the "health state" of a JMS server is queried. |
|
Cause
| The threshold was exceeded |
|
Action
| Verify that messages are being consumed and sufficient memory is available |
|
|
BEA-045031
|
Warning: The bytes threshold for the JMS server serverName has been exceeded for more than 90 percent of the running time of the server
|
Description
| The bytes threshold on a JMS server has been exceeded. This message is only generated when the "health state" of a JMS server is queried. |
|
Cause
| The threshold was exceeded |
|
Action
| Verify that messages are being consumed and sufficient memory is available |
|
|
BEA-045032
|
Error: While attempting to create destination destName in module modName the JMSServer of name beName could not be found.
|
Description
| While attempting to create a destination the JMSServer where the destination was targeted is not available. |
|
Cause
| The JMSServer may be shutting down, or may not have come up all the way. |
|
Action
| Deploy the module again once the JMSServer has come all the way up. |
|
|
BEA-045033(retired)
|
Error: An attempt was made to find the deployment named depName in module modName. However, that deployment could not be found in the runtime tree.
|
Description
| The JSR-88 module named modName was trying to find the application deployment named depName in the domain runtime tree. However, the deployment could not be found. |
|
Cause
| The runtime tree may be corrupted. |
|
Action
| Contact Oracle support |
|
|
BEA-045034(retired)
|
Error: The application context passed into the module modName had neither a JMSSystemResource nor an ApplicationDeployment.
|
Description
| The module modName is attempting to find its own deployment. However, the application context passed contains neither a JMSSystemResource reference nor an Application Deployment reference. |
|
Cause
| The application context may be corrupted. |
|
Action
| Contact Oracle support |
|
|
BEA-045035(retired)
|
Error: An attempt was made to find the JMSSystemResource named resName in module modName. However, that deployment could not be found in the runtime tree.
|
Description
| The system resource module named modName was trying to find the resource named resName in the domain runtime tree. However, the resource could not be found. |
|
Cause
| The runtime tree may be corrupted. |
|
Action
| Contact Oracle support |
|
|
BEA-045036(retired)
|
Warning: The file fileName either did not exist or could not be read in module modName
|
Description
| The given file name could not be found. |
|
Cause
| The given file name does not exist or is not readable. |
|
Action
| Create a new JMS Module file and put it in the location specified. If one already exists there, make sure it is readable by the JVM. |
|
|
BEA-045037(retired)
|
Warning: An error was encountered while parsing JMS module fileName in module modName
|
Description
| While attempting to parse file fileName in module modName an IOException was encountered. |
|
Cause
| See the linked java.io.IOException for more information on why this occurred. |
|
Action
| See the linked IOException to determine an appropriate course of action. |
|
|
BEA-045038(retired)
|
Warning: An error was encountered while closing JMS module file fileName in module modName
|
Description
| While attempting to close file fileName in module modName an IOException was encountered. |
|
Cause
| See the linked java.io.IOException for more information on why this occurred. |
|
Action
| See the linked IOException to determine an appropriate course of action. |
|
|
BEA-045039
|
Warning: An attempt was made to add a JMS entity of an unknown type type in module modName
|
Description
| An entity of the given type type was added to a JMS module modName. This type is unknown. |
|
Cause
| The JMS module given to the update is invalid. It contains an unknown type. |
|
Action
| Ensure the JMS module is valid. |
|
|
BEA-045040
|
Warning: While attempting to add a type of name name in module modName an error was encountered.
|
Description
| An error occurred while attempting to add a JMS resource of type type. The name of the resource was name. |
|
Cause
| A linked ModuleException will contain more detail about the cause of the failure. |
|
Action
| Examine the linked exception, which will contain more information about the cause of this failure. |
|
|
BEA-045041
|
Warning: An attempt was made to remove a JMS entity of an unknown type type in module modName
|
Description
| An entity of the given type type was removed from a JMS module modName. This type is unknown. |
|
Cause
| The JMS module given to the update is invalid. It contains an unknown type. |
|
Action
| Ensure the JMS module is valid. |
|
|
BEA-045042
|
Warning: An error occurred while adding name to JMS module modName
|
Description
| The JMS module modName encountered an error while adding JMS entity named name. |
|
Cause
| See the linked exception for more detail. |
|
Action
| The linked exception will contain more information about why this add operation failed. |
|
|
BEA-045043
|
Warning: An error occurred while removing name from JMS module modName
|
Description
| The JMS module modName encountered an error while removing JMS entity named name. |
|
Cause
| See the linked exception for more detail. |
|
Action
| The linked exception will contain more information about why this add operation failed. |
|
|
BEA-045044(retired)
|
Error: The parent of SubDeployment name in module modName is not an understood class. The parent has class cName.
|
Description
| A SubDeployment was added to a BasicDeploymentMBean. However, the parent of the SubDeployment was not a BasicDeploymentMBean. |
|
Cause
| The added SubDeployment is corrupted. |
|
Action
| Contact Oracle support. |
|
|
BEA-045045
|
Error: A SubDeployment named name was not found in module modName
|
Description
| An attempt was made to remove a SubDeployment named name in module modName. However, this SubDeployment is unknown to the module. |
|
Cause
| A SubDeployment removal was attempted, but the SubDeployment was unknown to the module. |
|
Action
| Contact Oracle support. |
|
|
BEA-045046(retired)
|
Error: The parent of SubDeployment name in module modName is not an understood class. The parent has class cName.
|
Description
| A SubDeployment was added to a BasicDeploymentMBean. However, the parent of the SubDeployment was not a BasicDeploymentMBean. |
|
Cause
| The added SubDeployment is corrupted. |
|
Action
| Contact Oracle support. |
|
|
BEA-045047
|
Error: The SubDeploymentMBean subDeploymentName in deployment name can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue, topic or quota) has a sub-deployment-name element with value subDeploymentName
|
Description
| The SubDeploymentMBean subDeploymentName in deployment name can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue, topic or quota) has a sub-deployment-name element with value subDeploymentName |
|
Cause
| The SubDeploymentMBean of the given name cannot be targeted to anything but a single JMSServer because an element of the JMS module that points to that sub-deployment can only be targeted to a single JMSServer. |
|
Action
| Modify the target of the SubDeployment so that it only contains a single JMS server. |
|
|
BEA-045048
|
Error: The JMSServer named beName has a temporary template configured. The JMSSystemResourceMBean name of the module containing the temporary template is modName, and the template name is templateName. However, a JMSSystemResourceMBean of name modName could not be found. The JMS Server beName will not boot until this problem has been fixed.
|
Description
| The JMSServer named beName has a temporary template configured. The JMSSystemResourceMBean name of the module containing the temporary template is modName, and the template name is templateName. However, a JMSSystemResourceMBean of name modName could not be found. The JMS Server beName will not boot until this problem has been fixed. |
|
Cause
| The temporary template for a JMS server must come from a JMSSystemResourceMBean. A common mistake is to put the temporary template into an AppDeployment. However, because the temporary template must be owned by the administrator, all temporary templates must come from JMSSystemResourceMBeans, not AppDeployments. |
|
Action
| Put the temporary template into a JMSSystemResource. |
|
|
BEA-045049
|
Warning: JMSServer beName does not have a configured temporary template. However an attempt was made to create a temporary destination. This is not allowed.
|
Description
| An attempt was made to create a temporary destination with JMS Server beName. No temporary template was configured for this JMSServer, and hence no temporary destinations can be created here. |
|
Cause
| A JMSServer without a configured temporary template was used to create a temporary destination. This usage is not allowed. |
|
Action
| Create a JMSSystemResource that contains a template. Use that template as the temporary template for this JMSServer. |
|
|
BEA-045050
|
Error: A destination of name conflicting has a jms-create-destination-identifier of name id. However, another destination of name original has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot be co-located on the JMSServer named beName.
|
Description
| A destination of name conflicting has a jms-create-destination-identifier of name id. However, another destination of name original has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot be co-located on the JMSServer named beName. |
|
Cause
| Two destinations cannot both have the same jms-create-destination-identifier on the same JMSServer, even if the two destinations are from different modules. |
|
Action
| Either deploy the destination with the offending jms-create-destination-identifier to a different JMSServer, or change the value of the jms-create-destination-identifier attribute. |
|
|
BEA-045051
|
Error: Two destinations with name destName were deployed to JMSServer beName.
|
Description
| Two destinations with name destName were deployed to JMSServer beName. |
|
Cause
| Two destinations with the same fully qualified name cannot be deployed to the same JMS Server. This error should have been caught during the validation phase of the JMS module. |
|
Action
| Contact Oracle support. |
|
|
BEA-045052
|
Error: An attempt was made to change the target of a JMS entity that cannot have its target changed. The entity has name "entityName". The original target has name "oldTarget". The proposed target has name "newTarget"
|
Description
| We do not allow entities such as Quotas, Queues or Topics to have their target changed dynamically. It is unclear what to do with any persistent state maintained by these entities. |
|
Cause
| An attempt was made to change the target of an entity that cannot have its target changed dynamically. |
|
Action
| One thing that can be done is to untarget a sub-deployment and then retarget that sub-deployment elsewhere. It should be made clear that by doing that the persistent state maintained for entities retargeted in this fashion will *not* be kept on the old target, and may or may not be removed by the system. |
|
|
BEA-045053(retired)
|
Error: All members of a JMS Distributed Destination name must exist and be in the same cluster. The problematic member is memberName.
|
Description
| All members of a JMS Distributed Destination name must exist and be in the same cluster. The problematic member is memberName. |
|
Cause
| Configuration error. |
|
Action
| Ensure that all the Distributed Destination members belong to the same cluster and redeploy the module. |
|
|
BEA-045054
|
Error: Cannot dynamically add member memberName to Distributed Destination $ddName.
|
Description
| Cannot dynamically add member memberName to Distributed Destination $ddName. |
|
Cause
| Either this member is not prepared yet or got removed already. |
|
Action
| Ensure that the Distributed Destination member is not removed and/or in prepared state. |
|
|
BEA-045055
|
Error: Cannot dynamically remove member memberName from Distributed Destination $ddName.
|
Description
| Cannot dynamically remove member memberName from Distributed Destination $ddName. |
|
Cause
| Either this member is not activated yet or it is an invalid member. |
|
Action
| Ensure that the Distributed Destination member is a valid one and/or in activated state. |
|
|
BEA-045056(retired)
|
Error: Cannot prepare member memberName of Distributed Destination $ddName.
|
Description
| Cannot prepare member memberName of Distributed Destination $ddName. |
|
Cause
| Configuration error. |
|
Action
| Ensure that the Distributed Destination member is not removed and/or in prepared state. |
|
|
BEA-045057(retired)
|
Error: Cannot unprepare member memberName of Distributed Destination $ddName.
|
Description
| Cannot unprepare member memberName of Distributed Destination $ddName. |
|
Cause
| Either this member is not prepared yet or it is an invalid member. |
|
Action
| Ensure that the Distributed Destination member is a valid one and/or in prepared state. |
|
|
BEA-045058(retired)
|
Error: Cannot activate member memberName of Distributed Destination $ddName.
|
Description
| Cannot activate member memberName of Distributed Destination $ddName. |
|
Cause
| Either this member is not in prepared state or it got removed already. |
|
Action
| Ensure that the Distributed Destination member is not removed and/or in prepared state. |
|
|
BEA-045059(retired)
|
Error: Cannot deactivate member memberName of Distributed Destination $ddName.
|
Description
| Cannot deactivate member memberName of Distributed Destination $ddName. |
|
Cause
| Either this member is not activated yet or it is an invalid member. |
|
Action
| Ensure that the Distributed Destination member is a valid one and/or in activated state. |
|
|
BEA-045060
|
Error: The JMS module named "modName" is neither an AppDeployment nor a JMSSystemResource
|
Description
| The JMS module named "modName" is neither an AppDeployment nor a JMSSystemResource |
|
Cause
| An invalid application context was passed to a JMS module |
|
Action
| Contact Oracle customer support |
|
|
BEA-045061
|
Error: An attempt was made to create a durable subscription on a queue named "name". The client identifier is "ClientId", the subscriptionName is "subName" and the selector is "sel". Durable subscriptions may only be created on topics.
|
Description
| An attempt was made to create a durable subscription on a queue named "name". The client identifier is "ClientId", the subscriptionName is "subName" and the selector is "sel". Durable subscriptions may only be created on topics. |
|
Cause
| An attempt was made to create a durable subscription on a queue. |
|
Action
| Do not attempt to create a durable subscription on a queue. |
|
|
BEA-045062
|
Error: There can be no more than one jms-interop-module element in config.xml
|
Description
| An attempt was made to boot a domain with more than one jms-interop-module defined. There can be no more than one JMS interop module in a domain. |
|
Cause
| More than one jms-interop-module element was found in config.xml |
|
Action
| Do not attempt to define more than one jms-interop-module element in config.xml |
|
|
BEA-045063
|
Error: The jms-interop-module must have name interop-jms and descriptor file name jms/interop-jms.xml. It has name "name".
|
Description
| The jms-interop-module element in config.xml must have the name interop-jms. No other name is allowed. |
|
Cause
| An attempt was made to use a jms-interop-module with a name other than interop-jms. |
|
Action
| Do not attempt to define a jms-interop-module element in config.xml with a name other than interop-jms. |
|
|
BEA-045064
|
Error: The target named "target" of a JMS module inside a deployment named "moduleName" must be a WLS server or a cluster. Instead, it is of type "type". If this was deployed from inside a J2EE application (an EAR file) the syntax for this (when using a deployment tool such as weblogic.Deployer or weblogic.WLST) is "sub-deployment-name + @ + ear-module-name + @ + target ". In this case sub-deployment-name is the name of the sub-deployment from the JMS module. The ear-module-name is the name of the JMS module found in the weblogic-application.xml file in the META-INF directory of the application. The target is the place where elements that have the given sub-deployment-name should be targeted. For example, if your JMS module has queue with a sub-deployment-name of "GroupA", and the name of the JMS module in the weblogic-application.xml file is "FirstJMSModule" and you wish that queue to be targeted to a JMS Server named "JServer" then the proper syntax when deploying this module through weblogic.Deployer or weblogic.WLST would be "GroupA@FirstJMSModule@JServer".
|
Description
| All the targets of a JMS module must be either of type ServerMBean or ClusterMBean. The target of this module is not one of those types. If this was deployed from inside a J2EE application (an EAR file) the syntax for this (when using a deployment tool such as weblogic.Deployer or weblogic.WLST) is sub-deployment-name + "@" + ear-module-name + "@;" + target. In this case sub-deployment-name is the name of the sub-deployment from the JMS module itself, the ear-module-name is the name of the JMS module found in the weblogic-application.xml file in the META-INF directory of the application and the target is the place where elements that have the given sub-deployment-name should be targeted. For example, if your JMS module has queue with a sub-deployment-name of "GroupA", and the name of the JMS module in the weblogic-application.xml file is "FirstJMSModule" and you wish that queue to be targeted to a JMS Server named "JServer" then the proper syntax when deploying this module through weblogic.Deployer or weblogic.WLST would be "GroupA@FirstJMSModule@JServer". |
|
Cause
| An attempt was made to target a JMS module to an invalid type of target. |
|
Action
| Do not attempt to target a JMS module to anything other than WLS servers or clusters. Any other type of target is not understood. |
|
|
BEA-045065
|
Error: A JMS module with fully qualified name "fullName" in an application named "moduleName" does not have the proper hierarchy of targets. In particular the subdeployment of name "subDeploymentName" has a target "subTarget" that is not a sub-target of any of the targets of "moduleName". For example, target "subTarget" is not a sub-target of "superTarget".
|
Description
| All the targets of the sub-deployment of a JMS module must be contained within the targets of the whole module. |
|
Cause
| A target of a sub-deployment of a JMS module is not contained within the targets of the whole JMS module. |
|
Action
| Either make sure that your JMS module is targeted to a super-set of all the targets of the sub-deployment or retarget the sub-deployment within the set of targets for the JMS module. |
|
|
BEA-045066
|
Error: The target named "target" of a JMS sub-deployment named "subName" inside a deployment named "moduleName" must be a JMS server, WLS server or a cluster. Instead, it is of type type.
|
Description
| All the targets of a JMS sub-deployment must be either of type JMSServerMBean, ServerMBean or ClusterMBean. The target of this sub-deployment is not one of those types. |
|
Cause
| An attempt was made to target a JMS sub-deployment to an invalid type of target. |
|
Action
| Do not attempt to target a JMS sub-deployment to anything other than JMS servers, WLS servers or clusters. Any other type of target is not understood. |
|
|
BEA-045067
|
Error: The field "destination-name" was set to "queueName" in distributed destination member "dqmName" in distributed destination "dqName" in module "moduleName". The destination-name field of a distributed destination may only be set in the interop module.
|
Description
| The destination-name field of a distributed destination member may only be set in the interop module. In all other modules this name may not be explicitly set, and will always take the default value that equals the name of the distributed-destination-member itself. |
|
Cause
| An attempt was made to set the destination-name field of a distributed-destination-member type. This is only allowed in the interop module, in order to accommodate older clients. |
|
Action
| Change the name of the distributed-destination-member to the name of the physical queue or topic being referenced, and unset the destination-name field. |
|
|
BEA-045068
|
Error: The physical destination named "queueName" in distributed destination member "dqmName" in distributed destination "dqName" in module "moduleName" does not exist.
|
Description
| The destination refereed to by the distributed destination member field must exist. |
|
Cause
| An attempt was made to reference a destination that does not exist by a distributed destination member. The physical destination refereed to by a distributed destination must already exist. |
|
Action
| Create the physical destination before referring to it, or create the physical destination in the same edit session as the creation of the distributed destination member. |
|
|
BEA-045069
|
Error: The JMS module entity named "entityName" of type "entityType" does not exist in JMSSystemResource "resourceName".
|
Description
| The JMS module entity refereed by the JMSModuleHelper API must exist in the specified JMSSystemResource. |
|
Cause
| An attempt was made to reference a JMS module entity that does not exist in the specified JMSSytemResource. |
|
Action
| Create the JMS module entity in the specified JMSSystemResource before referring to it. |
|
|
BEA-045070
|
Error: The configuration entity named "entityName" of type "entityType" does not exist in domain "domainName".
|
Description
| The configuration entity refereed by the JMSModuleHelper API must exist in the specified domain. |
|
Cause
| An attempt was made to reference a configuration entity that does not exist in the specified domain. |
|
Action
| Create the configuration entity in the specified domain before referring to it. |
|
|
BEA-045071
|
Error: The JMS module entity named "entityName" of type "entityType" cannot be created in JMSSystemResource "resourceName".
|
Description
| The JMS module entity creation using JMSModuleHelper API failed, see the accompanying exception for details. |
|
Cause
| The JMS module entity creation using JMSModuleHelper API failed, see the accompanying exception for details. |
|
Action
| Resolve problem identified by the accompanying exception and retry the operation. |
|
|
BEA-045072
|
Error: The configuration entity named "entityName" of type "entityType" cannot be created in domain "domainName".
|
Description
| The configuration entity creation using JMSModuleHelper API failed, see the accompanying exception for details. |
|
Cause
| The configuration entity creation using JMSModuleHelper API failed, see the accompanying exception for details. |
|
Action
| Resolve problem identified by the accompanying exception and retry the operation. |
|
|
BEA-045073
|
Error: The JMS module entity named "entityName" of type "entityType" cannot be deleted from JMSSystemResource "resourceName".
|
Description
| The JMS module entity deletion using JMSModuleHelper API failed, see the accompanying exception for details. |
|
Cause
| The JMS module entity deletion using JMSModuleHelper API failed, see the accompanying exception for details. |
|
Action
| Resolve problem identified by the accompanying exception and retry the operation. |
|
|
BEA-045074
|
Error: The configuration entity named "entityName" of type "entityType" cannot be deleted from domain "domainName".
|
Description
| The configuration entity deletion using JMSModuleHelper API failed, see the accompanying exception for details. |
|
Cause
| The configuration entity deletion using JMSModuleHelper API failed, see the accompanying exception for details. |
|
Action
| Resolve problem identified by the accompanying exception and retry the operation. |
|
|
BEA-045075
|
Error: The JMS module managed entity named "entityName" of type "entityType" cannot be found in JMSSytemResource "resourceName" for modification.
|
Description
| The JMS module entity modification using JMSModuleHelper API failed, see the accompanying exception for details. |
|
Cause
| The JMS module entity modification using JMSModuleHelper API failed, see the accompanying exception for details. |
|
Action
| Resolve problem identified by the accompanying exception and retry the operation. |
|
|
BEA-045076
|
Error: An attempt was made to find and modify a JMS module entity of of name "entityName" of type "entityType" from JMSSystemResource "resourceName" using a null modifier.
|
Description
| JMSEntityModifier argument for the findAndModifyEntity() helper API cannot be null. |
|
Cause
| JMSEntityModifier argument for the findAndModifyEntity() helper API cannot be null. |
|
Action
| Use a valid weblogic.jms.extensions.JMSEntityModifer implementation as the modifier argument. |
|
|
BEA-045077
|
Error: The destination named "dest" on JMS Server "jmsServer" would have caused the JMS Server to not boot because the destination hasStore value is true but the JMS Server does not have a store.
|
Description
| The destination named "dest" on JMS Server "jmsServer" would have caused the JMS Server to not boot because the destination StoreEnabled value is true but the JMS Server does not have a store. |
|
Cause
| This configuration could not have worked in older releases because of the mismatch between the destinations StoreEnabled value is true but the JMS Server does not have a store. |
|
Action
| Modify the configuration to remove this discrepency, and re-run the upgrade process. You can either add a store to the JMS Server or you can change the value of the StoreEnabled parameter on the destination. |
|
|
BEA-045078
|
Error: The destination named "dest" on JMS Server "jmsServer" has a DeliveryParamsOverrides.DeliveryMode parameter set to Persistent but the JMS Server does not have a store.
|
Description
| The destination named "dest" on JMS Server "jmsServer" has a DeliveryParamsOverrides.DeliveryMode parameter set to Persistent but the JMS Server does not have a store. |
|
Cause
| Messages cannot be made persistent on this JMS Server because it does not have a store. |
|
Action
| Modify the configuration to remove this discrepency, and re-run the upgrade process. You can either add a store to the JMS Server or you can change the value of the DeliveryParamsOverrides.DeliveryMode parameter. |
|
|
BEA-045079
|
Error: An attempt was made to send a persistent message to destination "destName" hosted on JMS Server "jmsServer". This JMS server does not have a store, so the quality of service requested is not available.
|
Description
| An attempt was made to send a persistent message to destination "destName" hosted on JMS Server "jmsServer". This JMS server does not have a store, so the quality of service requested is not available. |
|
Cause
| An attempt was made to send a persistent message to a destination hosted by a JMS Server that does not have a store. Since the message cannot be persisted this message cannot be sent at the required quality of service. |
|
Action
| There is a parameter on the JMS Server called "AllowsPersistentDowngrade". If this parameter is set to true then persistent messages sent to this JMS Server will be downgraded to non-persistent. |
|
|
BEA-045080
|
Error: The flow steps value steps is larger than the flow interval value interval in connection factory "facName". The flow steps value must be less than or equal to the flow interval value.
|
Description
| The flow steps value steps is larger than the flow interval value interval in connection factory "facName". The flow steps value must be less than or equal to the flow interval value. |
|
Cause
| This is an invalid configuration. The flow steps value must be less than the entire flow interval. |
|
Action
| Modify the configuration of the connection factory to have the flow steps value to be less than or equal to the flow interval. |
|
|
BEA-045081
|
Error: The SessionsMaximum attribute of a JMSSessionPoolMBean has the bad value maxValue. The value should be -1 or a positive integer.
|
Description
| The SessionsMaximum attribute of a JMSSessionPoolMBean has the bad value maxValue. The value should be -1 or a positive integer. |
|
Cause
| This is an invalid configuration. |
|
Action
| Modify the configuration of the JMSSessionPoolMBean. |
|
|
BEA-045082
|
Error: An unexpected naming exception occurred while binding destination "destName" to JNDI name "jndiName"
|
Description
| An unexpected naming exception occurred while binding destination "destName" to JNDI name "jndiName". This naming exception was not NameAlreadyBoundException. |
|
Cause
| The naming exception should contain more information about why this operation failed. |
|
Action
| See the naming exception attached to this exception. It should have more information about why this operation failed. |
|
|
BEA-045083
|
Error: An unexpected naming exception occurred while binding destination "destName" to JNDI name "jndiName" to the local JNDI context.
|
Description
| An unexpected naming exception occurred while binding destination "destName" to JNDI name "jndiName" to the local JNDI context. This naming exception was not NameAlreadyBoundException. |
|
Cause
| The naming exception should contain more information about why this operation failed. |
|
Action
| See the naming exception attached to this exception. It should have more information about why this operation failed. |
|
|
BEA-045084
|
Error: An unexpected naming exception occurred while binding destination "destName" to JNDI name "jndiName" to the application JNDI context.
|
Description
| An unexpected naming exception occurred while binding destination "destName" to JNDI name "jndiName" to the application JNDI context. This naming exception was not NameAlreadyBoundException. |
|
Cause
| The naming exception should contain more information about why this operation failed. |
|
Action
| See the naming exception attached to this exception. It should have more information about why this operation failed. |
|
|
BEA-045085
|
Warning: Could not find a license for JMS. Please contact Oracle to get a license.
|
Description
| Could not find a license for JMS. Please contact Oracle to get a license. |
|
Cause
| Unable to get license for JMS. |
|
Action
| Contact Oracle to get a license. |
|
|
BEA-045086
|
Error: The jms-system-resource cannot have name interop-jms.
|
Description
| The jms-system-resource element in config.xml cannot have the name interop-jms. |
|
Cause
| An attempt was made to define a jms-system-resource with name interop-jms. |
|
Action
| Do not attempt to define a jms-system-resource element in config.xml with name interop-jms. |
|
|
BEA-045087
|
Error: The JMS deployment "name" has descriptor file name "descriptorName" which is reserved for internal use only.
|
Description
| The file name interop-jms.xml is reserved for internal use only. JMS deployments are not allowed use this descriptor file name. |
|
Cause
| An attempt was made to define a JMS deployment with the reserved file name "interop-jms.xml". This name is reserved by the system for use as the interop module. |
|
Action
| Do not attempt to define a JMS deployment with the reserved name "interop-jms.xml" as its file name. |
|
|
BEA-045088
|
Error: The JMS module descriptor file "descriptorName" used by the jms-system-resource "name" is illegal. Either the descriptor file name does not end with "-jms.xml" or the descriptor is being used by another jms-system-resource in the configuration.
|
Description
| The descriptor file name of a jms-system-resource should end with -jms.xml and cannot be shared by more than one jms-system-resource. |
|
Cause
| An attempt was made to define a jms-system-resource with the illegal descriptor file name. |
|
Action
| Do not attempt to define a jms-system-resource element in config.xml with the illegal descriptor file name. |
|
|
BEA-045089
|
Error: SAF error destination edName of ehName is targeted to a different sub-deployment from beanName.
|
Description
| The error destination of a SAF imported destinations, a SAF queue, or a SAF topic has to be deployed to the same sub-deployment as the bean that refers to it. |
|
Cause
| Wrong configuration. |
|
Action
| Correct the deployment descriptor. |
|
|
BEA-045090
|
Error: The error handling ehName configured for beanName does not exist in the module.
|
Description
| A SAF imported destinations, SAF queue or SAF topic has an error handling name configured, but there is no such error handling found in the module. |
|
Cause
| Wrong configuration. |
|
Action
| Correct the deployment descriptor. |
|
|
BEA-045091
|
Error: One of the target ("targetName") of SubDeployment "subName" for Imported Destinations "beanName" is not a legal target type.
|
Description
| A target of a SAF Agent can only be a SAF agent, a Server or a Cluster. |
|
Cause
| Wrong configuration. |
|
Action
| Correct the configuration. |
|
|
BEA-045092
|
Error: Imported Destinations "beanName": its SubDeployment is targeted to a target ("targetName"), which is a Receiving-only SAF agent.
|
Description
| A sub deployment that an imported destinations is targeted to cannot be targeted to a Receiving-only SAF agent. |
|
Cause
| Wrong configuration. |
|
Action
| Correct the configuration. |
|
|
BEA-045093
|
Error: A Uniform Distributed Queue named "name" was found in the JMS interop module. Uniform Distributed Queues were not available prior to the 9.0 release of WLS, and hence cannot be in the JMS interop module. Please create another JMS module and put your Uniform Distributed Queue in that module.
|
Description
| A Uniform Distributed Queue named "name" was found in the JMS interop module. Uniform Distributed Queues were not available prior to the 9.0 release of WLS, and hence cannot be in the JMS interop module. Please create another JMS module and put your Uniform Distributed Queue in that module. |
|
Cause
| An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module. |
|
Action
| Place the entity into another JMS module and either deploy that module as a system resource or as a deployable resource. |
|
|
BEA-045094
|
Error: A Uniform Distributed Topic named "name" was found in the JMS interop module. Uniform Distributed Topics were not available prior to the 9.0 release of WLS, and hence cannot be in the JMS interop module. Please create another JMS module and put your Uniform Distributed Topic in that module.
|
Description
| A Uniform Distributed Topic named "name" was found in the JMS interop module. Uniform Distributed Topics were not available prior to the 9.0 release of WLS, and hence cannot be in the JMS interop module. Please create another JMS module and put your Uniform Distributed Topic in that module. |
|
Cause
| An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module. |
|
Action
| Place the entity into another JMS module and either deploy that module as a system resource or as a deployable resource. |
|
|
BEA-045095
|
Error: A SAF Imported Destinanations named "name" was found in the JMS interop module. SAF Imported Destinations were not available prior to the 9.0 release of WLS, and hence cannot be in the JMS interop module. Please create another JMS module and put your SAF Imported Destinations in that module.
|
Description
| A SAF Imported Destinanations named "name" was found in the JMS interop module. SAF Imported Destinations were not available prior to the 9.0 release of WLS, and hence cannot be in the JMS interop module. Please create another JMS module and put your SAF Imported Destinations in that module. |
|
Cause
| An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module. |
|
Action
| Place the entity into another JMS module and either deploy that module as a system resource or as a deployable resource. |
|
|
BEA-045096
|
Error: A SAF Remote Context named "name" was found in the JMS interop module. SAF Remote Contexts were not available prior to the 9.0 release of WLS, and hence cannot be in the JMS interop module. Please create another JMS module and put your SAF Remote Context in that module.
|
Description
| A SAF Remote Context named "name" was found in the JMS interop module. SAF Remote Contexts were not available prior to the 9.0 release of WLS, and hence cannot be in the JMS interop module. Please create another JMS module and put your SAF Remote Context in that module. |
|
Cause
| An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module. |
|
Action
| Place the entity into another JMS module and either deploy that module as a system resource or as a deployable resource. |
|
|
BEA-045097
|
Error: A SAF Error Handlings named "name" was found in the JMS interop module. SAF Error Handlings were not available prior to the 9.0 release of WLS, and hence cannot be in the JMS interop module. Please create another JMS module and put your SAF Error Handlings in that module.
|
Description
| A SAF Error Handlings named "name" was found in the JMS interop module. SAF Error Handlings were not available prior to the 9.0 release of WLS, and hence cannot be in the JMS interop module. Please create another JMS module and put your SAF Error Handlings in that module. |
|
Cause
| An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module. |
|
Action
| Place the entity into another JMS module and either deploy that module as a system resource or as a deployable resource. |
|
|
BEA-045098
|
Error: There is a JMS System Resource and an Application Deployment both named "name". The names of all JMS System Resources and all Application Deployments must be different.
|
Description
| There is a JMS System Resource and an Application Deployment both named "name". The names of all JMS System Resources and all Application Deployments must be different. |
|
Cause
| Both a JMS System Resource and an Application Deployment have the same name. This would cause similarly named resources in a JMS module descriptor file to have conflicting runtime names, and hence is not allowed. |
|
Action
| Change the name of either the JMS System Resource or Application Deployment so that there is no name conflict. |
|
|
BEA-045099
|
Error: An attempt was made to create a temporary destination. However, no JMSServer in the cluster is able to host temporary destinations. Ensure that at least one of the JMSServers in your cluster has the HostingTemporaryDestinations parameter set to true (which is the default).
|
Description
| An attempt was made to create a temporary destination. However, no JMSServer in the cluster is able to host temporary destinations. Ensure that at least one of the JMSServers in your cluster has the HostingTemporaryDestinations parameter set to true (which is the default). Note that in releases prior to 9.0 the default for the ability to host temporary destinations was false, while in 9.0 and beyond the default for the ability to host temporary destinations is true. |
|
Cause
| None of the JMSServers in the cluster is available for hosting temporary destinations. |
|
Action
| Modify the HostingTemporaryDestinations parameter on at least one JMSServer in the cluster. Note that in releases prior to 9.0 the default for the ability to host temporary destinations was false, while in 9.0 and beyond the default for the ability to host temporary destinations is true. |
|
|
BEA-045100
|
Error: The createQueue or createTopic call was made with a null or zero length destination name.
|
Description
| The createQueue or createTopic call was made with a null or zero length destination name. |
|
Cause
| The createQueue or createTopic call must be made with the name of a destination to find. |
|
Action
| Do not pass null or a zero length string to createQueue or createTopic. |
|
|
BEA-045101
|
Error: The destination name passed to createTopic or createQueue "destName" is invalid. If the destination name does not contain a "/" character then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character then the string before the "/" must be the name of a JMSServer or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WLS server will be returned.
|
Description
| The destination name passed to createTopic or createQueue "destName" is invalid. If the destination name does not contain a "/" character then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character then the string before the "/" must be the name of a JMSServer or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WLS server will be returned. |
|
Cause
| Either a distributed destination of the given name does not exist in the cluster to which the client is attached or the destination name passed to createTopic or createQueue does not contain a "/" character, or there is nothing before the "/" character. |
|
Action
| Make sure the distributed destination is available on the same cluster where the client is located or format the destination name string properly. |
|
|
BEA-045102
|
Error: A destination of name "destName" was not found on WLS server "wlsName".
|
Description
| A destination of name "destName" was not found on WLS server "wlsName". |
|
Cause
| An attempt was made to find a destination of a given name on a particular WLS server. No destination of that name could be found on that WLS server. |
|
Action
| It is possible that the createTopic or createQueue call was routed to a WLS server that does not contain a destination with the given name. The set of WLS servers where this request can be routed can be controlled by using a connection factory that is only targeted to WLS servers that have destinations of the desired name. |
|
|
BEA-045103
|
Error: While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
|
Description
| While trying to find a topic or a queue we could not find the specific JMSServer requested. The linked exception may contain more information about the reason for failure. |
|
Cause
| A specific JMSServer was requested by a call to createTopic or createQueue. However, the system could not locate the JMSServer of that name. |
|
Action
| The WLS server on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server, and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure. |
|
|
BEA-045104
|
Error: While trying to find a topic or a queue we could not find the specific JMSServer requested.
|
Description
| While trying to find a topic or a queue we could not find the specific JMSServer requested. |
|
Cause
| A specific JMSServer was requested by a call to createTopic or createQueue. However, the system could not locate the JMSServer of that name. |
|
Action
| Ensure the JMSServer requested exists in the configuration of the cluster to which the client is attached. |
|
|
BEA-045105
|
Error: While trying to find a topic or a queue we could not communicate with the specific JMSServer requested. The linked exception may contain more information about the reason for failure.
|
Description
| While trying to find a topic or a queue we could not communicate with the specific JMSServer requested. The linked exception may contain more information about the reason for failure. |
|
Cause
| A specific JMSServer was requested by a call to createTopic or createQueue. However, the system could not communicate with the JMSServer of that name. |
|
Action
| The WLS server on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server, and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure. |
|
|
BEA-045106
|
Error: We found a destination of name "destName". However, the requested destination was of type "type", and the destination found was not of that type.
|
Description
| We found a destination of name "destName". However, the requested destination was of type "type", and the destination found was not of that type. |
|
Cause
| The user called createTopic but the destination found is a queue or the user called createQueue and the destination found is a topic. |
|
Action
| Ensure that the destination name requested is of the correct type. |
|
|
BEA-045107
|
Error: A communication failure occurred while attempting to remove a durable subscription. The linked exception may contain more details about the cause of the failure.
|
Description
| A communication failure occurred while attempting to remove a durable subscription. The linked exception may contain more details about the cause of the failure. |
|
Cause
| While attempting to remove a durable subscription a communication failure occurred. |
|
Action
| Check on the status of WLS server where the destination which the durable subscription refers to resides. Check the linked exception for more information about the cause of this failure. |
|
|
BEA-045108
|
Error: The JMS system does not understand request id id.
|
Description
| The JMS system does not understand request id id. |
|
Cause
| An invalid request id was presented to the front end manager. |
|
Action
| If this condition persists contact your Oracle technical support. |
|
|
BEA-045109
|
Error: We found a ForeignServer of name "foreignServerName" which do not have a connection URL specified. However, it contains a "foreignJNDIObjectType" of name "foreignJNDIObjectName" that has same local and remote JNDI name value "jndiName". This is an invalid configuration and not allowed.
|
Description
| We found a ForeignServer of name "foreignServerName" which do not have a connection URL specified. However, it contains a "foreignJNDIObjectType" of name "foreignJNDIObjectName" that has same local and remote JNDI name value "jndiName". This is an invalid configuration and not allowed. |
|
Cause
| The user has configured a ForeignServer without connection URL and has either a Foreign Connection Factory or Foreign Destination with both local and remote JNDI name matching. topic. |
|
Action
| Ensure that either the Foreign Server has a connection URL to the foreign server or local and remote JNDI names are different. |
|
|
BEA-045110
|
Error: The JMS resource named "targetableName" has incorrect targeting information. This resource has both default-targeting-enabled attribute set to true and has a valid sub-deployment-name value specified.
|
Description
| A JMS resource cannot have both default targeting enabled and sub deployment name specified. |
|
Cause
| A JMS resource cannot have both default targeting enabled and sub deployment name specified. |
|
Action
| Ensure that either default targeting enabled or only valid sub deployment name specified. |
|
|
BEA-045111
|
Error: The JMS resource named "targetableName" has incorrect targeting information. A JMS physical destination cannot have default-targeting-enabled attribute set.
|
Description
| A JMS physical destination cannot have default-targeting-enabled attribute set. |
|
Cause
| A JMS physical destination cannot have default-targeting-enabled attribute set. |
|
Action
| Ensure that default-targeting-enabled attribute is not set for the physical destinations. |
|
|
BEA-045112
|
Error: The flow minimum value min is larger than or equal to the flow maximum value max in connection factory "facName". The flow minimum value must be less than the flow maximum value.
|
Description
| The flow minimum value min is larger than or equal to the flow maximum value max in connection factory "facName". The flow minimum value must be less than the flow maximum value. |
|
Cause
| This is an invalid configuration. The flow minimum value must be less than the flow maximum value. |
|
Action
| Modify the configuration of the connection factory to have the flow minimum value to be less than the flow maximum value. |
|
|
BEA-045113
|
Info: JMS distributed destination forward request denied for the destination named "destName". Reason "reason".
|
Description
| JMS distributed destinations are logical destinations that can automically forward messages between physical destination members. A forward request failed a security check. The request will automatically retry periodically. |
|
Cause
| JMS distributed destinations may not have fully initialized. |
|
Action
| If forwarding does not begin after a few minutes, contact customer support. |
|
|
BEA-045114
|
Error: Failed to unsubscribe subscription "name", client ID "clientID". This connection has a Client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription without a topic object.
|
Description
| An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a Client ID policy of UNRESTRICTED. |
|
Cause
| An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a Client ID policy of UNRESTRICTED. |
|
Action
| Use weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a Client ID policy of UNRESTRICTED. If you are using a pre-AS11gR1PS3 Java client, upgrade to AS11gR1PS3 client. If you are using a non-Java client, cleanup the durable subscription from the Admin Console, or using WLST commands or scripts. |
|
