so i've been looking into a queue bug and found that it is a bit more nasty than meets the eye. after seeing the queue somehow connect to itself on the same port: (tcp 88 0 127.0.0.1:57235 127.0.0.1:57235 ESTABLISHED21700/bongoqueue) i figured it was probably something ugly. i ran queue under valgrind and have found some issues with the connection pooling system that we got from hula. it seems that there are some memory issues with it that need to be straightened out. i'll get to that this week as i can (i should have some free time this wednesday night). i'm really surprised that we haven't seen this before but it seems to be easily reproduceable at my house when there are 1000 or so messages in the queue for delivery. i get all sorts of oddness when that happens with threads just disappearing off into la-la land and the queue stalling. the stall happens because the queue has a max threads limit and with threads not going anywhere we eventually exhaust the pool.
for those interested, here is the valgrind output. http://www.feltonline.com/p_c/queuevalgrind.txt _______________________________________________ Bongo-devel mailing list [email protected] https://mail.gna.org/listinfo/bongo-devel
