Error List

Posts Tagged ‘jmsmodulehelper’

BEA-045072 - 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.

WL103-JMSException , , , ,

BEA-045071 - 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.

WL103-JMSException , , , , , , , , , , , , ,

BEA-045073 - 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.

WL103-JMSException , , , ,

BEA-045074 - 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.

WL103-JMSException , , ,

BEA-045075 - 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.

WL103-JMSException , , ,

BEA-045069 - 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.

WL103-JMSException , ,

BEA-045070 - 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.

WL103-JMSException , ,

BEA-045069 - The JMS module entity named "entityName" of type "entityType" does not exist in JMSSystemResource "resourceName".

Description:
The JMS module entity refered 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.

WL92-JMSException , ,

BEA-045070 - The configuration entity named "entityName" of trype "entityType" does not exist in domain "domainName".

Description:
The configuration entity refered by the JMSModuleHelper API must exist in the specified domain.

Cause:
An attempt was made to reference a configuraiton entity that does not exist in the specified domain.

WL92-JMSException , ,

BEA-045071 - 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.

WL92-JMSException , , ,