jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "MARTINEZ Antonio" <Antonio.Marti...@alcatel-lucent.com>
Subject Jackrabbit standalone through RMI
Date Fri, 06 Feb 2009 01:07:52 GMT

After getting the standalone working I have verified that the queries
are about 10 times slower than same queries in my cluster setup.
I have seen warnings in this mailing list and the code stating that the
RMI is not optimized for performance.

Could I get more information on the technical reasons why there is such
a big performance gap ?
I would like to understand what would take to improve that.

Thanks in advance,

-----Original Message-----
From: MARTINEZ Antonio [mailto:Antonio.Martinez@alcatel-lucent.com] 
Sent: Tuesday, January 20, 2009 4:05 PM
To: users@jackrabbit.apache.org
Subject: RE: Bootstrap Jackrabbit without container

I found my answer in the release notes of Jackrabbit 1.5.2.
I was not aware of the standalone server process Regards, Antonio

-----Original Message-----
From: MARTINEZ Antonio [mailto:Antonio.Martinez@alcatel-lucent.com]
Sent: Monday, January 19, 2009 7:44 PM
To: users@jackrabbit.apache.org
Subject: Bootstrap Jackrabbit without container


I'm currently using Jackrabbit 1.4.4 in a cluster configuration (3 App
servers running JBoss).
The persistence manager I'm using is MySql, which is running in a DB
server (actually 2 DB servers in redundant configuration)

Everything is working fine, except that now I'm facing the problem that
I can not perform an online backup (since the local indexing of one of
the App servers is required). On top of that, in the near future I need
to support geo-redundancy, which seams kind of impossible with the
current configuration.

To be able to support online backup and geo redundancy, the data (DB +
local index) should actually be in the DB server, to simplify the
scripts in charge of those features.

I'm thinking of changing the architecture and run a single JackRabbit
instance in the DB server and use RMI to access the repository from the
App servers.

Now, in the DB server we are not running any container, just MySql, so
my question is if there would be any issue bootstrapping Jackrabbit
without container.

Any other experiences running this configuration are really appreciated:
any architecture issue with this approach, performance, etc..


View raw message