[ https://issues.apache.org/jira/browse/KARAF-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jamie goodyear updated KARAF-476:
---------------------------------
Fix Version/s: 3.0.0
2.2.1
> 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: console
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|