Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Actions in Project Firefly returning a 503 status code with some weird AWS Lambda error sporadically

Avatar

Avatar
Ignite 1
Level 1
rkishoreindraganti
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Ignite 1
View profile

Avatar
Ignite 1
Level 1
rkishoreindraganti
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Ignite 1
View profile
rkishoreindraganti
Level 1

15-04-2021

Hi,

 

I hope you are doing good!

 

We are facing a weird issue in our project firefly app development, in our API layer (using actions here; in node.js) we are trying to establish AEP datasets and issuing some query against the dataset using ODBC strategy (Not HTTP Query Service);

 

On invoking the REST endpoint that I stated above we are getting some weird error with a status code as 503 sporadically (Find the screenshot below).

 

rkishoreindraganti_0-1618496133853.png

 

 

This is being a show stopper to continue our development, we are feeling reluctant to proceed further considering this may be a limitation in the Adobe IO, your suggestions are much appreciated.

 

Please let us know the root cause and solution ASAP.

 

Thanks!

Replies

Avatar

Avatar
Boost 25
Employee
duypnguyen
Employee

Likes

27 likes

Total Posts

162 posts

Correct Reply

31 solutions
Top badges earned
Boost 25
Applaud 5
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Boost 25
Employee
duypnguyen
Employee

Likes

27 likes

Total Posts

162 posts

Correct Reply

31 solutions
Top badges earned
Boost 25
Applaud 5
Give Back 5
Give Back 3
Give Back 10
View profile
duypnguyen
Employee

15-04-2021

Hi @rkishoreindraganti - I assume you are calling your action via "https://your-namespace.adobeio-static.net/...", is that correct?

Please try replacing "adobeio-static.net" by "adobeioruntime.net", and try again.

The reason why you got this error is that, your action ran longer than 30 seconds and caused a timeout at the CDN "adobeio-static.net".

The "adobeioruntime.net" domain has a timeout of 1 minute, which is default for all web actions running on I/O Runtime.

That being said, a web request taking more than 30 seconds is considered very slow. Please re-visit the implementation to optimize it if possible, for example by moving the time consuming part to an async (non-blocking) execution.

As a side note, please also update your AIO CLI with "npm install -g @adobe/aio-cli". All the URLs should be on "adobeioruntime.net" in a recent CLI release.

Avatar

Avatar
Give Back 5
Level 1
kishoreindraganti
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile

Avatar
Give Back 5
Level 1
kishoreindraganti
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
kishoreindraganti
Level 1

15-04-2021

@duypnguyen : Thanks for the quick response, it is much appreciated! 

 

I have tried your approach on updating the @adobe/aio-cli though it is referring to adobe-io.static.net. Please find the below snippet. 

 

kishoreindraganti_1-1618500885965.png

 

Avatar

Avatar
Boost 25
Employee
duypnguyen
Employee

Likes

27 likes

Total Posts

162 posts

Correct Reply

31 solutions
Top badges earned
Boost 25
Applaud 5
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Boost 25
Employee
duypnguyen
Employee

Likes

27 likes

Total Posts

162 posts

Correct Reply

31 solutions
Top badges earned
Boost 25
Applaud 5
Give Back 5
Give Back 3
Give Back 10
View profile
duypnguyen
Employee

15-04-2021

@kishoreindraganti - thanks for sharing the screenshot. I can see the same output from the `aio app deploy` command.

Regardless, it is only an output from the CLI command. You should still be able to call the same URL with adobeioruntime.net - could you please try in Postman? If you develop your app locally by `aio app run`, adobeioruntime.net is used.

I will follow up with the team on fixing the CLI output.

(Just to clarify: the different domains mentioned above are only applied for the action URLs. The frond-end is always served from https://your-namespace.adobeio-static.net/index.html)

Avatar

Avatar
Give Back 5
Level 1
kishoreindraganti
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile

Avatar
Give Back 5
Level 1
kishoreindraganti
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
kishoreindraganti
Level 1

15-04-2021

I am trying your other solutions, in the meantime, I just want to make things clear, it is not only on the CLI output, even the application also makes the call to adobeio-static.net only not to the adobeioruntime.net though I am using the latest CLI version.

 

kishoreindraganti_0-1618503005635.png

 

Avatar

Avatar
Give Back 5
Level 1
kishoreindraganti
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile

Avatar
Give Back 5
Level 1
kishoreindraganti
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
kishoreindraganti
Level 1

15-04-2021

"aio app run"  uses "adobeioruntime.net" but "aio app deploy" using "adobe-io.static.net"

Avatar

Avatar
Boost 25
Employee
duypnguyen
Employee

Likes

27 likes

Total Posts

162 posts

Correct Reply

31 solutions
Top badges earned
Boost 25
Applaud 5
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Boost 25
Employee
duypnguyen
Employee

Likes

27 likes

Total Posts

162 posts

Correct Reply

31 solutions
Top badges earned
Boost 25
Applaud 5
Give Back 5
Give Back 3
Give Back 10
View profile
duypnguyen
Employee

15-04-2021

You're right, sorry for the confusion. And yes, pursuing the other approach (async call for long requests) is strongly recommended.

Avatar

Avatar
Give Back 5
Level 1
kishoreindraganti
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile

Avatar
Give Back 5
Level 1
kishoreindraganti
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
kishoreindraganti
Level 1

15-04-2021

What do you mean by async call? can you point me to some resources, please?

Avatar

Avatar
Boost 25
Employee
duypnguyen
Employee

Likes

27 likes

Total Posts

162 posts

Correct Reply

31 solutions
Top badges earned
Boost 25
Applaud 5
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Boost 25
Employee
duypnguyen
Employee

Likes

27 likes

Total Posts

162 posts

Correct Reply

31 solutions
Top badges earned
Boost 25
Applaud 5
Give Back 5
Give Back 3
Give Back 10
View profile
duypnguyen
Employee

15-04-2021

You can see how to call your action in async mode here: https://github.com/AdobeDocs/adobeio-runtime/blob/master/guides/asynchronous_calls.md.

I understand that your app has a UI as well. So the end user experience on the UI would be:

- you trigger the web action (A) to run dataset query

- (A) receives your request, calls another action to run the actual dataset query job (B) in an async mode

- (A) responds immediately to the UI (without waiting for (B) to complete), e.g. with status "Query is running"

- you have a button "check query status" to poll the progress of (B). When it's completed, you will receive "Query is complete. Here is the results..."

Avatar

Avatar
Give Back 5
Level 1
kishoreindraganti
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile

Avatar
Give Back 5
Level 1
kishoreindraganti
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 1
View profile
kishoreindraganti
Level 1

15-04-2021

Ok. For that, I want to create an action that has to reside out of the ProjectFirefly application? so we can't increase the timeout for the actions which is coming as part of ProjectFirefly? This is my understanding finally, is that correct?