AnsweredAssumed Answered

Error in Web Service Call for Create Change Request

Question asked by Sirisha Bomma on Oct 5, 2018
Latest reply on Jun 10, 2019 by Sirisha Bomma

Like • Show 0 Likes0
Comment • 9

When making a WebService call from workflow using a correct XML the below error is see in UI. The error does not happen all the times but sometimes. The webservice is called inside a loop from a workflowIGL version 702 P07

Error in Workflow UI - Error History:

<?xml version="1.0" encoding="UTF-8"?><createChangeRequest><Request type="fulfillment"/></createChangeRequest>

The XML sent is:

<Changes><Notes>Bulk Account Processing</Notes><AccountChange><Operation>Create</Operation><User>112233</User><BusinessSource>NA.ABC.COM</BusinessSource><Parameters><Parameter><Name>ACC_TYPE</Name><Value>CreateGeneric</Value></Parameter><Parameter><Name>ACCOUNT_NAME</Name><Value>sbthrgen</Value></Parameter><Parameter><Name>STR1</Name><Value>OU=Users,OU=ABC,OU=AM,DC=na,DC=abc,DC=com</Value></Parameter><Parameter><Name>STR2</Name><Value>CN=Domain Users,CN=Users,DC=na,DC=abc,DC=com</Value></Parameter><Parameter><Name>NUM1</Name><Value></Value></Parameter><Parameter><Name>NUM2</Name><Value></Value></Parameter></Parameters></AccountChange></Changes>

Below is the error seen in log:

10/05/2018 13:49:01.057 INFO (Worker_actionq#Script Queue - Normal#WPDS_40) [com.aveksa.server.workflow.scripts.nodes.RESTWebServic
eNode] Starting of REST Web Service Request.
10/05/2018 13:49:01.520 ERROR (default task-63) [com.aveksa.server.command.CreateChangeRequestCommand] Error updating the change item with account template data
10/05/2018 13:49:01.520 ERROR (default task-63) [com.aveksa.server.command.CreateChangeRequestCommand] Error creating document for '
createChangeRequest'.
java.lang.NullPointerException
at com.aveksa.server.core.account.IllegalAccountNameException.getMessage(IllegalAccountNameException.java:70)
at java.lang.Throwable.getLocalizedMessage(Throwable.java:391)
at java.lang.Throwable.toString(Throwable.java:480)
at org.apache.log4j.spi.VectorWriter.println(ThrowableInformation.java:97)
at java.lang.Throwable$WrappedPrintWriter.println(Throwable.java:764)
at java.lang.Throwable.printStackTrace(Throwable.java:655)
at java.lang.Throwable.printStackTrace(Throwable.java:721)
at org.apache.log4j.spi.ThrowableInformation.getThrowableStrRep(ThrowableInformation.java:59)
at org.apache.log4j.spi.LoggingEvent.getThrowableStrRep(LoggingEvent.java:342)
at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:304)
at org.apache.log4j.RollingFileAppender.subAppend(RollingFileAppender.java:236)

No one else has this question

Outcomes

Boris Lekumovich

Oct 8, 2018 3:37 AM

If you take the exact XML and try to send a request using a 3rd party tool, is the change request created successfully or you are getting the same error?

Actions

Sirisha Bomma @ Boris Lekumovich on Oct 8, 2018 8:58 AM

Thank you. I tried the exact same xml and token using an external client and was successful. Please note that this web service call is in a loop and the first 2 iterations are successful on the third item it has this issue - on going to actions resetting any of previous nodes - the webservice call is successful with the exact same parameters - not sure if looping has any issue with webservice calls? We have another workflow to reset password by creating CR in a loop and that works fine.

It’s the create account with the issue.

Actions

Sirisha Bomma Oct 8, 2018 12:21 PM

Also this is what I see:

HttpStatusCode:	409
HttpStatusMsg:	Conflict

StatusCode:

RSA004 : Request Failed

If I have a loop for 5 account creation - it failed with above error for 3 and created just 2 CR for account creation

Actions

Boris Lekumovich

@ Sirisha Bomma on Oct 9, 2018 12:43 AM

