glassfish
  1. glassfish
  2. GLASSFISH-18117

[Red Hat]Number of connections appear in TIME_WAIT state when accessing console.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1.2_b16
    • Component/s: admin_gui
    • Labels:
      None
    • Environment:

      RHEL 5

      Description

      Reproducible on RedHat Linux, Glassfish 3.1.2, build 16. Access console pages and then run netstat -a | grep appserv. A number of open connections are listed in TIME_WAIT for a short time. These are then released, after waiting for short time - I observed a minute or less.

      Related to http://java.net/jira/browse/GLASSFISH-16672. That issue was fixed. bthalmayr ran into issues running console on RedHat.

        Activity

        Hide
        Anissa Lam added a comment -

        In GLASSFISH-16672, bthalmayr reopened the bug with the following comment:

        >>>>>
        bthalmayr added a comment - 07/Nov/11 11:09 AM
        Can you please reopen this bug again?

        I'm still seeing it in 'GlassFish Server Open Source Edition 3.1.1 (build 12)' on RHEL 6.

        It's also seen when clicking on 'resource configurations' etc.

        No click within console for some time

        netstat -a | grep -c appserv
        1
        Click within console on 'resources -> connectors -> connector-resources -> resources'

        netstat -a | grep -c appserv
        172
        Exception from Log..

        [#|2011-11-07T12:09:14.291+0100|WARNING|glassfish3.1.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=11609;_ThreadName=Thread-2;|StandardWrapperValve[FacesServlet]: PWC1406: Servlet.service() for servlet FacesServlet threw exception
        java.lang.RuntimeException: java.lang.RuntimeException while attempting to process a 'beforeCreate' event for 'propertyContentPage'.
        at com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:422)
        at com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:394)
        at com.sun.jsftemplating.layout.descriptors.LayoutComponent.beforeCreate(LayoutComponent.java:348)
        ...
        ...
        >>>>>

        I have just tried this on a Linux machine,
        Linux liz-vm4 2.6.18-128.el5xen #1 SMP Wed Dec 17 12:22:24 EST 2008 i686 i686 i386 GNU/Linux
        GlassFish 3.1.2 promoted b16
        JDK 1.6.0_30.

        I monitored the netstat output, and saw the behavior that Siraj mentioned. However, there is no exception like bthalmayr mentioned, the # of open connections is very reasonable even at the peak when i click around the console, create password alias, create cluster, start cluster, look at instance information etc.
        The most that get created is 12, and after less than a min, went back down to 1.
        Here is what i saw:

        -bash-3.2$ date; netstat -a |grep -c appserv
        Sun Jan 8 18:56:08 PST 2012
        1
        -bash-3.2$ date; netstat -a |grep -c appserv
        Sun Jan 8 18:56:51 PST 2012
        12
        -bash-3.2$ date; netstat -a |grep appserv
        Sun Jan 8 18:57:00 PST 2012
        tcp 0 0 rhel5.3-32-vm:53602 rhel5.3-32-vm:appserv-http ESTABLISHED
        tcp 0 0 rhel5.3-32-vm:53601 rhel5.3-32-vm:appserv-http ESTABLISHED
        tcp 0 0 rhel5.3-32-vm:53600 rhel5.3-32-vm:appserv-http ESTABLISHED
        tcp 0 0 rhel5.3-32-vm:53597 rhel5.3-32-vm:appserv-http ESTABLISHED
        tcp 0 0 :appserv-http *: LISTEN
        tcp 0 0 rhel5.3-32-vm:53617 rhel5.3-32-vm:appserv-http TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:53598 rhel5.3-32-vm:appserv-http TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53597 ESTABLISHED
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53602 ESTABLISHED
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53600 ESTABLISHED
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53601 ESTABLISHED
        -bash-3.2$ date; netstat -a |grep -c appserv
        Sun Jan 8 18:57:03 PST 2012
        11
        -bash-3.2$ date; netstat -a |grep appserv
        Sun Jan 8 18:57:19 PST 2012
        tcp 1 0 rhel5.3-32-vm:53602 rhel5.3-32-vm:appserv-http CLOSE_WAIT
        tcp 1 0 rhel5.3-32-vm:53601 rhel5.3-32-vm:appserv-http CLOSE_WAIT
        tcp 1 0 rhel5.3-32-vm:53600 rhel5.3-32-vm:appserv-http CLOSE_WAIT
        tcp 1 0 rhel5.3-32-vm:53597 rhel5.3-32-vm:appserv-http CLOSE_WAIT
        tcp 0 0 :appserv-http *: LISTEN
        tcp 0 0 rhel5.3-32-vm:53617 rhel5.3-32-vm:appserv-http TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:53598 rhel5.3-32-vm:appserv-http TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53597 FIN_WAIT2
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53602 FIN_WAIT2
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53600 FIN_WAIT2
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53601 FIN_WAIT2
        -bash-3.2$ date; netstat -a |grep appserv
        Sun Jan 8 18:57:33 PST 2012
        tcp 0 0 :appserv-http *: LISTEN
        tcp 0 0 rhel5.3-32-vm:53617 rhel5.3-32-vm:appserv-http TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:53598 rhel5.3-32-vm:appserv-http TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53597 TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53602 TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53600 TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53601 TIME_WAIT
        -bash-3.2$ date; netstat -a | grep appserv
        Sun Jan 8 18:57:50 PST 2012
        tcp 0 0 :appserv-http *: LISTEN
        tcp 0 0 rhel5.3-32-vm:53617 rhel5.3-32-vm:appserv-http TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53597 TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53602 TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53600 TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53601 TIME_WAIT
        -bash-3.2$ date; netstat -a | grep appserv
        Sun Jan 8 18:58:17 PST 2012
        tcp 0 0 :appserv-http *: LISTEN
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53597 TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53602 TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53600 TIME_WAIT
        tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53601 TIME_WAIT
        -bash-3.2$ date; netstat -a | grep appserv
        Sun Jan 8 19:00:41 PST 2012
        tcp 0 0 :appserv-http *: LISTEN
        -bash-3.2$ date; netstat -a |grep -c appserv
        Sun Jan 8 19:01:03 PST 2012
        1

        So, the issues that bthalmayr reported for re-open that bug

        • # of open connection being 172
        • exception thrown when going to 'resources -> connectors -> connector-resources -> resources' cannot be reproduced on 3.1.2 b16.

        I am closing this issue. If bthalmayr still sees this with 3.1.2 latest promoted build, please reopen.

        Show
        Anissa Lam added a comment - In GLASSFISH-16672 , bthalmayr reopened the bug with the following comment: >>>>> bthalmayr added a comment - 07/Nov/11 11:09 AM Can you please reopen this bug again? I'm still seeing it in 'GlassFish Server Open Source Edition 3.1.1 (build 12)' on RHEL 6. It's also seen when clicking on 'resource configurations' etc. No click within console for some time netstat -a | grep -c appserv 1 Click within console on 'resources -> connectors -> connector-resources -> resources' netstat -a | grep -c appserv 172 Exception from Log.. [#|2011-11-07T12:09:14.291+0100|WARNING|glassfish3.1.1|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=11609;_ThreadName=Thread-2;|StandardWrapperValve [FacesServlet] : PWC1406: Servlet.service() for servlet FacesServlet threw exception java.lang.RuntimeException: java.lang.RuntimeException while attempting to process a 'beforeCreate' event for 'propertyContentPage'. at com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:422) at com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:394) at com.sun.jsftemplating.layout.descriptors.LayoutComponent.beforeCreate(LayoutComponent.java:348) ... ... >>>>> I have just tried this on a Linux machine, Linux liz-vm4 2.6.18-128.el5xen #1 SMP Wed Dec 17 12:22:24 EST 2008 i686 i686 i386 GNU/Linux GlassFish 3.1.2 promoted b16 JDK 1.6.0_30. I monitored the netstat output, and saw the behavior that Siraj mentioned. However, there is no exception like bthalmayr mentioned, the # of open connections is very reasonable even at the peak when i click around the console, create password alias, create cluster, start cluster, look at instance information etc. The most that get created is 12, and after less than a min, went back down to 1. Here is what i saw: -bash-3.2$ date; netstat -a |grep -c appserv Sun Jan 8 18:56:08 PST 2012 1 -bash-3.2$ date; netstat -a |grep -c appserv Sun Jan 8 18:56:51 PST 2012 12 -bash-3.2$ date; netstat -a |grep appserv Sun Jan 8 18:57:00 PST 2012 tcp 0 0 rhel5.3-32-vm:53602 rhel5.3-32-vm:appserv-http ESTABLISHED tcp 0 0 rhel5.3-32-vm:53601 rhel5.3-32-vm:appserv-http ESTABLISHED tcp 0 0 rhel5.3-32-vm:53600 rhel5.3-32-vm:appserv-http ESTABLISHED tcp 0 0 rhel5.3-32-vm:53597 rhel5.3-32-vm:appserv-http ESTABLISHED tcp 0 0 :appserv-http *: LISTEN tcp 0 0 rhel5.3-32-vm:53617 rhel5.3-32-vm:appserv-http TIME_WAIT tcp 0 0 rhel5.3-32-vm:53598 rhel5.3-32-vm:appserv-http TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53597 ESTABLISHED tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53602 ESTABLISHED tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53600 ESTABLISHED tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53601 ESTABLISHED -bash-3.2$ date; netstat -a |grep -c appserv Sun Jan 8 18:57:03 PST 2012 11 -bash-3.2$ date; netstat -a |grep appserv Sun Jan 8 18:57:19 PST 2012 tcp 1 0 rhel5.3-32-vm:53602 rhel5.3-32-vm:appserv-http CLOSE_WAIT tcp 1 0 rhel5.3-32-vm:53601 rhel5.3-32-vm:appserv-http CLOSE_WAIT tcp 1 0 rhel5.3-32-vm:53600 rhel5.3-32-vm:appserv-http CLOSE_WAIT tcp 1 0 rhel5.3-32-vm:53597 rhel5.3-32-vm:appserv-http CLOSE_WAIT tcp 0 0 :appserv-http *: LISTEN tcp 0 0 rhel5.3-32-vm:53617 rhel5.3-32-vm:appserv-http TIME_WAIT tcp 0 0 rhel5.3-32-vm:53598 rhel5.3-32-vm:appserv-http TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53597 FIN_WAIT2 tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53602 FIN_WAIT2 tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53600 FIN_WAIT2 tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53601 FIN_WAIT2 -bash-3.2$ date; netstat -a |grep appserv Sun Jan 8 18:57:33 PST 2012 tcp 0 0 :appserv-http *: LISTEN tcp 0 0 rhel5.3-32-vm:53617 rhel5.3-32-vm:appserv-http TIME_WAIT tcp 0 0 rhel5.3-32-vm:53598 rhel5.3-32-vm:appserv-http TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53597 TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53602 TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53600 TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53601 TIME_WAIT -bash-3.2$ date; netstat -a | grep appserv Sun Jan 8 18:57:50 PST 2012 tcp 0 0 :appserv-http *: LISTEN tcp 0 0 rhel5.3-32-vm:53617 rhel5.3-32-vm:appserv-http TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53597 TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53602 TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53600 TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53601 TIME_WAIT -bash-3.2$ date; netstat -a | grep appserv Sun Jan 8 18:58:17 PST 2012 tcp 0 0 :appserv-http *: LISTEN tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53597 TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53602 TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53600 TIME_WAIT tcp 0 0 rhel5.3-32-vm:appserv-http rhel5.3-32-vm:53601 TIME_WAIT -bash-3.2$ date; netstat -a | grep appserv Sun Jan 8 19:00:41 PST 2012 tcp 0 0 :appserv-http *: LISTEN -bash-3.2$ date; netstat -a |grep -c appserv Sun Jan 8 19:01:03 PST 2012 1 So, the issues that bthalmayr reported for re-open that bug # of open connection being 172 exception thrown when going to 'resources -> connectors -> connector-resources -> resources' cannot be reproduced on 3.1.2 b16. I am closing this issue. If bthalmayr still sees this with 3.1.2 latest promoted build, please reopen.

          People

          • Assignee:
            Anissa Lam
            Reporter:
            sirajg
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: