jerry
I have two different elixir applications on the same server.
One applications sends about 100 http requests per minute to the other application on the same server.
I am, however, experiencing a situation where some of the requests time out and do not get to the other application where they are being sent.
What do I have to do?
Could it be an issue with the number of connections Cowboy2 can accept?
Please help.
Thanks.
Jerry
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
outlog
how long does the requests take to complete(estimated)? cowboy2 has a default timeout of 60 secs - New default timeout of 60s in Cowboy 2 · Issue #3190 · phoenixframework/phoenix · GitHub
else I would think you should look for timeout on the client side? what http client are you using and how is the client config’ed?
jerry
Requests usually take up to one minute to complete.
outlog
follow the link above and config phoenix(cowboy) for a much longer timeout than the default 60 secs
jerry
The links haven’t helped much.
How do I alter the connection parameters of Cowboy to increase the number of connections that can be accepted at a time?
outlog
can you post the log with the timeout? both the client and the server pls..
you have to identify what is timing out.
cowboy can accept plenty of connections so shouldn’t be that.. what is the server doing? anything with the DB? anything that can timeout on it’s own?
jerry
My cowboy configuration is below:
Plug.Adapters.Cowboy2.child_spec(scheme: :http, plug: AppServer.Router, options: [port: port, ip: ip])