IBM-Blockchain-Archive/marbles

Event hub not getting disconnected in invoke_cc.js

Open

#151 opened on Sep 29, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (1,036 stars) (996 forks)batch import
bughelp wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
blockchainbackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.jsbasic understanding of EventHub
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue is in the file invoke cc.js in the invoke chaincode() function. The EventHub connection is not being disconnected after transaction events or timeouts, causing SSL socket leaks. The fix requires finding the existing EventHub connection and properly closing it in the success, failure, or timeout callbacks. Since the repository is archived, no further work is expected.