We fixed the problem by moving activemq to the new server, and having
everything connect to it as the broker instead of the other way around.
Thanks very much for your help, very appreciated.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connection-being-made-but-not-r
I think it's probably the following from a file called messaging.rb that
ActiveMessaging loads up automatically:
ActiveMessaging::Gateway.define do |s|
s.destination :my_publishing_queue, '/queue/myQueue_production'
end
--
View this message in context:
http://activemq.2283324.n4.nabble.c
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.
Thanks so much for your response. Unfortunately we did check all those things
but no luck. Do you have any other suggestions what could be going on here?
We've made sure that all the versions of ruby and the gems are the same on
both servers.
Here is a bit of info from the data/activemq.log
Whe
Hello. We recently moved our application to a new server and are trying to
get an activemq poller script to run there but for some reason it just isn't
working properly.
When I start the poller script on the old server I can see it show up in the
"Connections" menu, and when I click the connectio
