Hi Rob,
Thanks for making a fix in the dotNetRDF library ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www.openlinksw.com/
10 Burlington Mall Road, Suite 265, Burlington MA 01803
Weblog -- http://www.openlinksw.com/blogs/
LinkedIn -- ht
No that is not exposed in the public API anywhere but can be fixed
internally and I have just done so, unfortunately I already made the
0.6.0 release this past weekend so the fix won't hit an official release
until 0.6.1 now
Rob
On 2/21/12 6:44 AM, Hugh Williams wrote:
Hi Sherif / Rob,
The
Hi Sherif / Rob,
The Virtuoso ADO.Net Provider DBcommand class has a detault CommandTImeout
property value of 30 seconds, as detailed at:
http://docs.openlinksw.com/virtuoso/virtclientref.html#vcrvirtuosocommandclass
Which would be the timeout you are hitting, so does the dotN
sorry for being late,
The stack trace of the exception is:
System.SystemException was caught
Message=Timeout expired.
Source=OpenLink.Data.Virtuoso
StackTrace:
at OpenLink.Data.Virtuoso.Future.GetResult(ISession session,
FutureList futures, Boolean remove)
at OpenLink.Data.Virt
Hugh -
dotNetRDF does not explicitly set the timeout anywhere in our code so
the timeout Sherif sees presumably is set automatically in the ADO.Net
provider somewhere?
If he uses the constructor he shows where he passes a custom connection
string that gets used to create a VirtuosoConnection
Hi Sherif,
You say “The library makes the timeout 30seconds” by which I presume you mean
the dotNetRDF library, in which case where is this setting actually made and
what is the actual timeout error message being received as it sounds as if its
value is overriding the one you are setting in the
