Project

General

Profile

Bug #3068

rmiregistry should be started programmatically

Added by Chad Berkley over 11 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
distributed execution
Target version:
Start date:
01/16/2008
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3068

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.

History

#1 Updated by jianwu jianwu over 9 years ago

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).

#2 Updated by jianwu jianwu over 9 years ago

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.

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 3068

Also available in: Atom PDF