You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org> on 2012/01/19 22:50:40 UTC
[jira] [Closed] (KARAF-476) The admin-command should be extended to
handle RMI-server-port settings
[ https://issues.apache.org/jira/browse/KARAF-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear closed KARAF-476.
--------------------------------
> The admin-command should be extended to handle RMI-server-port settings
> -----------------------------------------------------------------------
>
> Key: KARAF-476
> URL: https://issues.apache.org/jira/browse/KARAF-476
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Affects Versions: 2.2.0, 3.0.0
> Reporter: Uwe Korte
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.1, 3.0.0
>
> Attachments: rmiserverport.patch
>
>
> [KARAF-253] introduced a new property to configure the server-port of the RMI-Server (rmiServerPort in management.cfg).
> When creating a new instance, you can configure the RMI-registry port, but the RMI-server port is constantly set to "44444".
> So when starting the newly created instance the RMI-connector does not work, because normally the root-instance occupies port 44444.
> There should be a way to configure the RMI-server port when creating an instance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira