karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] Commented: (KARAF-476) The admin-command should be extended to handle RMI-server-port settings
Date Wed, 23 Feb 2011 20:14:43 GMT

    [ https://issues.apache.org/jira/browse/KARAF-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998534#comment-12998534
] 

Jean-Baptiste Onofré commented on KARAF-476:
--------------------------------------------

I gonna submit the changes, you will be able to see the diff :)

> 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

       

Mime
View raw message