On 13-11-2007 13:22:23 -0800, jsolderitsch wrote:
I would not mind getting an updated jdbcclient jar as well.
http://www.cwi.nl/~fabian/troep/jdbcclient.jar
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.
Ahhh, well those kind of setups are legal to produce some lag... I was just imagining it to be your big server and thought maybe you don't know that there is a possible speed reduction going on over the wires...
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.
It indeed is a correct fix, as we saw the same happening with Windows. Thanks to your log I was actually able to pin-point the problem this time and fix it. It has been committed and we plan on making a little sub-component bugfix release out of it. So once again, thanks for the report.