HP Integrity NonStop H-Series - Manual (Page 61)

D FAQ/Common problems and error conditions
Listed below are some of the frequently asked questions or common problems and error conditions
faced by users while using NSMQ. This list may contain some of the problems faced in ActiveMQ.
For a complete list of commonly asked questions in ActiveMQ, see the
ActiveMQ FAQ .
1. While creating a cluster, the following error displays:
ERROR - *1017* PATHCTL FILE (file-err-num)
The reason can be while creating a cluster, the PATHMON configuration file [PATHCTL] is
created in the sub volume of pathway process. If the volume already has PATHCTL file used
by some other TSMP process, then this error is displayed.
Modify the CLUSTER.rsp and change the sub volume name of the pathway process to point
to another existing volume to which the logged-in user has permission.
2. Unable to create the schema during installation of NSMQ.
•
Ensure that the SQL/MX version is >= 3.1
•
Ensure that the JDBC/MX T2 or T4 driver version is >= 3.2
•
Ensure the SQL/MX catalog and schema exists and are empty (they must not contain any
tables, indexes, etc.)
3. There is no communication between the TCP/IP subsystem and the brokers or
producers/consumers. What could be wrong?
Check the TS/MP, CIP subsystem. It may not be configured properly. For more information,
see the TCP/IP Configuration and Management Manual.
4. The broker log displays “Port already in use/port already bound”.
The following may be possible reasons:
•
Another process is listening on the port configured for local clustering.
•
The slave broker log may be displaying this message.
•
If the master broker log is displaying the message, some other NonStop process is already
listening on that port. JMX consoles may not be able to connect to the broker.
5. NonStop TCP/IP DEFINES not configured properly.
Ensure that all the IP-CIP DEFINES are configured for the user running the NSMQ broker.
a.
To verify this, ensure the $JAVA_HOME/install/javachk program runs without errors.
b. The TCP/IP process provided during NSMQ installation is configured for CIPSAM or
TCP6SAM. For more information, see the TCP/IP Configuration and Management Manual.
6. Can I create brokers having same names in two different clusters?
Broker names must be unique across all the clusters. For example, if you create a broker B1
on cluster C1, you cannot have broker name B1 on cluster C2 (or any other cluster).
Also, there must be no PATHMON process name configured with the same cluster name and
no process must be running with the same broker.
NOTE: It is mandatory to have different SQL/MX catalog/schema across different NSMQ
installations.
7. Can I uninstall NSMQ when clusters are running?
The uninstall program requires all clusters to be down. Before you uninstall, stop all the running
instances of NSMQ and remove all the clusters.
The uninstall program may not remove all the files from the installed directory. You must delete
these files/directory manually.
8. Can I remove a broker when the cluster is running?
Yes, but exceptions are thrown when a broker is removed from the running cluster. HP
recommends you to stop the cluster and remove the broker.
61