deepstreamio/deepstream.io-msg-amqp

The AMQP connector for deepstream.io

deepstream.io-msg-amqp's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

issues with [email protected]

I've got issues with AMQP message connector.

config.yml

plugins:
   message:
     name: amqp
     options:
       host: localhost
       port: 5672

> deepstream start -c config.yml

INFO | State transition (start): Stopped -> LoggerInit
INFO | logger ready: std out/err
INFO | State transition (logger-started): LoggerInit -> PluginInit
INFO | deepstream version: 3.1.1
INFO | configuration file loaded from config.yml
INFO | library directory set to: /usr/local/lib/deepstream/
INFO | storage ready: no storage connector specified
INFO | cache ready: local cache
INFO | authenticationHandler ready: none
PLUGIN_INITIALIZATION_ERROR | message needs to implement isReady or be an emitter
/usr/local/lib/node_modules/deepstream.io/src/utils/dependency-initialiser.js:32
      throw error
      ^

Error: message needs to implement isReady or be an emitter
    at new DependencyInitialiser (/usr/local/lib/node_modules/deepstream.io/src/utils/dependency-initialiser.js:30:21)
    at _options.pluginTypes.forEach (/usr/local/lib/node_modules/deepstream.io/src/deepstream.io.js:247:27)
    at Array.forEach (native)
    at Deepstream._pluginInit (/usr/local/lib/node_modules/deepstream.io/src/deepstream.io.js:245:31)
    at Deepstream._transition (/usr/local/lib/node_modules/deepstream.io/src/deepstream.io.js:183:28)
    at DependencyInitialiser.loggerInitialiser.once (/usr/local/lib/node_modules/deepstream.io/src/deepstream.io.js:220:12)
    at DependencyInitialiser.g (events.js:292:16)
    at emitNone (events.js:86:13)
    at DependencyInitialiser.emit (events.js:185:7)
    at DependencyInitialiser._emitReady (/usr/local/lib/node_modules/deepstream.io/src/utils/dependency-initialiser.js:123:10)

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Error while initialising messageConnector: Oversized frame

I'm trying to connect deepstream to activemq server. Activemq is listening on port 5672. Here goes the transport configuration:

<transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>

Server Configuration is the following:

var DeepstreamServer = require( 'deepstream.io' ),
    AmqpMessageConnector = require( 'deepstream.io-msg-amqp' ),
    server = new DeepstreamServer();
server.set( 'messageConnector', new AmqpMessageConnector({
    port: 5672,
    host: 'localhost' 
}));
// start the server
server.start();

when I run the server I get following message in the console:

PLUGIN_ERROR | Error while initialising messageConnector: Oversized frame 1342177536

Any idea why I'm getting this error?

PLUGIN_INITIALIZATION_ERROR | message needs to implement isReady or be an emitter

when I install amqp plugin and config it in config.yml like:
plugins:
message:
name: amqp
options:
host: ${AMQP_HOST}
port: ${AMQP_PORT}
then start deepstream,deepstream can not start and run ,
how to fix it
it show:

| | ___ ___ _ __ | | _ __ ___ __ _ _ __ ____
/ |/ _ \/ _ \ '_ \/ __| __| '__/ _ \/ _ | ' ` _
| (| | __/ __/ |) _ \ || | | __/ (| | | | | | |
_,|_|_| ./|/_|| ___|_,|| || ||
||
===================== starting =====================
INFO | logger ready: std out/err
INFO | deepstream version: 3.1.0
INFO | configuration file loaded from conf\config.yml
INFO | library directory set to: D:\tools\deepstream.io-windows-3.1.0\lib
INFO | storage ready: no storage connector specified
INFO | cache ready: local cache
INFO | authenticationHandler ready: none
PLUGIN_INITIALIZATION_ERROR | message needs to implement isReady or be an emitter
[eval]:49329
throw error
^

Error: message needs to implement isReady or be an emitter
at new DependencyInitialiser ([eval]:49327:21)
at _options.pluginTypes.forEach ([eval]:40901:27)
at Array.forEach (native)
at Deepstream._pluginInit ([eval]:40899:31)
at Deepstream._transition ([eval]:40837:28)
at DependencyInitialiser.loggerInitialiser.once ([eval]:40874:12)
at DependencyInitialiser.g (events.js:292:16)
at emitNone (events.js:86:13)
at DependencyInitialiser.emit (events.js:185:7)
at DependencyInitialiser._emitReady ([eval]:49420:10)