[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Once and only once delivery?

[genman]

But then, what's the use of tracking on the client side when the client doesn't know the message did arrive successfully?

I've had to deal with billable message traffic coming from an SMPP interface. Ultimately, to prevent the system from billing twice, the client had to supply a unique message ID. This ID was tracked in a central database.

Something like this could be easily managed by a JBossCache instance, which would manage replication and expiration of old data.  It might be only useful to a few users, and only useful if the client didn't have a transaction going.

A more common issue than the JMS client reporting error, is that the interface which generates the JMS traffic (such as an SMPP or HTTP interface for instance), fails to send back "success" and the remote system reattempts the same SMPP/HTTP/etc. transaction again.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977124#3977124

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977124