I know that in the EJB model, it's not correct that beans launch their own threads. Is that also true for webapps in tomcat? Is there a portability issue if I have a servlet launch it's own thread for doing application-based housekeeping chores, such as listening for new messages via JMS and POP/IMAP, or periodically cleaning up "old" database entries, etc.? Thanks, David
- Tomcat 3.2, RMI, JNDI & Classloaders: a solution Carlos Pita
- Re: Is launching threads okay in a web app? David Wall
- Re: Is launching threads okay in a web app? David Bullock
- Re: Is launching threads okay in a web app? Craig R. McClanahan
- Re: Is launching threads okay in a web ap... David Wall
- Re: Is launching threads okay in a we... Craig R. McClanahan
- RE: Tomcat 3.2, RMI, JNDI & Classloaders: a s... Andrew Gilbert
- RE: Tomcat 3.2, RMI, JNDI & Classloaders:... Craig R. McClanahan
- RE: Tomcat 3.2, RMI, JNDI & Classloaders: a s... Andrew Gilbert