Can't get it work, port conflict.
activemq + stomp use 61613 port,
orbited's stomp must set to another port, but orbited plugin also look for
/extlib/stomp's setting.
e.g. orbited stomp set using 61614, it not only connect to 61614, but also
connect to 61613 through extlib's stomp setting.

hope you can understand what I said.

On Thu, Jan 7, 2010 at 4:14 PM, Evan Prodromou <e...@status.net> wrote:

> CdrPlum wrote:
>
>> I reinstalled zope.interface, orbited and simple json.
>> That error disappeared. Oribited works well.
>> But when I tried to start statusnet daemons, the new error occurred. It
>> seems related to stomp.
>>
>> As Evan said, the orbited plugin still not finished. I will give up it and
>> going to use Meteor.
>>
> I just checked over the Orbited plugin. I was wrong; it does in fact work
> fine. I guess I did more work on it than I remembered!
>
> You may need to be careful using the same stomp server for Orbited and for
> notice queues. What error were you getting?
>
>
> -Evan
>
> --
> Evan Prodromou
> CEO, StatusNet, Inc.
> e...@status.net - http://identi.ca/evan - +1-514-554-3826
>
>
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev

Reply via email to