92
Views
9
Comments
Solved
[Automatic Deployment] The underlying connection was closed : An unexpected error occurred on a receive.
Question
automatic-deployment
Web icon
Forge asset by Evergreen IT

I'm using this Forge Automatic Deployment

Along with Part 4 here on Documentation, I created the URL for Web service.



I created Consume REST API, and set the parameters and tested it but it doesn't work.


This is the Test result.


Where am I missing? Are you familiar with this kind of error?

I'd appreciate your advice.

Best,

2023-12-07 07-51-40
Remco Dekkinga
 
MVP
Solution

Tsubasa,

Did you try to contact OS Support as I suggested above? The API is provided by OS and the error you are receiving is from the API. I'm sorry, but I can't look into this matter for you.

Kind regards,

Remco

UserImage.jpg
Tsubasa Yoshikawa

Remco,

I touched base with OS Support and I understood the error is from Lifetime API.

Thanks. I'll just address it.

Best,

2023-12-07 07-51-40
Remco Dekkinga
 
MVP

Hi Tsubasa,

I've uploaded a new version of the component and updated the Documentation.

Part 4 was only needed when you deploy via an external service like Jenkins. When you want to use the timer, you can now easily follow the new Documentation manual. You don't have to adjust anything inside the AutomaticDeployment module.

Kind regards,

Remco Dekkinga

UserImage.jpg
Tsubasa Yoshikawa

Hi Remco,


Thank you for the new version module.


I retried my automatic deploy inside Lifetime. I set timer to 11:45.

I followed Documentation part1~4 .

Part4 I did is "Only when you want to automatically deploy from inside LifeTime"

I created a new deployment plan and executed it but it didn't work.

Here is the error log.




I wonder where I'm missing. I think I set along with Documentation.

Do you have any ideas on this error (Failed to retrieve ・・・)?

I'd appreciate it if you could give me good advice.


Best.

2023-12-07 07-51-40
Remco Dekkinga
 
MVP

Hi Tsubasa,

This is indeed a strange issue. When everything is installed correctly on LifeTime and your application is available in the source environment, the systems should be able to deploy the application from the source environment to the target environment.

Are you able to deploy this application by hand?

If not, it could be that the source environment is not reachable or that the application doesn't exist yet in the source environment.

If it is possible, I'm not sure what the cause could be, but we might need to call in the support of the OutSystems team responsible for the LifeTime Deployment API.

Kind regards,

Remco Dekkinga



UserImage.jpg
Tsubasa Yoshikawa

Hi Remco,

Thank you for your reply.

I'm able to deploy the applications from  Development environment to TEST environment by hand with Lifetime.

source:  Development environment (name is "開発" in Japanese.)

target:  TEST environment (name is "Test Server" in English.)

Now I suppose the source environment name is not recognized  when detecting each Environment name. I mean probably "開発" is being garbled and this Forge module can't detect Source Environment. That is, I have a hunch the cause is that my Development environment name is garbled when deploying automatically by this Forge module.

I think that's why error message says "Failed to retrieve environment with key of test environment or application with key of application" . 

I'm trying to change Development Environment name to English name in Environment Configuration of ServiceCenter, but in this case I wonder if I can't edit Environment name by myself and I have to touch base with Outsystems Support...


Do you think that it is worth trying this?  Also, I've checked that the steps I followed Documentation is right.


Sorry for the long sentence.  I look forward to your comment.

Best,


2023-12-07 07-51-40
Remco Dekkinga
 
MVP

Hi Tsubasa,

It would be very strange if it is the Japanese text, because it's looking for the GUID and not on the text.

You could check with OS Support if they could see what could be the cause of this problem.

Kind regards,

Remco

UserImage.jpg
Tsubasa Yoshikawa

I tried again but it didn't work.

I end up getting 404 error with the same error (Failed to retrieve the environment with key・・ ).

I received the result e-mail but the message says as below.

------------------------------------------

Automatic Deployment of DeveloptToTest: Failed: Unknown status: 保存

21-01-2022 15:02

Instant

Message

No items to show...

----------------------------------------


I wonder in what case this error is happening for this Forge..

Are you familiar with this?

Best,

UserImage.jpg
Tsubasa Yoshikawa

I looked into this matter.

I set the deploy plan like this.



I checked this Forge module and I can see this kind of stuff here in the Entity. Is there no issue here?

And then according to what I checked, it seems like my deploy is going into this switch flow.


Anyway, I tried again however I end up getting the error saying "Failed to retrieve the environment with key ・・・" as I mentioned from the above post.


Do you have any ideas on this issue?

I wonder where I'm missing...I can not figure out.


Best,

2023-12-07 07-51-40
Remco Dekkinga
 
MVP
Solution

Tsubasa,

Did you try to contact OS Support as I suggested above? The API is provided by OS and the error you are receiving is from the API. I'm sorry, but I can't look into this matter for you.

Kind regards,

Remco

UserImage.jpg
Tsubasa Yoshikawa

Remco,

I touched base with OS Support and I understood the error is from Lifetime API.

Thanks. I'll just address it.

Best,

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.