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

Error Reporting and Messages
NonStop Server for Java Message Service User’s Manual522356-002
A-2
Administrative Utility Error Messages
For example, the following error message might be displayed if an exception occurs
while preparing an embedded SQL statement:
See the SQL/MX Messages Manual for information about SQL messages.
Administrative Utility Error Messages
Add Failed
Cause. An attempt was made to add a queue or topic name that already exists.
Effect. The queue or topic name was not added.
Recovery. Reenter the command, specifying a queue or topic name that does not
already exist.
Destination ID Already Exists
Cause. The specified destination ID already exists.
Effect. The command is not executed.
Recovery. Reenter the command, specifying a different destination ID.
javax.jms.JMSException: SQL error -4081 reading messages: java.sql.SQLException:
SQLCODE: -4081
SQLSTATE: 42000
condition number: 1
message text: *** ERROR[4081] SQL/MP error:
*** ERROR from SQL [-4004]: Object \KONA.$DATA30.NSJMS.MESSAGE is not an SQL table
or view.
SQLCODE: -4082
SQLSTATE: 42000
condition number: 2
message text: *** ERROR[4082] Table \KONA.$DATA30.NSJMS.MESSAGE does not exist or
is inaccessible.
SQLCODE: -8822
SQLSTATE: X0X08
condition number: 3
message text: *** ERROR[8822] Unable to prepare the statement.
at com.tandem.nsjms.client.JmsMessageConsumer.receiveNoWaitIntJNI(JmsMessage
Consumer.java, Compiled Code)
at com.tandem.nsjms.client.JmsMessageConsumer.receive(JmsMessageConsumer.java,
Compiled Code)
at com.tandem.nsjms.examples.SimpleReceiver.main(SimpleReceiver.java, Compiled
Code)
NSJMS Err: Add queue|topic name failed:queue|topic name
already exists.
NSJMS Err: Destination ID already exists