I tried the reverse direction with mjclient: going from the centos install back to the database running on my Mac and I get the same errors. This was after I added ant to my centos install so I could build the jdbc jar there. So the problem is not a quirk of Mac to Linux. It is quite repeatable in either direction. Thanks for taking the time to look into this. Jim Fabian Groffen wrote:
Well, not really. The problem now is to determine who is at fault. JDBC thinks it gets a too large block, but the question remains whether the server really sends a too large block or not. I've never been able to reproduce it, meaning I can't just put the debugger on it to pinpoint who is at fault here.
The debug needs to be done on the server side in stream.mx, however, for that code I need Niels to be able to quickly analyse it to see if it is theoretically possible at all that too big blocks are being sent, or that maybe somewhere some bitshifting doesn't take something into account which it should have...
------------------------------------------------------------------------- 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-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- View this message in context: http://www.nabble.com/Using-JDBC-for-MonetDB-across-the-network-tf4793137.ht... Sent from the monetdb-users mailing list archive at Nabble.com.