I would not mind getting an updated jdbcclient jar as well. Interesting news about the non-ideal network in my case. The linux host is actually a VMware can installed on the network somewhere. There are several of these in simultaneous operation on the same physical box so network characteristics are unpredictable. I usually access this can via nxclient (NoMachine). I also sometimes use a VPN connection from home (my DSL account) to work with all of the firewalling that this arrangement includes. We also have regular network annoyances -- like our Outlook clients losing contact with the Exchange server. I suspect that there is a general network misalignment of some kind. I guess I will open a trouble ticket with out IT department. So I am glad to have "arranged" a testing environment to reveal a lurking misbehavior. I assume this fix is actually the right solution for the monetdb jdbc implementation, rather than a work-around for my particular situation and that it will be included in the next MonetDB release. Fabian Groffen wrote:
On 13-11-2007 12:03:30 -0800, jsolderitsch wrote:
Yes!
The new jar works from inside Aqua Data Studio -- connecting to the Linux Monet DB from Aqua Data Studio running on the Mac. I see the demo DB now and all of the schemas within -- just like localhost.
Actually, what you may be interested in, is what revealed this bug. The bug actually was wrong use of basically a non-blocking read. The problem here was that the code assumed a blocking read. It appeared to go well in our entire testing suite and desktops, basically because local and our tested network connections were fast enough to have the TCP buffers filled fast enough to have the non-blocking read get what it needs (at max 8K). In your case it seems that the network connection is too slow for this. This may be due to firewalls, or just a very busy network stack, but just so you are aware of this. This also explains why it worked locally. Anyway, the fix I made was basically to make the read blocking.
I first tried mjclient but that fails because it wants a jdbcclient.jar and the one you built is missing a main class -- even after I adjusted the script to compensate and use the new jar instead.
If you want, I can just give you the jdbcclient.jar as well.
I will report back here is there are any further.
I was getting to switch to mysql :-(
Oh noes!!!!!! ;)
------------------------------------------------------------------------- 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.