Thread: Connect is not available, request timeout after 30000ms.

Connect is not available, request timeout after 30000ms.

From
Pawan Sharma
Date:
Hi All,


I have upgarded my PostgreSQL database from 10 to 11 version using pg_dump method.

That database is used by two apps.

1. A   (most of the transaction are SELECT AND INSERT)
2. B   ( most of the transaction UPDATE AND DELETE)

After the upgarde I am facing *error:connection is not available, request timeout after 3000ms* with app B whereas app A is working fine with same database..

I have upgarded my JDBC driver with lastest driver to fix this issue but no luck.


Thanks for advance help.


Regards,
Pawan

Re: Connect is not available, request timeout after 30000ms.

From
Adrian Klaver
Date:
On 6/25/19 6:49 AM, Pawan Sharma wrote:
> Hi All,
> 
> 
> I have upgarded my PostgreSQL database from 10 to 11 version using 
> pg_dump method.
> 
> That database is used by two apps.
> 
> 1. A   (most of the transaction are SELECT AND INSERT)
> 2. B   ( most of the transaction UPDATE AND DELETE)
> 
> After the upgarde I am facing *error:connection is not available, 
> request timeout after 3000ms* with app B whereas app A is working fine 
> with same database..

Can the app connect at all?

What is the app doing when it gets the error?

Where is the error message appearing?

Are there other error messages befor eor afterthe above?

> 
> I have upgarded my JDBC driver with lastest driver to fix this issue but 
> no luck.
> 
> 
> Thanks for advance help.
> 
> 
> Regards,
> Pawan
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



Re: Connect is not available, request timeout after 30000ms.

From
Pawan Sharma
Date:
Can the app connect at all?
- yes connection between database and app B is successfully established. 
What is the app doing when it gets the error?
- from the app B we trying to delete some records in database.
Where is the error message appearing?
- messages are appearing in app server log.
Are there other error messages before or after the above?
-no there, nothing and after.

On Tue, Jun 25, 2019 at 7:25 PM Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 6/25/19 6:49 AM, Pawan Sharma wrote:
> Hi All,
>
>
> I have upgarded my PostgreSQL database from 10 to 11 version using
> pg_dump method.
>
> That database is used by two apps.
>
> 1. A   (most of the transaction are SELECT AND INSERT)
> 2. B   ( most of the transaction UPDATE AND DELETE)
>
> After the upgarde I am facing *error:connection is not available,
> request timeout after 3000ms* with app B whereas app A is working fine
> with same database..

Can the app connect at all?

What is the app doing when it gets the error?

Where is the error message appearing?

Are there other error messages befor eor afterthe above?

>
> I have upgarded my JDBC driver with lastest driver to fix this issue but
> no luck.
>
>
> Thanks for advance help.
>
>
> Regards,
> Pawan
>


--
Adrian Klaver
adrian.klaver@aklaver.com

Re: Connect is not available, request timeout after 30000ms.

From
Adrian Klaver
Date:
On 6/25/19 7:06 AM, Pawan Sharma wrote:
> Can the app connect at all?
> - yes connection between database and app B is successfully established.
> What is the app doing when it gets the error?
> - from the app B we trying to delete some records in database.
> Where is the error message appearing?
> - messages are appearing in app server log.

What shows up in the Postgres log at around the same time?

> Are there other error messages before or after the above?
> -no there, nothing and after.
> 
> On Tue, Jun 25, 2019 at 7:25 PM Adrian Klaver <adrian.klaver@aklaver.com 
> <mailto:adrian.klaver@aklaver.com>> wrote:
> 
>     On 6/25/19 6:49 AM, Pawan Sharma wrote:
>      > Hi All,
>      >
>      >
>      > I have upgarded my PostgreSQL database from 10 to 11 version using
>      > pg_dump method.
>      >
>      > That database is used by two apps.
>      >
>      > 1. A   (most of the transaction are SELECT AND INSERT)
>      > 2. B   ( most of the transaction UPDATE AND DELETE)
>      >
>      > After the upgarde I am facing *error:connection is not available,
>      > request timeout after 3000ms* with app B whereas app A is working
>     fine
>      > with same database..
> 
>     Can the app connect at all?
> 
>     What is the app doing when it gets the error?
> 
>     Where is the error message appearing?
> 
>     Are there other error messages befor eor afterthe above?
> 
>      >
>      > I have upgarded my JDBC driver with lastest driver to fix this
>     issue but
>      > no luck.
>      >
>      >
>      > Thanks for advance help.
>      >
>      >
>      > Regards,
>      > Pawan
>      >
> 
> 
>     -- 
>     Adrian Klaver
>     adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



