Previous Contents Index Next |
Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 2 Error Messages Reference

> ## Chapter 15
> Java Message Service

> This chapter lists error messages that originate from the Java messaging service.

> ##

> JMS

> Java Message Service is a standard set of interfaces and semantics that define how a JMS client accesses the facilities of a JMS message service. These interfaces provide a standard way for Java programs to create, send, receive, and read messages.

> This chapter contains error messages that occur in the JMS system.

> ##### JMS5004

> Severity | SEVERE
> Description | The session could not be closed.
> Action | See exception message and stack trace for information on why the session could not be closed.

> ##### JMS5005

> Severity | SEVERE
> Description | Resource handle could not be created.
> Action | See exception message and stack trace for information on why the resource handle could not be created.

> ##### JMS5006

> Severity | SEVERE
> Description | Resource handle could not be registered.
> Action | See exception message and stack trace for information on why the resource handle could not be registered.

> ##### JMS5007

> Severity | SEVERE
> Description | An illegal access to the connection factory was performed. J2EE components must access JMS connection factories through a resource-ref in java:comp/env subcontext.
> Action | Make sure that the correct application accesses resource-ref in java:comp/env subcontext.

> ##### JMS5008

> Severity | WARNING
> Description | The resource-reference for JMS connection factory specifies container authorization but no user name and password is available.
> Action | Specifying default-resource-principal for the JMS resource-reference removes this warning message. If you intend to use the resource sign-on information configured in the JMS connection factory resource, then you may ignore this warning message.

> ##### JMS5009

> Severity | WARNING
> Description | Calling createQueueConnection() on resource-ref with APPLICATION authentication.
> Action | Use createQueueConnection(username, password) instead.

> ##### JMS5010

> Severity | WARNING
> Description | JMS connection with container authentication cannot programmatically set user name and password.
> Action | Correct the application to use the no-argument JMS connection creation method.

> ##### JMS5011

> Severity | WARNING
> Description | Calling createTopicConnection() on resource-ref with APPLICATION authentication.
> Action | Use createTopicConnection(username, password) instead.

> ##### JMS5012

> Severity | SEVERE
> Description | The connection factory could not be found.
> Action | Check the stack trace following this error message for reason.

> ##### JMS5014

> Severity | SEVERE
> Description | A pooling exception occurred while creating resource. The create resource handle failed.
> Action | See the stack trace for more information on why it failed.

> ##### JMS5016

> Severity | SEVERE
> Description | An error occurred while installing JMS resources.
> Action | See the error message for reason. Check the stack trace following this error message for more information.

> ##### JMS5018

> Severity | SEVERE
> Description | An error occurred while deleting a JMS connection factory resource.
> Action | See the error message and the stack trace following this error message for information on how to fix this error.

> ##### JMS5020

> Severity | SEVERE
> Description | An error occurred while deleting a JMS destination administered object.
> Action | See the error message and the stack trace following this error message for reason.

> ##### JMS5022

> Severity | SEVERE
> Description | This message can occur during application server initialization and the application server aborts. It indicates conflicting configuration of JMS port number.
> Action | Assign an unused port number to the application server's JMS service and restart the application server.

> ##### JMS5024

> Severity | SEVERE
> Description | The message queue broker startup failed for an unknown reason. Consequently, the application server aborts.
> Action | Check the application server's JMS service configuration. See the exception stack trace following this message. If it does not provide sufficient information, lower the application server’s log level and try again. See the message queue broker log file also. Start the message queue broker manually to narrow down the cause of failure.

> ##### JMS5027

> Severity | SEVERE
> Description | An exception occurred while creating JMS destination administered object.
> Action | See the exception message and the stack trace following this error message for reason.

> ##### JMS5028

> Severity | SEVERE
> Description | An exception occurred while creating JMS connection factory resource.
> Action | See the exception message and the stack trace following this error message for reason.

> ##### JMS5031

> Severity | SEVERE
> Description | An exception occurred while creating JMS connection factory resource.
> Action | See the exception message and the stack trace following this error message for reason.

> ##### JMS5033

> Severity | INFO
> Description | Unable to attach to an existing JMS service broker process. This message occurs during application server initialization. It precedes a SEVERE error and causes the application server to abort. It indicates a problem in the application server's JMS service configuration. For instance, JMS service port number may already be used by another server application.
> Action | Check the JMS service configuration. Assign an unused port number to the JMS service and restart the application server.

> ##### JMS5034

> Severity | INFO
> Description | Unable to start the JMS service broker process. This message can occur during application server initialization. It precedes a SEVERE error and causes the application server to abort. It indicates the application server’s inability to spawn the message queue broker process. This can happen due to a variety of reasons such as, improper installation (missing message queue broker packages), or lack of system resources such as, swap space, and so on.
> Action | Examine the Java exception details following this message. Ensure that the system has sufficient swap space. You may also want to verify if the message queue broker can be started manually.

> ##### JMS5035

> Severity | INFO
> Description | This message can occur during application server initialization. It precedes a SEVERE error and causes the application server to abort. It indicates that the application server tried to start the message queue broker but could not establish communication with it.
> Action | Make sure that the message queue broker started. If you have a large number of persistent messages pending, the message queue broker may take a long time to start. If this is the case, you may want to check the application server's JMS service configuration and increase the initialization timeout value. If the message queue broker is not running, check the log file.

> ##### JMS5036

> Severity | INFO
> Description | This message can occur during the application server initialization. It precedes a SEVERE error and causes the application server to abort. It indicates that the message queue broker runs as a separate process and generates a separate log file. So in order to isolate the initialization problem, it may be necessary to check both the application server log file and the message queue broker log file.
> Action | See the message queue broker log file for the error messages specific to the JMS service.

> Previous Contents Index Next

> Copyright 2005 Sun Microsystems, Inc. All rights reserved.