[
https://issues.apache.org/jira/browse/KARAF-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998330#comment-12998330
]
Uwe Korte commented on KARAF-476:
---------------------------------
Jean-Baptiste, thank you very much for reviewing and correcting the patch.
I thought about enhancing the admin:list command too, but when you see it from
the adminstration-side there're actually just parameters listed for connecting
and identifiying instances.
Of course, from the configuration-side the rmiServerPort would be a valuable
information, but shouldn't there also the VM-Parameters be listed (as they can
also be configured)?
admin:clone: shame on me... Sorry, there I was blind on the "trunk"-eye.
Should have seen this.
rmiServerPort property not used everywhere: Can you give me a hint? I thought
that I found all relevant places ... If neccessary I'll correct it asap.
> 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
> 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
