Hi Steve; I'll look into the ChunkedOutput approach; though this is not what we need right now it might come in useful in other situations.
As far as the parallel requests are concerned: Am Donnerstag, den 20.07.2017, 14:36 -0700 schrieb Steve Kradel: > > It sounds like something outside of the test resource+method shown is > blocking the requests. Maybe the filter itself? What does the > bootstrap config (YAML) look like--perhaps some nonstandard options > appeared while grappling with inherently slow requests? > Well I am slowly running out of ideas by now. So far I broke it down to disable virtually everything specific to our application in both bootstrap code and YAML and still the behaviour is all the same. Log snippet (root level set to DEBUG) is here: https://pastebin.com/ZMBxfzmt There seems only one thread (dw-19) dealing with both requests, and indeed the "second" requests seems to even be accepted by the server only after the first one finished; I don't see it hanging around elsewhere in the server before. Any other ideas? :| We're on Dropwizard 1.0.5 but changing to 1.1.2 didn't help either so at least it's not version-specific... TIA and all the best, Kristian -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
