Agree with you on the inefficiencies front. At least I am facing severe performance issues. Did ask a question on the forum couple of days back to get an opinion on proper Type2 , Type3 deployment models.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 07 November 2008 13:19 To: [email protected] Subject: RE: deployment models Hello, Please someone correct me if I'm wrong, but it seems to me the Jackrabbit RMI support is just a handy way of connecting to a repository, but not an efficient one. I only use it for connecting a remote administration client. IMHO, you'd better use a cluster: http://wiki.apache.org/jackrabbit/Clustering BR, Stéphane Landelle Le Ven 7 novembre 2008 5:17, Boni Gopalan (BioImagene) a écrit : > If you are using TransientRepository then multiple parallel connections > are not possible. I am using a deployment model where the repository is > wrapped as an RMI Server and this RMI Server is exposed through the JNDI. > The client sessions looks up this instance through the JNDI. > > > http://wiki.apache.org/jackrabbit/JackrabbitOnJBoss > > > thanks boni > > > -----Original Message----- > From: Virtual Light [mailto:[EMAIL PROTECTED] > Sent: 06 November 2008 23:37 > To: [email protected] > Subject: deployment models > > > > > Is it possible to have multiple servers all pointing to and > accessing one repository? It appears that there can be only one server > that accesses the repository which can have multiple clients. We are > looking at Jackrabbit as a possible solution for a high volume binary > content repository where we would need to have multiple servers for fail > over purposes all sitting behind a load balancer accessing the same > repository. When more than one server attempts to access the repository > an error is generated stating that the repository is locked. Have I > missed something? Is there a way around the locking situation? > > Thanks in advance for any info. > Bill > >
