Hi Miguel,
Yes, I'd be very interested in your PostgreSQL specific DDL to include
in the upcoming 1.3 release. Please note, that there has been a slight
schema change: I would appreciate if you could synchronize with
default.ddl in trunk.
Kind regards
Dominique
On 2/21/07, Miguel Ángel Jiménez
Hi,
I'm testing the new DatabaseJournal with a PostgreSQL. Since there was no
ddl for this database I had to generate one and thought you could upload it
to subversion.
Regards,
On 21/02/07, Dominique Pfister [EMAIL PROTECTED] wrote:
Hi Miguel
On 2/20/07, Miguel Ángel Jiménez [EMAIL
I'm working on some tests to reproduce this issue. However looking at the
code in 1.2.1, in method commit() of FileJournal.java, I can't find the lock
operation on the global revision file. Here is the code:
public void commit() throws JournalException {
try {
Hi Miguel,
On 2/20/07, Miguel Ángel Jiménez [EMAIL PROTECTED] wrote:
The call to globalRevision.set (that implies a lock) is done after the call
to recordLog.append() so I think the write is not protected. I'm rather new
to JCR and jackrabbit so maybe I'm missing something but the cluster
Thanks again for the response. I have another issue about FileJournal. In
our test environment, we have several instances doing concurrent
modifications to the repository and have been able to trace what I see as a
possible bug in log file rotation. It seems that the renaming of old files
is not
Hi Miguel,
writing to the journal log file should only be possible after having
obtained an exclusive lock on the global revision file (R), located in
the same directory as the journal log file (L). The exact sequence of
operations is as follows:
- exclusive lock is obtained on R
- journal
Hi,
I'm trying the new cluster feature of Jackrabbit 1.2.1 and found some
issues. Using FileJournal to synchronize state between instances, we are
experiencing some errors that point to a possible corruption of the log
file:
2007-02-14 10:34:00,911 ERROR
