Products | Versions |
---|---|
TIBCO Enterprise Message Service | - |
Not Applicable | - |
Resolution:
Environment:
===========
All versions of TIBCO Enterprise Message Service
Resolution:
==========
No we do not provide a comprehensive list but we do have documented most of the error messages that are thrown by EMS server. Refer to the TIBCO EMS Users Guide, Appendix C, Error and Status Messages.
1). For server related errors (you can see these errors in EMS server logs), refer to the Error and Status message section in the TIBCO EMS User guide which lists most of the common errors.
2). For API related errors, you should refer to the appropriate API calls and their return values - error message/stack and interpret them. These are documented in the appropriate TIBCO EMS API reference guides. In most of the cases the JMS / EMS Java API provides detail on the error and status messages.
As of now, we do not use vendor specific error code for any JMSException thrown since the exception “reason” fields used are descriptive.
We do not list all possible exceptions as the depend on Java and the particular JVM implementation.
You can get the error code using JMSException.getErrorCode(). We have put all information into the exception's message.
Note that you can get the error message using the JMSException.getMessage(). Example:: "Connection to the server has been terminated".