Loicram Kro | 24 May 11:41 2016
Picon

Changes not visible in new sessions

Hi.

I'm using oak in version 1.2.11.
I have a problem with visibility of changes in new sessions.
Steps which I do:
1. Send a request to save some changes (changes are saved by OSGI Service)
2. Changes are saved and response is sent back
3. I send new request which tries to read the changes from the previous
request
4. Changes are not visible

I read in the docs, that Oak for each new session is taking a repository
snapshot. From what I've understood, changes from the point number one, may
not be visible for sessions which were already created, but they will be
visible for new sessions.
I've tried to refresh the Session, by calling refresh(false) on Session
object, but usually changes are still not visible.
Of course if I will wait 2-3 second between those requests then everything
is fine, but that is not possible in my case.

I assume that save is not done when immediately, and still something is
happening in the background (maybe there are some default commit hooks,
which need some time to process).

It's time for questions:
1. Is it proper behaviour ? That I don't see changes from previous request
in the new request?
2. If yes, how can I get those changes? I mean, i know that I can do
everything in one request, so I will see my changes, but maybe there is a
way to get those changes for example from repository directly? I couldn't
(Continue reading)

Amit Jain | 19 May 05:41 2016
Picon

[ANNOUNCE] Apache Jackrabbit Oak 1.2.15 released

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.2.15 The release is available for download at:

    http://jackrabbit.apache.org/downloads.html

See the full release notes below for details about this release:

Release Notes -- Apache Jackrabbit Oak -- Version 1.2.15

Introduction
------------

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.2.15 is a patch release that contains fixes and
improvements over Oak 1.2. Jackrabbit Oak 1.2.x releases are considered
stable and targeted for production use.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.2.15
--------------------

Sub-task

    [OAK-2943] - Support measure for union queries
    [OAK-2944] - Support merge iterator for union order by queries
(Continue reading)

Davide Giannella | 16 May 16:03 2016
Picon

[ANNOUNCE] Apache Jackrabbit Oak 1.5.2 released

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.5.2 The release is available for download at:

    http://jackrabbit.apache.org/downloads.html

See the full release notes below for details about this release:

Release Notes -- Apache Jackrabbit Oak -- Version 1.5.2

Introduction
------------

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.5.2 is an unstable release cut directly from
Jackrabbit Oak trunk, with a focus on new features and other
improvements. For production use we recommend the latest stable 1.4.x
release.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.5.2
---------------------

Technical task

    [OAK-3840] - Clean up the FileStore constructor
(Continue reading)

techie2k | 16 May 08:43 2016
Picon

Get Repository from OAK

Hi,

I have created jackrabbit oak repository with mongodb as nodestore.

MongoConnection  connection = MongoUtils.getConnection();
database = connection.getDB();
documentNodeStore = new
DocumentMK.Builder().setMongoDB(database).getNodeStore();
	    
Jcr jcr = new Jcr(new Oak(documentNodeStore)).with(getSecurityProvider());
Repository repository = getIndexConfig(jcr).createRepository();

But what api will provide me the existing repository, when I supply
connection of MongoDB?
Hardly finding a clue. 
Appreciate your help on this.

Using Oak 1.4.1 and MongoDB 3.2

--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Get-Repository-from-OAK-tp4664045.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Giovanni L | 12 May 13:45 2016
Picon
Gravatar

Oak PropertyIndex on node name

We are using Jackrabbit Oak in a project, and i'm investigating indexes,
since we do a lot of queries filters on node names. I read you can build a
lucene index on a node name, and I was wondering if you could do the same
using a PropertyIndex. I tried to get the "propertyNames" empty in the index
definition (as stated in the PropertyIndex javadoc), or using "jcr:name" as
a indexed property (as I read in another post in this mailing list), but
neither did the trick.
Does anybody know how to do, if there's a way to do that?

Thanks,
Giovanni

--
View this message in context: http://jackrabbit.510166.n4.nabble.com/Oak-PropertyIndex-on-node-name-tp4664034.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Amit Jain | 12 May 06:18 2016
Picon

[ANNOUNCE] Apache Jackrabbit 2.10.3 released

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit 2.10.3 The release is available for download at:

    http://jackrabbit.apache.org/downloads.html

See the full release notes below for details about this release:

Release Notes -- Apache Jackrabbit -- Version 2.10.3

Introduction
------------

This is Apache Jackrabbit(TM) 2.10.3, a fully compliant implementation of
the
Content Repository for Java(TM) Technology API, version 2.0 (JCR 2.0) as
specified in the Java Specification Request 283 (JSR 283).

Apache Jackrabbit 2.10.3 is a patch release that contains fixes and
improvements over Jackrabbit 2.10.2. Jackrabbit 2.10.x releases are
considered
stable and targeted for production use.

