[
https://issues.apache.org/jira/browse/KARAF-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997391#comment-12997391
]
Uwe Korte commented on KARAF-476:
---------------------------------
I'd like to propose to implement the neccessary parameters for the
admin:create-command as
"-rs <RmiServerPort>" resp. "--rmi-server-port <RmiServerPort>"
and for the admin-command itself as "change-rmi-server-port"
I am attaching a patch that implements the functions. Changes to the
webconsole-admin-plugin are also included.
There are also some minor bug-fixes in the admin-plugin done (create did not
work, ...).
It was developed against the karaf-2.2.x-branch, but should be also appliable
to the trunk.
I hope, you like it ...
> 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
> Priority: Minor
>
> [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
