Hello, we sometimes have an issue about calling a specific event which runs an http request, sometimes, IFS takes a lot of time to execute the event. How can we reduce this time execution? Thanks
Question
Application message and queue list
+23Hi
If you have too many entries, it will take time.
Maybe you can clean up old entries.
+23Are you in cloud or onPrem?
I don’t fully understand your message, why cleaning up old entries? old entries already ran, so they have no impact on performances, right?
+23We are on IFS 10 upd 5
I know. This is the version. 😊
How do you host IFS? In cloud or in your company?
+23OK. Is it slow in this case only, or generally?
this occurs sometimes but not regularly, we can spend months with no issue, but lately, that occured 2 times in 1 week. Last time, it was on hold for about 30 minutes
+23The reason can be that you have sometimes a lot of entries on this screen.
And then the event check the condition in all these data.
Is that a SQL event?
+22Hi
What is the most time consuming part, is t the application message in Released state or the Processing time (actual execution time)?
Hello
the process to switch the state, from processing to finished.
When that works fine, the execution lasts less than 0.01 second
+22Hello
the process to switch the state, from processing to finished.
When that works fine, the execution lasts less than 0.01 second
It looks like the http call from the application message which takes time. In the routing rule, check if you have defined a Queue.
If no queue is defined, then the transaction (event) will wait until the response back from the http call. If the response is not needed to proceed with the transaction, by setting up a queue in the routing rule will run the http call asynchronous from the main transaction.
Hope it helps!
Damith
about the process that we have a time execution issue, it’s a custom event which calls an http request with no response
+22Hi
Right click on one of your application message, View Details...
Here you can see what’s the routing rule used and and navigate to the routing rule page by clicking the link
Check the Queue and if it’s None, that means no queue is used.
For outbound messages you can pick OUT1 which is a predefined queue. But you can configure your own queue as well.
Read more about Routing address/routing rules here
+22Hi
What is the Event action type you created for this? is it a REST call or a SQL type action?
+22
Can you please share a screenshot of the event action setup?
+22Hi
When you define the Connector and the Address data, it will not use the IFS Connect routing to process the application message. But the message is queued in the Notification queue. So your setup is correct.
Back to the question: time the application message in Processing state is actual time it takes to invoke the http call. Since the issue happens sometimes, best thing is to check the http endpoint for any problems.
BR,
Damith
hello
Weeks later, we didn’t meet any new issue, a workmate planned to restart the servers, since, everything seem to work fine now
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.