I start with ./fuseki-server --update --mem --debug /ds logging comes to the shell.
Here's a bit of recent log. 16:44:58 INFO Fuseki :: [219] OK/select 16:44:58 INFO Fuseki :: [219] 200 OK 16:44:58 INFO Fuseki :: [220] POST http://localhost:3030/ds/update 16:44:58 INFO Fuseki :: [220] 200 OK 16:44:58 INFO Fuseki :: [221] POST http://localhost:3030/ds/update 16:44:58 INFO Fuseki :: [221] 200 OK 16:45:09 INFO Fuseki :: [222] GET http://localhost:3030/ds/query?query=SELECT+*+WHERE+%7B%0D%0A+GRAPH+%3Fg+%7B%3Fs+%3Fp+%3Fo%7D%0D%0A%7D+LIMIT+10&output=xml&stylesheet=%2Fxml-to-html.xsl 16:45:09 INFO Fuseki :: [222] Query = SELECT * WHERE { GRAPH ?g {?s ?p ?o} } LIMIT 10 16:45:09 INFO Fuseki :: [222] OK/select 16:45:09 INFO Fuseki :: [222] 200 OK Leaving for a train now. Tonight or tomorrow will try to produce a complete minimal log and also report what (I believe that) the POST arguments are. Thanks Bob On Tue, Jun 5, 2012 at 4:43 PM, Andy Seaborne <[email protected]> wrote: > On 05/06/12 21:02, Bob Morris wrote: >> >> Ah, I see that the query is reflected for GET, but the content of POST >> messages apparently are not (?) > > > I see: > > INFO Fuseki :: [1] POST http://localhost:3030/ds/sparql > INFO Fuseki :: [1] Query = ASK{} > > showing the query is logged. > > What do you get in the log file? > > Andy > > >> >> On Tue, Jun 5, 2012 at 3:40 PM, Bob Morris<[email protected]> wrote: >>> >>> I am using Fuseki from >>> jena-fuseki-0.2.2-incubating-20120509.202022-18-distribution.zip in >>> conjunction with SPARQLPuSH [1]. So far, most of my difficulties >>> surround providing the right details of the queries when constructed >>> by the the PHP that implements SPARQLPusH. My debugging life would be >>> much easier if I could get fuseki to reveal the queries it receives >>> via http, both post and get, before logging its response. >>> >>> Is there a way to force this? >>> >>> Use case: >>> >>> Right now my debugging tends to take the form of figuring out where in >>> the PHP app the query is constructed, making that point log to the >>> apache server supporting the PHP, grabbing the query there and putting >>> it into the fuseki web query form, and hoping that the error reported >>> corresponds reasonably to the one signalled by fuseki when started in >>> a Linux shell. I'd rather see those hints coming out of Fuseki >>> before I dig into the calling code. Otherwise, I am hopping back and >>> forth between my own Apache server logs and the reports Fuseki makes >>> of its issues with my queries. >>> >>> Ideally, I'd be able to optionally see the query url-decoded, since >>> the url-encoding library of most(?) application languages is rarely(?) >>> problematic. >>> >>> Thanks >>> Bob Morris >>> >>> >>> [1] http://code.google.com/p/sparqlpush/ >>> >>> -- >>> Robert A. Morris >>> >>> Emeritus Professor of Computer Science >>> UMASS-Boston >>> 100 Morrissey Blvd >>> Boston, MA 02125-3390 >>> >>> IT Staff >>> Filtered Push Project >>> Harvard University Herbaria >>> Harvard University >>> >>> email: [email protected] >>> web: http://efg.cs.umb.edu/ >>> web: http://etaxonomy.org/mw/FilteredPush >>> http://www.cs.umb.edu/~ram >>> === >>> The content of this communication is made entirely on my >>> own behalf and in no way should be deemed to express >>> official positions of The University of Massachusetts at Boston or >>> Harvard University. >> >> >> >> > -- Robert A. Morris Emeritus Professor of Computer Science UMASS-Boston 100 Morrissey Blvd Boston, MA 02125-3390 IT Staff Filtered Push Project Harvard University Herbaria Harvard University email: [email protected] web: http://efg.cs.umb.edu/ web: http://etaxonomy.org/mw/FilteredPush http://www.cs.umb.edu/~ram === The content of this communication is made entirely on my own behalf and in no way should be deemed to express official positions of The University of Massachusetts at Boston or Harvard University.
