search cancel

XOG calls return different results when connecting to different servers in our Load Balanced nodes

book

Article ID: 190236

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

We are running 2 On-premise nodes in AWS  and are not using multicast.  Instead we are using JDBCPing to support these clustered instances.
I'm working with this XOG call:

<?xml version='1.0' encoding='UTF-8' ?>
<ns2:Envelope xmlns:ns3="http://www.niku.com/xog/Query" xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/">
 <ns2:Header>
  <Auth>
      <SessionID>55106702__9144082A-B9A4-46F5-83AA-73AC906F155D</SessionID>
  </Auth>
 </ns2:Header>
 <ns2:Body>
  <ns3:Query>
      <ns3:Filter xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="caPpmTaskQueryFilter">
    <ns3:internalid>6967795</ns3:internalid>
      </ns3:Filter>
      <ns3:Slice>
    <ns3:Number>0</ns3:Number>
    <ns3:Size>100</ns3:Size>
      </ns3:Slice>
      <ns3:Sort>
    <ns3:Column>
        <ns3:Name>last_updated_date</ns3:Name>
        <ns3:Direction>desc</ns3:Direction>
    </ns3:Column>
      </ns3:Sort>
      <ns3:Code>Tasktop_SearchTasks</ns3:Code>
  </ns3:Query>
 </ns2:Body>
</ns2:Envelope>


When I run this XOG against one server, I get a single result.
<Records>
            <Record>
               <internalid>6967795</internalid>
               <prexternalid>TA190628</prexternalid>
               <pristask>1</pristask>
               <last_updated_date>2020-04-24T12:53:11</last_updated_date>
               <prname>research</prname>
               <prprojectid>6385684</prprojectid>
            </Record>
         </Records>

When I run a xog call (in Soap UI) against the other server, I get a different result (39 records for the same item)


         <Records>
            <Record>
               <internalid>6967795</internalid>
               <prexternalid>TA190628</prexternalid>
               <pristask>1</pristask>
               <last_updated_date>2020-04-24T12:53:11</last_updated_date>
               <prname>research</prname>
               <prprojectid>6385684</prprojectid>
            </Record>
            <Record>
               <internalid>6967795</internalid>
               <prexternalid>TA190628</prexternalid>
               <pristask>1</pristask>
               <last_updated_date>2020-04-24T12:53:11</last_updated_date>
               <prname>research</prname>
               <prprojectid>6385684</prprojectid>
            </Record>
            <Record>
                          .
                          .
                          .
                          .
                          .
             </Record>
         </Records>
        <Slice>
            <Number>0</Number>
            <Size>39</Size>
            <Total>39</Total>
         </Slice>


Is this expected behavior?
How can we correct it?

Environment

Release : 15.7.1

Component : CA PPM APPLICATION

Resolution

Issue is fixed at the AWS level. They enabled traffic between the servers.