We're seeing a puzzling behaviour where the same tuple is acked several times at the spout. This is causing problems, as we've assumed each tuple is only acked once. Is it valid for storm to ack the same message id several times, or have we screwed up the topology somewhere? In what situations might this happen?
Thanks, SimonC
