fix(backend-server): notification(non localhost) connect failed #1500
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…) connect fail if the backend-server connects to the address configured in SOCKET_URL, which is not the local process address, in the absence of transports configuration, the connection fails and the notification cannot be sent over the ws connection.
|
|
ChambersChan
changed the title
|
It is recommended not to add configured default values. Modify the transports attribute only when the configuration is not empty. This also does not affect the default initialization. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix backend-server connect to SOCKET_URL(non localhost address) failed without transports configured
Why?
When I deployed room-server in my test environment, I found that the connection from local backend-server to notification is false, which means that the ws connection is failing
After troubleshooting, I found that I need to add the following configuration for the connection to succeed
What?
If the backend-server connects to the local room-server, the connection succeeds with or without transports.
If the backend-server connects to a non-local room-server, you need to add a transports configuration for the connection to succeed.
So in order to connect successfully, the transports configuration is added.
How?
add
starter.socketio.client.transports=websocketin application.ymladd
private List<String> transports = Collections.singletonList("websocket");and getter/setter incom.apitable.starter.socketio.autoconfigure.SocketioProperties.Clientadd
options.transports= client.getTransports().toArray(new String[0]);incom.apitable.starter.socketio.autoconfigure.SocketioAutoConfiguration#createInstance