Hi Jane,
this indeed sounds like you may be dealing with the intermittent authentication
bug (see: https://jira.duraspace.org/browse/FCREPO-393). It was fixed in the
Fedora 3.2 release. You can find out if this bug is causing the 401 by looking
at the Fedora log file. If it shows exceptions tha
Hi All,
We have been experiencing intermittent 401 errors with Fedora 3.1. All
requests sent to Fedora will get 401 errors, despite that it has been
working well before it happens. This issue will usually last for about 10
minutes, and then authorization becomes ok again.
I did a little bit sea
Hi Ludovic,
> we do need (unfortunately) the resource index during the initial load
> because there's an external component that perform some calculations
> based on what digital objects are created per FOXML ingest.
If that is the case, can we assume you are either flushing the triple
store whe
It's a supported configuration. Best to use the same version of Mulgara
that's currently packaged with Fedora. The configuration is described here:
https://wiki.duraspace.org/display/FCR30/Resource+Index#ResourceIndex-Remote
MulgaraDatastoreConfiguration
> -Original Message-
> From: Sco
I've also heard talk of people extracting the resource index from Fedora
core, and running a standalone instance of Mulgara in its own JVM for
the resource index. I recall some recent traffic on the lists on that
topic. Not sure if that's feasible with current versions of Fedora, though.
-- S
Ludovic-
Another option, if you're worried about the initial load, is to turn
off the resource index during the ingest. Then, when the ingest is
complete, enable the resource index and run the rebuilder.
- Ben
On 7/14/11, Ludovic Deravet wrote:
> Hello Scott,
>
> Yes. We do use it with the fo
Gus
Have a look at projecthydra.com
There you will find all the links for download of various heads from github
which include the Active Fedora gem (which is maybe what you were thinking
about when you said 'ruby-fedora'?). There are also links to things like
Hydra's wiki which has a lot of t
Hello Scott,
Yes. We do use it with the following value:
-XX:MaxPermSize=256m
We came to the conclusion that since we create thousands of digital objects
during consecutive hours (with of course creation of content datastreams and
setting relationships between digital objects) this lead to the c
