On Dec 14, 2012, at 9:38 AM, "Howard W. Smith, Jr." <smithh032...@gmail.com> wrote:
> David (and any/all interested), > > Please click URL below to see my latest test results (along with code > changes). It took about 12 seconds to perform the update on the Windows > Server 2003 32bit 4GB RAM. > > https://issues.apache.org/jira/browse/OPENEJB-1968#comment-13532480 > > > I know, I know, I need to consider moving away from Apache Derby database > to a 'real database', but I hope to do that, ASAP. > > Thanks for all the responses/recommendations/etc... Absolutely amazing. This is fantastic!! Now that things are working, I suggest converting your @Schedule bean from @Stateless to @Singleton for the reasons mentioned before. If you someday (knock on wood) get totally nailed with a ton of emails/orders, the @Singleton with @Lock(WRITE) will prevent any situations where your timers start to overlap due to backlog and you accidentally process emails twice or more. -David
