Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CometD Angular - How to reduce meta/connect requests interval on production #874

Open
ddouras opened this issue Sep 3, 2019 · 7 comments

Comments

@sbordet

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

@ddouras you have to explain in more details what's the difference between your local runs and production.

If the server is continuously streaming events to your client, then the behavior is normal.

@ddouras

This comment has been minimized.

Copy link
Author

commented Sep 3, 2019

@sbordet sorry I have to rephrase. Is there any configuration variable or other way to increase the polling interval that cometd uses for the subscription channels (i.e salesforce channel)?

@sbordet

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

@ddouras CometD does not "poll", it "long polls".
The server is configured with the long poll timeout, so there is little you can do from the client.

I think you are looking at this problem in the wrong way: you think the problem is the poll interval, but it's likely something entirely different, such as many messages delivered from the server onto the channels you subscribe.

It would help if you take the client side DEBUG logs and see what's going on.

@ddouras

This comment has been minimized.

Copy link
Author

commented Sep 3, 2019

The polling request that happens almost every second is the meta/connect one. This is sent form client to server and I have no messages form server to client

@sbordet

This comment has been minimized.

Copy link
Member

commented Sep 3, 2019

@ddouras I need evidence. Attach the DEBUG logs to this issue.

@ddouras

This comment has been minimized.

Copy link
Author

commented Sep 3, 2019

image

here's a snapshot from my production app. When I run on production message advice is set to 2000ms but locally it is set 0 for some reason

@sbordet

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.