Bugs item #1914463, was opened at 2008-03-14 19:04 Message generated for change (Comment added) made by sjoerd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1914463&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: Core Group: MonetDB4 4.22 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Richard Eckart (wyldfire) Assigned to: Nobody/Anonymous (nobody) Summary: Client hangs unless somebody presses enter at server prompt Initial Comment: ====== System ====== OS: OS X Tiger 10.4.11 gcc: powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5250) MonetDB was compiled from the Feb 2008 Superball. ====== Problem ====== I start up MServer: $ ./Mserver --dbinit="module(pathfinder);" # MonetDB Server v4.22.0 # based on GDK v1.22.0 # Copyright (c) 1993-2008, CWI. All rights reserved. # Compiled for powerpc-apple-darwin8.11.0/32bit with 32bit OIDs; dynamically linked. # Visit http://monetdb.cwi.nl/ for further information. # PF/Tijah module v0.5.0 loaded. http://dbappl.cs.utwente.nl/pftijah # MonetDB/XQuery module v0.22.0 loaded # XRPC administrative console at http://127.0.0.1:50001/admin MonetDB> On another terminal I run a simple test: $ cat > test.xq (1, 42.0, "Hello World", <node attr="value">test</node>) $ ./mclient -lx test.xq _ (blink blink blink ...) and there it hangs. So I go back to the server to see what's up. I tried the "threads()" and "clients()" commands. Well, to me all looks fine except that the "monetdb" client does not seem to have actually sent any command (""). Funnily when I got back to the first terminal, the mclient command had completed. So I tried again. It seems that the mclient command will complete as soon as I hit "return" a couple of times on the MonetDB> prompt. The same goes for the mjclient command. ---------------------------------------------------------------------- >Comment By: Sjoerd Mullender (sjoerd) Date: 2008-04-22 14:48 Message: Logged In: YES user_id=43607 Originator: NO We do this kind of thing all the time without any problems. The difference seems to be that we use different O/S's and distributions. I'm inclined to call this an O/S bug (or bug in the thread implementation). I guess what would help is to attach a debugger while the Mserver is hanging and to look at what all the threads are doing. Then we know for sure. So can you do gdb -p <Mserver-pid> and then at the gd prompt thread apply all bt ---------------------------------------------------------------------- Comment By: Wouter Alink (vzzzbx) Date: 2008-03-16 11:48 Message: Logged In: YES user_id=621590 Originator: NO (i posted this first at the users-mailinglist, but i guess it belongs here) I witnessed a similar problem yesterday on freebsd (with the Feb2008 release). It was not my computer, and I do not really have more details. somehow (when running Mserver in a shell) setting "deamon=yes" in the MonetDB.conf seemed to help. it doesn't solve the actual problem, but perhaps it might help finding it...? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1914463&group_id=56967 ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
