Thanks Hugh,
you are right, the request is not reaching the server.
What should I change?
On Fri, May 23, 2014 at 12:41 PM, Hugh Williams wrote:
> Hi Gofran,
>
> The trace results are written to the "virtuoso.log" in the database
> directory on the server ... remember to run "trace_off()" to tur
Hi Gofran,
The trace results are written to the "virtuoso.log" in the database directory
on the server ... remember to run "trace_off()" to turn it off when done
otherwise the log can grow quite quickly especially if all tracing is on ...
Best Regards
Hugh Williams
Professional Services
OpenLin
Hello Hugh,
I was check the trace_on function, and it seems it does not return values.
Here is how I am running it:
1- I log in to ISQL with DBA.
2- I run the command
trace_on ('user_log', 'failed_log');
but still no results
On Fri, May 23, 2014 at 11:46 AM, Hugh Williams wrote:
> Hi Gofra
Hi Nicola,
If not already done, you could try running the DB.DBA.VT_INDEX_DB_DBA_RDF_OBJ
() to reindex that data. Note there is also the "DB.DBA.RDF_OBJ_FT_RECOVER ()"
which inserts missing indexes that could be tried running as well indicated at:
http://docs.openlinksw.com/virtuoso/s
Hi Gofran,
If you turn server side tracing on in Virtuoso using the "trace_on()" [1]
command is the request actually reaching the server ?
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www.openlinksw.com/
Weblog -- http://www.openlinksw.co
Hello all,
I was hoping that you could help me with this issue related to Virtuoso. I
have problem with the update query using HTTP call from Jena.
Running the same query from the SPARQL interface in the conductor –logged
in as DBA- works fine, but calling the SPARQL endpoint from Java program
wi