From: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | [patch][pgAdmin4] Windows error - The application server could not be contacted occasionally |
Date: | 2019-01-01 10:24:34 |
Message-ID: | CAM9w-_nJm3V6Fv9e7gTgVGPnqzFYUabQy5RUUP3TStUL_3J2OA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Hackers,
Some of the windows users are facing the error as "The application server could
not be contacted" while starting pgAdmin4. The startup logs had nothing.
Just that the application timed out.
I was able to simulate the issue for sometime when I started my windows
machine, but later it did not throw any error and worked fine.
It turned out that due to the slowness of the Windows OS initially the
application took time to setup which was longer than the app start timeout
- 30secs and so, timed out.
In the attached patch, I have increased the timeout to 90secs (difficult to
figure out the standard timeout). Plus, I have changed the messages at
intervals when the app is starting so that it does not look stuck.
Kindly review.
--
Thanks and Regards,
Aditya Toshniwal
Software Engineer | EnterpriseDB Software Solutions | Pune
"Don't Complain about Heat, Plant a tree"
Attachment | Content-Type | Size |
---|---|---|
timeout.splash.patch | application/octet-stream | 1.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2019-01-02 05:18:39 | pgAdmin 4 commit: pgBrowser tree does not need to save tree state, when |
Previous Message | Akshay Joshi | 2019-01-01 09:48:08 | Re: [pgAdmin4][Patch] - RM 3780 pgAdmin4 lacks ability to specify NULL values in CSV export |