Re: Connect is not available, request timeout after 30000ms.

From
Pawan Sharma
Date:
In PostgreSQL logs it's showing select queries are running with duration approx 37001.347ms

On Tue, Jun 25, 2019, 7:44 PM Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 6/25/19 7:06 AM, Pawan Sharma wrote:
> Can the app connect at all?
> - yes connection between database and app B is successfully established.
> What is the app doing when it gets the error?
> - from the app B we trying to delete some records in database.
> Where is the error message appearing?
> - messages are appearing in app server log.

What shows up in the Postgres log at around the same time?

> Are there other error messages before or after the above?
> -no there, nothing and after.
>
> On Tue, Jun 25, 2019 at 7:25 PM Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.com>> wrote:
>
>     On 6/25/19 6:49 AM, Pawan Sharma wrote:
>      > Hi All,
>      >
>      >
>      > I have upgarded my PostgreSQL database from 10 to 11 version using
>      > pg_dump method.
>      >
>      > That database is used by two apps.
>      >
>      > 1. A   (most of the transaction are SELECT AND INSERT)
>      > 2. B   ( most of the transaction UPDATE AND DELETE)
>      >
>      > After the upgarde I am facing *error:connection is not available,
>      > request timeout after 3000ms* with app B whereas app A is working
>     fine
>      > with same database..
>
>     Can the app connect at all?
>
>     What is the app doing when it gets the error?
>
>     Where is the error message appearing?
>
>     Are there other error messages befor eor afterthe above?
>
>      >
>      > I have upgarded my JDBC driver with lastest driver to fix this
>     issue but
>      > no luck.
>      >
>      >
>      > Thanks for advance help.
>      >
>      >
>      > Regards,
>      > Pawan
>      >
>
>
>     --
>     Adrian Klaver
>     adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>


--
Adrian Klaver
adrian.klaver@aklaver.com

Re: Connect is not available, request timeout after 30000ms.

From
Adrian Klaver
Date:
On 6/25/19 7:24 AM, Pawan Sharma wrote:
> In PostgreSQL logs it's showing select queries are running with duration 
> approx 37001.347ms
> 

Is this normal?

Did you run ANALYZE on the database after you restored it to the new 
Postgres 11 cluster?

If not do so.

Then run the query in psql or something similar with EXPALIN ANALYZE and 
see what the time is.


I cannot find the error message string in the Postgres source code, so I 
am guessing it came from somewhere else. Best guess is the app/driver 
has a timeout set.


-- 
Adrian Klaver
adrian.klaver@aklaver.com



Re: Connect is not available, request timeout after 30000ms.

From
Pawan Sharma
Date:
Ya this is because of ANALYZE.

now it's working fine.

Thanks for your support.


On Tue, Jun 25, 2019, 8:03 PM Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 6/25/19 7:24 AM, Pawan Sharma wrote:
> In PostgreSQL logs it's showing select queries are running with duration
> approx 37001.347ms
>

Is this normal?

Did you run ANALYZE on the database after you restored it to the new
Postgres 11 cluster?

If not do so.

Then run the query in psql or something similar with EXPALIN ANALYZE and
see what the time is.


I cannot find the error message string in the Postgres source code, so I
am guessing it came from somewhere else. Best guess is the app/driver
has a timeout set.


--
Adrian Klaver
adrian.klaver@aklaver.com