Hardcoded values

[isati]

Not sure if this is a known issue or not:

I have recently been pulling my hair out trying to get echowaves (http://echowaves.com) [which utilises ruby-stomp] to run on webfaction. As webfaction is shared hosting, ports tend to be somewhat random..usually requiring manual configuration to get things to work.

It came to my attention that upon changing the configured stomp port (default: 61613), within the rails/echowaves environment (and also orbited itself) led to connection refused errors. This appears to be a result of some hardcoded(?) values with the ruby stomp gem which I rather dirtily hacked around by running 'perl -pi -e 's/61613/$NEWPORT/g' on all of the files within the stomp gem directory..which has fixed the issue.

So perhaps there are hardcoded values within the stomp rubygem or environmental values aren't being read correctly?

[gmallard]

It would be interesting to know what you changed.

61613 is indeed hard coded a few places: because it is the default if no port is specified when creating a new connection or client.

It is also hard coded in example code .... but that should not affect you.

It is also hard coded for tests unless there is an environment variable override. Were you running actual gem tests?

[morellon]

Thanks for the help gmallard. Isati, i will close this issue. If you have this problem again, please contact me or gmallard.