Hi everybody, I ran into a problem where my Dropwizard based application can't create any more native threads (java.lang.OutOfMemoryError: unable to create new native thread), however there's apparently still enough memory to keep the application running. This causes all subsequent requests to hang, making the app unusable. At the same time requests to the admin port are handled correctly, since admin connectors use a separate thread pool ( https://github.com/dropwizard/dropwizard/blob/master/dropwizard-core/src/main/java/io/dropwizard/server/DefaultServerFactory.java#L215).
My problem is that I'm not sure how to detect this kind of situation. Ideally I'd like to have a healthcheck for that, but it seems that the state of the server/connectors is still set to "STARTED" after the error occurs. Another solution would be to use the same thread pool for app and admin connectors, since I don't know the original rationale of separating them. Has anyone here had a problem like this? Any sugesstions? Thanks -- 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.
