Error List

Error List for the ‘WL92-JMSException’ Category

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

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 , , ,

BEA-045104 - While trying to find a topic or a queue we could not find the specific JMSServer requested.

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

WL92-JMSException , , , , , , , , , , , , , , ,

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

WL92-JMSException , , , ,

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

WL92-JMSException ,

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

WL92-JMSException ,

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

WL92-JMSException , , ,

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.

WL92-JMSException , , ,

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

WL92-JMSException , , , , , , ,