Fw: NodeJs hung ports

Hi all,


I'm trying to create a simple reverse proxy to front our application servers using this https://www.npmjs.com/package/http-proxy but I'm finding that after I execute it through the QP2TERM shell the port number is still in use after the shell session ends. Netstat shows no jobs or tasks associated with the port, but it does show my user profile as being the associated user. Is there a) a way to prevent this happening, b) a way to forcibly free the ports that appear to be hung?


Many thanksm


Tim.

[https://www.npmjs.com/static/images/touch-icons/open-graph.png]<https://www.npmjs.com/package/http-proxy>

http-proxy - npm<https://www.npmjs.com/package/http-proxy>
www.npmjs.com
node-http-proxy node-http-proxy is an HTTP programmable proxying library that supports websockets. It is suitable for implementing components such as reverse proxies ...