jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Erstellt: (JCR-396) RMI published Repository using the jcr-rmi library gets lots over time
Date Wed, 12 Apr 2006 13:10:21 GMT
RMI published Repository using the jcr-rmi library gets lots over time

         Key: JCR-396
         URL: http://issues.apache.org/jira/browse/JCR-396
     Project: Jackrabbit
        Type: Bug

  Components: rmi  
    Versions: 1.0    
 Environment: Jackrabbit Rev. 393410 WebApp
    Reporter: Felix Meschberger
 Assigned to: Felix Meschberger 
     Fix For: 1.1

The jcr-server/webapp project contains a servlet - RepositoryStartupServlet - which may be
used in a web app to start a repository and optionally register the repository with JNDI and
RMI. To register the repository with JNDI, the jcr-rmi library is used to create a Remote
repository instance, which is registered with the RMI registry. Inside the RMI implementation
mechanisms based on stub classes created by the RMI compiler are created to make the remote
repository available remotely. This includes creating a object table to map remote references
to local objects. This table stores references to the local object as weak references to support
distributed garbage collection.

Over time, it may now be that this remote repository instance is actually collected and the
object table cannot access it anymore thus preventing the repository from being accessed remotely.
To prevent this from happening, the RepositoryStartupServlet must keep a strong reference
to the remote repository and drop this reference when the servlet is destroyed and the repository

*NOTE:* This is an issue to all long running applications which publish repository instances
over RMI using the jcr-rmi library.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message