jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rocco Russo" <rocco.ru...@eng.it>
Subject R: jackrabbit cluster
Date Wed, 21 May 2008 09:29:15 GMT
Thank you Perry for your reply

I have changed in my configuration  SimpleDbPersistenceManager,
DbFileSystem, and DatabaseJournal to OraclePersistenceManager,
OracleFileSystem and OracleDatabaseJournal (The same used in the wiki) and
now all works fine also leaving the SearchIndex  element in workspace tag.

It seems that SimpleDbPersistenceManager doesn't work well for MySql
database. Do I have to use another persistence manager for my purpose or is
a bug of Jackrabbit?
Are there some persons with this error on MySql Database? The version of
MySql that I use for the test is 5.0.24-community-nt. I need to use a non
commercial db (mySql in the first choice) so this feature is very important
for me.

Regards 

Rocco

-----Messaggio originale-----
Da: Perry.yin [mailto:perry.yin@gmail.com] 
Inviato: mercoledì 21 maggio 2008 7.11
A: users@jackrabbit.apache.org
Oggetto: Re: jackrabbit cluster


Hi, Rocco:
  Remove the element '<SearchIndex' of the '<workspace' tag. And try again.
Hope helps.

cheers
Perry


Perry.yin wrote:
> 
> Hi, Rocco:
>   I got the same problem. I wonder whether it does matter with cache or
> not.
>   Take a look at this thread. Hope it helps. 
>    http://www.nabble.com/Clusters-td14884942.html#a14884942
> http://www.nabble.com/Clusters-td14884942.html#a14884942 
> 
> Thanks
> Perry  
> 
> 
> joung wrote:
>> 
>> Errata correge
>> 
>> 
>> 5) I upload a binary file from server 2 using a webdav client.
>> (DAVExplorer). 
>> 
>> 	On server 2 the logs say:
>> 		20.05.2008 10:14:09 *INFO * ClusterNode: Appended revision:
>> 1 (ClusterNode.java, line 616)
>> 
>> 
>> 	On server 1 the logs say:
>> 		20.05.2008 10:14:17 *INFO * ClusterNode: Processing
>> revision: 1 (ClusterNode.java, line 963)
>> 		20.05.2008 10:14:17 *INFO * SearchManager: Node no longer
>> available f3eecb87-add1-4091-aadd-b29d37490a60, skipped.
>> (SearchManager.java, line 467)
>> 		20.05.2008 10:14:17 *INFO * SearchManager: Node no longer
>> available ad23c6da-558a-41ae-9a6b-8e8a5f873967, skipped.
>> (SearchManager.java, line 467)
>> 		20.05.2008 10:14:17 *INFO * AbstractJournal: Synchronized to
>> revision: 1 (AbstractJournal.java, line 213)
>> 
>> -----Messaggio originale-----
>> Da: dpfister@day.com [mailto:dpfister@day.com] Per conto di Dominique
>> Pfister
>> Inviato: lunedì 19 maggio 2008 17.33
>> A: users@jackrabbit.apache.org
>> Oggetto: Re: R: jackrabbit cluster
>> 
>> Hi Rocco,
>> 
>> your configuration looks fine to me. Are you sure, that there is no
>> workspace.xml configuration lying around that has a different setting?
>> I still think that the informational message, indicating that some
>> nodes are no longer available, actually tells that the content stored
>> on machine 1 is not visible to machine 2. Did you check what UUID your
>> added item contains and whether it matches one of the two logged in
>> the messages?
>> 
>> Kind regards
>> Dominique
>> 
>> On 5/19/08, Rocco Russo <rocco.russo@eng.it> wrote:
>>>
>>>  Hi Dominique,
>>>  thank you for your ready reply.
>>>  Sorry for the incorrect report in the first mail (a cut/past mistake).
>>> In
>> my
>>>  configuration I use a "shared" database installed on the machine 1
>>>  (192.168.11.240) so web-app 1 must be connected to localhost while the
>>>  web-app 2 (on machine 2 192.168.11.170) must be connected to
>> 192.168.11.240.
>>>
>>>
>>>  The correct configuration files are reported below. I hope it will be
>> useful
>>>  for you. Thanks a lot.
>>>
>>>
>>>  Machine 1
>> -----------------------------------------------------------------
>>>
>>>  <?xml version="1.0"?>
>>>  <!DOCTYPE Repository PUBLIC "-//The Apache Software Foundation//DTD
>>>  Jackrabbit 1.4//EN"
>>>
>>>  "http://jackrabbit.apache.org/dtd/repository-1.4.dtd">
>>>  <!-- Example Repository Configuration File -->
>>>  <Repository>
>>>
>>>
>>>     <!--
>>>         Database File System (Cluster Configuration)
>>>
>>>         This is sample configuration for mysql persistence that can be
>> used
>>>  for
>>>         clustering Jackrabbit. For other databases, change the
>>> connection,
>>>         credentials, and schema settings.
>>>         -->
>>>
>>>         <FileSystem
>>> class="org.apache.jackrabbit.core.fs.db.DbFileSystem">
>>>         </FileSystem>
>>>
>>>
>>>     <!--
>>>         security configuration
>>>     -->
>>>     <Security appName="Jackrabbit">
>> 
>>>     </Security>
>>>
>>>     <!--
>>>         location of workspaces root directory and name of default
>> workspace
>>>     -->
>>>     <Workspaces rootPath="${rep.home}/workspaces"
>>>  defaultWorkspace="default"/>
>>>     <!--
>>>         workspace configuration template:
>>>         used to create the initial workspace if there's no workspace yet
>>>     -->
>>>     <Workspace name="${wsp.name}">
>>>         <!--
>>>             virtual file system of the workspace:
>>>             class: FQN of class implementing the FileSystem interface
>>>         -->
>>>         <!--
>>>         <FileSystem
>>>  class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
>>>             
>>>         </FileSystem>
>>>         -->
>>>
>> 
>> 
> 
> 

-- 
View this message in context:
http://www.nabble.com/jackrabbit-cluster-tp17315831p17355911.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.



Mime
View raw message