Skip to main content
Solved

Upgraded to 2022.2.3 now I can't send large XML POST SOAP API calls via HTTPcaller.


robotix
Contributor
Forum|alt.badge.img+10

The caller just hangs.

Works fine on desktop but not the server.

I had to add a feature holder between the HTTP Caller and the XML templater. Any other suggestions?? That seems to be only part of the solution.

Best answer by robotix

hkingsbury wrote:

do you have any reverse proxy/firewall/load balancer that may have size restrictions on calls causing it to be blocked on server?

 

That was a good suggestion. That got me thinking in a new direction. The throughput for the job doesn't exceed the limit on the network. However, I did scale back concurrency and rate limit. That did help so maybe there is an app limit for throughput. I still have to use the feature holder between the xmltemplater and the HTTP caller. Unsure why. It seems like its trying to make the call before the templater is done? Anyways with the feature holder, concurrency limit and throwing in an attribute keeper [to limit data to the last HTTP transformer], things seem to be working now.

View original
Did this help you find an answer to your question?

3 replies

robotix
Contributor
Forum|alt.badge.img+10
  • Author
  • Contributor
  • March 13, 2023

I had to add a feature holder between the XML templater and the HTTP Caller.

Seems like only part of the solution though.


hkingsbury
Celebrity
Forum|alt.badge.img+55
  • Celebrity
  • March 14, 2023

do you have any reverse proxy/firewall/load balancer that may have size restrictions on calls causing it to be blocked on server?

 


robotix
Contributor
Forum|alt.badge.img+10
  • Author
  • Contributor
  • Best Answer
  • March 14, 2023
hkingsbury wrote:

do you have any reverse proxy/firewall/load balancer that may have size restrictions on calls causing it to be blocked on server?

 

That was a good suggestion. That got me thinking in a new direction. The throughput for the job doesn't exceed the limit on the network. However, I did scale back concurrency and rate limit. That did help so maybe there is an app limit for throughput. I still have to use the feature holder between the xmltemplater and the HTTP caller. Unsure why. It seems like its trying to make the call before the templater is done? Anyways with the feature holder, concurrency limit and throwing in an attribute keeper [to limit data to the last HTTP transformer], things seem to be working now.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings