Bugs item #1765919, was opened at 2007-08-02 10:16
Message generated for change (Comment added) made by mr-meltdown
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1765919&group_id=56967
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: SQL/JDBC
Group: Clients 1.18
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Sjoerd Mullender (sjoerd)
Assigned to: Fabian (mr-meltdown)
Summary: Incomplete block read from stream (Mserver still alive?)
Initial Comment:
From a message sent directly to Peter:
I ran tests with 4.18.0 version of the database on windows platform using the
MonetDB4-XQuery-i686-0.18.2.msi install. I work on a bi-processor machine under
Windows XP.
Problems with the JDBC interface
Opening documents
If I try to open a document (giving the doc (“documentName”) instruction) which
is bigger than 150ko I get an error most of the time (60%):
Incomplete block read from stream (Mserver still alive?)
I ran a code from the tutorial :
public class testMonet {
public static void main(String[] args) {
int errors = 0;
for(int k=0;k<100;k++){
System.out.println(k);
try {
Class.forName("nl.cwi.monetdb.jdbc.MonetDriver");
} catch (Exception e1) {
e1.printStackTrace();
}
try {
Connection myConnection =
DriverManager.getConnection("jdbc:monetdb://localhost:50000/database?language=xquery","monetdb",
"monetdb");
Statement myStatement = myConnection.createStatement();
ResultSet myResultSet =
myStatement.executeQuery("doc(\"new\")");
myResultSet.next();
String buffer = myResultSet.getString(1);
myConnection.close();
System.out.println("ok");
} catch (SQLException e) {
System.out.println("error");
errors ++;
}
}
System.out.println("Errors "+errors);
}
}
I had the same problems with more complex queries returning too big results.
It seems to be a thread problem. The success rate of opening documents is even
under 1% for documents which are bigger than 10megs.
----------------------------------------------------------------------
>Comment By: Fabian (mr-meltdown)
Date: 2007-08-02 10:21
Message:
Logged In: YES
user_id=963970
Originator: NO
I would like to have a (tail of a) JDBC logfile of such "crash" occurring.
You can obtain it by using the following connection creation statement:
DriverManager.getConnection("jdbc:monetdb://localhost:50000/database?language=xquery&debug=true","monetdb",
"monetdb");
it will generate a monet_4987427864287323.log file located in the current
working directory.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1765919&group_id=56967
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
