Hi Hugh,

First, let me introduce myself.
My name is Jonathan Dray. I am working with Alexandre on the french national
librairy's project.
As Alexandre recently left the project, I will continue to communicate with
you on previously submitted issues.


> Alexandre,
> On 7 Jul 2009, at 15:41, Alexandre Bertails wrote:
>
>>> Can you please confirm if their are any created Virtuoso RDFViews
>>> in the
>>> database, as the query looks fine, but we note the following in
>>> the error
>>> output:
>>
>> I don't understand what you want : we don't use RDFViews...
>>
>>> What happens if the same is executed against the Virtuoso SPARQL
>>> endpoint or
>>> isql interface ?
>>
>> I have tested with both of them : no problem at all!
>
> [Hugh] Given the same query works again the sparql endpoint and isql,
> are you sure the Virtuoso jena provider and JDBC driver being used
> are the ones shipped with the updated snapshot archive and not
> possibly the ones from the 5.0.9 archive which you say works. As
> their have been changes both these components since this release ?


You had the right guess.

We compiled with a 5.0.12 version of the Virtuoso Jena provider but not of
the JDBC driver which remained in a 5.0.9 version.
After a few investigations we changed the JDBC driver version and it now
perfectly works.
Sorry for the inconvenience.

Thanks for your help.
Regards,

Jonathan Dray

>>
>>> Please enable extra debugging on the server using the trace_on/off
>>> functions as detailed at:
>>> http://docs.openlinksw.com/virtuoso/fn_trace_on.html#(NULL)
>>> and provide the trace information for an instance when the query
>>> is failing
>>> via JDBC, SPARQL endpoint or isql, which ever fails.
>>
>> Ok, we will give you that. I tested it but I don't remember
>> something weird.
>
> [Hugh] If you have confirmed the latest jena and jdbc components are
> being used then please provide the trace_on output for the failing
> query.
>
> Best Regards
> Hugh Williams
> OpenLink Software
>
>>
>> Best regards,
>>
>> Alexandre Bertails.

Reply via email to