Re: WorkManager replacement

2015-02-14 Thread Everton H . P . Custódio
Hi, When we needed that kind of functionality in tomcat we created an implementation of the old commonj.work and commonj.timer api using timers and threads. With that implementation we could port the application to websphere when needed. 2015-02-13 17:22 GMT-02:00 Terence M. Bandoian : > On 2/13

Re: WorkManager replacement

2015-02-13 Thread Terence M. Bandoian
On 2/13/2015 8:52 AM, Kevin Hale Boyes wrote: I'll look into the timers for sure. I've also noticed that my application (lots of code) also uses Executors and ExecutorService so I might do something there. One of the things that WorkManager gave us, and we take advantage of, is a callback handle

Re: WorkManager replacement

2015-02-13 Thread Kevin Hale Boyes
We use quartz already for scheduled tasks but the work that I'm talking about doesn't necessarily happen on a timer. The main use for us is the asynchronous execution of work once we've figured out which node in our cluster should handle it. I'm still going to consider java.util.concurrent since we

Re: WorkManager replacement

2015-02-13 Thread Kevin Hale Boyes
Spring is starting to appear to be the best choice. Thanks for the reference. On 13 February 2015 at 08:04, Daniel Mikusa wrote: > On Fri, Feb 13, 2015 at 9:49 AM, Kevin Hale Boyes > wrote: > > > We already use Spring in the project so I'll have a look there. > > > > > http://docs.spring.io/sp

Re: WorkManager replacement

2015-02-13 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dan, On 2/13/15 7:29 AM, Daniel Mikusa wrote: > On Thu, Feb 12, 2015 at 11:59 PM, Kevin Hale Boyes > wrote: > >> I currently have an application running on weblogic that I'm >> moving over to tomcat 8. One of the things the application does >> is

Re: WorkManager replacement

2015-02-13 Thread Daniel Mikusa
On Fri, Feb 13, 2015 at 9:49 AM, Kevin Hale Boyes wrote: > We already use Spring in the project so I'll have a look there. > http://docs.spring.io/spring/docs/current/spring-framework-reference/htmlsingle/#scheduling Dan > Thanks > > On 13 February 2015 at 05:29, Daniel Mikusa wrote: > > > O

Re: WorkManager replacement

2015-02-13 Thread Kevin Hale Boyes
I'll look into the timers for sure. I've also noticed that my application (lots of code) also uses Executors and ExecutorService so I might do something there. One of the things that WorkManager gave us, and we take advantage of, is a callback handler that lets us know when the work was accepted f

Re: WorkManager replacement

2015-02-13 Thread Kevin Hale Boyes
We already use Spring in the project so I'll have a look there. Thanks On 13 February 2015 at 05:29, Daniel Mikusa wrote: > On Thu, Feb 12, 2015 at 11:59 PM, Kevin Hale Boyes > wrote: > > > I currently have an application running on weblogic that I'm moving over > to > > tomcat 8. > > One of th

Re: WorkManager replacement

2015-02-13 Thread David kerber
On 2/13/2015 7:29 AM, Daniel Mikusa wrote: On Thu, Feb 12, 2015 at 11:59 PM, Kevin Hale Boyes wrote: I currently have an application running on weblogic that I'm moving over to tomcat 8. One of the things the application does is run background jobs using the commonj WorkManager. These jobs ar

Re: WorkManager replacement

2015-02-13 Thread Daniel Mikusa
On Thu, Feb 12, 2015 at 11:59 PM, Kevin Hale Boyes wrote: > I currently have an application running on weblogic that I'm moving over to > tomcat 8. > One of the things the application does is run background jobs using the > commonj WorkManager. These jobs are managed by weblogic which seems to b

WorkManager replacement

2015-02-12 Thread Kevin Hale Boyes
I currently have an application running on weblogic that I'm moving over to tomcat 8. One of the things the application does is run background jobs using the commonj WorkManager. These jobs are managed by weblogic which seems to be the recommended practice. What is the best/recommended way to run