alexsysm

alexsysm

controller

  def process_test(conn, _) do
    Plug.Conn.configure_session(conn, renew: true)
    Logger.debug("Controler Process : #{inspect self()}")

    make_monitor_process()

    # IO.inspect conn
    Process.sleep(10_000)

    text conn, "#{inspect self()} : Done"
  end

  def make_monitor_process do
    target_pid = self()

    spawn(fn ->
      Logger.debug("Monitor Process : #{inspect self()} , target : #{inspect target_pid}")
      Process.flag(:trap_exit, true)
      Process.link(target_pid)

      receive do
        msg -> Logger.debug("Received : #{inspect msg}")
      end
    end)
  end

open your browser and put “localhost:4000/test” on address box and push enter key,
and then refresh your browser before 10 seconds. (just refresh as soon as push enter key)

you’ll see below.

iex(5)> [info] GET /test
[debug] Processing with TestWeb.PageController.process_test/2
  Parameters: %{}
  Pipelines: [:browser, :not_authenticated]
[debug] Controler Process : #PID<0.1335.0>
[debug] Monitor Process : #PID<0.1345.0> , target : #PID<0.1335.0>

*> [debug] Received : {:EXIT, #PID<0.1335.0>, :shutdown}*

[info] GET /test
[debug] Processing with TestWeb.PageController.process_test/2
  Parameters: %{}
  Pipelines: [:browser, :not_authenticated]
[debug] Controler Process : #PID<0.1347.0>
[debug] Monitor Process : #PID<0.1357.0> , target : #PID<0.1347.0>
[info] Sent 200 in 10004ms

I am guessing that cowboy killed previous request process
whenever it receives next request before sending response for first one.

my question is that where I can find cowbow or something else’s source
that affect killing process I mentioned above?

and is there any ways to config that kind of thing like waiting for processing request instead of killing it?

Thanks.

Showing Posts 1 to 4

cmo

cmo

What is it that you want to continue doing and why do you want to keep doing it once the connection has been closed? Where’s the result of this supposed to end up?

alexsysm

alexsysm OP

I just want to know how it works and who makes it get killed.

Received : {:EXIT, #PID<0.1335.0>, :shutdown}*

I think it’s sophisticated way that killing unfinished process just after receiving new process.
and wanna know the drills

LostKobrakai

LostKobrakai

There’s no previous/next process to cowboy – it just deals with requests one at a time. If a request is closed by the client (when you hit reload, the active request is closed) the process handling that request will be shut down. There’s noone to receive a response to the request anymore anyways. This happens completely independant to any other request cowboy might be handling.

You can probably see this by closing your browser instead of hitting reload. This should close the active request and not start a new one.

alexsysm

alexsysm OP

Thanks @LostKobrakai.

I get that cowboy kill current request process when the connection between browser and cowboy has been destroyed.

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

Latest on Elixir Forum

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews