NonStop JMS User's Manual (NonStop JMS 2.0+)

NonStop Server for Java Message Service User’s Manual—522356-002
A-1
A Error Reporting and Messages
This appendix provides information about JMS API error messages, the NSJMS API
logging facility, SQL messages, administrative utility error messages, and
administrative utility warning messages.
JMS API Error Messages
JMS API error messages and exceptions are described in The Java Message Service
specification (see Compliance Information on page 1-4).
NSJMS API Logging Facility
All log records generated by the NSJMS API are contained in the nsjms.log file. The
type of records generated by the NSJMS API is determined by the Logger.loglevel
setting in the nsjms.properties file. See Logger.loglevel on page 2-14 for a
description of the level of records that can be generated and reported to the
nsjms.log File.
SQL/MX Messages
SQL/MX reports exception condition messages during the execution of an NSJMS
TopicSubscriber or an NSJMS QueueReceiver. Exception conditions are returned to
the JMS client as a javax.jms.JMSException that is linked with a nested
java.sql.SQLException. The fields returned in the SQLException area are
SQLCODE, SQLSTATE, CONDITION_NUMBER and MESSAGE_TEXT.
The SQLCODE field returns a value that describes error information after the execution
of an embedded SQL statement:
The SQLSTATE field returns a five-character variable string with two parts. The first part
is a two-character class code, and the second part is a three-character subclass code.
An SQLSTATE value of 00000 indicates successful completion. See the SQL/MX
Programming Manual for C and Cobal for a listing of the class and subclass values.
The CONDITION_NUMBER field returns the number of an exception condition.
The MESSAGE_TEXT field returns the SQL message number and the message text.
Value Description
< 0 An error occurred.
> 0 (<> 100) A warning occurred.
100 No data was found.
0 The statement completed successfully.