[rabbitmq-discuss] error message trying to start stomp adapter?

[Erik Anderson]

On Jan 29, 2:57 am, Matthias Radestock <matth... at lshift.net> wrote:
> Erik,
>
> Erik Anderson wrote:
> > For what it's worth, it looks on the surface in {invalid_host,
> > [49,50,55,46,48,46,48,46,49],timeout} that the numbers are the ascii
> > representation of "127.0.0.1".  Along with a new delay that feels like
> > a timeout when launching the normal TCP listeners, was some of the
> > "short node" stuff done in the last version affecting this?
>
> The "short node" changes in the last release relate to Erlang's
> inter-node communication. They do not affect ordinary network
> operations, so that's not the source of the problem.

Okay, this is really starting to get frustrating.  Googling this error
gives me the strong impression that the timeout here is a DNS timeout,
but I have no clue how to get our DNS servers to respond to something
like 127.0.0.1.  I tried changing it to "::1" but it just moved the
error up to when starting up TCP Listeners instead.  It also said that
I should be giving 127.0.0.1 in "tuple form", but i'm not sure what
that means at the moment.

I replaced Erlang v5.6.5 R12B-5 (as included in the official
installation) with v5.7.3 R13B02-1 (what the server that works is
using) with no effect.  I copied the rabbitmq_server.1.7.0 folder
(with the installed plugin) from the server that works with no
effect.  Same with wiping the database folder.

ProcessExplorer trace shows no registry or file activity during the
"timeouts", the next action after the first one is a load of
stomp.beam, the action after the second is a write to the log file.
The only attempt to access %APPDATA% is to write a file
named .erlang.cookie - no other file or folder existence check is
made.

Modifying the stomp_listener line to change the ip address to 0.0.0.0
or scramble to a dummy port has no effect (is this thing hardcoded to
{"127.0.0.1",61613} or something?)

The fact that this is working on the testbed but is throwing a tantrum
on the server it might actually have value on means that it's an
environmental fault of some kind, either a file I haven't found or a
different server setup that is causing confusion.

Maybe I'll try to get this working sometime next week - I'm running
out of ideas.  I don't have anything on me that I can see to intercept
WINSOCK calls either.

Any suggestions on where to go from here?  Dumping my 1.7.1 startup
trace here...

> We welcome patches, and feedback in general. If you have managed to
> build rabbitmq-c on Windows, could you perhaps post the instructions?

Unfortunately, If it hadn't taken two weeks of my boss's time to try
to get it working I think I would be more amenable to sneaking
something like that out.  As it is I'd like to have something to show
first before dealing with that.  I can bellyache some more about the
kinds of changes I needed to make, but I'm not sure how constructive
that would be.

---

Using Custom Boot File "C:\tw\comet\rabbitmq_server-1.7.1\sbin\..\ebin
\rabbit.boot"

+---+   +---+
|   |   |   |
|   |   |   |
|   |   |   |
|   +---+   +-------+
|                   |
| RabbitMQ  +---+   |
|           |   |   |
|   v1.7.1  +---+   |
|                   |
+-------------------+
AMQP 8-0
Copyright (C) 2007-2009 LShift Ltd., Cohesive Financial Technologies
LLC., and Rabbit Technologies Ltd.
Licensed under the MPL.  See http://www.rabbitmq.com/

node          : rabbit at D3Z2VPD1
app descriptor: c:/tw/comet/rabbitmq_server-1.7.1/sbin/../ebin/
rabbit.app
home dir      : C:\Documents and Settings\EAnderson.TEAMWORK
cookie hash   : hiMbehi/N72av8n8XzaPNg==
log           : c:/tw/comet/rabbitmq-data/log/rabbit.log
sasl log      : c:/tw/comet/rabbitmq-data/log/rabbit-sasl.log
database dir  : c:/tw/comet/rabbitmq-data/db/rabbit-mnesia

starting database             ...done
starting core processes       ...done
starting recovery             ...done
starting persister            ...done
starting guid generator       ...done
starting builtin applications ...done
starting TCP listeners        ...done
starting SSL listeners        ...done

broker running
starting STOMP Adapter (binding to [{"127.0.0.1",61613}])  ...{"Kernel
pid
terminated",application_controller,"{application_start_failure,rabbit_stomp,
{{invalid_host,[49,50,55,46,48,46,48,46,49],timeout},
{rabbit_stomp,start,[normal,[]]}}}"}


Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller)
({application_start_failure,rabbit_stomp,{{invalid_host,
[49,50,55,46,48,46,48,46,49],timeout},{rabbit_stomp,start,[normal,
[]]}}})