glassfish
  1. glassfish
  2. GLASSFISH-3196

<BT6569431>[NEW-SSL] Increasing SSL Acceptor threads with enabling handshake flag causes unresponsive instance

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 9.1pe
    • Fix Version/s: not determined
    • Component/s: logging
    • Labels:
      None
    • Environment:

      Operating System: Solaris
      Platform: All

    • Issuezilla Id:
      3,196

      Description

      *********READ-ONLY Data from Bugtraq*********************
      Inside SWAN :http://swsblweb1.central.sun.com:8080/CrPrint?id=6569431
      Outside SWAN :http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6569431
      **********READ-ONLY Data from Bugtraq Ends********
      *********READ-ONLY Data from Bugtraq*********************
      Description Build: AS 9.1 PE B50 Application: Richaccess using in-memory replication

      Ran Richaccess with 100 users in SSL Mode after increasing acceptor threads from 1 to 5 for http-listener-2. Also had the following jvm option to monitor the requests.
      <jvm-options>-Djavax.net.debug=ssl,handshake</jvm-options>

      After about 15 mins into the run, saw client failures and webserver logs stated that 2nd instance, ypingsol2 cannot be serviced. When checking this instance manually on browser, it is not accessible and gives the following error:

      Error on Browser:
      ******************

      Data Transfer Interrupted

      The connection to ypingsol2.red.iplanet.com:38181 has terminated unexpectedly. Some data may have been transferred.

      The browser connected successfully, but the connection was interrupted while transferring information. Please try again.

      • Are you unable to browse other sites ? Check the computer's network connection.
      • Still having trouble ? Consult your network administrator or Internal provider for assistance.

      Error in webserver log:
      ***********************

      [13/Jun/2007:11:54:44] failure ( 873): for host 192.18.86.38 trying to GET /richAccess, service-passthrough reports: timed out waiting for response
      [13/Jun/2007:11:54:44] warning ( 873): reports: lb.runtime: ROUT1014: Non-idempotent request /richAccess cannot be retried.
      [13/Jun/2007:11:54:44] info ( 873): reports: lb.runtime: RNTM3003 : Error servicing the request : selected server could not service, server: https://ypingsol2.red.iplanet.com:38181
      [13/Jun/2007:11:56:55] failure ( 873): for host 192.18.86.38 trying to POST /richAccess/Order, service-passthrough reports: timed out waiting for request body
      [13/Jun/2007:11:56:55] failure ( 873): for host 192.18.86.38 trying to POST /richAccess/Order, service-passthrough reports: timed out waiting for response

      This application had run successfully for 3 days when using default acceptor threads of 1 and without the handshake flag enabled.

      I am attaching the jstack of the 2nd instance, ypingsol2 when the instance was not responding.This is attached in this bug report.

      **********READ-ONLY Data from Bugtraq Ends********
      *********READ-ONLY Data from Bugtraq*********************
      Justification Priority changed from [] to [2-High]Customer can encounter similar XXXXXX 2007-06-13 22:52:37 GMT

      **********READ-ONLY Data from Bugtraq Ends********

        Activity

        Hide
        sanandal added a comment -

        "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
        release whose primary release driver is SailFin.
        This issue will be scrubbed after this release and will be given the right
        priority for the next release."

        Show
        sanandal added a comment - "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1 release whose primary release driver is SailFin. This issue will be scrubbed after this release and will be given the right priority for the next release."
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

          People

          • Assignee:
            dpatil
            Reporter:
            gfbugbridge
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: