You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2005/12/15 10:16:53 UTC

[jira] Reopened: (JCR-291) jcr-server-webapp: RMI Registration unstable

     [ http://issues.apache.org/jira/browse/JCR-291?page=all ]
     
Jukka Zitting reopened JCR-291:
-------------------------------


Reopened to change fix version to 1.0.

> jcr-server-webapp: RMI Registration unstable
> --------------------------------------------
>
>          Key: JCR-291
>          URL: http://issues.apache.org/jira/browse/JCR-291
>      Project: Jackrabbit
>         Type: Improvement
>  Environment: SVN Rev. 355696
>     Reporter: Felix Meschberger
>     Assignee: Felix Meschberger
>     Priority: Minor
>      Fix For: 1.0.1
>  Attachments: RMIRegistry_fm_051211.diff
>
> Registration of the repository to a RMI registry in RepositoryStartupServlet.registerRMI uses web application parameters inconsistently and may not always succeed registering the repository.
> Today, the registerRMI uses these parameters for registration to RMI:
>     rmi-host : The name of the host on which the registry is running
>     rmi-port : The port on which the registry is running
>     rmi-uri : An RMI URI to use for registration
>     repository-name : The name to bind the repository to
> The problem is, that rmi-port is used to try to create the registry to make sure a registry is running on the local host. The rmi-uri is used to register the repository using the static Naming.bind method. If the rmi-uri is not configured, the URI is created from rmi-host, rmi-port and repository-name.
> This may now create a bunch of problems: If the rmi-port and rmi-uri configurations do not match, registration fails, if rmi-host does not resolve to an IP address to which the registry is bound, registration fails.
> I encounter this issue, when trying to register the repository to an RMI registry using default rmi-port configuration (rmi-host and rmi-uri not configured) when running the web app in Jetty.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira