There is very little code, just a ruby script with the following contents:
#!/usr/bin/env ruby # Make sure stdout and stderr write out without delay for using with daemon like scripts STDOUT.sync = true; STDOUT.flush STDERR.sync = true; STDERR.flush # Load Rails RAILS_ROOT=File.expand_path(File.join(File.dirname(__FILE__), '..')) load File.join(RAILS_ROOT, 'config', 'environment.rb') # Load ActiveMessaging processors #ActiveMessaging::load_processors # Start it up! ActiveMessaging::start And I don't think anything gets done with ActiveMQ until the 'ActiveMessaging::start' call. The code is identical on both servers, as well, but for some reason won't become a consumer on the new server. -- View this message in context: http://activemq.2283324.n4.nabble.com/Connection-being-made-but-not-registering-as-a-Consumer-of-any-queues-tp4676052p4676489.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
