Chetan,
When running locally with similar data, the indexing is nearly
instantaneous. Here¹s the output from persisting data; the first line is
the actual creation of the asset:
2015-12-07T09:29:37,871-0600 INFO ServiceLogger:53 - Call to:
Chetan,
I really appreciate the quick response. Our application is capable of
running singleton scheduled jobs already, so I believe I can take care of
that aspect. Would it be as simple as omitting the withAsyncIndexing()
argument to the constructor, and then
- create an AsyncIndexUpdate
resource contention? It would
appear to me that they should.
Many thanks,
Jim Tully
On 12/7/15, 10:50 AM, "Jim.Tully" <jim.tu...@target.com> wrote:
>Chetan,
>
>I really appreciate the quick response. Our application is capable of
>running singleton scheduled jobs
We are using Oak embedded in a web application, and are now experiencing
significant delays in async indexing. New nodes added are sometimes not
available by query for up to an hour. I’m hoping you can identify areas I
might explore to improve this performance.
We have multiple instances of
I apologize for the noise. Digging deeper into my code, I discovered that
I was not logging out of the sessions as I thought I was. Once I resolved
that, the memory issue disappeard.
Jim Tully
On 10/17/15, 2:21 PM, "Jim.Tully" <jim.tu...@target.com> wrote:
the application by calling:
((RepositoryImpl) repository).shutdown();
ns.dispose();
Jim Tully
This is probably something that we are doing incorrectly, but it has me
scratching my head.
We are running Oak embedded in a web application. We construct a repository at
startup using fairly standard construction:
DocumentNodeStore ns= new
Would it be possible for the Oak documentation to give some kind of indication
as to the differences between the 1.0.x and 1.2.x branches?
Thanks,
Jim Tully
I am working with Oak version 1.2.2, and have recently encountered unexpected
behavior.
I have a custom node type that includes a PATH property, not required. In
previous versions, it was legal to specify either an empty path (“”) or a
default (“.”). In the current version, the default is
Marcel,
I register an EventListener at application startup, using the
ObservationManager.addEventListener, using Event.PROPERTY_ADDED |
Event.PROPERTY_CHANGED as the EventType.
In the onEvent() method, I create an Event Handler with the Event as an
argument, and it does the processing in a new
Hi,
We are using Oak in one of our applications, and have come up with a problem
that I can’t seem to find an answer to.
We have an Event Listener registered to listen for changes to properties in a
node. It is always notified of the events properly. Upon notification, the
listener
suspect that the answers are both yes, but confirmation would be appreciated.
Thanks,
Jim Tully
2
ContentRepository instances, but the second instance apparently causes
duplicate indexing.
Jim
From: Jim Tully jim.tu...@target.commailto:jim.tu...@target.com
Date: Thursday, October 16, 2014 at 9:06 PM
To: oak-dev@jackrabbit.apache.orgmailto:oak-dev@jackrabbit.apache.org
oak-dev
().getProviderName().equals(idp.getName())) {
Where getProviderName() returned null.
Any pointers would be appreciated.
Jim Tully
repository. This
threw a null pointer exception in ExternalLoginModule at this line:
if(!sId.getExternalIdRef().getProviderName().equals(idp.getName())) {
Where getProviderName() returned null.
Any pointers would be appreciated.
Jim Tully
,
mix, rep]): tgt
I've also tried programmatically creating the namespace using
workspace.getNamespaceRegistry().registerNamespace(). This throws an exception:
OakNamespace0005: Namespace modification not allowed: rep:nsdata
I've tried with both version 1.0.0 and 1.0.1
Thank you,
Jim Tully
16 matches
Mail list logo
