Hmm... looking at the stack trace of a stuck thread, I'd be inclined to
guess that this problem was actually outside of Fedora, and relates
either to the client consuming the resource, or the tcp connection
itself.
Here's the last part of the stack trace:
[1] java.net.SocketOutputStream.socke
What is the recommended path for getting up to date and learning about
Fedora for a user and developer?
I have been following the documents at
https://wiki.duraspace.org/display/FCR30/Getting+Started+with+Fedora,
but they seem out of date and missing chunks (see my earlier message
on the tutorial
Our install.properties is attached. The only update is that we now have the
resource index enabled.
The only additionally interesting thing about our setup is that we are
redirecting port 8080 to 80 at the kernel level using iptables. Obviously,
this will change if we use httpd in addition t
There's no migration utility currently, but there is a JIRA issue to provide
one - https://jira.duraspace.org/browse/FCREPO-769
The legacy low-level storage simply wraps a file in a FileInputStream, so I
think it is unlikely to be that. I believe (but haven't checked) that the
resulting InputStre
Scott and Asger, thanks very much for responding. I thought of adding the
structMap DS myself, and hearing that someone else has done this already
validates that approach. I'm going to tinker with embedding sequences in the
RELS-EXT as well.
Mark
- Original Message -
> Hello, Mark --
>
Interesting. We're using the legacy low-level storage. Is there a migration
utility available for the switch to Akubra?
Our current next step is to try putting Apache httpd in front of Tomcat and see
if its improved socket handling would help.
Rob
-Original Message-
From: Stephen
I just hit a similar (but unrelated) issue, the underlying cause of which
was a PrintWriter on the HTTP response not being flushed - I got partial
content, but it was intermittent.
So I wonder if this could be related?
Are you using the legacy low-level storage implementation or Akubra?
(And, if
Hello, Mark --
We ran into the same problem with sequenced images in a set. Rather try
to bend RELS-EXT to our will, we decided to create a STRUCT datastream
that contains a METS structmap with the structure of the atomistic
object, including ORDER. This approach has a couple of downsides: i
Hi
What you have found is one of weaknesses in the Fedora RDF structure.
The normal way, btw, is to have each of the pages declare their page
number in a literal relation.
Remember, a RELS-EXT relation does not have to be to another object, it
can be literal.
so something like
15