I would try to add a delay node for 20 seconds in the loop and see if it solves the problem

Actions

Sirisha Bomma @ Boris Lekumovich on Oct 9, 2018 4:11 AM

I have tried that approach as well a few days back - delay was for 3 min - still failed in 3rd iteration. The first two were success. I can try once again. Am trying to understand from you why we need delay if token is different and data is different on each iteration?

Sent from my iPhone

Actions

Edwin Mullie

@ Sirisha Bomma on Oct 9, 2018 4:30 AM

It looks like it’s failing on the account name creation, is the account template and naming policy you use generating unique account names?

Actions

Sirisha Bomma @ Edwin Mullie on Oct 9, 2018 4:59 AM

Yes it is, as already mentioned there is no data issue - works fine. It’s with the looping and making web service calls

Sent from my iPhone

Actions

Sean Miller

Oct 12, 2018 9:05 AM

Can you enable debugging here so we can maybe understand what is going on here?  From the error message it sure seems like we are hitting some form of a race condition where multiple requests might be settling on the same account name after pluggin in all the parameters for the account template.

Please try enabling the following log4j categories:

com.aveksa.server.core.cr.ChangeRequestServiceProvider
com.aveksa.server.command.CreateChangeRequestCommand

Actions

Sirisha Bomma Jun 10, 2019 11:08 AM

Once IGL was restarted seems to be working. Not sure what was wrong before that.

Actions

9 Replies

Boris Lekumovich Oct 8, 2018 3:37 AM
Mark Correct
Correct Answer
If you take the exact XML and try to send a request using a 3rd party tool, is the change request created successfully or you are getting the same error?
Like • Show 1 Like1
Actions
- Sirisha Bomma @ Boris Lekumovich on Oct 8, 2018 8:58 AM
  Mark Correct
  Correct Answer
  Thank you. I tried the exact same xml and token using an external client and was successful. Please note that this web service call is in a loop and the first 2 iterations are successful on the third item it has this issue - on going to actions resetting any of previous nodes - the webservice call is successful with the exact same parameters - not sure if looping has any issue with webservice calls? We have another workflow to reset password by creating CR in a loop and that works fine.
  
  It’s the create account with the issue.
  Like • Show 0 Likes0
  Actions
Sirisha Bomma Oct 8, 2018 12:21 PM
Mark Correct
Correct Answer
Also this is what I see:
HttpStatusCode: 409
HttpStatusMsg: Conflict

StatusCode: RSA004 : Request Failed
If I have a loop for 5 account creation - it failed with above error for 3 and created just 2 CR for account creation
Like • Show 0 Likes0
Actions
- Boris Lekumovich @ Sirisha Bomma on Oct 9, 2018 12:43 AM
  Mark Correct
  Correct Answer
  I would try to add a delay node for 20 seconds in the loop and see if it solves the problem
  Like • Show 0 Likes0
  Actions
  - Sirisha Bomma @ Boris Lekumovich on Oct 9, 2018 4:11 AM
    Mark Correct
    Correct Answer
    I have tried that approach as well a few days back - delay was for 3 min - still failed in 3rd iteration. The first two were success. I can try once again. Am trying to understand from you why we need delay if token is different and data is different on each iteration?
    
    Sent from my iPhone
    Like • Show 0 Likes0
    Actions
    - Edwin Mullie @ Sirisha Bomma on Oct 9, 2018 4:30 AM
      Mark Correct
      Correct Answer
      It looks like it’s failing on the account name creation, is the account template and naming policy you use generating unique account names?
      Like • Show 0 Likes0
      Actions
      - Sirisha Bomma @ Edwin Mullie on Oct 9, 2018 4:59 AM
        Mark Correct
        Correct Answer
        Yes it is, as already mentioned there is no data issue - works fine. It’s with the looping and making web service calls
        
        Sent from my iPhone
        Like • Show 0 Likes0
        Actions

Sirisha Bomma Jun 10, 2019 11:08 AM
Mark Correct
Correct Answer
Once IGL was restarted seems to be working. Not sure what was wrong before that.
Like • Show 0 Likes0
Actions

Error in Web Service Call for Create Change Request

Outcomes

Related Content

Recommended Content