title: Java internal message queue /JMS
body: <p>I have a web application i am rewriting that currently performs a large amount of audit data sql writes. Every step of user interaction results in a method being executed that writes some information to a database. 
  This has the potential to impact users by causing the interaction to stop due to database problems.</p>
  
  <p>Ideally I want to move this is a message based approach where if data needs to be written it is fired off too a queue, where a consumer picks these up and writes them to the database. It is not essential data, and loss is acceptable if the server goes down. </p>
  
  <p>I'm just a little confused if I should try and use an embedded JMS queue and broker, or a Java queue. Or something I'm not familiar with (suggestions?)</p>
  
  <p>What is the best approach? </p>
  
  <p>More info: 
  The app uses spring and is running on websphere 6. All message communication is local, it will not talk to another server. </p>