I know that java.util.Timer is not supposed to be used in the servlet or EJB containers (is the recommendation as strong for the servlet container?). Despite that advisement, I'd really like to understand what the specific risks are. I know that it spawns new threads to execute tasks. What if that spawned task does an EJB lookup and executes a session bean method? What if the Timer is used in a standalone app, and just has the tasks do remote connections to execute EJBs? If the Timer is created inside a session bean method, what sorts of problems could occur?
Note that the environment this would be on is Weblogic 8.1SP4. (I'm not recommending we do this, I'm just trying to find enough arguments against doing it.) =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
