Not possible to run two instances of appsync-emulator at once on different ports about aws-utils HOT 10 CLOSED

Hi @mattgibson -- this is a known issue.

I think somewhere near here we need to tell mosca to choose an unused port.

We will investigate and get back to you. Let us know if you come up with anything.

from aws-utils.

Hrm I re-read that code and looked up the port 1883 and now know it has something to do with the mqtt setup.

from aws-utils.

Previous attempt at fixing this issue was : 99bb347

from aws-utils.

Looking at where mosca is started here https://github.com/ConduitVC/aws-utils/blob/master/packages/appsync-emulator-serverless/serverCore.js#L323

I found I could fix the error in one line if I did this:

  const mqttServer = new mosca.Server({
    port: pareseInt(port, 10) + 1,
    backend: { type: 'memory' },
  });

But i'm not sure if that actually broke the subscriptions or not. it just fixed the error and let me start both instances.

from aws-utils.

My hypothesis is there is an additional port bound by mosca that we are in fact not using. There should be some mechanism to turn that off (I am investigating now)

from aws-utils.

I can reproduce this issue on ^0.7.1 (in our test repo) but cannot reproduce on master...

from aws-utils.

I found another issue on master and will publish a version shortly which will include this fix ! I also updated our test repo to run tests in parallel to verify we don't break this in future.

from aws-utils.

Please try 0.12 and see if that works better! I published a few fixes.

from aws-utils.

Marking this as closed . please reopen if issue persists.

from aws-utils.

@lightsofapollo Thanks for the quick fix! Version 0.12 does fix the issue of not being able to run two instances, but I was unable to verify that the subscriptions function correctly. I'll open another issue if that turns out to be the case in future.

from aws-utils.