That's good news you were able to identify the potential root cause.
Is it possible that the merovinigan is trying to reuse ports from the
connection threads that are leaking?
On Tue, Sep 30, 2008 at 7:54 AM, Fabian Groffen
I think I at least identified the problem. Thanks to my Solaris OS, I can see how many threads are being used. And with a quick stress-test, my merovingian now already has 6000 threads in use, which feels like something is leaking :)
We hunted for this on Linux, but couldn't find anything, as we only saw a bit of memory leaking. Now on Solaris I can clearly see the threads are leaking.
On 22-09-2008 23:05:55 +0200, Fabian Groffen wrote:
On 21-09-2008 16:40:22 -0500, Ross Bates wrote:
I haven't made any changes to the default settings for merovinigian, here they are without comments:
Ok, thanks.
As for your question about the type of query, unfortunately I can't reproduce the lockup in a certain number of steps or with a certain query. The queries are dynamically generated by a script, but they are all simple like "select col1, col2 from table where col1='foo'".
After I recompile with --enable-debug, how do use gdb to monitor the process? If I run the following command can I just leave the gdb attach process running until it crashes?
gdb attach pid
yep, like that.
Are you using stable or current? I'll try to reproduce it so I can debug and fix myself.
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users