GlassFish v3 Error Message Reference
\

JMS

This page lists error messages with the JMS prefix.

See How to Contribute for more information about adding to and enhancing the information on this page.

----JMS5001 Starting JMS service...

Cause

TBD

Solution

TBD

----JMS5002 Binding -(0)

Cause

TBD

Solution

TBD

----JMS5003 Couldn't start JMS service...

Cause

TBD

Solution

TBD

----JMS5004 Session cannot be closed

Cause

TBD

Solution

TBD

----JMS5005 resource handle could not be created

Cause

TBD

Solution

TBD

----JMS5006 resource handle could not be registered

Cause

TBD

Solution

TBD

----JMS5007 Illegal connection factory access to -(0). J2EE Components should access JMS Connection Factories through a resource-ref in java:comp/env

Cause

TBD

Solution

TBD

----JMS5008 A resource-reference for JMS Connection Factory specifies container authorization but no username/password is available -(0)

Cause

TBD

Solution

TBD

----JMS5009 Calling createQueueConnection() on resource-ref with APPLICATION authentication. Should use createQueueConnection(username, password) instead

Cause

TBD

Solution

TBD

----JMS5010 JMS Connection with container authentication cannot programmatically set username and password

Cause

TBD

Solution

TBD

----JMS5011 Calling createTopicConnection() on resource-ref with APPLICATION authentication. Should use createTopicConnection(username, password) instead

Cause

TBD

Solution

TBD

----JMS5012 Connection Factory -(0) not found

Cause

TBD

Solution

TBD

----JMS5013 Connection Factory not found

Cause

TBD

Solution

TBD

----JMS5014 Unexpected pooling exception creating resource

Cause

TBD

Solution

TBD

----JMS5015 Install JMS resources ...

Cause

TBD

Solution

TBD

----JMS5016 Install JMS resources error: -(0)

Cause

TBD

Solution

TBD

----JMS5017 Install JMS resources throw Exception

Cause

TBD

Solution

TBD

----JMS5018 Delete Connection factory resource error: -(0)

Cause

TBD

Solution

TBD

----JMS5019 Delete connection factory resource got exception

Cause

TBD

Solution

TBD

----JMS5020 Delete destination resource error: -(0)

Cause

TBD

Solution

TBD

----JMS5021 Delete destination resource got exception

Cause

TBD

Solution

TBD

----JMS5022 A Message Queue broker instance -(0) is already running at port -(1). Please configure a different port number for the JMS service.

Cause

TBD

Solution

TBD

----JMS5023 JMS service successfully started. Instance Name = {0}, Home = -(1).

Cause

TBD

Solution

TBD

----JMS5024 JMS service startup failed.

Cause

TBD

Solution

TBD

----JMS5025 JMS service shutting down.

Cause

TBD

Solution

TBD

----JMS5026 JMS service shutdown complete.

Cause

TBD

Solution

TBD

----JMS5027 Exception in creating JMS destination administered object -(0): -(1)

Cause

TBD

Solution

TBD

----JMS5028 Exception in creating JMS connection factory resource -(0): -(1)

Cause

TBD

Solution

TBD

----JMS5029 Successfully attached to an existing Message Queue broker. Instance Name = {0}

Cause

TBD

Solution

TBD

----JMS5030 JMS resource {0} Type: {1} is disabled.

Cause

TBD

Solution

TBD

----JMS5031 Exception in creating JMS destination administered object

Cause

TBD

Solution

TBD

----JMS5032 Exception in creating JMS connection factory resource

Cause

TBD

Solution

TBD

----JMS5033 Could not attach to an existing JMS service broker process.

Cause

TBD

Solution

TBD

----JMS5034 Could not start the JMS service broker process.

Cause

TBD

Solution

TBD

----JMS5035 Timed out after {0} milliseconds while trying to verify if the JMS service startup succeeded.

Cause

TBD

Solution

TBD

----JMS5036 More details may be available in the log file for the JMS service broker instance {0}. Please refer to the JMS provider documentation for the exact location of this log file.

Cause

TBD

Solution

TBD

----JMS5037 Check permissions of MQ instance directory {0}

Cause

TBD

Solution

TBD

----JMS5038 jms-service element in domain.xml is configured to have type={0}. JMS service will be started locally only if type is LOCAL.

Cause

TBD

Solution

TBD