Edwin,
thanks for the PATCH, but unfortunately, I always have the warning messages of "Inoperable DSLocation" in my log files. And there is always the same exponential number of messages. The PATCH hasn't change anything.
Pierre-Yves

PS: I have installed the .jar file in $CATALINA_HOME/webapps/fedora/WEB-INF/lib (and renamed it). I have also restarted the server.

Edwin Shin a écrit :
Pierre-Yves,

Actually, I wasn't suggesting that you were somehow passing in the wrong 
dsLocations. The problem is Fedora is complaining about its own internal 
identifier for dsLocations. For example, you added/modified a datastream with 
dsLocation uploaded://2107 which Fedora then rewrites to 
MY-NS:MY-ID+MY-DS61+MY-DS61.0:

INFO 2010-03-12 16:32:32.816 [http-8080-2] (DefaultDOManager) Getting managed 
datastream from internal uploaded location: uploaded://2107
INFO 2010-03-12 16:32:32.881 [http-8080-2] (DefaultDOManager) Replaced managed 
datastream location with internal id: MY-NS:MY-ID+MY-DS61+MY-DS61.0


When Fedora subsequently examines the object's datastreams as part of serialization, it logs a 
warning that its own internally assigned dsLocation is "inoperable" because the 
dsLocation (here MY-NS:MY-ID+MY-DS61+MY-DS61.0) isn't matched by the regular expression 
"^\\w+:\\/.*$".

