0xcodezero / activemessaging

Automatically exported from code.google.com/p/activemessaging
0 stars 0 forks source link

Cannot use stomp as a frozen gem #33

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Freeze stomp gem into project
2. Uninstall gem from global gem list
3. Run script/poller run

What is the expected output? What do you see instead?
Poller starts (no visible output if activemq running)

Actual behaviour is NoMethodError is raised on line 112 of gateway.rb from
lib/activemessaging.

What version of the product are you using? On what operating system?
Stomp 1.0.5.
ActiveMessaging (current as of today).

Please provide any additional information below.
We fixed this error by removing the deprecated "gem 'stomp'" line from line
1 of acivemessaging/adapters/stomp.rb.

Original issue reported on code.google.com by nigel.pe...@gmail.com on 11 Jun 2008 at 10:52

GoogleCodeExporter commented 9 years ago
what version of rails are you on?
could I get a full stack trace here?

Original comment by kooks...@gmail.com on 11 Jun 2008 at 3:04

GoogleCodeExporter commented 9 years ago
wait - you fixed it by messing with the stomp gem?
that means you need to go submit a bug to the stomp project, not here.

Original comment by kooks...@gmail.com on 11 Jun 2008 at 3:04

GoogleCodeExporter commented 9 years ago
We're using Rail 2.1.0

Stack trace:

/var/nimbus/releases/20080611160324/vendor/plugins/activemessaging/lib/activemes
saging/gateway.rb:112:in
`connection': undefined method `new' for nil:NilClass (NoMethodError)
    from
/var/nimbus/releases/20080611160324/vendor/plugins/activemessaging/lib/activemes
saging/gateway.rb:394:in
`unsubscribe'
    from
/var/nimbus/releases/20080611160324/vendor/plugins/activemessaging/lib/activemes
saging/gateway.rb:129:in
`unsubscribe'
    from
/var/nimbus/releases/20080611160324/vendor/plugins/activemessaging/lib/activemes
saging/gateway.rb:129:in
`each'
    from
/var/nimbus/releases/20080611160324/vendor/plugins/activemessaging/lib/activemes
saging/gateway.rb:129:in
`unsubscribe'
    from
/var/nimbus/releases/20080611160324/vendor/plugins/activemessaging/lib/activemes
saging/gateway.rb:105:in
`stop'
    from
/var/nimbus/releases/20080611160324/vendor/plugins/activemessaging/lib/activemes
saging/gateway.rb:67:in
`start'
    from
/var/nimbus/releases/20080611160324/vendor/plugins/activemessaging/lib/activemes
saging.rb:108:in
`start'
    from /var/nimbus/releases/20080611160324/vendor/plugins/activemessaging/poller.rb:14
    from
/usr/local/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/application.rb:176:
in `load'
    from
/usr/local/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/application.rb:176:
in
`start_load'
    from
/usr/local/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/application.rb:253:
in
`start'
    from
/usr/local/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/controller.rb:72:in
 `run'
    from /usr/local/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons.rb:139:in `run'
    from /usr/local/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/cmdline.rb:105:in
`call'
    from /usr/local/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons/cmdline.rb:105:in
`catch_exceptions'
    from /usr/local/lib/ruby/gems/1.8/gems/daemons-1.0.10/lib/daemons.rb:138:in `run'
    from script/poller:21

We changed the activemessaging adapter for stomp, not the stomp gem itself. We
changed the file 
vendor/plugins/activemessaging/lib/activemessaging/adapters/stomp.rb so that it
starts with:

require 'stomp'

not:

gem 'stomp'
require 'stomp'

The version of RubyGems we're using is 1.1.1

Original comment by paul.t.m...@googlemail.com on 11 Jun 2008 at 4:25

GoogleCodeExporter commented 9 years ago
Just to be clear, my comment does relate to the original report and  your 
questions -
Nigel has gone home for the day now

Original comment by paul.t.m...@googlemail.com on 11 Jun 2008 at 4:29

GoogleCodeExporter commented 9 years ago
sorry - my bad - read quickly and on too little sleep, just checked in a fix.

Original comment by kooks...@gmail.com on 11 Jun 2008 at 4:55

GoogleCodeExporter commented 9 years ago

Original comment by kooks...@gmail.com on 11 Jun 2008 at 4:55

GoogleCodeExporter commented 9 years ago
Thanks for fixing so quickly

Original comment by paul.t.m...@googlemail.com on 12 Jun 2008 at 9:35