trebor iksrazal wrote: > Wouldn't a Mailet > block, only returning after a db write? If the db is > down, and there were a lot of timeouts for a lot of > messages, would a JMS queue processed in intervals, > via extending GenericMailet, help? My idea is to use > Message-driven beans and entity beans to write emails > to the db.
In order to be sure that messages were not lost, the JMS queue would need to be persistent. Persistence would most likley be provided by storing the JMS message in a database. So, rather than circumventing any database bottleneck problems, we would be increasing the database activity, making such problems more likely. James runs in an Avalon container which is not J2EE compatible - there are no message driven or entity beans to use. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
