I have written a simple server which listens to a queue and when it gets a message processes it. Now I want this server to run all the time and have the following options - I am using Tomcat.
1. Write a script which runs the main method and periodically checks if the process is running , if not then start the process.
2. (I am leaning towards this one) Write a servlet that initializes on start up and starts the server. This would be nice since I can let the container manage the starting/stopping etc, also there is a web console for people to monitor the server and I can add more things for monitoring. Is there any reason this is not a good idea ? What are the limitations of running my process within the container ?
Originally posted by Rob Prime: I think running the application as a service is a better idea. For Windows you need to search for "Java Service Wrapper", a solution that can wrap your Java programs into a Windows service.
The "Java Service Wrapper" is not just for windows - it is for almost all platforms [ September 30, 2008: Message edited by: Rene Larsen ]