On Tue, May 17, 2011 at 7:58 PM, Joegen Baclor <[email protected]> wrote: > On 05/18/2011 05:26 AM, George Niculae wrote: >> On Tue, May 17, 2011 at 5:13 PM, Douglas Hubler<[email protected]> wrote: >>> On Tue, May 17, 2011 at 9:25 AM, George Niculae<[email protected]> wrote: >>>> Thanks Joegen. Other opinions about mongo db update? Or should we >>>> handle this to QA team to see if solves the issue and if not to go for >>>> an update? >>> I gathered that using the threadsafe driver class should be irrelevant >>> to the original condition but just a good idea. >>> >>> Yes, we can upgrade mongo if it fixes a bug. I would install mongo >>> 1.8 on your development machine and see if the bug goes away. >> Can we have new rpms built with Joegen's patch, if still a problem >> then will consider mongo upgrade >> > > Is it the DB that is buggy or the client connection? If it is the > client, then you must build the RPM's with 1.8 already
George, if you can reproduce this problem, then you should be able to test if joegen's patch fixes anything. If it doesn't then you can also test if mongo 1.8 fixes anything by installing it before we upgrade the build system. you dig? Joegen, when you say "client", you mean the mongo client shared library that is built w/the mongo rpm or are you talking about another client. I kicked off a new build because it was time anyway. It's been a while, so there might be some compiler issues to get thru. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
