Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event hub not getting disconnected in invoke_cc.js #151

Open
venugopv opened this issue Sep 29, 2017 · 1 comment
Open

Event hub not getting disconnected in invoke_cc.js #151

venugopv opened this issue Sep 29, 2017 · 1 comment

Comments

@venugopv
Copy link

Eventhub is not getting disconnected in invoke_cc.js invoke_chaincode().

Once after transaction event is notified or failed/timedout, the Eventhub has to be disconnected.

This is leading SSL socket leak (i.e socket which is used to connect Eventhub) and causing NODE.JS app not getting exited properly.

@dshuffma-ibm
Copy link
Contributor

thanks! you are right, it was hanging onto the sockets. sort of fixed in d509207 ...

before this "fix" the connections were growing by 2 every invoke. now they are growing by one... i'm not sure where the other connection is coming from, might be sdk? i'll have to revisit this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants