jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duke Fong" <df...@idc-global.com>
Subject RE: [jira] Erledigt: (JCR-291) jcr-server-webapp: RMI Registration unstable
Date Mon, 12 Dec 2005 19:39:37 GMT
Hello all.

I've been trying to work with the Jackrabbit JCR in Server/RMI mode.  Read
only and simple Value object insertions work fine.  

However, when I attempt to insert a file object (InputStream) via a JCR
client to a JCR Server via RMI, I get a socket exception.

Has anyone successfully performed this on the JCR Server?  If so, I would
love to share the experiences and get any input on the concept.

Regards,
Duke
 


Duke K. Fong
Integrated Data Corporation
dfong@idc-global.com
310-367-8412
310-815-2800 ext. 215
http://www.idc-global.com
 

-----Original Message-----
From: Felix Meschberger (JIRA) [mailto:jira@apache.org] 
Sent: Monday, December 12, 2005 4:20 AM
To: jackrabbit-dev@incubator.apache.org
Subject: [jira] Erledigt: (JCR-291) jcr-server-webapp: RMI Registration
unstable

     [ http://issues.apache.org/jira/browse/JCR-291?page=all ]
     
Felix Meschberger resolved JCR-291:
-----------------------------------

    Fix Version: 1.0.1
     Resolution: Fixed

Commited proposed patch.

Fixed in Rev. 356251

> 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


Mime
View raw message