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 object directly and
we don't build the connection string ourselves.
This would suggest to me that either the ADO.Net provider is not
respecting the Connection Timeout setting or it is getting overridden
elsewhere in the Virtuoso layers.
Sherif -
Both me and Hugh have now asked for the error messages you see, please
include these error messages in future messages as it is hard for either
of us to pin down where the problem is if you haven't shown the actual
error message you receive
Also can you please show a code snippet of code that actually causes the
error, all you have shown so far is the constructor which doesn't
actually open the connection it just prepares it so we are still left
guessing as to what your code is doing when it encounters the timeout
error. I assume you are just calling the Query() method on the
VirtuosoManager object but I don't know that for sure without seeing a
code sample.
Rob
On 2/17/12 5:11 AM, Hugh Williams wrote:
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 ConnectString ?
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 -- 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 17 Feb 2012, at 01:37, sherif kandel wrote:
Hi,
I started the virtuoso service on windows with the following
configurations (configuration files attached)
I'm using the dotNetRDF
<http://www.dotnetrdf.org/content.asp?pageID=Using%20Virtuoso%20Universal%20Server>library
to make local queries to the local server (The library makes the
timeout 30seconds) , but I can override the default timeout by
sending a connection string when starting the object:
VirtuosoManager manager = new
VirtuosoManager("Server=localhost;Uid=dba;pwd=dba;Connection
Timeout=500");
it still times out at 30seconds (if my query is complex enough to
process in more than 30 seconds...
My project uses some complex queries, so I need the timeout property
as large as possible , how can I override that property ?
<virtuoso2.ini>------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
------------------------------------------------------------------------------
Virtualization& Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
