I am trying to use Asynchronous Beans in one of my project to leaverage asynchronous processing (basically defer the processing and insulate the client from having to wait until all the processing is done). We are using IBM Websphere 6.1 and Java 1.5.
1) I would like to find out if any you have use this feature successfully in your APP server environment?
2) My idea is to start the async bean from a stateless EJB bean (Container Managed). Will this work? Is there any gotchat/catches here I need to be aware of?
When I run this asynchronous beans (with TX REQUIRED) I see that the EJB starts a transaction (I can verify that by looking at the extendedjtatransaction object of Websphere's getLocalId and getGlobalId() methods). For Asynchronous beans, I see the local id is 0, and global id is null (There is some documentation in IBM site, but that is inadequate, I would like to hear from someone who has used this successfully)
Any quick and timely input on this will be of great use.
Thanks a lot. [ November 11, 2008: Message edited by: Ram Kumar ]