How do I organize my routine server software?

My software in Java 1.6 is a sort of crawler, going through the database and making certain calculations, in an endless loop. The calculations are of different types and organized as a collection of classes.

The question is - how do I deploy this application to the server? As a standalone application executed just once from command line and running endlessly (I don't like this approach), or with some application server? Please, give me a general advise.
Who is Participating?
sciuriwareConnect With a Mentor Commented:
Let JAVA do the threading.
Just split-off a thread per task.
In 2004 I had some process that was not endless, but ran over days that had to contain
some 50-100 threads that were fed to it on the run and all I had to do
is create the environment and 'spawn' the thread-workers.
The only concern is, with ending processes: what to do to signal a supervising
process that keeps track of the whole task.

In your case you only need to check of no thread crashes.
That means that the 'run' of every thread must catch all Exception types
and report them, in order to prevent termination of the application.

The best I see it, is creating a service for your java app, I presume that your application is for windows only.

The following two links have articles/tutorials about how one can make services for Java Apps.
An endless process on the database doesn't have to do anything with a server,
unless the access to the database is server-controlled.
So your process can be stand-alone (background) or client.

On most O.S.'s you can automate the start-up of such a process from
the system start-up, un-related to any login.
If however it needs survey and possible re-start, it's better
to have it run from an operator login-account.

It all depends on the nature of the process.
Is it critical? Do other processes depend on it's results?

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

technoparkcorpAuthor Commented:
My main concern is multi-threading in the software. Classes should be executed concurrently and I need to have like 50-100 concurrent threads/processes. If I do it manually inside the application, I will have a big headache with organizing all this.

It's much better to rely to some application server (Tomcat?), instead of manage this threading inside Java.

This application is NOT client-oriented, just a server side calculation. No GUI. And it's Linux, not Windows.
technically Tomcat is a web server, but can be used as application server, depends on how you use it.

The following links might help.

Regarding the job scheduling, I need to do some more research on how to do that in Linux. (Sort of replicating the windows based service in linux).
The main difference between LINUX and MSWINDOWS with threads is that threads on LINUX show up as if those were individual tasks/programs that only share
some addressing space.
That means that priorities can be fine-tuned and thread behavior can be monitored
on the outside (by ps or top).

P.S.: in the past I kept all threads in an

ArrayList<Thread> activeThreads;

and made the 'run()' just before termination move the thread to

ArrayList<Thread> terminatedThreads;

in order to have their status and result sets accessed from a monitor thread.


technoparkcorpAuthor Commented:
This 'threading' sounds like a very straight-forward solutions, which will lead to big problems later. I will have to think about this threading and about stability of the application in general... I don't like this idea.

I think that some application server may do this work for me. Maybe I need EJB here?
humanonomicsConnect With a Mentor Commented:
You don't need EJB in here, its for the web based applications, use of EJBs will just complicate things.

Just use Plain Java, that should work fine for you.
>>> about stability of the application in general... I don't like this idea.

Where does this idea come from?
A multi-threaded application will be more stable than a single-threaded
application that must loop through many tasks.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.