Hi Melanie,
On 8/2/12 2:17 PM, Melanie Reiplinger wrote:
Also, when you rebuilt Stanbol did you remember to replace the
Clerezza - SCB Jena TDB Storage Provider with the one from the
0.6-incubating-SNAPSHOT? Your delays could be due to many databases
being created by the old implementation.
o, sorry, I did not check for that since simple updating of
components didn't make any change here. But my last rebuild was a
complete re-installation, that's why now I sitll have the 0.5 Version
there. Thank you. Might be this explains it all, I will test it and
then report.
Didn't help very much. First it looked like with the single dataset tc
provider it worked better. Still, the GET requests failed (I see that
in the network log of the browser), and still, they took several
seconds, but at least they didn't cause a time out. But after a few
minutes of testing it was just the same as before: time out and
failure of uploading for ontologies.
Then I think I'm going to need a detailed log. That also says something
about the time taken for loading ontologies and stuff. Would you mind
setting up a "Debug" logger for the ontology manager classes before you
try loading an ontology again?
To do so,
1. go to [stanbol]/system/console/configMgr with your browser
2. create a new "Apache Sling Logging Logger Configuration" (click on
the "+" button)
3. Set log level to "Debug", give the log file the name you want and for
"Logger" type "org.apache.stanbol.ontologymanager"
4. Click "Save"
5. do your stuff (e.g. upload an ontology onto a scope, do a GET afterwards)
6. Post the new logfile as an attachment of ticket
https://issues.apache.org/jira/browse/STANBOL-422
We might need to increase the log verbosity incrementally and produce
further logs, so I'll keep you posted after that.
btw: is it possible meanwhile to delete a scope from a session by
curl -X DELETE .../ontonet/session?scopeid=<scopeID>
? I'm just asking; this is no urgent issue.
Not with DELETE. In the end I decided to do it via POST. Basically any
appended scopes that do *not* belong to the values of the "scope"
parameter (can be multiple) are automatically detached.
Example: suppose you have "scope2" already appended to "sessionX". Then
if you do
curl -X POST -F "scope=scope1" -F "scope=scope3"
[stanbol]/ontonet/session/sessionX
will append scopes 1 and 3 and detach number 2 which was not included.
DELETE should be used for deleting resources for which a corresponding
GET exists, but there's no resource associated with
/ontonet/session?scopeid=<scopeID> (nor would it make much sense to make
one, since it would contain the same data as the scope alone).
Also an empty multipart POST (with no form parameters at all) is
interpreted as "detach all scopes".
HTH
Alessandro
--
M.Sc. Alessandro Adamou
Alma Mater Studiorum - Università di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, 40127 Bologna - Italy
Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, 00161 Rome - Italy
"I will give you everything, just don't demand anything."
(Ettore Petrolini, 1917)
Not sent from my iSnobTechDevice
