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

WebSocket channel closes after 10 responses #78

Open
SavvyEngineer opened this issue Jan 15, 2023 · 1 comment
Open

WebSocket channel closes after 10 responses #78

SavvyEngineer opened this issue Jan 15, 2023 · 1 comment

Comments

@SavvyEngineer
Copy link

SavvyEngineer commented Jan 15, 2023

the things board Ce version 3.4.3 monolith K8s setup closes the WebSocket channel after 10 responses (no reason, error code 1006)and as the Documents show there isn't any limitations also I tried the linux VM setup and it didn't close is there any limitation in the docker image setup? I also tried adding 0 value for ws env's and it didn't help
my changes to the ConfigMap
apiVersion: v1 kind: ConfigMap metadata: name: tb-node-config namespace: thingsboard labels: name: tb-node-config data: conf: | export TB_SERVER_WS_TENANT_RATE_LIMITS_MAX_SESSIONS_PER_TENANT=0 export TB_SERVER_WS_TENANT_RATE_LIMITS_MAX_SESSIONS_PER_CUSTOMER=0 export TB_SERVER_WS_TENANT_RATE_LIMITS_MAX_SESSIONS_PER_REGULAR_USER=0 export TB_SERVER_WS_TENANT_RATE_LIMITS_MAX_SESSIONS_PER_PUBLIC_USER=0 export TB_SERVER_WS_TENANT_RATE_LIMITS_MAX_QUEUE_PER_WS_SESSION=5000 export TB_SERVER_WS_TENANT_RATE_LIMITS_MAX_SUBSCRIPTIONS_PER_TENANT=0 export TB_SERVER_WS_TENANT_RATE_LIMITS_MAX_SUBSCRIPTIONS_PER_CUSTOMER=0 export TB_SERVER_WS_TENANT_RATE_LIMITS_MAX_SUBSCRIPTIONS_PER_REGULAR_USER=0 export TB_SERVER_WS_TENANT_RATE_LIMITS_MAX_SUBSCRIPTIONS_PER_PUBLIC_USER=0 export TB_SERVER_WS_TENANT_RATE_LIMITS_MAX_UPDATES_PER_SESSION=0

the logs
751.7a70ed70206456d6d163.js:1 WebSocket error event CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: '', type: 'close', …} onError @ 7751.7a70ed70206456d6d163.js:1 (anonymous) @ 7751.7a70ed70206456d6d163.js:1 __tryOrUnsub @ vendor.3f3611f892c51888617d.js:1 error @ vendor.3f3611f892c51888617d.js:1 _error @ vendor.3f3611f892c51888617d.js:1 error @ vendor.3f3611f892c51888617d.js:1 error @ vendor.3f3611f892c51888617d.js:1 j.onclose @ 7751.7a70ed70206456d6d163.js:1 V @ polyfills.775a399a0b5f9321b84c.js:1 invokeTask @ polyfills.775a399a0b5f9321b84c.js:1 onInvokeTask @ vendor.3f3611f892c51888617d.js:1 invokeTask @ polyfills.775a399a0b5f9321b84c.js:1 runTask @ polyfills.775a399a0b5f9321b84c.js:1 invokeTask @ polyfills.775a399a0b5f9321b84c.js:1 at @ polyfills.775a399a0b5f9321b84c.js:1 it @ polyfills.775a399a0b5f9321b84c.js:1 mt @ polyfills.775a399a0b5f9321b84c.js:1 7751.7a70ed70206456d6d163.js:1 WebSocket error event CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: '', type: 'close', …} onError @ 7751.7a70ed70206456d6d163.js:1 (anonymous) @ 7751.7a70ed70206456d6d163.js:1 __tryOrUnsub @ vendor.3f3611f892c51888617d.js:1 error @ vendor.3f3611f892c51888617d.js:1 _error @ vendor.3f3611f892c51888617d.js:1 error @ vendor.3f3611f892c51888617d.js:1 error @ vendor.3f3611f892c51888617d.js:1 j.onclose @ 7751.7a70ed70206456d6d163.js:1 V @ polyfills.775a399a0b5f9321b84c.js:1 invokeTask @ polyfills.775a399a0b5f9321b84c.js:1 onInvokeTask @ vendor.3f3611f892c51888617d.js:1 invokeTask @ polyfills.775a399a0b5f9321b84c.js:1 runTask @ polyfills.775a399a0b5f9321b84c.js:1 invokeTask @ polyfills.775a399a0b5f9321b84c.js:1 at @ polyfills.775a399a0b5f9321b84c.js:1 it @ polyfills.775a399a0b5f9321b84c.js:1 mt @ polyfills.775a399a0b5f9321b84c.js:1

@SavvyEngineer
Copy link
Author

The issue was from the default timeout value of the GCP network load balancer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant