sailfin
  1. sailfin
  2. SAILFIN-1972

SipApplicationSession creation for an app with SAS key results in a broadcast

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: b31c
    • 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 :31
        Cluster size : 10 instances
        Happens in a single instance (y/n) n/a:
        Test id : st5_1_conference
        Location of the test : as-telco-sqe/stress-ws/conference
        JDK version : 1.6.0_16
        CLB used : Yes
        HW LB used : NO
        SSR enabled : Yes
        **********************************************************************

      Within few minutes of starting the SIP and HTTP traffic for the converged test
      the clients stall. This seems to be caused because the sip container worker
      threads are all doing broadcast to load SAS or DF.

      This is a stack trace taken immediately after starting traffic. The create SAS
      call is incorrectly doing a broadcast while creating a SAS. The application uses
      a SAS key for linking SIP and Http sessions.
      java.lang.Thread.State: TIMED_WAITING (on object monitor)
      at java.lang.Object.wait(Native Method)
      at
      com.sun.enterprise.ee.web.sessmgmt.FederatedRequestProcessor.call(FederatedRequestProcessor.java:122)

      • locked <0x00002aaab0b2ad08> (a
        com.sun.enterprise.ee.web.sessmgmt.FederatedRequestProcessor)
        at
        com.sun.enterprise.ee.web.sessmgmt.FederatedRequestProcessor.doFederatedQuery(FederatedRequestProcessor.java:90)
        at
        com.sun.enterprise.ee.web.sessmgmt.JxtaReplicationSender.sendReplicationStateQuery(JxtaReplicationSender.java:1109)
        at
        com.sun.enterprise.ee.web.sessmgmt.JxtaBackingStoreImpl.findSessionViaBroadcast(JxtaBackingStoreImpl.java:912)
        at
        com.sun.enterprise.ee.web.sessmgmt.JxtaBackingStoreImpl.__load(JxtaBackingStoreImpl.java:195)
        at
        org.jvnet.glassfish.comms.replication.sessmgmt.SipApplicationSessionStoreImpl.findSessionViaBroadcast(SipApplicationSessionStoreImpl.java:333)
        at
        org.jvnet.glassfish.comms.replication.sessmgmt.SipApplicationSessionStoreImpl.findSessionViaBroadcastOrUnicast(SipApplicationSessionStoreImpl.java:298)
        at
        org.jvnet.glassfish.comms.replication.sessmgmt.SipApplicationSessionStoreImpl.__load(SipApplicationSessionStoreImpl.java:262)
        at
        org.jvnet.glassfish.comms.replication.sessmgmt.SipTransactionPersistentManager.__load(SipTransactionPersistentManager.java:4855)
        at
        com.sun.enterprise.ee.web.sessmgmt.JxtaBackingStoreImpl.load(JxtaBackingStoreImpl.java:180)
        at
        com.sun.enterprise.ee.web.sessmgmt.JxtaBackingStoreImpl.load(JxtaBackingStoreImpl.java:69)
        at
        org.jvnet.glassfish.comms.replication.sessmgmt.SipApplicationSessionStoreImpl.loadFromBackingStore(SipApplicationSessionStoreImpl.java:192)
        at
        org.jvnet.glassfish.comms.replication.sessmgmt.SipApplicationSessionStoreImpl.load(SipApplicationSessionStoreImpl.java:155)
        at
        org.jvnet.glassfish.comms.replication.sessmgmt.SipApplicationSessionStoreImpl.load(SipApplicationSessionStoreImpl.java:120)
        at
        org.jvnet.glassfish.comms.replication.sessmgmt.SipTransactionPersistentManager.swapInSipApplicationSession(SipTransactionPersistentManager.java:4976)
        at
        org.jvnet.glassfish.comms.replication.sessmgmt.SipTransactionPersistentManager.swapInSipApplicationSession(SipTransactionPersistentManager.java:4930)
        at
        org.jvnet.glassfish.comms.replication.sessmgmt.SipTransactionPersistentManager.swapInSipApplicationSession(SipTransactionPersistentManager.java:4905)
        at
        com.ericsson.ssa.sip.PersistentSipSessionManagerBase.findSipApplicationSession(PersistentSipSessionManagerBase.java:243)
        at
        com.ericsson.ssa.sip.PersistentSipSessionManagerBase.findSipApplicationSession(PersistentSipSessionManagerBase.java:210)
        at
        com.ericsson.ssa.config.SipFactoryFacade.extractSasFromBekeyAndSak(SipFactoryFacade.java:362)
        at
        com.ericsson.ssa.config.SipFactoryFacade.createApplicationSession(SipFactoryFacade.java:274)
        at
        com.ericsson.ssa.container.sim.ServletDispatcher.invoke(ServletDispatcher.java:260)
        at
        com.ericsson.ssa.container.sim.ApplicationDispatcher.invokeServletDispatchers(ApplicationDispatcher.java:365)
        at
        com.ericsson.ssa.container.sim.ApplicationDispatcher.dispatch(ApplicationDispatcher.java:174)
        at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:53)
        at
        com.ericsson.ssa.container.sim.ApplicationDispatcher.next(ApplicationDispatcher.java:697)
        at com.ericsson.ssa.sip.LayerHelper.next(LayerHelper.java:60)

      1597,9 57%

        Issue Links

          Activity

          Hide
          sonymanuel added a comment -

          Created an attachment (id=1112)
          instance104 jstack out

          Show
          sonymanuel added a comment - Created an attachment (id=1112) instance104 jstack out
          Hide
          Mahesh Kannan added a comment -

          Assigning to Bhavani as he is working on the Conference app

          Show
          Mahesh Kannan added a comment - Assigning to Bhavani as he is working on the Conference app
          Hide
          sonymanuel added a comment -

          Because of this issue we are unable to verify the fix for 1953.

          Show
          sonymanuel added a comment - Because of this issue we are unable to verify the fix for 1953.
          Hide
          Bhavanishankar added a comment -

          workaround for this issue to restart the cluster after deploying the application.

          The fix is in progress.

          Show
          Bhavanishankar added a comment - workaround for this issue to restart the cluster after deploying the application. The fix is in progress.
          Hide
          Bhavanishankar added a comment -

          Fix is available (being reviewed) at http://fisheye5.atlassian.com/cru/SFIN-137

          Show
          Bhavanishankar added a comment - Fix is available (being reviewed) at http://fisheye5.atlassian.com/cru/SFIN-137
          Hide
          varunrupela added a comment -

          updated keyword

          Show
          varunrupela added a comment - updated keyword
          Hide
          Bhavanishankar added a comment -
          Show
          Bhavanishankar added a comment - Fixed. Check-in to SJSAS91_FCS_BRANCH https://glassfish.dev.java.net/servlets/ReadMsg?list=cvs&msgNo=31251 Check-in to SGES211_FCS_BRANCH: https://glassfish.dev.java.net/servlets/ReadMsg?list=cvs&msgNo=31252

            People

            • Assignee:
              Bhavanishankar
              Reporter:
              sonymanuel
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: