Fibers strategy doesn't work for embeddedHttpServer
See original GitHub issueThe simple http server code given in the example:
Stereotypes.def.embeddedHttpServer(8080, new Stereotypes.HttpStringWorker("/", ex -> "Hello world!"));
works, but if I change def
to fibers
, it doesn’t work. The client connects, but no response is received from the server.
Tested on latest loom EA build: 16-loom+4-56
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
lucav76/Fibry: The first Java Actor System supporting fibers ...
Fibry is the first Java Actor System using fibers (now called Virtual Threads) from Project Loom, however it also works with threads using...
Read more >Project Loom: Java With a Stronger Fiber - DZone
Project Loom introduces continuations (co-routines) and fibers (a type of green threads), allowing you to choose between threads and fibers.
Read more >What is a good strategy to queue incoming queries (posting to ...
Yes, I am running them on the same database, and you are right in your above comment that I want to run them...
Read more >Practical network security: experiences with ntop - ScienceDirect
Ntop is an open-source web-based traffic measurement and monitoring ... This means that they do not provide network/subnet detection/protection nor do they ...
Read more >EMC NetWorker Administration Guide - Dell
The EMC NetWorker Data Domain Boost Integration Guide provides detailed information about setting up DD Boost deduplication devices to work ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the fix! Will try it out later.
Just another request: can you please create a release on Github whenever a new version is tagged? Those who are “watching for releases” will get a notification automatically from Github.
Now the version on GitHub should work. As soon as I can I will publish version 2.2 on Maven Central. Thank you again for submitting the bug.