Friday 9 June 2017

NodeJS / sockjs client - app starts new process of itself

i'm running two nodeJS applications (appA and appB) on a Linux VM. Both applications create their own websocket connection to a server. Both are using the sockjs module. While appA is running as it is supposed to, the other one (appB) creates new processes of itself (visible via: ps aux | grep node). The strange thing is, that the new processes of appB are not owned by my normal user but by root.

Do you have an idea why the appB creates new processes of itself or do you have an idea how i'm able to debug it?

Thanks and Best wishes, BiG



via BiG

No comments:

Post a Comment