Why is My WSO2 API Manager Constantly Reaching out to an Endpoint on port 9099 when we don't have a websocket API published?

Asked Aug 18 '21 at 16:19

Active Oct 06 '21 at 20:23

Viewed 152 times

As the title suggests, I have an API Manager that is unsuccessfully reaching out on port 9099 multiple times per second and filling up the wso2carbon.log (as seen below)

I do not have any websocket APIs published so I'm unsure what endpoint it's looking for. We tried commenting out the ws_endpoint in the apim.gateway.environment block of the deployment.toml but that did not produce any perceptible changes. Any help would be greatly appreciated.

UPDATE: I have noticed whenever I shut down API manager, this stack trace below appears. It is failing to destroy this Inbound endpoint, and then tries to recreate it after the service starts, but says it already exists (so any changes on the websocket endpoint configs do nothing)

edited Oct 06 '21 at 20:23

asked Aug 18 '21 at 16:19

BB97

what is the version of APIM? – Pubci Aug 18 '21 at 16:51
Version is 3.1.0 @Pubci – BB97 Aug 18 '21 at 17:07
If you don't have any websocket API, you can remove the files in repository/deployment/server/synapse-configs/default/inbound-endpoints location – Pubci Aug 19 '21 at 04:37
Better to take a backup when removing the files – Pubci Aug 19 '21 at 04:38
Is there any health check configured for the websocket port? – Pubci Aug 19 '21 at 04:41
If the requests are coming to websocket port, you can get these log lines – Pubci Aug 19 '21 at 04:42
I took backups of those files so I'll have to see how that affects it the next time I am able to restart the wso2 service. You'll have to forgive me, which cmd are you referring to to check the logs on the port? – BB97 Aug 19 '21 at 14:56

Why is My WSO2 API Manager Constantly Reaching out to an Endpoint on port 9099 when we don't have a websocket API published?

0 Answers0