[rabbitmq-discuss] stomp plugin doesn't work in Ubuntu Natty

[Brian Thomason]

Hi All,

I recently emailed the list about a config file change in 2.3 that was preventing stomp from loading properly and Simon was kind enough to provide the solution.  unfortunately, we are now seeing another error:

/usr/sbin/mc-ping failed to run: incompatible marshal file format (can't be read)

        format version 4.8 required; 89.111 given (TypeError)

The full log can be found here:

http://pastebin.com/DcMzc8S0

Thanks in advance for any help!

-Brian

[Simon MacMullen]

On 12/04/11 15:16, Brian Thomason wrote:
> The full log can be found here:
>
> http://pastebin.com/DcMzc8S0

From the pastebin:

> ## Huh? "Embedded Rabbit Stomp Adapter","0.0.0" & "RabbitMQ AMQP
> Client","0.0.0" version 0.0.0?

Plugins show version 0.0.0 if they're self-compiled and you didn't
specify a VERSION when bulding them.

> Server private detail: {{{case_clause,
> {badrpc,
> {'EXIT',
> {undef,
> [{rabbit_direct,connect,

I think you're running self-compiled plugins from hg default against the
2.3.1 server release - certainly there were some API changes in this
area. This won't work - plugins tend to be bound tightly to a given
server release.

So either download binary plugins from
http://www.rabbitmq.com/releases/plugins/v2.3.1/ or update all your
plugin repos to tag rabbitmq_v2_3_1, make clean everywhere, and rebuild.

Cheers, Simon

--
Simon MacMullen
Staff Engineer, RabbitMQ
SpringSource, a division of VMware

_______________________________________________
rabbitmq-discuss mailing list
rabbitmq...@lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

[brian.t...@gmail.com]

Thanks Simon,

Yes, these are plugins built from hg, but we tried the binary ones and received the same error.  I'll try fixing the version string and seeing if that has any effect.

Thanks!

-Brian

[Simon MacMullen]

On 12/04/11 17:30, brian.t...@gmail.com wrote:
> Yes, these are plugins built from hg, but we tried the binary ones and
> received the same error. I'll try fixing the version string and seeing
> if that has any effect.

Hi Brian. The error you're seeing isn't to do with the version string
being set to 0.0.0, but is to do with running different versions of the
server and plugins.

[brian.t...@gmail.com]

I figured as much.  There must have been subtle API changes as you suggested in the repo when we pulled it in march.  I'll try to pull a tag of the 2.3.1 release and try again. 

-Brian