Support Article

Queued Connect-HTTP requests do not work without a commit

SA-29343

Summary



Queued Connect-HTTP requests do not work without a commit in Pega 7.1.9.

The execution mode of "Queue" on the Connect-HTTP method does not result in any action being taken unless a commit is performed. The queue entry should be immediately written to the database for the connect request processor to pick up.

Our use case is that there is lot of background operations which do not contain explicit commits on the threads, but that are required to invoke external http services.

The http service invocations we would like to offload to a background agent process.



Error Messages

Not applicable

Steps to Reproduce

  1. Request a Connect Request Processor instance using queue class name = System-Queue-ExecutionRequest-Connect-Default.
  2. Create a Connect-HTTP rule. Under "Processing Options", choose "Intended for" = "Queuing". Add the Connect Request Processor instance.
  3. Create an activity to invoke the Connect-HTTP rule.
  4. In the Connect-HTTP step of the activity, choose "Queue" as the Execution Mode.
  5. Run the activity.
  6. Note that the http service does not get invoked.
  7. Add a commit step to the end of the activity, and run the activity again.
  8. Note that the http service is invoked by the agent process.


Root Cause



This is expected behavior for both Connect-HTTP and Connect-SOAP implementations (the latter is explained in PDN document).

Resolution



Referred to PDN:

https://pdn.pega.com/calling-web-services-using-queued-execution/calling-web-services-using-queued-execution


 

Published October 19, 2016 - Updated October 25, 2016

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.