Bug #3068
closed
rmiregistry should be started programmatically
Added by Chad Berkley over 16 years ago.
Updated over 14 years ago.
Category:
distributed execution
Description
A user wanting to use the distributed system should not have to start the rmiregistry manually. kepler should start this for him/her when it starts up.
Users may start Kepler GUI at slave side. They also may only need to start slaveController especially when they can only access slave remotely.
So rmiregistery should be started either by starting Kepler GUI or a separate slave controller start command line (similar to previous ant runSlaveController).
It is fixed at Kepler trunk version 23363. rmi registry will be done automatically when using startSlave or startSlaveAsyn commands or starting Kepler GUI with master-slave module.
Original Bugzilla ID was 3068
Also available in: Atom
PDF