Changes in Jackrabbit 2.10.3
-------------------------------

Bug

    [JCR-3958] - Endless loop until async upload completes
    [JCR-3965] - RepositoryStatistics is reset per second for bundle cache
size which should not be the case for the bundle cache stats
(Continue reading)

Davide Giannella | 9 May 17:19 2016
Picon

[ANNOUNCE] Apache Jackrabbit Oak 1.4.2 released

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.4.2 The release is available for download at:

    http://jackrabbit.apache.org/downloads.html

See the full release notes below for details about this release:

Release Notes -- Apache Jackrabbit Oak -- Version 1.4.2

Introduction
------------

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Jackrabbit Oak 1.4.2 is a patch release that contains fixes and
improvements over Oak 1.4. Jackrabbit Oak 1.4.x releases are
considered stable and targeted for production use.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.4.2
---------------------

Technical task

    [OAK-4204] - GarbageCollectorFileState.copy() leaks
    FileOutputStream
(Continue reading)

Ankush Mishra | 8 May 13:37 2016
Picon

Re: Current status of the Jackrabbit WebDAV ACL

Just bumping up this thread, and still wondering on the status of this?

Ankush Mishra

On 30-04-2016 05:16, Christopher Rockwell wrote:
> I am out of the office until 5/9/2016.
>
> On Apr 28, 2016, at 10:18 AM, Ankush Mishra <ankushmishra9 <at> gmail.com> 
> wrote:
>
>     Thanks for the response, but according to this page here:
>     https://jackrabbit.apache.org/jcr/components/jackrabbit-webdav-library.html
>
>
>     It states:
>
>     The following RFCs have been integrated:
>
>     RFC 4918 (WebDAV - HTTP Extensions for Distributed Authoring,
>     obsoleting RFC 2518)
>     RFC 3253 (DeltaV - Versioning Extensions to WebDAV)
>     RFC 3648 (Ordered Collections Protocol)
>     *RFC 3744 (Access Control Protocol)*
>     RFC 5323 (WebDAV SEARCH; previously DASL - DAV Searching and
>     Locating)
>
>     Also, there seems to be a package
>     org.apache.jackrabbit.webdav.security, which seems to be the
>     implementation of it. The Javadoc on the package can be found
>     here:
(Continue reading)

mike osterhout | 5 May 06:59 2016
Picon
Gravatar

query next/previous object

Hi,

I am a little confused on the best way to query the next/previous object in
the tree. In a traditional database it would just be a query where a number
is > or < than the id. How can I do the same with Jackrabbit? It seems that
the best way is to query by jcr:created but that doesn't seem stable.

--

-- 
Regards,
Mike
techie2k | 3 May 16:05 2016
Picon

Jackrabbit 2.8.1 to Oak 1.4.1 migration

When trying to execute migration command:

/java -jar oak-upgrade-1.4.1.jar D:/data/temp/jackrabbit
mongodb://localhost:27017/oak /

yields failed to copy content error;

In repository.xml reference is:

<PersistenceManager
class="org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager">

    

    

    

    

    

    

    
</PersistenceManager>
Since Derby is embedded and during migration, oak is expecting derby server
to be up and running;

Kindly advise on migration options.
(Continue reading)

Robert Botzer | 28 Apr 17:55 2016

Reaching out about Jackrabbit performance and scalability...

Hi...

I am looking for any thoughts and info about how much volume a single instance of a Jackrabbit server can handle...
Especially if anyone has experience with using it as a component of a large web based
(and if there is a way and how to measure / predict that..)

Here is some background on what I'm looking for...

We are currently using a  Jackrabbit server and content repository as a component  of our web application
solution.  ( I believe it is  2.2.13 )
We are storing simple text documents like 1 page notes,  or 1- 5 page letters.
We are using simple file system storage, and we store a reference link to the document in our relational database.
We DO NOT do any searching against these documents.  (So we have turned that indexing off..)
So basically we upload a small document,  keep and store the reference to it, and retrieve the doc based on that.
We also use a hashing algorithm to distribute documents to separate folders so we do not run into file system
performance issues
(like 20,000 files in one directory).

We can scale our web application server 'out' by having multiple instances behind a load balancer...
But all of those instances currently use the same (singular) Jackrabbit server / repository.
( btw: The file system repository is on the same server as the Tomcat/Jackrabbit instance - so no network
access for Jackrabbit  to access the docs.)

We are having good results with 3  of our application servers - for   ~ 600 users,  using a single Jackrabbit instance...

However, we have a new prospect/client that is asking for  ~ 3000 users...  So we could be deploying  something
like 30+ servers  each connecting to Jackrabbit

I think that ultimately the actual Jackrabbit load will likely  depend on how many documents per minute  ( or
some unit of time).
(Continue reading)


Gmane