> Do you control the app?
Nop Just I know how it's developed.
> The app has a pooling component and you still are having problems, have
> you looked at what the pooler is actually doing?
As far as I know, the wildfly's jdbc pool. No really I don't know what are
doing. I suspect that problem is that in DAO's not are closing the sessions
or not beginning transactions properly. I going to ask them send me the
logfile or I'll could verify the pool behavior.
> Not sure what the above means. Are you saying the application you refer
> to above has a history of not correctly closing connections or are you
> talking in general terms about applications interacting with databases.
Sorry, it's not like that, just was a comment, The problem I have is with a
specific application.
> I've attached two files that may be helpful to you.
Melvin , Thanks for the scripts! I owe one!
I have another question, I've was reading about the lock_timeout, Somehow
this parameter will help or could affect all the behaviour?
Thanks!
-----
Dame un poco de fe, eso me bastará.
Rozvo Ware Solutions
--
View this message in context: http://www.postgresql-archive.org/postgres-dbname-dbuser-9- 9-9-9-2222-PARSE-waiting- tp5968923p5969552.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
>I've was reading about the lock_timeout, Somehow this parameter will help or could affect all the behaviour?
https://www.postgresql.org/docs/9.4/static/runtime-config-client.html
- lock_timeout (integer)
-
Abort any statement that waits longer than the specified number of milliseconds while attempting to acquire a lock on a table, index, row, or other database object. The time limit applies separately to each lock acquisition attempt. The limit applies both to explicit locking requests (such as LOCK TABLE, or SELECT FOR UPDATE without NOWAIT) and to implicitly-acquired locks. If log_min_error_statement is set to ERROR or lower, the statement that timed out will be logged. A value of zero (the default) turns this off.
Unlike statement_timeout, this timeout can only occur while waiting for locks. Note that if statement_timeout is nonzero, it is rather pointless to set lock_timeout to the same or larger value, since the statement timeout would always trigger first.
Setting lock_timeout in postgresql.conf is not recommended because it would affect all sessions.
https://www.postgresql.org/docs/current/static/runtime-config-connection.html
--
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
