search for: threadgroup

...ndex.html listing_allowed: false path: / guard: !ruby/object:Mutex {} klass: !ruby/object:Module {} listener: *id001 death_time: 60 host: 0.0.0.0 num_processors: 1073741823 port: "3001" socket: !ruby/object:TCPServer {} timeout: 0 workers: !ruby/object:ThreadGroup {} What''s weird is that i can go to: http://localhost:3001/config/resources and see the erb template output with <% .. %>. Currently I am running Mongrel 0.3.20 but i had the issue with 0.3.18 as well. System is an Ubuntu Edgy on 2.6.17-10 kernel. Any help would be greatly apprec...

....00 0.00 Kernel.respond_to? 0.00 6.55 0.00 2 0.00 0.00 Module#const_defined? 0.00 6.55 0.00 2 0.00 0.00 Kernel.require 0.00 6.55 0.00 1 0.00 2750.00 #toplevel 0.00 6.55 0.00 1 0.00 0.00 ThreadGroup#add 0.00 6.55 0.00 38 0.00 0.00 Module#to_s 0.00 6.55 0.00 1 0.00 0.00 DispatchServlet#handle_dis patch 0.00 6.55 0.00 1 0.00 0.00 IO#close 0.00 6.55 0.00 1 0.00 0.00 DRb::DRbTCPSocket#acc...

...ope at the beginning for large-scale HPC systems, but I’m not sure how important that is to anyone. As a related question, do we actually need the local scopes to be target specific? Are there systems, real or planned, that *aren’t* captured by: [Network —> ] System —> AllThreads —> ThreadGroup —> SingleThread ? —Owen

I recently upgraded to 1.8.4 to try out mongrel, and so far have been in a kind of hell where I can''t get my app working! Currently running (or trying to run): Ruby version 1.8.4 (i386-mswin32) RubyGems version 0.8.11 Rails version 1.0.0 Active Record version 1.13.2 Action Pack version 1.11.2 Action Web Service version 1.0.0 Action Mailer version 1.1.5 Active Support version

...in service_init, but because that greatly complicated matters, and I was just trying to get something that WORKED first, the current code does not do this. * now the service terminates if service_init or service_main exit or raise exceptions. Problems I encountered or resolved: * Waiting for the ThreadGroup is not sufficient to make sure ALL threads have exited. Instead, I wait on Thread.list to == 1. I don''t know that this was really necessary. * raising exceptions in service_init and service_main left the service running - required service_init and main to have rescue clauses to catch al...

....000000000 -0700 +++ mongrel-1.0.1/lib/mongrel.rb.zero_port_fix 2007-08-05 15:29:23.000000000 -0700 @@ -560,7 +560,7 @@ @socket = TCPServer.new(host, port) @classifier = URIClassifier.new @host = host - @port = port + @port = @socket.addr[1] @workers = ThreadGroup.new @timeout = timeout @num_processors = num_processors

Howdy Folks, This release is after painstaking analysis of a memory leak that was reported by Bradley Taylor, reduced by myself, and then fixed after much work. You should all thank Bradley for finding the bizarre fix. It turns out the Ruby has a memory leak when you use pretty much any thread locking primitive other than Sync (Mutex, Monitor, etc.): http://pastie.caboo.se/10194 The fix (for

I''m developing a stateful Ruby application that needs to keep data in one location where all people accessing the site can modify its contents. This data will be read-from/written to often, so I would prefer for rails to keep it in memory, rather than a database. My frist try involved global variables. After discovering that they were being "re-initialized" with each new

Hello! Run problems after upgrading to mongrel 1.0.3 from 1.0.1: # uname -sr FreeBSD 7.0-BETA1 # mongrel_rails start ** Starting Mongrel listening at :3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload

I've not had a good chance to look at the patches in detail, but just to clarify one point: I don't really care whether we number things going up or down from single threaded to "every thread". I just think it makes sense to expose them in the in-memory IR interface as an enum with a particular ordering so that code can use the obvious sorts of tests for comparing two orderings

....java ../../../src/share/classes/java/lang/Runtime.java ../../../src/share/classes/java/lang/Short.java ../../../src/share/classes/java/lang/StackOverflowError.java ../../../src/share/classes/java/lang/String.java ../../../src/share/classes/java/lang/Thread.java ../../../src/share/classes/java/lang/ThreadGroup.java ../../../src/share/classes/java/lang/Throwable.java ../../../src/share/classes/java/lang/ref/Reference.java ../../../src/share/classes/java/lang/ref/SoftReference.java ../../../src/share/classes/java/lang/reflect/Field.java ../../../src/share/classes/java/lang/reflect/Method.java ../../../src/...

