Hi Sriram,

Both of these basic scenarios should definitely work and I still think
that there's something wrong with your setup. Scenario A would even
work without clustering, because the second instance has no memory
representation to update when it is freshly started. Given that the
PersistenceManagers point to the same database I'd try the following:

(1) Verify that your new node actually appears in the database, in a table
     named <schemaObjectPrefix>_NODE.
(2) Set logging level to info, in order to see whether the FileJournal
correctly processes
     changes made by another instance.

Kind regards
Dominique

On 3/7/07, Sriram Narayanan <sriramnrn@gmail.com> wrote:
> Hi all:
>
> I have three JR instances.
>
> Each instance
> - points to the same Oracle database
> - shares a journal folder (FileJournal)
> - has a unique ID
> - has separate index and revision folders.
>
> Scenario A:
> 1. Run the first instance and add a node into the repository.
> 2. Start the second instance and try to read that node.
>
> I get a javax.jcr.PathNotFoundException
>
> Scenario B:
>
> 1. Run all the instances.
> 2. From the first instance, create a Node and set an attribute for it.
> 3. From the second instance, try to read back that node.
>
> I get a javax.jcr.PathNotFoundException
>
> What am I possibly doing wrong here ?
>
> -- Sriram
>