Project

General

Profile

Actions
Copy link

Bug #3068

closed

rmiregistry should be started programmatically

Added by Chad Berkley almost 17 years ago. Updated over 14 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
jianwu jianwu
Category:
distributed execution
Target version:
master-slave-2.0.0
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.

Actions
Copy link
 #1

Updated by jianwu jianwu almost 15 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).

Actions
Copy link
 #2

Updated by jianwu jianwu over 14 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.

Actions
Copy link
 #3

Updated by Redmine Admin over 11 years ago

Original Bugzilla ID was 3068

Actions
Copy link

Also available in: Atom PDF