How to increase the XOG instance limit in Clarity?

[mailtojustine]

I am trying to XOG instances of 50 Cost Plans in a single batch file through Gel Script. I am getting "no active session' error after 20 instances have been xogged, but the same xog file is able to process though command prompt without any issues. Can anyone help me on this?

[Legacy User]

Hope you are creating only one session and using the same session to XOG in cost plan instances. Are you preparing only one XOG XML (with 50 instances) or one XOG of one XML at a time? How much time is the XOG in taking when you are doing from command prompt? Also check what is the session timeout in Clarity administration. Usually 50 instances should not be taking long.

 

I usually handle the session in GEL script(only if I am processing batch instances of ~100-200+) by closing the current session and recreating the session in between the batches. Example code snippet below:

v_xogtimeout: I will ensure to configure this parameter value to be less than the session timeout configuration set in Clarity administration.

 <core:forEach begin="${v_header_rows}" indexVar="v_csvRow" items="${v_csv.rows}" step="1" trim="true" var="v_row">
          <gel:parameter var="v_xogtimeout"/>      
          <core:set value="${v_xogtimeout-1}" var="v_xogLogoutinterval"/>
          <core:set value="${v_xogLogoutinterval/v_csvRow}" var="v_xoglogout"/>
          <core:set value="${v_csvRow%v_xogtimeout}" var="v_xoglogin"/>
          <core:if test="${v_xoglogout == 1}">
            <!-- Logout if already logged in -->
            <core:if test="${sessionID != 0 }">
              <gel:log> Logging out now </gel:log>
              <soap:invoke endpoint="${v_XOGURL}/niku/xog" var="logoutresult">
                <soap:message>
                  <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xog="http://www.niku.com/xog">
                    <soapenv:Header>
                      <xog:Auth>
                        <xog:SessionID>${sessionID}</xog:SessionID>
                      </xog:Auth>
                    </soapenv:Header>
                    <soapenv:Body>
                      <xog:Logout/>
                    </soapenv:Body>
                  </soapenv:Envelope>
                </soap:message>
              </soap:invoke>
            </core:if>
          </core:if>
         <core:if test="${v_csvRow == 1 or v_xoglogin == 0}">
            <!-- login here-->
         </core:if>
 </core:forEach>

 

 

Regards

Praneeth

[Deactivated User]

Have a look at turst07 's post

https://communities.ca.com/message/242042113-re-xog-performance-improvement-for-data-migration?commentID=242042113#comme… 

He is the granddaddy of  data transfer and performance.

[mailtojustine]

Thanks for responses. I am using a single XML file to xog all these 50 instances. I don't think it's a performance issue, because the xog in process taking only 1 minute and getting the error "no active session" after xogging 21 instances out of 50.

[Nick Darlington]

What approach are you using to obtain a session ID or are you putting the username/password credentials directly in to your XOG?

 

Which user does it use, one of your own created ones, or an internal one like process_admin? (please don't use this if so)

 

Have you marked the GEL script to perform synchronously or asynchronously?  If asynchronously, can you change it?

 

Do you call the XOG logout service in your process, and is it in the same step/action or another step/action?

 

Do you have any gel scripts (anywhere) on the server that are attempting to 'flush caches' of the service?

 

 

What I'm trying to establish is whether there may be something that is invalidating your session in the BG before the operation could complete.

[mailtojustine]

I am not using Session ID here, instead putting the Xog username/password credentials directly in to my Gel Script. To XOGGING through command prompt also I am using this same user credentials.

[mailtojustine]

I have tried with different user login too. Still getting same issue. "No Active session error" after 21 instances have been xogged.

[Nick Darlington]

Given what you've shared so far, and if you're having that happen with high consistency, I think you're going to need this looked at by product support.  It is good that you checked some of these items over, but unfortunately they're not getting us closer to the reason why the session is getting lost in the bg.

 

Edit: Actually not even lost in the bg, since it's still the app that is performing the XOG and reporting that error, if you're using the regular soap:invoke tag.

[mailtojustine]

Thank you. I am working with Product support on this now.

[RajatAr]

Can you check whether u r looping in the login code or not? Because as per the error message it seems that multiple login session are being created at once without logging out from the previous sessions.

[mailtojustine]

Hi Rajat, we are not using any loop for login.