ws2s: connection type is null (#638)

Eric Dziewa opened 9 years ago

Trying to configure unencrypted websocket port 444, the encrypted socket is fine.

--debug=server
ws2s/connections/ports[i]=444,443
ws2s/connections/443/socket=ssl
ws2s/connections/443/type=accept

2016-02-05 17:19:31.448 [main]             ConnectionManager.reconnectService()  FINER: Reconnecting service for: ws2s, scheduling next try in 2secs, cid: null@null, props: {port-no=444}
2016-02-05 17:19:33.448 [scheduler_pool-18-thread-1-ws2s]  ConnectionManager$1.run()  FINE: Reconnecting service for component: ws2s, to remote host: null on port: 444
2016-02-05 17:19:33.453 [scheduler_pool-18-thread-1-ws2s]  ConnectionManager$ConnectionListenerImpl.getConnectionType()  WARNING: ws2s: connection type is null: 444

Port 444 never gets bound. Nothing else is using the port.

Activities

Andrzej Wójcik (Tigase) commented 9 years ago
Eric, add following lines:

ws2s/connections/444/socket=plain ws2s/connections/444/type=accept

This will configure server to use port 444 as plain (not encrypted) and with type set to @accept@, so it will listen for incoming connections.

This is required as there is no default configuration for ports which are not default ports.
Eric Dziewa commented 9 years ago

Thanks Andrzej.

Daniel can you update the documentation for this?

http://docs.tigase.org/tigase-server/7.0.0/Administration_Guide/html_chunk/_websocket.html

http://docs.tigase.org/tigase-server/7.0.0/Administration_Guide/webhelp/_tip_1_encrypted_websocket_connection.html
Daniel Wisnewski commented 9 years ago

Edits made in 1be6921
Login to comment

Type	Bug
Priority	Normal
Assignee	Daniel Wisnewski
RedmineID	3915
Spent time	0

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#638