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

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
roeland
Kia ora, We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
rahultumpala
Hello, I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance 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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
mcass19
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews