Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Is there a way to not consume 2 threads per-client? #30

Open
svetlyak40wt opened this issue Sep 26, 2022 · 0 comments
Open

Is there a way to not consume 2 threads per-client? #30

svetlyak40wt opened this issue Sep 26, 2022 · 0 comments

Comments

@svetlyak40wt
Copy link
Contributor

I noticed, that each connected client consumes 2 threads. One thread is created by Hunchentoot and other by JSONRPC:

#<SB-THREAD:THREAD "jsonrpc/transport/websocket processing" RUNNING
    {1012704EF3}>
 #<SB-THREAD:THREAD "hunchentoot-worker-127.0.0.1:54832" RUNNING {10124993B3}>

it will relatively easy to do DoS attack on such server by just creating a few thousands connections.

Is there a way to not create new threads or use some thread pool? Or at least to respond to client call and close the connection?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@svetlyak40wt