Hi Hugh
The exact cause of the problem remained unclear for us, and the sequence
for reproducing it was not clear; we only know it is somehow related to
accented characters in literals. Would you been able to describe exactly
_when_ this bug occur, and/or what is its exact cause ?
Is it described in a Github issue ?
Thanks
2017-10-31 11:40 GMT+01:00 Hugh Williams <hwilli...@openlinksw.com>:
> Hi Thomas,
>
> There is no work around currently I’m afraid.
>
> I will notify when the fix is committed to the open source develop/7
> branch or if you track the git commits [1] you will see when it is
> committed ...
>
> [1] https://github.com/openlink/virtuoso-opensource/commits/develop/7
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software, Inc. // http://www.openlinksw.com/
> Weblog -- http://www.openlinksw.com/blogs/
> LinkedIn -- http://www.linkedin.com/company/openlink-software/
> Twitter -- http://twitter.com/OpenLink
> Google+ -- http://plus.google.com/100570109519069333827/
> Facebook -- http://www.facebook.com/OpenLinkSoftware
> Universal Data Access, Integration, and Management Technology Providers
>
>
>
> On 31 Oct 2017, at 08:20, Thomas Francart <thomas.franc...@sparna.fr>
> wrote:
>
> Hugh
>
> Thanks.
> Can you suggest a workaround while waiting for the fix ? (using Jena
> adapter instead of RDF4J ? using a different RDF serialization than Turtle
> ? send the file to the server and run a Virtuoso load command ? ...)
> How can we be notified when the fix will be available ?
>
> Best Regards
> Thomas
>
>
> 2017-10-30 22:39 GMT+01:00 Hugh Williams <hwilli...@openlinksw.com>:
>
>> Hi Thomas,
>>
>> This is a known issue on the server side we are working on a fix for
>> already, which should be completed and available soon ...
>>
>> Best Regards
>> Hugh Williams
>> Professional Services
>> OpenLink Software, Inc. // http://www.openlinksw.com/
>> Weblog -- http://www.openlinksw.com/blogs/
>> LinkedIn -- http://www.linkedin.com/company/openlink-software/
>> Twitter -- http://twitter.com/OpenLink
>> Google+ -- http://plus.google.com/100570109519069333827/
>> Facebook -- http://www.facebook.com/OpenLinkSoftware
>> Universal Data Access, Integration, and Management Technology Providers
>>
>>
>>
>> On 30 Oct 2017, at 20:37, Thomas Francart <thomas.franc...@sparna.fr>
>> wrote:
>>
>>
>>
>> 2017-10-25 15:26 GMT+02:00 Sergey Malinin <sergmali...@gmail.com>:
>>
>>> On 10/25/2017 05:46 PM, Thomas Francart wrote:
>>>
>>> Hello
>>>
>>> (copy of https://stackoverflow.com/questions/46912359/virtuoso-cra
>>> sh-search-c326-box-serial-length-not-supported-for-data-type)
>>>
>>> I am connecting to a Virtuoso 7.20.3216 compiled and installed inside a
>>> VirtualBox CentOS 7.3 64bit, using the RDF4J Virtuoso adapter.
>>>
>>> I try to load a Turtle file in Virtuoso using this code :
>>>
>>> Repository r = new virtuoso.rdf4j.driver.VirtuosoRepository(url, login,
>>> password);
>>> RepositoryConnection connection = r.openConnection();
>>>
>>> ByteArrayOutputStream baos = new ByteArrayOutputStream();
>>> // Turtle data written inside baos
>>>
>>> String graphUri = ... ;
>>> connection.add(new ByteArrayInputStream(baos.toByteArray()), RDF.NAMESPACE,
>>> RDFFormat.TURTLE, SimpleValueFactory.getInstance().createIRI(graphUri));
>>>
>>> Virtuoso crashes (stops) with the following logs :
>>>
>>> 12:10:01 box_serial_len called with dtp 225
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x8c6d3a]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x8c6d98]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x4fba85]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x629664]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x629997]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x622485]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x65233d]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x6524dd]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x592328]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x59a807]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x59760a]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x5c0e30]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x5ca63b]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x59370c]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x597d13]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x5c0e30]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x5cbeee]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x5d3d36]
>>> 12:10:01
>>> /usr/local/virtuoso-opensource/bin/virtuoso-t(sf_sql_execute_w+0x7b)
>>> [0x5d3edb]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x8cb297]
>>> 12:10:01 /usr/local/virtuoso-opensource/bin/virtuoso-t() [0x8d1683]
>>> 12:10:01 /lib64/libpthread.so.0(+0x7e25) [0x7fe04db7ee25]
>>> 12:10:01 /lib64/libc.so.6(clone+0x6d) [0x7fe04d3a634d]
>>> 12:10:01 GPF: search.c:326 box_serial_length not supported for data type
>>>
>>> The same Turtle string, when uploaded to the conductor back-office,
>>> works properly. The file is pretty large so I can't paste it here.
>>>
>>> We have narrowed down the problem to a character encoding issue. The
>>> turtle file contains literals with accented characters such as "Disque
>>> à gravure directe"@fr.
>>>
>>> We haven't set any character encoding parameters, neither on the
>>> Virtuoso config side, nor in the JDBC connection side. We tried by adding
>>> charset=UTF-8 in the JDBC connection string, with no luck.
>>>
>>>
>>>
>>> - The charset=UTF-8 is auto added, if it isn't existed in the URL
>>> connection string (in the RDF4J provider)
>>> - To be sure, that you have UTF8 data in the your stream and better to
>>> use
>>>
>>> connection.add(new InputStreamReader(new
>>> ByteArrayInputStream(baos.toByteArray()), "UTF8"), RDF.NAMESPACE,
>>> RDFFormat.TURTLE, SimpleValueFactory.getInstance().createIRI(graphUri));
>>>
>>>
>>>
>>>
>> Thanks for your answer. Adding the explicit encoding did not change the
>> behavior. Should I file a bug report ?
>>
>> Thomas
>>
>>
>>>
>>> It seems also that the problem only arises when the database is empty.
>>> When the database already contains some data, Virtuoso does not crash.
>>>
>>> Any idea on
>>>
>>> 1. what the error message means?
>>> 2. how to get some additionnal logs ?
>>> 3. what could be the cause of the problem?
>>> 4. how to fix or work around this?
>>>
>>> Thanks!
>>>
>>> --
>>>
>>> *Thomas Francart* -* SPARNA*
>>> Web de *données* | Architecture de l'*information* | Accès aux
>>> *connaissances*
>>> blog : blog.sparna.fr, site : sparna.fr, linkedin :
>>> fr.linkedin.com/in/thomasfrancart
>>> tel : +33 (0)6.71.11.25.97 <+33%206%2071%2011%2025%2097>, skype :
>>> francartthomas
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>>> http://sdm.link/slashdot
>>>
>>>
>>>
>>> _______________________________________________
>>> Virtuoso-users mailing
>>> listVirtuoso-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>>
>>>
>>> --
>>> Best Regards,
>>> Sergey Malinin
>>>
>>>
>>
>>
>> --
>>
>> *Thomas Francart* -* SPARNA*
>> Web de *données* | Architecture de l'*information* | Accès aux
>> *connaissances*
>> blog : blog.sparna.fr, site : sparna.fr, linkedin :
>> fr.linkedin.com/in/thomasfrancart
>> tel : +33 (0)6.71.11.25.97 <+33%206%2071%2011%2025%2097>, skype :
>> francartthomas
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://
>> sdm.link/slashdot_______________________________________________
>> Virtuoso-users mailing list
>> Virtuoso-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>
>>
>>
>
>
> --
>
> *Thomas Francart* -* SPARNA*
> Web de *données* | Architecture de l'*information* | Accès aux
> *connaissances*
> blog : blog.sparna.fr, site : sparna.fr, linkedin : fr.linkedin.com/in/
> thomasfrancart
> tel : +33 (0)6.71.11.25.97 <+33%206%2071%2011%2025%2097>, skype :
> francartthomas
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org <http://slashdot.org>!
> http://sdm.link/slashdot_______________________________________________
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>
>
>
--
*Thomas Francart* -* SPARNA*
Web de *données* | Architecture de l'*information* | Accès aux
*connaissances*
blog : blog.sparna.fr, site : sparna.fr, linkedin :
fr.linkedin.com/in/thomasfrancart
tel : +33 (0)6.71.11.25.97, skype : francartthomas
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
