Resolution: Duplicated cmname can lead to a flood of _RVCMQ.REGISTERED protocol messages. The symptom can be reproduced by running tests with the sample program cmqmember.java and cmsender.java (by removing the setTimeLimit). You could avoid the duplicated cmname problem by monitoring the “REGISTERATION.COLLISION” advisory.
Test steps:
1). tibrvlisten "_RVCMQ.REGISTERED.>
2). java cmqmembero
3). Start three “java cmsender” with the same cmname at the same time. Two cmsender can reproduce the problem also but three cmsenders is easier to reproduce.
4). Before the sender finishes sending 10 messages, restart the cmqmember.
5). If all the cmsender messages are confirmed, the cmsender will exit. Restart the cmsender.
6). If step 5 above did not reproduce the "REGITERED" flooding issue, start the cmsender again and before all the messages are confirmed, stop the cmqmember until all 10 messages are published. Restart the cmqmember.
7). If step 6 above did not reproduce the issue, repeat step 6 several times as you should be able to reproduce the issue.