Uploaded image for project: 'Undertow'
  1. Undertow
  2. UNDERTOW-1180

Undertow is not cleaning up the resources, namely XnioWorker non daemon threads, which prevents JVM from terminating

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.0.0.Beta1, 1.4.21.Final
    • 1.4.15.Final
    • Core
    • None
    • Hide

      Start undetrow server in a programmatic way on some port say (58080).
      Start another instances of undertow server on same port (58080). The server does not start but JVM does not terminate.

      Workaround:
      Call a stop (io.undertow.Undertow#stop) method even if start method fails.

      Show
      Start undetrow server in a programmatic way on some port say (58080). Start another instances of undertow server on same port (58080). The server does not start but JVM does not terminate. Workaround: Call a stop (io.undertow.Undertow#stop) method even if start method fails.

      When undertow server fails to start, for example with port already in use exception, the resources allocated while starting the server are not cleaned up, which prevents JVM from terminating.

      While starting the undertow server (io.undertow.Undertow#start) the xnio worker is started, which starts few non daemon threads. If code fails with some exception after starting the xnio workers, start method throws exception to the caller without cleaning up the worker, this is causing worker to run even when undertow server fails to start.

              sdouglas1@redhat.com Stuart Douglas (Inactive)
              ajinkya_vaze Ajinkya Vaze (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: