java - Concurrent database access pattern for web applications -


i'm trying write spring web application on weblogic server makes several independent database selects(i.e. can safely called concurrently), 1 of takes 15 minutes execute.

once results fetched, email containing results sent user list.

what's way around problem? there spring library can or go ahead , create daemon threads job?

edit: have done @ application layer (business requirement) , email sent out web application.

  1. are sure doing optimally? 15 minutes long time unless have gabillion rows across dozens of tables , need heckofalot of joins....this highest priority -- why taking long?

  2. do email job @ set intervals, or invoked web app? if set intervals, should in outside job, possibly on machine. can use daemons or quartz scheduler.

  3. if need fire process off web app, need asynchronously. use jms, or have table enter new job request, daemon process looks new jobs every x time period. firing off background threads possible, error prone , not worth complication, since have other valid options simpler.


Comments

Popular posts from this blog

python - Scipy curvefit RuntimeError:Optimal parameters not found: Number of calls to function has reached maxfev = 1000 -

c# - How to add a new treeview at the selected node? -

java - netbeans "Please wait - classpath scanning in progress..." -