Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7688223
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T19:52:14+00:00 2026-05-31T19:52:14+00:00

In an embedded Jetty container I have a servlet which pushes data to the

  • 0

In an embedded Jetty container I have a servlet which pushes data to the clients via long-polling, and I would like to inform the clients when the server is being shut down by sending them a message before their connection is closed. When a client receives this message it is supposed to warn the user and stop making http requests.

Unfortunately, the first thing Jetty does when Server.stop() is called is closing all connectors, so the shutdown message is not sent. The only solution I have found so far is to register a LifeCycle.Listener on the server, which is called back before the connections are closed.

Is there a better way to achieve this? I would have expected the servlet to be informed via a callback of the imminent server shutdown, before the connections were closed.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T19:52:16+00:00Added an answer on May 31, 2026 at 7:52 pm

    I guess what you do is the only way. Looking at the code of Jetty 8.1, calling stop() calls

            try
            {
                if (_state == __STOPPING || _state == __STOPPED)
                    return;
                setStopping();
                doStop();
                setStopped();
            }
            catch (Exception e)
            {
                setFailed(e);
                throw e;
            }
            catch (Error e)
            {
                setFailed(e);
                throw e;
            }
    

    An setStopping() is

    private void setStopping()
    {
        LOG.debug("stopping {}",this);
        _state = __STOPPING;
        for (Listener listener : _listeners)
            listener.lifeCycleStopping(this);
    }
    

    So a registered LifeCycle.Listener is the only thing really called before anything else.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am using an embedded Jetty implementation as my servlet container. Here is a
I would like to serve servlets and static content with jetty embedded in JRuby.
I have a standalone application with embedded Jetty and Wicket. I'd like to use
I have a scenario configuring Spring Security on embedded Jetty which seems to be
I have a (custom) embedded jetty launcher which I had been using to develop/test
I have a spring application that uses an embedded Jetty instance. Since I am
Using Embedded Jetty I am trying to get a very simple servlet to forward
I am using hsqldb and an embedded jetty instance (via) maven for testing locally.
i'm working on a project where i have an embedded jetty server for serving
I would like to use neo4j's embedded db on my web app. Unfortunately I

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.