I currently have a non-servlet daemon that starts up at boot
time as "java KitServer" that talks to the outside world
through RMI. The KitServer manages many threads
that monitors a number of workflow tasks.
I have another servlet that displays the status of all these
threads called "KitQueue." It gets the status of the
threads from KitServer through RMI.
I am realizing that I can reduce quite a bit of RMI overhead
by merging the thread management into KitQueue. This
solves a number of complex issues for me, but I am concerned
that the thread performance, since it is thrown in with all
other active servlets, will drop and threads will not get
the attention they need. Or, that the interface side will suffer
performance problems because of all the active threads.
What do you all think about this from my description, as
short as it is? Is it ok to merge the two together? Is it ok
to run them all under one JVM, or should I use some
trick to cause another JVM to be running for the threads.
Any advice on this is appreciated before I start down
a bad path one of you may have done before.
Thanks to all on this list...Frank
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
