Thank you so much for your response!So, the second approach is to just use a static variable in the service. I did think about this but was nervous about race conditions with getting the token and managing it. If I do this, this will definitely cut down on the calls being made to the API. I can t...
Hey @MukeshYadav_ , Checking back in on ideas on how to accomplish #1. Is there a way to store something that can be shared across different workflow instances?
@AmitVishwakarma for number 2 I misunderstood. You were talking about the configuring the actual Httpclient directly like so:import org.apache.http.impl.conn.PoolingHttpClientConnectionManager;
import org.apache.http.client.config.RequestConfig;
import org.apache.http.impl.client.CloseableHttpClien...
Thanks @sarav_prakash! When you say this:"I faced similar problem in my project. I ended up writing AIO Runtime action. Download from DAM and upload of files to 3rd, happened outside AEM. At Runtime action." This was the approach I was originally taken which was to monitor a directory in AEM and g...
1. I would love to do this but not sure how. A new workflow instance is created for each and every file. One doesn't know about another right?2. So I poked around for those settings and I can't find them. Do you know where those are?3. The problem is I can't tell if the call was successful or not...
"should consider decoupling this addFileToItem() API call outside AEM, like on cloud microservice."I'm not sure how to do this. If you go and look at the thread I mentioned in the beginning of my question it was recommended to me to use a launcher and a workflow with a call to the an API to send th...
Due to some of the responses I think I need to reiterate 2 important points here 1. This logic is completely successful when dropping 1, 2, or even 3 files in the directory. The problem ONLY occurs when dropping a large number of files into the directory all at once.2. The exception is coming from ...
Thanks for the suggestions.1. How do I do that? Doesn't my component get instantiated for each workflow? Or does it only get instantiated once and the execute is called multiple times? I would love to make this optimization if I can reliably store that information and not introduce race conditio...
I feel like I'm not saying the correct thing. The problem is the socket exception which only happens within the AEM platform. There should be no socket exception. Custom retrying is not an option because in the case I show the call was actually successful so the retry sends a second file. I test...