This is not possible through the JMS API. As a general rule, message transports are optimized to deliver messages as fast as possible and lack schedulers to hold a message for redelivery at some arbitrary interval. Assuming there is a transport provider that does have such functionality, anything you write would then be bound to that transport provider because, although the code might be JMS-compliant, the app itself would rely on this vendor-specific behavior.
In this situations, Container Managed Transactions are used. The transaction is started when the onMessage method is called by the container and is commited if the onMessage method finishes successfuly (it will fail when a RuntimeException is thrown or setRollBackOnly is called from the MessageDrivenBean context). You can also configure the redelivery interval and maximum number of redelivery's.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.