search for: threadsafing

I have been unable to install Microsoft Office 2000 under wine on several Fedora Linux machines. The problem seemed to start with the June 2004 release of wine and has persisted for every version I have tried up to and including the latest 12/01/2004 version. I have tried both RPM install and compiling from source with similar results. I have one machine running the May 2004 wine that

I'm trying to install Office XP on Fedora 3, with the 12/1/2004 wine build from the source. I tried the suggestions given by Ronald Nave on Dec 2/2004 (installing DCOM98, windows installer), but to no avail, and I get the following errors, any help/suggestions are appreciated! ------------------------------------ fixme:wininet:FindFirstUrlCacheEntryA ((null), 0x7fd943b0, 0x5b41ea38): stub

Hey, We hit a bug today because Arel::Visitors::ToSql is not threadsafe. Here is what is happening: Arel::Visitors::ENGINE_VISITORS is a cache of visitors instances. These instances are not inherently threadsafe because it contains state ''@last_column'', ''@connection'' that is shared between threads. The other variables ''@pool'',

I was reading here and there about the differences between Merb and Rails [1] and became curious about statements such as this: > It is threadsafe with configurable Mutex Locks (Routing is also > threadsafe) Having mucked with the routes system, I had this awful feeling that I don''t understand threading well enough to know if my contribution is "thread safe".

Hi There Is active record 3.1.1 supposed to be threadsafe? In other words, should the following (concurrent access to a model) work? Thread.new do MyModel.where(some_condition).first end Thread.new do MyModel.where(some_condition).first end I ask because upon the answer, it depends which component should handle synchronization, and in consequence, which component to patch/fix. A bit of

Hey I am playing with a LOT of threads right now, and I want to know if the threads all need their own little vorbis encoders running in them or what exactly is threadsafe in vorbis? So here are the functions that would be called from many threads of with buffer = vorbis_analysis_buffer( &m_vorbisDsp, 4*DATA_CHUNK_SIZE ); vorbis_analysis_wrote( &m_vorbisDsp, dataLength/dataSize );

Is Rails Logger truly not Thread Safe? http://log.kares.org/2011/04/railslogger-is-not-threadsafe.html This seems like an issue that should have been picked up quite a long time ago. I just set config.threadsafe! in my config/application.rb and my log output from rails server has completely disappeared. If the logger is not thread-safe, I cannot help but wonder how much of the Rails core is

Hi, I use Mongrel to serve my Rails applications on my server, but how can I serve more than one application with one mongrel server? Thanks. -jec -- Best regards / Salutations. Jean-Eric Cuendet Senior developer / Technical support Riskpro Technologies SA Av. Louis-Ruchonnet 2 CH-1003 Lausanne Switzerland Direct : +41 21 637 0123 Principal : +41 21 637 0110 Fax : +41 21 637 0111

Hi mongrel-users, This is my first post, so I''m not sure if it''s been asked before, but I can''t find an answer anywhere. If I have one rails application running, one processor I''m running it on, and mongrel is multi-threaded, why should I have more than one mongrel running? Everyone seems to agree on 3-5 mongrels per rails app, but why? I must be

In Rails 3.0 (both RC and edge), any constant that''s defined while loading a file in development mode will get unloaded on each request, regardless of whether it comes from an autoload path in the application or from external code such as a gem. Example file (tested on a fresh edge app): # kittens.rb require ''nibbler/json'' # "nibbler" is a gem specified

I am running jruby (1.7.3) & rails 2.3.17 application whose apis are exposed to outside app. When I add "config.threadsafe!" in my development.rb/production.rb & hit lot many api requests in a second then I am getting following errors randomly for some of the api requests: 1. TypeError (NilClass can't be coerced into Float) 2. RuntimeError (can't add a new key

Hi all, Both the rails book (1st Ed) and the docs on the rails site (*and* the Mongrel FAQ) tell me that rails (& ActionPack /ActiveRecord) is not threadsafe. Since I need lots of worker threads in the app I''m working on (details at the end of this mail) this poses quite a problem for me. Is the lack of thread safety a conscious design decision (kind of understandable for rails

Hi I have some questions regarding threads in Mongrel and Rails. According to the FAQ: "Ruby on Rails is not thread safe so there is a synchronized block around the calls to Dispatcher.dispatch. This means that everything is threaded right before and right after Rails runs. While Rails is running there is only one controller in operation at a time." Isn''t this going

On Fri, Mar 27, 2009 at 2:25 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: > On Fri, Mar 27, 2009 at 3:48 PM, Evan Cheng <evan.cheng at apple.com> wrote: >> Run with -debug-only=jit. > > OT: I take it the recommended model for tools that embed LLVM is for > them to accept all of LLVM's command line arguments on their own > command lines? Well, sort of...

On Fri, Mar 27, 2009 at 3:48 PM, Evan Cheng <evan.cheng at apple.com> wrote: > Run with -debug-only=jit. OT: I take it the recommended model for tools that embed LLVM is for them to accept all of LLVM's command line arguments on their own command lines? For Python, it'd be much nicer to make this stuff tweakable through a module at runtime, or even, for thread-safety reasons, as

>From http://blog.codefront.net/2008/01/02/whats-new-on-edge-rails-the-pilot/ A native Mongrel handler has been introduced. This is so that it can be worked on independent of Mongrel?s release cycle (the Rails handler is currently in the Mongrel codebase). Jeremy Kemper (bitsweat) has already made a minor performance improvement by moving the mutex from the handler itself into the dispatcher.

[caution: this is an IPv6 e-mail address. if you don't have IPv6-capable mail then best keep replies on the list only] > >existing getipnodebyname() call fails with IPv4 on my machine)... > Well, if you can make it work properly - send your patches in, please. The following enhancements to src/net/resolver.c (which looks identical across icecast, ices, libshout, and who knows what

On 2009-11-01 08:40, Jeffrey Yasskin wrote: > 2009/10/30 Török Edwin <edwintorok at gmail.com>: > >> On 2009-10-29 23:55, Jeffrey Yasskin wrote: >> >>> On Thu, Oct 29, 2009 at 2:30 PM, Nicolas Geoffray >>> <nicolas.geoffray at lip6.fr> wrote: >>> >>> >>>> Hi Jeffrey, >>>> >>>>

I''m creating a message queue system, (think JMS message queue) Basically, I''ll be firing off an http request as soon as a row appears in a database. Now in past implementations I''ve done the following. 1. Polled the database every 0.10 seconds. 2. If something was there to work, I''d tag it as complete. 3. Create a separate thread. (no further database hits

Hi Running ./configure --prefix=/whatever I got stuck with checking for pkg-config... /usr/bin/pkg-config checking shout/shout.h usability... no checking shout/shout.h presence... no checking for shout/shout.h... no configure: error: must have libshout installed! Having edited configure line 20056 and changed shout/shout.h to /usr/include/shout.h , I run into the next problem: