[
https://issues.apache.org/jira/browse/CONNECTORS-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Wolfinger updated CONNECTORS-1670:
--------------------------------------
Description:
We recently upgraded Manifold version to 2.19 and PostgreSQL version to 12.5.
So far everything worked fine, except some warnings within the database (row
13):
1: 2021-07-06 08:51:46.366 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
Execute <unnamed>: START TRANSACTION
2: 2021-07-06 08:51:46.366 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
Execute S_38: SELECT id,status,connectionname FROM jobs WHERE
assessmentstate=$1 FOR UPDATE
3: 2021-07-06 08:51:46.366 CEST-1013441-172.16.172.133(45412)-xxxxxxx: DETAIL:
Parameter: $1 = 'N'
4: 2021-07-06 08:51:46.367 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
Execute S_39: SELECT transformationname FROM jobpipelines WHERE ownerid=$1 AND
transformationname IS NOT NULL
5:2021-07-06 08:51:46.367 CEST-1013441-172.16.172.133(45412)-xxxxxxx: DETAIL:
Parameter: $1 = '1615294637875'
6:2021-07-06 08:51:46.368 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
Execute S_40: SELECT outputname FROM jobpipelines WHERE ownerid=$1 AND
outputname IS NOT NULL
7:2021-07-06 08:51:46.368 CEST-1013441-172.16.172.133(45412)-xxxxxxx: DETAIL:
Parameter: $1 = '1615294637875'
8:2021-07-06 08:51:46.369 CEST-10134
9:2021-07-06 08:55:02.148 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
Execute <unnamed>: START TRANSACTION
10:2021-07-06 08:55:02.149 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
Execute S_4: SELECT id,lasttime,status,startmethod,connectionname FROM jobs
WHERE (status=$1 OR status=$2 OR status=$3 OR status=$4 OR status=$5) AND
startmethod!=$6 FOR UPDATE
11:2021-07-06 08:55:02.149 CEST-1012399-172.16.172.133(45330)-xxxxxxx: DETAIL:
Parameter: $1 = 'N', $2 = 'W', $3 = 'w', $4 = 'Z', $5 = 'z', $6 = 'D'
12:2021-07-06 08:55:02.151 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
Execute <unnamed>: START TRANSACTION
13:2021-07-06 08:55:02.151 CEST-1012399-172.16.172.133(45330)-xxxxxxx:
WARNING: there is already a transaction in progress
14:2021-07-06 08:55:02.153 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
execute S_14: SELECT * FROM schedules WHERE ownerid=$1 ORDER BY ordinal ASC
15:2021-07-06 08:55:02.153 CEST-1012399-172.16.172.133(45330)-xxxxxxx: DETAIL:
Parameter: $1 =
as we can see a new transaction ist startet in row 9 and then another one in
row 12, which causes the warning in row 13. The reason for this seems, that the
first transaction is not terminated when the second one starts. I tried to look
up the code in the source, but i couldnt find the right location.
Has anyone else encountered the behaviour or know, where to lookup the location
in the source code?
was:
We recently upgraded Manifold version to 2.19 and PostgreSQL version to 12. So
far everything worked fine, except some warnings within the database (row 13):
1: 2021-07-06 08:51:46.366 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
Execute <unnamed>: START TRANSACTION
2: 2021-07-06 08:51:46.366 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
Execute S_38: SELECT id,status,connectionname FROM jobs WHERE
assessmentstate=$1 FOR UPDATE
3: 2021-07-06 08:51:46.366 CEST-1013441-172.16.172.133(45412)-xxxxxxx: DETAIL:
Parameter: $1 = 'N'
4: 2021-07-06 08:51:46.367 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
Execute S_39: SELECT transformationname FROM jobpipelines WHERE ownerid=$1 AND
transformationname IS NOT NULL
5:2021-07-06 08:51:46.367 CEST-1013441-172.16.172.133(45412)-xxxxxxx: DETAIL:
Parameter: $1 = '1615294637875'
6:2021-07-06 08:51:46.368 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
Execute S_40: SELECT outputname FROM jobpipelines WHERE ownerid=$1 AND
outputname IS NOT NULL
7:2021-07-06 08:51:46.368 CEST-1013441-172.16.172.133(45412)-xxxxxxx: DETAIL:
Parameter: $1 = '1615294637875'
8:2021-07-06 08:51:46.369 CEST-10134
9:2021-07-06 08:55:02.148 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
Execute <unnamed>: START TRANSACTION
10:2021-07-06 08:55:02.149 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
Execute S_4: SELECT id,lasttime,status,startmethod,connectionname FROM jobs
WHERE (status=$1 OR status=$2 OR status=$3 OR status=$4 OR status=$5) AND
startmethod!=$6 FOR UPDATE
11:2021-07-06 08:55:02.149 CEST-1012399-172.16.172.133(45330)-xxxxxxx: DETAIL:
Parameter: $1 = 'N', $2 = 'W', $3 = 'w', $4 = 'Z', $5 = 'z', $6 = 'D'
12:2021-07-06 08:55:02.151 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
Execute <unnamed>: START TRANSACTION
13:2021-07-06 08:55:02.151 CEST-1012399-172.16.172.133(45330)-xxxxxxx: WARNING:
there is already a transaction in progress
14:2021-07-06 08:55:02.153 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
execute S_14: SELECT * FROM schedules WHERE ownerid=$1 ORDER BY ordinal ASC
15:2021-07-06 08:55:02.153 CEST-1012399-172.16.172.133(45330)-xxxxxxx: DETAIL:
Parameter: $1 =
as we can see a new transaction ist startet in row 9 and then another one in
row 12, which causes the warning in row 13. The reason for this seems, that the
first transaction is not terminated when the second one starts. I tried to look
up the code in the source, but i couldnt find the right location.
Has anyone else encountered the behaviour or know, where to lookup the location
in the source code?
> PostgreSQL: transaction in progress
> -----------------------------------
>
> Key: CONNECTORS-1670
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1670
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework core
> Affects Versions: ManifoldCF 2.19
> Reporter: Uwe Wolfinger
> Priority: Major
>
> We recently upgraded Manifold version to 2.19 and PostgreSQL version to 12.5.
> So far everything worked fine, except some warnings within the database (row
> 13):
> 1: 2021-07-06 08:51:46.366 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
> Execute <unnamed>: START TRANSACTION
> 2: 2021-07-06 08:51:46.366 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
> Execute S_38: SELECT id,status,connectionname FROM jobs WHERE
> assessmentstate=$1 FOR UPDATE
> 3: 2021-07-06 08:51:46.366 CEST-1013441-172.16.172.133(45412)-xxxxxxx:
> DETAIL: Parameter: $1 = 'N'
> 4: 2021-07-06 08:51:46.367 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
> Execute S_39: SELECT transformationname FROM jobpipelines WHERE ownerid=$1
> AND transformationname IS NOT NULL
> 5:2021-07-06 08:51:46.367 CEST-1013441-172.16.172.133(45412)-xxxxxxx:
> DETAIL: Parameter: $1 = '1615294637875'
> 6:2021-07-06 08:51:46.368 CEST-1013441-172.16.172.133(45412)-xxxxxxx: LOG:
> Execute S_40: SELECT outputname FROM jobpipelines WHERE ownerid=$1 AND
> outputname IS NOT NULL
> 7:2021-07-06 08:51:46.368 CEST-1013441-172.16.172.133(45412)-xxxxxxx:
> DETAIL: Parameter: $1 = '1615294637875'
> 8:2021-07-06 08:51:46.369 CEST-10134
> 9:2021-07-06 08:55:02.148 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
> Execute <unnamed>: START TRANSACTION
> 10:2021-07-06 08:55:02.149 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
> Execute S_4: SELECT id,lasttime,status,startmethod,connectionname FROM jobs
> WHERE (status=$1 OR status=$2 OR status=$3 OR status=$4 OR status=$5) AND
> startmethod!=$6 FOR UPDATE
> 11:2021-07-06 08:55:02.149 CEST-1012399-172.16.172.133(45330)-xxxxxxx:
> DETAIL: Parameter: $1 = 'N', $2 = 'W', $3 = 'w', $4 = 'Z', $5 = 'z', $6 = 'D'
> 12:2021-07-06 08:55:02.151 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
> Execute <unnamed>: START TRANSACTION
> 13:2021-07-06 08:55:02.151 CEST-1012399-172.16.172.133(45330)-xxxxxxx:
> WARNING: there is already a transaction in progress
> 14:2021-07-06 08:55:02.153 CEST-1012399-172.16.172.133(45330)-xxxxxxx: LOG:
> execute S_14: SELECT * FROM schedules WHERE ownerid=$1 ORDER BY ordinal ASC
> 15:2021-07-06 08:55:02.153 CEST-1012399-172.16.172.133(45330)-xxxxxxx:
> DETAIL: Parameter: $1 =
> as we can see a new transaction ist startet in row 9 and then another one in
> row 12, which causes the warning in row 13. The reason for this seems, that
> the first transaction is not terminated when the second one starts. I tried
> to look up the code in the source, but i couldnt find the right location.
> Has anyone else encountered the behaviour or know, where to lookup the
> location in the source code?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
