Un-browsable messages in broker mesh with large volume of data

When processing large volumes of data we occasionally see 1 or 2 messages left behind on queues. Consumers are still connecting and waiting for the messages. When trying to browse them, the message returned is an empty screen. Restarting the brokers frees them up.During some spot checks it appears the store cursor may have been hit and the caching shut off. There could be a bug here. We are testing if useCache="false" on the destination policy works around the issue. Well also try to come up with a smaller test case than 8 mesh broker setup.