Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-366

AJP Connector Threads Hung in CLOSE_WAIT Status

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 4.2.0.GA_CP02
    • 4.2.0.GA, 4.2.0.GA_CP01
    • System
    • None

    • 1) Apache 2.2.3 + mod_jk 1.2.21 on RHEL5 Workstation
      2) JBoss EAP 4.2.0.GA on RHEL4
      3) Both boxes on same subnet
      4) Attached httpd.conf, mod_jk.conf, workers.properties, uriworkermap.properties.

    • Release Notes
    • Workaround Exists
    • Hide

      Use the JbossWeb native component (See http://labs.jboss.com/jbossweb/install/). It provides better performance and it is not affected by the bug.

      Show
      Use the JbossWeb native component (See http://labs.jboss.com/jbossweb/install/ ). It provides better performance and it is not affected by the bug.

    Description

      1) Use out-of-box EAP 4.2.0.GA.
      2) Configure Apache + mod_jk to front JBoss (attached config files).
      3) Start JBoss:
      run.sh -b 192.168.2.12
      4) Run test:
      ab -n 100 -k -c 10 -t 30 http://localhost/jmx-console/

      This produced 5 CLOSE_WAIT ajp connector threads that did not go away.

      Attachments

        1. AjpPatch.patch
          9 kB
        2. httpd.conf
          33 kB
        3. mod_jk.conf
          2 kB
        4. patch.txt
          1 kB
        5. uriworkermap.properties
          0.2 kB
        6. workers.properties
          0.8 kB

        Activity

          People

            Unassigned Unassigned
            rhn-support-mmillson Michael Millson
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: