forever for chat does not manage start/stop of XMPP server
We are using forever to manage chat service. For start up of chat, we use "forever start app.js". app.js internally will start XMPP server.
When chat goes down, for some reason at times XMPP server does not go down (port 5280 of xmpp server will still be listening).
Forever will then try starting app.js. chat will come up on port 443 and it will keep trying to start XMPP server with error "port 5280 already in use"
Can anyone tell me why XMPP does not always go down when chat goes down? and how to make forever manage XMPP server as well?
***Edited by Moderator Marissa to update categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Accenture
AU
We use Forever to start Chat node which in turn starts XMPP server. XMPP process is not directly managed through Forever. When Chat process is stopped, it should in turn manage shutdown of XMPP server, but this is not happening.
We have scripted to kill XMPP process whenever Chat is shutdown
Pegasystems Inc.
US
Hi Sreethi,
I spoke to some of my Subject Matter Experts for our Chat and they have stated that this should be taken to the Forever chat team. Have you reached out to them already?
Thanks!
Pegasystems Inc.
IN
Hi Sreethi,
I'm afraid the response will be the same when you create an SR with Pega Support for your query. Please try working on this with the forever chat team and let us know your findings. That would help us evaluate on next action.
Regards,
Accepted Solution
Accenture
AU
We use Forever to start Chat node which in turn starts XMPP server. XMPP process is not directly managed through Forever. When Chat process is stopped, it should in turn manage shutdown of XMPP server, but this is not happening.
We have scripted to kill XMPP process whenever Chat is shutdown