Comments on: Scheduling a servlet in WebSphere Application Server http://www.albeesonline.com/blog/2008/01/16/scheduling-a-servlet-in-websphere-application-server/ Something about JEE and WebSphere. Java, JEE and WebSphere tips and tutorials Thu, 04 Dec 2008 00:47:37 +0000 http://wordpress.org/?v=abc By: carl http://www.albeesonline.com/blog/2008/01/16/scheduling-a-servlet-in-websphere-application-server/#comment-1598 carl Wed, 09 Jul 2008 11:02:32 +0000 http://www.albeesonline.com/2008/01/16/scheduling-a-servlet-in-websphere-application-server/#comment-1598 It appears you can use the Scheduler API for what you want (servlet) - bit check the Info Center for more details under the 'Developing and scheduling tasks' section: "Creating and manipulating scheduled tasks through the Scheduler interface is only supported from within the EJB container or Web container (Enterprise beans or servlets). Looking up and using a configured scheduler from a J2EE application client container is not supported." It appears you can use the Scheduler API for what you want (servlet) - bit check the Info Center for more details under the ‘Developing and scheduling tasks’ section:
“Creating and manipulating scheduled tasks through the Scheduler interface is only supported from within the EJB container or Web container (Enterprise beans or servlets). Looking up and using a configured scheduler from a J2EE application client container is not supported.”

]]> By: carl http://www.albeesonline.com/blog/2008/01/16/scheduling-a-servlet-in-websphere-application-server/#comment-1589 carl Wed, 09 Jul 2008 09:38:03 +0000 http://www.albeesonline.com/2008/01/16/scheduling-a-servlet-in-websphere-application-server/#comment-1589 HI. IBM notes:When inside these managed environments, the Timer API (or WebSphere Scheduler API) is a much better alternative to java.util.Timer: ** java.util.Timer should never be used within managed environments, as it creates threads outside the purview of the container. ** HI. IBM notes:When inside these managed environments, the Timer API (or WebSphere Scheduler API) is a much better alternative to java.util.Timer: ** java.util.Timer should never be used within managed environments, as it creates threads outside the purview of the container. **

]]> By: Albin Joseph http://www.albeesonline.com/blog/2008/01/16/scheduling-a-servlet-in-websphere-application-server/#comment-780 Albin Joseph Mon, 23 Jun 2008 08:09:15 +0000 http://www.albeesonline.com/2008/01/16/scheduling-a-servlet-in-websphere-application-server/#comment-780 As you mentioned if we create our own thread in WebSphere, none of the WebSphere resources will be available in our thread. So if our scheduler needs the context or any other container provided information we should not go for the TimerTask scheduler approach. We should use this approach only if we need a scheduler that does not require any of the container resources. I feel this approach is more like creating a scheduler using Cron job or something. I was using this approach for polling a directory and for invoking a webservice using the polled data. In my case it worked well as I was not using any of the WebSphere resources. This approach is good if we need a very simple scheduler in WebSphere that does not require any container resources. Unluckily there is no other option to schedule a servlet in WebSphere as far as I know. The WebSphere scheduler or alarm manager is used for scheduling an EJB or JMS. Correct me if I am wrong. As you mentioned if we create our own thread in WebSphere, none of the WebSphere resources will be available in our thread. So if our scheduler needs the context or any other container provided information we should not go for the TimerTask scheduler approach.

We should use this approach only if we need a scheduler that does not require any of the container resources. I feel this approach is more like creating a scheduler using Cron job or something. I was using this approach for polling a directory and for invoking a webservice using the polled data. In my case it worked well as I was not using any of the WebSphere resources. This approach is good if we need a very simple scheduler in WebSphere that does not require any container resources.

Unluckily there is no other option to schedule a servlet in WebSphere as far as I know. The WebSphere scheduler or alarm manager is used for scheduling an EJB or JMS. Correct me if I am wrong.

]]> By: Gary Pankey http://www.albeesonline.com/blog/2008/01/16/scheduling-a-servlet-in-websphere-application-server/#comment-751 Gary Pankey Sun, 22 Jun 2008 12:30:18 +0000 http://www.albeesonline.com/2008/01/16/scheduling-a-servlet-in-websphere-application-server/#comment-751 Thanks for the information. One question. I typically avoid creating my own threads within the WebSphere container because I'm taking away resources away from the container. I realize if I were to use something like the WebSphere scheduler or alarm manger resources will be used but at least WebSphere will know about the resource use. The example you provide is lightweight and straitforward and therefore I'm inclined to use the strategy as you have documented. Can you comment on your experiences with using this strategy in WebSphere and creating your own threads within the container? Thanks for the information. One question.

I typically avoid creating my own threads within the WebSphere container because I’m taking away resources
away from the container. I realize if I were to use something like the WebSphere scheduler or alarm manger
resources will be used but at least WebSphere will know about the resource use. The example you provide is
lightweight and straitforward and therefore I’m inclined to use the strategy as you have documented.

Can you comment on your experiences with using this strategy in WebSphere and creating your own threads within
the container?

]]> By: leonardo http://www.albeesonline.com/blog/2008/01/16/scheduling-a-servlet-in-websphere-application-server/#comment-106 leonardo Sat, 17 May 2008 09:54:34 +0000 http://www.albeesonline.com/2008/01/16/scheduling-a-servlet-in-websphere-application-server/#comment-106 Thanks, exacly what I looking for :-) Thanks, exacly what I looking for :-)

]]>