| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server Message Queue 4.5 Developer's Guide for Java Clients |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle GlassFish Server Message Queue 4.5 Developer's Guide for Java Clients |
3. Message Queue Clients: Design and Features
4. Using the Metrics Monitoring API
6. Embedding a Message Queue Broker in a Java Client
This appendix provides reference information for warning messages and for error codes returned by the Message Queue client runtime when it raises a JMS exception.
A warning message is a message output when the Message Queue Java client runtime experiences a problem that should not occur under normal operating conditions. The message is displayed where the application displays its output. Usually, this is the window from which the application is started. Table A-1 lists Message Queue warning messages.
In general, a warning message does not cause message loss or affect reliability. issues. But when warning messages appear constantly on the application’s console, the user should contact Message Queue technical support to diagnose the cause of the warning messages.
Error codes and messages are returned by the client runtime when it raises an exception. You can obtain the error code and its corresponding message using the JMSException.getErrorCode() method and the JMSException.getMessage() method. Table A-2 lists Message Queue error codes.
Note that warning messages and error codes are not defined in the JMS specification, but are specific to each JMS provider. Applications that rely on these error codes in their programming logic are not portable across JMS providers.
|