You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Tim McConnell (JIRA)" <ji...@apache.org> on 2008/08/20 21:24:44 UTC

[jira] Resolved: (GERONIMODEVTOOLS-176) GeronimoServerBehaviourDelegate always uses rmi port 1099

     [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim McConnell resolved GERONIMODEVTOOLS-176.
--------------------------------------------

    Resolution: Fixed

Tried all combinations that I could think of. Ran server both in and outside of Eclipse using non-default RMI naming port and Eclipse is able to synchronize with the server. Deployed and undeployed various artifacts using port 2222 and all deployed and ran fine. Nice work. Applied to GEP trunk at r687428. Thanks BJ Reed for the patch.....

> GeronimoServerBehaviourDelegate always uses rmi port 1099
> ---------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-176
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-176
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.1.3
>            Reporter: Donald Woods
>            Assignee: Tim McConnell
>             Fix For: 2.1.3
>
>         Attachments: GERONIMODEVTOOLS-176.patch
>
>
> We need to allow the user to reconfigure the RMI port, for the cases where they have mapped the server to use something besides the default 1099 port.  Also, this would allow the plugin to support the new multiple server instance feature in the 2.0 server....

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.