sailfin
  1. sailfin
  2. SAILFIN-1869

Subscribe-refresh, an instance was killed, were created a lot of errors, communication stopped.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: milestone 1
    • Component/s: session_replication
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

      Description

      ********************************************************************************
      **********************

      • Template v0.1 ( 05/01/08 )
      • Sailfin Stress test issue
        ********************************************************************************
        **********************
        Sailfin Build : 23
        Cluster size : 10
        Happens in a single instance (y/n) ? : NA
        Test id : st2_4_presence_subscribe-refresh
        Location of the test : as-telco-sqe/stress-ws/presence
        JDK version : 1.6.0_14, 64 bits
        CLB used : Yes
        HW LB used : No.
        SSR: Enabled
        =========================================================

      SuSe machines (asqe-oblade-{1-10].sfbay.sun.com), one instance per a machine,
      Were running 9 sipp.

      The loading was -m 333333 -r 305 per one sipp (9 sipp sessions totally).

      The run was fine during about 4 hours, until one instance (instance4) was
      killed.

      Then countless number of error messages were created in server.log files:

      ==============================================================
      SEVERE|sun-glassfish-comms-
      server2.0|javax.enterprise.system.container.sip|_ThreadID=22;_ThreadName=SipCont
      ainer-serversWorkerThread-5060-6;_RequestID=d13298fe-d6ae-483b-9e29-
      37caa9caf17c;|"Cant find matching transaction - Terminating"|#]

      WARNING|sun-glassfish-comms-
      server2.0|javax.enterprise.system.container.sip|_ThreadID=34;_ThreadName=Thread-
      39;_RequestID=d1046b7e-5ae4-48f6-a16f-938f2aa8a336;|Transaction was null:
      z9hG4bKd57df8d052efe87b4fd69d3553337d242ea5|#]
      ================================================================

      Finally, after several hours of such error messages in server.log files, the
      sipp communication stopped. On sipp screens after the instance was killed I saw
      around 300000 errors per a screen.

      Please see the logs from this run at /net/asqe-
      logs/export1/SailFin/Results/sfbuild23/sbrf.

        Issue Links

          Activity

          easarina created issue -
          kenaiadmin made changes -
          Field Original Value New Value
          issue.field.bugzillaimportkey 1869 19121
          made changes -
          Link This issue depends on SAILFIN-1877 [ SAILFIN-1877 ]

            People

            • Assignee:
              Joe Fialli
              Reporter:
              easarina
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: