Read a single book or technical article about JMS on your own !!! If you then have a problem, ask the forum, but do not ask for doing your own homework !
All of the information I got from book or technical article is about how to persist or cache message at server/middleware side and how to ensure delivery of message in the case of the target (receiving) application is unavailable (e.g. using durable message).
However, in my case I failed to send the message to the server/middleware in the first place due to network failure at the client side.
I would very much like to know the answer here too. I inherited some code that literally writes out the messages to a file on failure and resends when next message goes out if it can. I have the following settings on the client side...
and it is a clustered jboss on the remote side. If our remote side goes down, the messages are not resent . How do we tweak a setting so I can get rid of this code that persists and resends so that JBossMQ does the work for me?