.... WARNING: Class file 'java/lang/System' requires Java version 1.7. This JVM only supports Java versions up to 1.6. WARNING: Class file 'java/lang/AssertionStatusDirectives' requires Java version 1.7. This JVM only supports Java versions up to 1.6. WARNING: Class file 'java/lang/ThreadGroup' requires Java version 1.7. This JVM only supports Java versions up to 1.6. WARNING: Class file 'java/lang/Thread$UncaughtExceptionHandler' requires Java version 1.7. This JVM only supports Java versions up to 1.6. WARNING: Class file 'sun/reflect/ConstantPool' requires Java ver...

...is an explicit optimization over a narrower set of threads. > As a related question, do we actually need the local scopes to be > target specific? Are there systems, real or planned, that > *aren’t* captured by: > > [Network —> ] System —> AllThreads —> ThreadGroup —> SingleThread ? > > > Sadly, I don't think this will work. In particular, there are > real-world accelerators with multiple tiers of thread groups that are > visible in the cache hierarchy subsystem. The HSAIL 1.0 provisional spec has the following scopes: workitem, wave...

.../System' requires Java version 1.7. This >> JVM only supports Java versions up to 1.6. >> WARNING: Class file 'java/lang/AssertionStatusDirectives' requires >> Java version 1.7. This JVM only supports Java versions up to 1.6. >> WARNING: Class file 'java/lang/ThreadGroup' requires Java version 1.7. >> This JVM only supports Java versions up to 1.6. >> WARNING: Class file 'java/lang/Thread$UncaughtExceptionHandler' >> requires Java version 1.7. This JVM only supports Java versions up to >> 1.6. >> WARNING: Class file 'su...

...e 'java/lang/System' requires Java version 1.7. This > JVM only supports Java versions up to 1.6. > WARNING: Class file 'java/lang/AssertionStatusDirectives' requires > Java version 1.7. This JVM only supports Java versions up to 1.6. > WARNING: Class file 'java/lang/ThreadGroup' requires Java version 1.7. > This JVM only supports Java versions up to 1.6. > WARNING: Class file 'java/lang/Thread$UncaughtExceptionHandler' > requires Java version 1.7. This JVM only supports Java versions up to > 1.6. > WARNING: Class file 'sun/reflect/ConstantPo...

...uires Java version 1.7. This >>> JVM only supports Java versions up to 1.6. >>> WARNING: Class file 'java/lang/AssertionStatusDirectives' requires >>> Java version 1.7. This JVM only supports Java versions up to 1.6. >>> WARNING: Class file 'java/lang/ThreadGroup' requires Java version 1.7. >>> This JVM only supports Java versions up to 1.6. >>> WARNING: Class file 'java/lang/Thread$UncaughtExceptionHandler' >>> requires Java version 1.7. This JVM only supports Java versions up to >>> 1.6. >>> WARNING...

...dead_service.rb:119:in `service_main'': uninitialized constant RUNNING (NameError) from U:/Programming/Sources/ruby/try/dead_service.rb:131 Just commenting the sleep command solves that problem, but leaves other issues there... like the impossible task of killing running threads (from a ThreadGroup, as example). Also, removing the while state == RUNNING loop solves the sleep and file handling issues, but still exist problems with already running threads that must be killed/stopped. Or: I''m doing something wrong (in which case please enlighten me) or there is something wrong on how...

I also misunderstood :) So, in this case, the problem is that your version of openjdk is probably not supported. In fact, we only support the version 7u23 of openjdk :) You can find this version here: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html#jdk-7u25-oth-JPR Currently, I'm modifying the internal design of vmkit and I'm not working

I guess I mispoke, I checked out the source from http://llvm.org/svn/llvm-project/vmkit/trunk. I thought this was vmkit2. I guess I was just referring to vmkit then. On Thu, Nov 21, 2013 at 12:10 PM, Gaël Thomas <gael.thomas00 at gmail.com> wrote: > Hi Adam, > > I don't know which repo you have used? Because only the llvm repo is > maintained (not the gforge one), and