Recorded as JENA-1312, with a test case.
The difference between -v and no -v is that the verbose logging code
uses java to convert bytes to chars, while the non-verbose path uses javacc.
Andy
On 28/03/17 15:23, Andrew U Frank wrote:
the server was started with
exec /home/frank/jena/apache-jena-fuseki-2.5.0/fuseki-server -v --update
--loc=/home/frank/march19 /marchDB
and then with
exec /home/frank/jena/apache-jena-fuseki-2.5.0/fuseki-server --update
--mem /memDB
(first with -v and got the error message, then i removed the -v and got
204). the 204 return and no insertion happens in both memory cases.
i do think it would be sufficient to inform the sender that the request
is not ok and rejected (when the position can be indicated, the better).
the "restart effect" is not produced by the restart, just the difference
between starting fuseki server with -v or not. with -v, the error 500 is
returned, without -v an ok return is returned.
my problem is only that the error message 500 (which is internally
produced) is not sent back when -v is not present. (i am, at least at
the moment, not interested to send a BOM character, it is rather an
annoying problem caused by a file i probably received from somewhere and
which i now routinely filter out. nevertheless, thank you for the
information you pointed me to. i understand now that sending a BOM
character as is not a legal literal). however, i am ONLY concerned when
i see a 200 return and the triples are not inserted.
if you cannot reproduce the effect, i could try to see if i can produce
it with using curl/wget - at the moment i tested with a program which
inserts the triples.
does your system insert triples where an (illegal) BOM character is in a
literal unencode sent (and not running with the -v flag)?
thank you for your effort and time!
andrew
