Hi, I’m using the last version, and I this work really great.
But I have a question probably a silly one how can I close the connection and terminate the process with :normal. I’m going to have a pool of clients and this is one of the things that I need. Other thing that I’m doing is handling disconnects inside the client so we reconnect automatically without terminating the process but that’s other thing we want.
Thanks in advance.
Yeah, I thought about this and I couldn’t come up with a good API solution that I liked.
For now, you can use exit(:normal) in the terminate callback.
If you want to open an issue, I will either add documentation or come up with a better solution for the next release.
Hopefully anytime that the process is going to exit for whatever reason.
If there is a time that terminate isn’t called then it is considered a bug.
@Azolo Is there a OS configuration necessary to be able to create 1K websockets connecting to the same Phoenix instance. I am getting this error
(MatchError) no match of right hand side value:
{:error, %WebSockex.ConnError{original: :closed}}
after about 200 processes created with this code
opts = [
{:debug, [:trace]},
{:socket_connect_timeout, Keyword.get(
opts, :socket_connect_timeout, @socket_connect_timeout)},
{:socket_recv_timeout, Keyword.get(
opts, :socket_recv_timeout, @socket_recv_timeout)},
]
WebSockex.start_link(conn_info, __MODULE__, state, [ {:debug, [:trace]} | opts] )
I would guess that is probably an OS file descriptor limit, but other than that I don’t know.
Mt best guess would be to try increasing the maximum file descriptors on the server and client using ulimit -n.
@Azolo thank you for the prompt response… I increased the number of “open files” to 200K but still no luck.
I changed the code to display a specific error in
websockex/websockex/conn.ex
91 @spec socket_send(__MODULE__.t, binary) :: :ok | {:error, reason :: term}
92 def socket_send(conn, message) do
93 case conn.conn_mod.send(conn.socket, message) do
94 :ok -> :ok
95 {:error, error} -> {:error, %WebSockex.ConnError{original: "ERR_A"}}
96 end
97 end
so it looks like this is triggered in a “SEND”.
How would you recommend to debug the
“conn.conn_mod.send(conn.socket, message)” call?
===== Fragment of code which you can test
5 def start(server, users) do
6 all_users = 1..users
7
8 Logger.info("Simulator: registering #{users} users...")
9 all_users
10 |> Enum.map(fn i ->
11 Task.async(fn ->
12 {:ok, client} = WebSockex.start_link("ws://0.0.0.0:4000/socket/websocket", [])
15 end)
16 end)
17 |> Enum.each(&Task.await/1)
Ulimit does only increase the softlimit which can never be higher than the hard limit. The hardlimit needs to be increased first, on most systems you can do so via sysctl AFAIR.
Im in mobile so it’s hard to do a proper check right now.
Hi @Azolo!
I wonder if it’s possible to use WebSockex with subprotocols? I can’t seem to find any mention of it neither in the docs nor in code …
EDIT:
WebSockex.start_link(url, __MODULE__, state, [
name: __MODULE__, extra_headers: [{"Sec-WebSocket-Protocol", "my-protocol"}]
])
seems to work fine.