Notification Broker Notes

• Restarting the Notification Broker
• Testing the Notification Broker
• Cleaning out old Notification Broker subscriptions

Restarting the Notification Broker

To restart the notification broker and MessageBox, you first need to kill the running notification broker and MessageBox. First, log into rainier as drlead: ssh drlead@rainier, then go to the following directory: /u/drlead/services. Run ./findPids.sh and this will list the process ids that need to be killed before restarting the notification broker.

Then, to start up the notification broker and MessageBox, run now the ./servicesMsg.sh. This will start these services.

Testing the Notification Broker

Log into rainier as drlead. Then execute the following:
cd Forge/xsul/messenger/java
source setenv.sh
run_TestController.sh

If you get:

  Got lock
  Finished shuting down XC
  Deleted Subscription.
  Finished
  

then you are okay. If it hangs in the middle, it has problems.

Cleaning out old Notification Broker subscriptions

From an email from Alek:

  after you have account use 'mysql' on rainier to connect to database 'wsnt' and then

  DELETE FROM subscription;

  alek
  ps. here is an example:
  $ /l/local/packages/MySQL/latest/bin/mysql  -u smarru -p wsnt
  Enter password:
  Reading table information for completion of table and column names
  You can turn off this feature to get a quicker startup with -A

  Welcome to the MySQL monitor.  Commands end with ; or \g.
  Your MySQL connection id is 35991 to server version: 3.23.58-log

  Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

  mysql> SHOW TABLES;
  +-------------------+
  | Tables_in_wsnt    |
  +-------------------+
  | subscription      |
  | subscription_test |
  +-------------------+
  2 rows in set (0.01 sec)

  mysql> SELECT * FROM subscription;
  Empty set (0.00 sec)

  mysql>