IBM-Blockchain-Archive/marbles

Event hub not getting disconnected in invoke_cc.js

Open

#151 创建于 2017年9月29日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)JavaScript (1,036 star) (996 fork)batch import
bughelp wanted

描述

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.

贡献者指南

技术栈
javascriptnodejs
领域
blockchainbackend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Node.jsbasic understanding of EventHub
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
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.