The jPOS MUX Pool, Part 3

See previous posts on the jPOS MUX Pool in Part 1 and Part 2 of this series.  This one is quicker.  I just wanted to pass along the little test I sent to our client after we made the changes discussed in Part 2:

1. Install
2. Ensure clean start-up
3. Watch traces for, say, 30 minutes to ensure echoes get generated correctly on both channels every 90 seconds.*
4. Try a CMC transaction.
5. STOP the ‘A’ channel
6. Do a transaction.  [Should get authorized via the ‘B’ channel.]
7. START the ‘A’ channel.
8. STOP the B’ channel.
9. Do a transaction.  [Should get authorized via the ‘A’ channel.]
10. START the ‘B’ channel.
11. Do a transaction.

* On Step 3, where I say "every 90 seconds," it's because 90 seconds was what we chose as our echo-interval.  Your value may differ here, but you get the idea.  You know your MUX Pool implementation is NOT working if the echoes get sent to one channel or another (but not both) over a period long enough to prompt a peer-disconnect from the other side.

Don't put this into production until you confirm that this works.