We are using Messaging 1.4.4 and I am reviewing the documents and our configuration files. I happened to come across this WARNING in section 4.1.2, but it gives no clue as to why the ServerPeerID must be unique for a non-clustered or what might happen if you don't ensure uniqueness. Any thoughts, ideas on this???
Each node must have a unique ServerPeerID irrespective of whether you are using clustering.
The ServerPeerID is used to generate message ID for each message. If you have multiple JBM servers their message IDs may be duplicate.
Unless those servers have nothing to do with each other, duplicated message IDs can cause problems. For example if you use a bridge to move the messages from one server to another.