Uploaded image for project: 'Yell'
  1. Yell
  2. YELL-730

Requests are internally routing to other Queue

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Draft Deployment v1, Extensions
    • Fix Version/s: None
    • Component/s: Other
    • Labels:
      None
    • Environment:

      Environment : YELL1 VM
      Builds
      BidMgr : p10-r2765
      MMS : p1-r3378

      Description

      As Deployment listener dedicate to listen update and deploy Queue of Jboss's. When the deploy and update requests are coming only from Jboss1, Jboss2 is idle then some of the requests are listen by listener which is listening to Jboss2 deploy/update queue and requests are processed by it.

      Following are the step to reproduce.

      Step 1: Both Jboss1 and Jboss2 are up.
      Step 2: Deployment Listener is listening to deploy and update queue.
      Step 3: Send the request for Jboss1 and keep Jboss2 idle.

      Actual Result : Some of the requests are internally routing to other Queue(Requests from Jboss1 queue are listened by deployment listener of Jboss2 deploy/update queue).

      Expected Result : Requests should be listened by respective nodes from deployment listener deploy/update queue and should not route to another Queue.

      Log snippet.

      We have sent 5 Deployment and 5 Update requests from Jboss1 and following is the log snippet, shows after processing the requests. Thread limit is default ie 3.

      2013-06-26 11:58:14.184 (3) [pool-1-thread-1]:
      =======================YELL_VM_JBOSS1--/queue/AdMaxDeployRequestQueue Processor=======================
      /queue/AdMaxDeployRequestQueue-Receptor:ACTIVE:4
      /queue/AdMaxDeployRequestQueue-Responder:ACTIVE:4
      =======================YELL_VM_JBOSS1--/queue/AdMaxDeployRequestQueue Processor=======================
      2013-06-26 11:58:14.184 (3) [pool-1-thread-1]:
      =======================YELL_VM_JBOSS1--/queue/AdMaxUpdateRequestQueue Processor=======================
      /queue/AdMaxUpdateRequestQueue-Receptor:ACTIVE:3
      /queue/AdMaxUpdateRequestQueue-Responder:ACTIVE:3
      =======================YELL_VM_JBOSS1--/queue/AdMaxUpdateRequestQueue Processor=======================
      2013-06-26 11:58:14.184 (3) [pool-1-thread-1]:
      =======================YELL_VM_JBOSS2--/queue/AdMaxDeployRequestQueue Processor=======================
      /queue/AdMaxDeployRequestQueue-Receptor:ACTIVE:1
      /queue/AdMaxDeployRequestQueue-Responder:ACTIVE:1
      =======================YELL_VM_JBOSS2--/queue/AdMaxDeployRequestQueue Processor=======================
      2013-06-26 11:58:14.184 (3) [pool-1-thread-1]:
      =======================YELL_VM_JBOSS2--/queue/AdMaxUpdateRequestQueue Processor=======================
      /queue/AdMaxUpdateRequestQueue-Receptor:ACTIVE:2
      /queue/AdMaxUpdateRequestQueue-Responder:ACTIVE:2
      =======================YELL_VM_JBOSS2--/queue/AdMaxUpdateRequestQueue Processor=======================

      Adding to this

      We have following observations when we set thread limit to 2. We have sent 4 deployment requests from jboss1 and kept jboss2 idle. All 4 requests are picked for process at a time. Ideally only two jobs should pick from jboss1 to process and rest 2 should be in queue(ie., one in internal Queue and another in jboss1 queue).

        Attachments

          Activity

            People

            • Assignee:
              ajay.nagaraj Ajay Nagaraj (Inactive)
              Reporter:
              anil.kumar Anil Kumar Halmadgi
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: