Bug #80
RMI port change not possible
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
fixed
Description
When RMIServer starts up it attempts to use an InitialContext that has a PROVIDER_URL set to rmi://localhost. However, this is never updated for those occasions when the port has been configured differently, so the RMI service is not allowed to start in these conditions.
Pulling apart the URL to check if it is correct cannot be done by default for URLs with the RMI protocol. Either the URL string has to be parsed manually, or else a protocol handler needs to be registered for RMI. Since we use RMI URLs in a number of places, it seems to make sense to create the handler, making these legal to create.
Updated by Paula Gearon about 16 years ago
- Status changed from New to Closed
- Resolution set to fixed