BEA-040374 - JMS Module "uri" failed to un-load, e.
Description:
Unable to un-load the JMS module by the container.
Cause:
Internal error.
Error List
Error List for the ‘WL92-JMS’ Category
BEA-040513 - JMSServer "serverName". Error occurred while cleaning up Durable Subscriber after consumer creation failure : ClientId "clientId", subscriber name "subscriberName", topic "TopicName " Exception is "t".
Description:
An error occurred while cleaning up a durable subscriber on JMSServer “serverName” after a consumer creation failure, ClientId “clientId“, subscriber name “subscriberName“, topic “TopicName“.
Cause:
On createDurableSubscriber consumer creation failure, JMS attempts to cleanup and remove any durable subscription that may have already been recorded to the JMS persistent store, if the cleanup of the durable subscription from the JMS persistent store fails, this error will be logged. Please check exception logged for cause of failure.
BEA-040403 - JMS Module "uri" failed to de-activate, e.
Description:
Unable to de-activate the JMS module by the container.
Cause:
Internal error.
BEA-040404 - Failed to bind an entity of Foreign JMS Server "name" with their JNDI names due to e.
Description:
Failed to bind an entity of a foreign JMS server due to an exception.
Cause:
JNDI failure.
BEA-040406 - Failed to bind default connection factory "name" with its JNDI name "jndiName" due to e.
Description:
Failed to bind a default connection factory due to an exception.
Cause:
JNDI failure.
BEA-040409 - Failed to serialize the XML message.
Description:
Failed to serialize an XML message because an invalid XML document was specified.
Cause:
Attempted to serialize an invalid XML document.
BEA-040441 - Failed to parse the XML message.
Description:
Failed to parse an XML message because an invalid XML document was specified.
Cause:
Attempted to serialize an invalid XML document.
BEA-040442 - 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.
BEA-040493 - While attempting to change the targeting of JMS module "modName" an error occurred while activating the change. The exception returned is exc
Description:
While attempting to change the targeting of JMS module “modName” an error occurred while activating the change. The exception returned is exc
Cause:
The JMS Module failed to activate a prepared change during a targeting update.
BEA-040503 - Failed to $operation JMS Server "name" because the earlier attempt to $cause was failed.
Description:
Failed to deploy JMS Server because one of the deploment operation failed.
Cause:
Error occured during deployment of the JMS Server.