In any case, have a look at the tracker 
(http://www.fedora-commons.org/jira/browse/FCREPO-665). I've added both a 
source patch and a binary patch. Unless you want to recompile yourself, just 
use the jar to replace your existing one and let me know if that solves the 
problem.

Eddie


On 15 Mar 2010, at 9:54 AM, Pierre-Yves JALLUD wrote:

Hi Eddie,
Thanks for your answer. You think that there is a bug in Fedora... maybe (... probably!), 
but I'm not agree with your hypothesis. You wright that the cause is that I don't use a 
dsLocation matching the pattern string "^\\w+:\\/.*$". I have some arguments 
again that:

  * in the addDatastream function, for the dsLocation, I use the
    string that is returned by the upload function (without
    modification: should I add something?)
  * if the string should not matching the pattern, the addDatastream
    should return an exception (isn't it?)
  * the datastream is correctly created, I can download it thrue the
    FedoraCommons server

Here is a more clarify extract of my logs:

...
WARN 2010-03-12 16:32:32.815 [http-8080-2] (DefaultDOManager) Inoperable DSLocation 
"MY-NS:MY-ID+MY-DS59+MY-DS59.0" given for MY-NS:MY-ID+MY-DS59+MY-DS59.0
WARN 2010-03-12 16:32:32.815 [http-8080-2] (DefaultDOManager) Inoperable DSLocation 
"MY-NS:MY-ID+MY-DS60+MY-DS60.0" given for MY-NS:MY-ID+MY-DS60+MY-DS60.0
INFO 2010-03-12 16:32:32.816 [http-8080-2] (DefaultDOManager) Getting managed 
datastream from internal uploaded location: uploaded://2107
INFO 2010-03-12 16:32:32.881 [http-8080-2] (DefaultDOManager) Replaced managed 
datastream location with internal id: MY-NS:MY-ID+MY-DS61+MY-DS61.0
INFO 2010-03-12 16:32:34.035 [http-8080-2] (DefaultDOManager) Updating 
dissemination index
INFO 2010-03-12 16:32:34.035 [http-8080-2] (DefaultDOManager) Updating 
FieldSearch index
INFO 2010-03-12 16:32:34.105 [http-8080-2] (DefaultManagement) Completed 
addDatastream(pid: MY-NS:MY-ID, dsID: MY-DS61, altIDs: , dsLabel: , 
versionable: false, MIMEType: text/plain, formatURI: , dsLocation: 
uploaded://2107, controlGroup: M, dsState: A, checksumType: SHA-256, checksum: 
3de53c3c240a4fc9b7f1d1af39060dd35f4bd45484f87093f184a85f6f9a7af3, logMessage: 
My message)
INFO 2010-03-12 16:32:40.136 [http-8080-1] (Cache) Authenticating user [MyUser]
INFO 2010-03-12 16:32:40.137 [http-8080-1] (UploadServlet) Got next item: 
isFormField=false fieldName=file
INFO 2010-03-12 16:32:40.149 [http-8080-1] (UploadServlet) Successful upload, 
id=uploaded://2108
INFO 2010-03-12 16:32:40.155 [http-8080-2] (Cache) Authenticating user [MyUser]
INFO 2010-03-12 16:32:40.401 [http-8080-2] (DefaultDOManager) Committing 
modification of MY-NS:MY-ID
WARN 2010-03-12 16:32:40.402 [http-8080-2] (DefaultDOManager) Inoperable DSLocation 
"MY-NS:MY-ID+MY-DS1+MY-DS1.0" given for MY-NS:MY-ID+MY-DS1+MY-DS1.0
WARN 2010-03-12 16:32:40.402 [http-8080-2] (DefaultDOManager) Inoperable DSLocation 
"MY-NS:MY-ID+MY-DS2+MY-DS2.0" given for MY-NS:MY-ID+MY-DS2+MY-DS2.0
...

Are those informations changing your conclusions?

But I'm agree with you that the message:
WARN 2010-03-12 16:32:40.402 [http-8080-2] (DefaultDOManager) Inoperable DSLocation 
"MY-NS:MY-ID+MY-DS2+MY-DS2.0" given for MY-NS:MY-ID+MY-DS2+MY-DS2.0
is not very clear. I don't see differences between "MY-NS:MY-ID+MY-DS2+MY-DS2.0" and 
MY-NS:MY-ID+MY-DS2+MY-DS2.0, except of course the " in the first string.

Pierre-Yves

Edwin Shin a écrit :
Pierre-Yves,

DefaultDOManager is expecting a dsLocation that is prefixed with a recognizable URL 
scheme, specifically, your datastream's dsLocation isn't matching the following pattern 
string: "^\\w+:\\/.*$".

If you're using Fedora's upload method, the dsLocation should begin with "uploaded://". The excess of messages is because DefaultDOManager is iterating through the datastreams and their revisions and evidently having the same issue with their dsLocations. There should be some more info in the logs to help indicate what's going on (the log level will need to be at INFO if it isn't already):

1) The log for the first add of managed datastream via upload method should begin with: 
"Getting managed datastream from internal uploaded location: XXX"
2) Followed by "Replaced managed datastream location with internal id: YYY"

If you can report back with what XXX and YYY are, that should help run down the 
problem.

Eddie

On 12 Mar 2010, at 4:14 PM, Pierre-Yves JALLUD wrote:

Dear community,
I just installed FedoraCommons 3.3 and I'm making test on it. I'm using the 
same JAVA program to ingest data, but with the new version (the last version of 
FedoraCommons was 3.2.1), I have the following inconvenient message in the 
server/logs/fedora.log file:

WARN 2010-03-12 15:26:07.099 [http-8080-1] (DefaultDOManager) Inoperable DSLocation 
"MY_NS:MY_ID+DS1.0" given for MY_NS:MY_ID+DS1.0

The datstream is created correctly and I can download it. I create the 
datastream using the upload function so I'm using temporary DSLocation. The 
message is all the more strange that each time I create a new datastream in the 
same object, a new message per existing datastream is create. I.e. when I 
create the 5th datastream in a object, there'are 4 new warnings in my logs. The 
number of warning message is exponential! And some objects can have 1000 
datastreams. The log file is exploding.

Does anyone knows what this message means?

Greetings
Pierre-Yves
<pierre-yves_jallud.vcf>------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
<pierre-yves_jallud.vcf>

<<attachment: pierre-yves_jallud.vcf>>

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to