Am 29.11.2015 um 19:24 schrieb Martijn Slouter:
Thanks for your reply, comments below:
...
Any suggestion how I can accomplish the configuration, if I start
tomcat with the MPI web application using "mpirun -n 2 java ..." so
that only the first MPI process opens the tomcat communication ports,
while all other MPI processes disable their communicators?
As an alternative I can run the MPI application as a separate server
(tested across 16 hosts already), and use tomcat as a (serial) client
to this parallel server. The disadvantage is that huge amounts of data
need to be processed another time instead of being served directly
from the MPI application.
How does mpirun communicate to the started java process that it is the
first process? Maybe it is easier to write a wrapper that can decide
which tomcat configuration to use depending if this is your master
process or not. If you write this wrapper in java you could use an
embedded tomcat or jetty to startup a servlet container where needed.
Regards,
Stefan Mayr
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
