You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Kumawat, Priyanka" <pr...@dxc.com> on 2022/10/18 18:55:28 UTC
DB2 database locks
Hello Team ,
We have been encountered another issue with the Database locks recently , yesterday there was been Table locks identified from the Database team , and after certain period of time we have received the below error on the Apache logs and we have to restart the tomcat/Apache instances.
: [Mon Oct 17 04:21:04.599196 2022] [mpm_event:error] [pid 10576:tid 140052698470144] AH00484: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
we needed your suggestion as how these errors can cause the Apache to go with worker exhaustion error.
Apache version - 2.4.25
*******************************************************************************************
Below are details given by DB team -
INSTANCE: db2inst
DATABASE: tirehq
TIMESTAMP: 2022-10-17.02.20.01
HOLDAPP HOLDER AGNTHLDLCK WAITTAPP WAITER WTAGNTID HOLDMODE OBJTYPE TABNAME SCHEMA WTNGSECS
--------------- ---------- ---------- --------------- ---------- --------- ---------- ------------------ ------------------------- ---------- -----------
db2bp DB2INST 25726 db2jcc_applicat WING2 26171 U TABLE_LOCK SALESDOCLI WING2 616
db2bp DB2INST 25726 db2jcc_applicat WING2 26217 U TABLE_LOCK SALESDOCLI WING2 336
db2bp DB2INST 25726 db2jcc_applicat WING2 26263 U TABLE_LOCK SALESDOCLI WING2 135
db2bp DB2INST 25726 db2jcc_applicat WING2 26276 U TABLE_LOCK SALESDOCLI WING2 13
db2bp DB2INST 25726 db2jcc_applicat WING2 26151 U TABLE_LOCK SALESDOCLI WING2 781
db2bp DB2INST 25726 db2jcc_applicat WING2 26197 U TABLE_LOCK SALESDOCLI WING2 540
db2bp DB2INST 25726 db2jcc_applicat WING2 26164 U TABLE_LOCK SALESDOCLI WING2 663
db2bp DB2INST 25726 db2jcc_applicat WING2 26210 U TABLE_LOCK SALESDOCLI WING2 420
db2bp DB2INST 25726 db2jcc_applicat WING2 26256 U TABLE_LOCK SALESDOCLI WING2 237
db2bp DB2INST 25726 db2jcc_applicat WING2 131 U TABLE_LOCK SALESDOCLI WING2 3071
db2bp DB2INST 25726 db2jcc_applicat WING2 26144 U TABLE_LOCK SALESDOCLI WING2 764
db2bp DB2INST 25726 db2jcc_applicat WING2 26269 U TABLE_LOCK SALESDOCLI WING2 75
db2bp DB2INST 25726 db2jcc_applicat WING2 26190 U TABLE_LOCK SALESDOCLI WING2 560
db2bp DB2INST 25726 db2jcc_applicat WING2 111 U TABLE_LOCK SALESDOCLI WING2 1782
db2bp DB2INST 25726 db2jcc_applicat WING2 26157 U TABLE_LOCK SALESDOCLI WING2 721
db2bp DB2INST 25726 db2jcc_applicat WING2 26203 U TABLE_LOCK SALESDOCLI WING2 459
db2bp DB2INST 25726 db2jcc_applicat WING2 26170 U TABLE_LOCK SALESDOCLI WING2 636
db2bp DB2INST 25726 db2jcc_applicat WING2 26216 U TABLE_LOCK SALESDOCLI WING2 357
db2bp DB2INST 25726 db2jcc_applicat WING2 26262 U TABLE_LOCK SALESDOCLI WING2 159
db2bp DB2INST 25726 db2jcc_applicat WING2 26275 U TABLE_LOCK SALESDOCLI WING2 16
db2bp DB2INST 25726 db2jcc_applicat WING2 26150 U TABLE_LOCK SALESDOCLI WING2 794
db2bp DB2INST 25726 db2jcc_applicat WING2 26196 U TABLE_LOCK SALESDOCLI WING2 540
db2bp DB2INST 25726 db2jcc_applicat WING2 26242 U TABLE_LOCK SALESDOCLI WING2 257
db2bp DB2INST 25726 db2jcc_applicat WING2 117 U TABLE_LOCK SALESDOCLI WING2 2806
db2bp DB2INST 25726 db2jcc_applicat WING2 26163 U TABLE_LOCK SALESDOCLI WING2 660
db2bp DB2INST 25726 db2jcc_applicat WING2 130 U TABLE_LOCK SALESDOCLI WING2 1399
db2bp DB2INST 25726 db2jcc_applicat WING2 26176 U TABLE_LOCK SALESDOCLI WING2 563
db2bp DB2INST 25726 db2jcc_applicat WING2 110 U TABLE_LOCK SALESDOCLI WING2 1527
db2bp DB2INST 25726 db2jcc_applicat WING2 26156 U TABLE_LOCK SALESDOCLI WING2 676
db2bp DB2INST 25726 db2jcc_applicat WING2 26202 U TABLE_LOCK SALESDOCLI WING2 478
db2bp DB2INST 25726 db2jcc_applicat WING2 26169 U TABLE_LOCK SALESDOCLI WING2 621
db2bp DB2INST 25726 db2jcc_applicat WING2 26215 U TABLE_LOCK SALESDOCLI WING2 338
db2bp DB2INST 25726 db2jcc_applicat WING2 26261 U TABLE_LOCK SALESDOCLI WING2 176
db2bp DB2INST 25726 db2jcc_applicat WING2 26274 U TABLE_LOCK SALESDOCLI WING2 31
db2bp DB2INST 25726 db2jcc_applicat WING2 116 U TABLE_LOCK SALESDOCLI WING2 2705
db2bp DB2INST 25726 db2jcc_applicat WING2 26162 U TABLE_LOCK SALESDOCLI WING2 663
db2bp DB2INST 25726 db2jcc_applicat WING2 26208 U TABLE_LOCK SALESDOCLI WING2 439
db2bp DB2INST 25726 db2jcc_applicat WING2 129 U TABLE_LOCK SALESDOCLI WING2 927
db2bp DB2INST 25726 db2jcc_applicat WING2 26175 U TABLE_LOCK SALESDOCLI WING2 599
db2bp DB2INST 25726 db2jcc_applicat WING2 26221 U TABLE_LOCK SALESDOCLI WING2 277
db2bp DB2INST 25726 db2jcc_applicat WING2 26267 U TABLE_LOCK SALESDOCLI WING2 117
db2bp DB2INST 25726 db2jcc_applicat WING2 109 U TABLE_LOCK SALESDOCLI WING2 1229
db2bp DB2INST 25726 db2jcc_applicat WING2 26155 U TABLE_LOCK SALESDOCLI WING2 719
db2bp DB2INST 25726 db2jcc_applicat WING2 26201 U TABLE_LOCK SALESDOCLI WING2 521
db2bp DB2INST 25726 db2jcc_applicat WING2 26214 U TABLE_LOCK SALESDOCLI WING2 378
db2bp DB2INST 25726 db2jcc_applicat WING2 26260 U TABLE_LOCK SALESDOCLI WING2 155
db2bp DB2INST 25726 db2jcc_applicat WING2 26273 U TABLE_LOCK SALESDOCLI WING2 12
db2bp DB2INST 25726 db2jcc_applicat WING2 26148 U TABLE_LOCK SALESDOCLI WING2 824
db2bp DB2INST 25726 db2jcc_applicat WING2 115 U TABLE_LOCK SALESDOCLI WING2 3294
db2bp DB2INST 25726 db2jcc_applicat WING2 26161 U TABLE_LOCK SALESDOCLI WING2 662
db2bp DB2INST 25726 db2jcc_applicat WING2 26207 U TABLE_LOCK SALESDOCLI WING2 399
db2bp DB2INST 25726 db2jcc_applicat WING2 128 U TABLE_LOCK SALESDOCLI WING2 843
db2bp DB2INST 25726 db2jcc_applicat WING2 26174 U TABLE_LOCK SALESDOCLI WING2 601
db2bp DB2INST 25726 db2jcc_applicat WING2 26220 U TABLE_LOCK SALESDOCLI WING2 317
db2bp DB2INST 25726 db2jcc_applicat WING2 26266 U TABLE_LOCK SALESDOCLI WING2 96
db2bp DB2INST 25726 db2jcc_applicat WING2 26154 U TABLE_LOCK SALESDOCLI WING2 743
db2bp DB2INST 25726 db2jcc_applicat WING2 26167 U TABLE_LOCK SALESDOCLI WING2 642
db2bp DB2INST 25726 db2jcc_applicat WING2 26259 U TABLE_LOCK SALESDOCLI WING2 195
db2bp DB2INST 25726 db2jcc_applicat WING2 134 U TABLE_LOCK SALESDOCLI WING2 2928
db2jcc_applicat WING2 135 db2bp DB2INST 25726 IX TABLE_LOCK SALESDOCLI WING2 3524
db2bp DB2INST 25726 db2jcc_applicat WING2 26272 U TABLE_LOCK SALESDOCLI WING2 36
db2bp DB2INST 25726 db2jcc_applicat WING2 26147 U TABLE_LOCK SALESDOCLI WING2 785
db2bp DB2INST 25726 db2jcc_applicat WING2 114 U TABLE_LOCK SALESDOCLI WING2 2523
db2bp DB2INST 25726 db2jcc_applicat WING2 26160 U TABLE_LOCK SALESDOCLI WING2 664
db2bp DB2INST 25726 db2jcc_applicat WING2 26081 U TABLE_LOCK SALESDOCLI WING2 1094
db2bp DB2INST 25726 db2jcc_applicat WING2 26206 U TABLE_LOCK SALESDOCLI WING2 439
db2bp DB2INST 25726 db2jcc_applicat WING2 127 U TABLE_LOCK SALESDOCLI WING2 846
db2bp DB2INST 25726 db2jcc_applicat WING2 26173 U TABLE_LOCK SALESDOCLI WING2 622
db2bp DB2INST 25726 db2jcc_applicat WING2 26219 U TABLE_LOCK SALESDOCLI WING2 298
db2bp DB2INST 25726 db2jcc_applicat WING2 26265 U TABLE_LOCK SALESDOCLI WING2 136
db2bp DB2INST 25726 db2jcc_applicat WING2 26153 U TABLE_LOCK SALESDOCLI WING2 763
db2bp DB2INST 25726 db2jcc_applicat WING2 26199 U TABLE_LOCK SALESDOCLI WING2 500
db2bp DB2INST 25726 db2jcc_applicat WING2 26166 U TABLE_LOCK SALESDOCLI WING2 638
db2bp DB2INST 25726 db2jcc_applicat WING2 26212 U TABLE_LOCK SALESDOCLI WING2 378
db2bp DB2INST 25726 db2jcc_applicat WING2 26258 U TABLE_LOCK SALESDOCLI WING2 197
db2bp DB2INST 25726 db2jcc_applicat WING2 133 U TABLE_LOCK SALESDOCLI WING2 1794
db2bp DB2INST 25726 db2jcc_applicat WING2 26100 U TABLE_LOCK SALESDOCLI WING2 870
db2bp DB2INST 25726 db2jcc_applicat WING2 26146 U TABLE_LOCK SALESDOCLI WING2 842
db2bp DB2INST 25726 db2jcc_applicat WING2 26271 U TABLE_LOCK SALESDOCLI WING2 55
db2bp DB2INST 25726 db2jcc_applicat WING2 113 U TABLE_LOCK SALESDOCLI WING2 2624
db2bp DB2INST 25726 db2jcc_applicat WING2 26159 U TABLE_LOCK SALESDOCLI WING2 682
db2bp DB2INST 25726 db2jcc_applicat WING2 26251 U TABLE_LOCK SALESDOCLI WING2 256
db2bp DB2INST 25726 db2jcc_applicat WING2 126 U TABLE_LOCK SALESDOCLI WING2 865
db2bp DB2INST 25726 db2jcc_applicat WING2 26218 U TABLE_LOCK SALESDOCLI WING2 319
db2bp DB2INST 25726 db2jcc_applicat WING2 26264 U TABLE_LOCK SALESDOCLI WING2 134
db2bp DB2INST 25726 db2jcc_applicat WING2 26139 U TABLE_LOCK SALESDOCLI WING2 781
db2bp DB2INST 25726 db2jcc_applicat WING2 26152 U TABLE_LOCK SALESDOCLI WING2 743
db2bp DB2INST 25726 db2jcc_applicat WING2 26198 U TABLE_LOCK SALESDOCLI WING2 499
db2bp DB2INST 25726 db2jcc_applicat WING2 26165 U TABLE_LOCK SALESDOCLI WING2 658
db2bp DB2INST 25726 db2jcc_applicat WING2 26211 U TABLE_LOCK SALESDOCLI WING2 417
db2bp DB2INST 25726 db2jcc_applicat WING2 26257 U TABLE_LOCK SALESDOCLI WING2 218
db2bp DB2INST 25726 db2jcc_applicat WING2 132 U TABLE_LOCK SALESDOCLI WING2 3172
db2bp DB2INST 25726 db2jcc_applicat WING2 26178 U TABLE_LOCK SALESDOCLI WING2 577
db2bp DB2INST 25726 db2jcc_applicat WING2 26099 U TABLE_LOCK SALESDOCLI WING2 804
db2bp DB2INST 25726 db2jcc_applicat WING2 26145 U TABLE_LOCK SALESDOCLI WING2 725
db2bp DB2INST 25726 db2jcc_applicat WING2 26270 U TABLE_LOCK SALESDOCLI WING2 73
db2bp DB2INST 25726 db2jcc_applicat WING2 26191 U TABLE_LOCK SALESDOCLI WING2 539
db2bp DB2INST 25726 db2jcc_applicat WING2 112 U TABLE_LOCK SALESDOCLI WING2 2442
db2bp DB2INST 25726 db2jcc_applicat WING2 26158 U TABLE_LOCK SALESDOCLI WING2 703
Thanks & Regards,
Priyanka Kumawat | Middleware Admin
T +91.7879364483
EMail - priyanka.kumawat@dxc.com<ma...@dxc.com>
DL - ams-leveraged-webadmin-offshore@dxc.com<ma...@dxc.com>
DXC Technology
Thanks & Regards,
Priyanka Kumawat | Middleware Admin
T +91.7879364483
EMail - priyanka.kumawat@dxc.com<ma...@dxc.com>
DL - ams-leveraged-webadmin-offshore@dxc.com<ma...@dxc.com>
DXC Technology
DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
RE: DB2 database locks [EXTERNAL]
Posted by "Beard, Shawn" <SB...@wrberkley.com.INVALID>.
Make changes to your mpm config in Apache. It sounds like there is increased traffic. It could be that you reach the max then it holds all those connections. There are a lot of online resources that have Apache Webserver recommended mpm settings and models to use for high traffic systems.
Also check with the application devs for any changes that have been made that might increase this traffic. A database lock means that something is updating the database while something else needs to update at the same time.
Shawn Beard • Sr. Systems Engineer
Middleware Engineering
[cid:image806415.png@89620066.06C47AAC]
3840 109th Street , Urbandale , IA 50322
Phone: +1-515-564-2528<tel:+1-515-564-2528>
Email: SBeard@wrberkley.com<ma...@wrberkley.com>
Website: https://berkleytechnologyservices.com/
[cid:image361079.jpg@4E765429.20B14B49]
Technology Leadership Unleashing Business Potential
-----Original Message-----
From: Kumawat, Priyanka <pr...@dxc.com>
Sent: Tuesday, October 18, 2022 1:55 PM
To: users@tomcat.apache.org
Subject: DB2 database locks [EXTERNAL]
** CAUTION: External message
Hello Team ,
We have been encountered another issue with the Database locks recently , yesterday there was been Table locks identified from the Database team , and after certain period of time we have received the below error on the Apache logs and we have to restart the tomcat/Apache instances.
: [Mon Oct 17 04:21:04.599196 2022] [mpm_event:error] [pid 10576:tid 140052698470144] AH00484: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
we needed your suggestion as how these errors can cause the Apache to go with worker exhaustion error.
Apache version - 2.4.25
*******************************************************************************************
Below are details given by DB team -
INSTANCE: db2inst
DATABASE: tirehq
TIMESTAMP: 2022-10-17.02.20.01
HOLDAPP HOLDER AGNTHLDLCK WAITTAPP WAITER WTAGNTID HOLDMODE OBJTYPE TABNAME SCHEMA WTNGSECS
--------------- ---------- ---------- --------------- ---------- --------- ---------- ------------------ ------------------------- ---------- -----------
db2bp DB2INST 25726 db2jcc_applicat WING2 26171 U TABLE_LOCK SALESDOCLI WING2 616
db2bp DB2INST 25726 db2jcc_applicat WING2 26217 U TABLE_LOCK SALESDOCLI WING2 336
db2bp DB2INST 25726 db2jcc_applicat WING2 26263 U TABLE_LOCK SALESDOCLI WING2 135
db2bp DB2INST 25726 db2jcc_applicat WING2 26276 U TABLE_LOCK SALESDOCLI WING2 13
db2bp DB2INST 25726 db2jcc_applicat WING2 26151 U TABLE_LOCK SALESDOCLI WING2 781
db2bp DB2INST 25726 db2jcc_applicat WING2 26197 U TABLE_LOCK SALESDOCLI WING2 540
db2bp DB2INST 25726 db2jcc_applicat WING2 26164 U TABLE_LOCK SALESDOCLI WING2 663
db2bp DB2INST 25726 db2jcc_applicat WING2 26210 U TABLE_LOCK SALESDOCLI WING2 420
db2bp DB2INST 25726 db2jcc_applicat WING2 26256 U TABLE_LOCK SALESDOCLI WING2 237
db2bp DB2INST 25726 db2jcc_applicat WING2 131 U TABLE_LOCK SALESDOCLI WING2 3071
db2bp DB2INST 25726 db2jcc_applicat WING2 26144 U TABLE_LOCK SALESDOCLI WING2 764
db2bp DB2INST 25726 db2jcc_applicat WING2 26269 U TABLE_LOCK SALESDOCLI WING2 75
db2bp DB2INST 25726 db2jcc_applicat WING2 26190 U TABLE_LOCK SALESDOCLI WING2 560
db2bp DB2INST 25726 db2jcc_applicat WING2 111 U TABLE_LOCK SALESDOCLI WING2 1782
db2bp DB2INST 25726 db2jcc_applicat WING2 26157 U TABLE_LOCK SALESDOCLI WING2 721
db2bp DB2INST 25726 db2jcc_applicat WING2 26203 U TABLE_LOCK SALESDOCLI WING2 459
db2bp DB2INST 25726 db2jcc_applicat WING2 26170 U TABLE_LOCK SALESDOCLI WING2 636
db2bp DB2INST 25726 db2jcc_applicat WING2 26216 U TABLE_LOCK SALESDOCLI WING2 357
db2bp DB2INST 25726 db2jcc_applicat WING2 26262 U TABLE_LOCK SALESDOCLI WING2 159
db2bp DB2INST 25726 db2jcc_applicat WING2 26275 U TABLE_LOCK SALESDOCLI WING2 16
db2bp DB2INST 25726 db2jcc_applicat WING2 26150 U TABLE_LOCK SALESDOCLI WING2 794
db2bp DB2INST 25726 db2jcc_applicat WING2 26196 U TABLE_LOCK SALESDOCLI WING2 540
db2bp DB2INST 25726 db2jcc_applicat WING2 26242 U TABLE_LOCK SALESDOCLI WING2 257
db2bp DB2INST 25726 db2jcc_applicat WING2 117 U TABLE_LOCK SALESDOCLI WING2 2806
db2bp DB2INST 25726 db2jcc_applicat WING2 26163 U TABLE_LOCK SALESDOCLI WING2 660
db2bp DB2INST 25726 db2jcc_applicat WING2 130 U TABLE_LOCK SALESDOCLI WING2 1399
db2bp DB2INST 25726 db2jcc_applicat WING2 26176 U TABLE_LOCK SALESDOCLI WING2 563
db2bp DB2INST 25726 db2jcc_applicat WING2 110 U TABLE_LOCK SALESDOCLI WING2 1527
db2bp DB2INST 25726 db2jcc_applicat WING2 26156 U TABLE_LOCK SALESDOCLI WING2 676
db2bp DB2INST 25726 db2jcc_applicat WING2 26202 U TABLE_LOCK SALESDOCLI WING2 478
db2bp DB2INST 25726 db2jcc_applicat WING2 26169 U TABLE_LOCK SALESDOCLI WING2 621
db2bp DB2INST 25726 db2jcc_applicat WING2 26215 U TABLE_LOCK SALESDOCLI WING2 338
db2bp DB2INST 25726 db2jcc_applicat WING2 26261 U TABLE_LOCK SALESDOCLI WING2 176
db2bp DB2INST 25726 db2jcc_applicat WING2 26274 U TABLE_LOCK SALESDOCLI WING2 31
db2bp DB2INST 25726 db2jcc_applicat WING2 116 U TABLE_LOCK SALESDOCLI WING2 2705
db2bp DB2INST 25726 db2jcc_applicat WING2 26162 U TABLE_LOCK SALESDOCLI WING2 663
db2bp DB2INST 25726 db2jcc_applicat WING2 26208 U TABLE_LOCK SALESDOCLI WING2 439
db2bp DB2INST 25726 db2jcc_applicat WING2 129 U TABLE_LOCK SALESDOCLI WING2 927
db2bp DB2INST 25726 db2jcc_applicat WING2 26175 U TABLE_LOCK SALESDOCLI WING2 599
db2bp DB2INST 25726 db2jcc_applicat WING2 26221 U TABLE_LOCK SALESDOCLI WING2 277
db2bp DB2INST 25726 db2jcc_applicat WING2 26267 U TABLE_LOCK SALESDOCLI WING2 117
db2bp DB2INST 25726 db2jcc_applicat WING2 109 U TABLE_LOCK SALESDOCLI WING2 1229
db2bp DB2INST 25726 db2jcc_applicat WING2 26155 U TABLE_LOCK SALESDOCLI WING2 719
db2bp DB2INST 25726 db2jcc_applicat WING2 26201 U TABLE_LOCK SALESDOCLI WING2 521
db2bp DB2INST 25726 db2jcc_applicat WING2 26214 U TABLE_LOCK SALESDOCLI WING2 378
db2bp DB2INST 25726 db2jcc_applicat WING2 26260 U TABLE_LOCK SALESDOCLI WING2 155
db2bp DB2INST 25726 db2jcc_applicat WING2 26273 U TABLE_LOCK SALESDOCLI WING2 12
db2bp DB2INST 25726 db2jcc_applicat WING2 26148 U TABLE_LOCK SALESDOCLI WING2 824
db2bp DB2INST 25726 db2jcc_applicat WING2 115 U TABLE_LOCK SALESDOCLI WING2 3294
db2bp DB2INST 25726 db2jcc_applicat WING2 26161 U TABLE_LOCK SALESDOCLI WING2 662
db2bp DB2INST 25726 db2jcc_applicat WING2 26207 U TABLE_LOCK SALESDOCLI WING2 399
db2bp DB2INST 25726 db2jcc_applicat WING2 128 U TABLE_LOCK SALESDOCLI WING2 843
db2bp DB2INST 25726 db2jcc_applicat WING2 26174 U TABLE_LOCK SALESDOCLI WING2 601
db2bp DB2INST 25726 db2jcc_applicat WING2 26220 U TABLE_LOCK SALESDOCLI WING2 317
db2bp DB2INST 25726 db2jcc_applicat WING2 26266 U TABLE_LOCK SALESDOCLI WING2 96
db2bp DB2INST 25726 db2jcc_applicat WING2 26154 U TABLE_LOCK SALESDOCLI WING2 743
db2bp DB2INST 25726 db2jcc_applicat WING2 26167 U TABLE_LOCK SALESDOCLI WING2 642
db2bp DB2INST 25726 db2jcc_applicat WING2 26259 U TABLE_LOCK SALESDOCLI WING2 195
db2bp DB2INST 25726 db2jcc_applicat WING2 134 U TABLE_LOCK SALESDOCLI WING2 2928
db2jcc_applicat WING2 135 db2bp DB2INST 25726 IX TABLE_LOCK SALESDOCLI WING2 3524
db2bp DB2INST 25726 db2jcc_applicat WING2 26272 U TABLE_LOCK SALESDOCLI WING2 36
db2bp DB2INST 25726 db2jcc_applicat WING2 26147 U TABLE_LOCK SALESDOCLI WING2 785
db2bp DB2INST 25726 db2jcc_applicat WING2 114 U TABLE_LOCK SALESDOCLI WING2 2523
db2bp DB2INST 25726 db2jcc_applicat WING2 26160 U TABLE_LOCK SALESDOCLI WING2 664
db2bp DB2INST 25726 db2jcc_applicat WING2 26081 U TABLE_LOCK SALESDOCLI WING2 1094
db2bp DB2INST 25726 db2jcc_applicat WING2 26206 U TABLE_LOCK SALESDOCLI WING2 439
db2bp DB2INST 25726 db2jcc_applicat WING2 127 U TABLE_LOCK SALESDOCLI WING2 846
db2bp DB2INST 25726 db2jcc_applicat WING2 26173 U TABLE_LOCK SALESDOCLI WING2 622
db2bp DB2INST 25726 db2jcc_applicat WING2 26219 U TABLE_LOCK SALESDOCLI WING2 298
db2bp DB2INST 25726 db2jcc_applicat WING2 26265 U TABLE_LOCK SALESDOCLI WING2 136
db2bp DB2INST 25726 db2jcc_applicat WING2 26153 U TABLE_LOCK SALESDOCLI WING2 763
db2bp DB2INST 25726 db2jcc_applicat WING2 26199 U TABLE_LOCK SALESDOCLI WING2 500
db2bp DB2INST 25726 db2jcc_applicat WING2 26166 U TABLE_LOCK SALESDOCLI WING2 638
db2bp DB2INST 25726 db2jcc_applicat WING2 26212 U TABLE_LOCK SALESDOCLI WING2 378
db2bp DB2INST 25726 db2jcc_applicat WING2 26258 U TABLE_LOCK SALESDOCLI WING2 197
db2bp DB2INST 25726 db2jcc_applicat WING2 133 U TABLE_LOCK SALESDOCLI WING2 1794
db2bp DB2INST 25726 db2jcc_applicat WING2 26100 U TABLE_LOCK SALESDOCLI WING2 870
db2bp DB2INST 25726 db2jcc_applicat WING2 26146 U TABLE_LOCK SALESDOCLI WING2 842
db2bp DB2INST 25726 db2jcc_applicat WING2 26271 U TABLE_LOCK SALESDOCLI WING2 55
db2bp DB2INST 25726 db2jcc_applicat WING2 113 U TABLE_LOCK SALESDOCLI WING2 2624
db2bp DB2INST 25726 db2jcc_applicat WING2 26159 U TABLE_LOCK SALESDOCLI WING2 682
db2bp DB2INST 25726 db2jcc_applicat WING2 26251 U TABLE_LOCK SALESDOCLI WING2 256
db2bp DB2INST 25726 db2jcc_applicat WING2 126 U TABLE_LOCK SALESDOCLI WING2 865
db2bp DB2INST 25726 db2jcc_applicat WING2 26218 U TABLE_LOCK SALESDOCLI WING2 319
db2bp DB2INST 25726 db2jcc_applicat WING2 26264 U TABLE_LOCK SALESDOCLI WING2 134
db2bp DB2INST 25726 db2jcc_applicat WING2 26139 U TABLE_LOCK SALESDOCLI WING2 781
db2bp DB2INST 25726 db2jcc_applicat WING2 26152 U TABLE_LOCK SALESDOCLI WING2 743
db2bp DB2INST 25726 db2jcc_applicat WING2 26198 U TABLE_LOCK SALESDOCLI WING2 499
db2bp DB2INST 25726 db2jcc_applicat WING2 26165 U TABLE_LOCK SALESDOCLI WING2 658
db2bp DB2INST 25726 db2jcc_applicat WING2 26211 U TABLE_LOCK SALESDOCLI WING2 417
db2bp DB2INST 25726 db2jcc_applicat WING2 26257 U TABLE_LOCK SALESDOCLI WING2 218
db2bp DB2INST 25726 db2jcc_applicat WING2 132 U TABLE_LOCK SALESDOCLI WING2 3172
db2bp DB2INST 25726 db2jcc_applicat WING2 26178 U TABLE_LOCK SALESDOCLI WING2 577
db2bp DB2INST 25726 db2jcc_applicat WING2 26099 U TABLE_LOCK SALESDOCLI WING2 804
db2bp DB2INST 25726 db2jcc_applicat WING2 26145 U TABLE_LOCK SALESDOCLI WING2 725
db2bp DB2INST 25726 db2jcc_applicat WING2 26270 U TABLE_LOCK SALESDOCLI WING2 73
db2bp DB2INST 25726 db2jcc_applicat WING2 26191 U TABLE_LOCK SALESDOCLI WING2 539
db2bp DB2INST 25726 db2jcc_applicat WING2 112 U TABLE_LOCK SALESDOCLI WING2 2442
db2bp DB2INST 25726 db2jcc_applicat WING2 26158 U TABLE_LOCK SALESDOCLI WING2 703
Thanks & Regards,
Priyanka Kumawat | Middleware Admin
T +91.7879364483
EMail - priyanka.kumawat@dxc.com<ma...@dxc.com>
DL - ams-leveraged-webadmin-offshore@dxc.com<ma...@dxc.com>
DXC Technology
Thanks & Regards,
Priyanka Kumawat | Middleware Admin
T +91.7879364483
EMail - priyanka.kumawat@dxc.com<ma...@dxc.com>
DL - ams-leveraged-webadmin-offshore@dxc.com<ma...@dxc.com>
DXC Technology
DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
CONFIDENTIALITY NOTICE: This e-mail and the transmitted documents contain private, privileged and confidential information belonging to the sender. The information therein is solely for the use of the addressee. If your receipt of this transmission has occurred as the result of an error, please immediately notify us so we can arrange for the return of the documents. In such circumstances, you are advised that you may not disclose, copy, distribute or take any other action in reliance on the information transmitted.
Please know that our company will never ask that you transfer money by wire or check without verbal confirmation. If you receive an e-mail from our company or any third party purporting to represent our company requesting money be transferred, please report it to me immediately. Our company will only transfer money after receiving verbal confirmation.
Re: [OT] DB2 database locks
Posted by Christopher Schultz <ch...@christopherschultz.net>.
Simon,
On 10/21/22 15:12, Simon Matter wrote:
> Hi,
>
>> Hello Christopher,
>>
>> Thankyou !
>>
>> Seems we are not using the connection pooling from Tomcat side , below are
>> the DB configuration parameters on context.xml file, do not see any
>> connection pool details here.
>>
>> <Resource
>> name="jdbc/db2"
>> auth="Container"
>> type="javax.sql.DataSource"
>> driverClassName="com.ibm.db2.jcc.DB2Driver"
>> url="jdbc:db2://30.177.13.12:3700/TIREHQ"
>> maxActive="200"
>> maxIdle="30"
>> maxWait="10000"
>> username="xxxxxx"
>> password="*******" />
>
> Don't forget to change this password!
:D
Hmm...
> "ip": 30.177.13.12
> "country_name": United States
> "state_prov": Ohio
> "city": Columbus
> "latitude": 39.97883
> "longitude": -82.89573
> "time_zone": America/New_York
> "isp": DoD Network Information Center
> "currency": US Dollar
DoD? I guess the DoD probably does have a Tire HQ.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: DB2 database locks
Posted by Simon Matter <si...@invoca.ch>.
Hi,
> Hello Christopher,
>
> Thankyou !
>
> Seems we are not using the connection pooling from Tomcat side , below are
> the DB configuration parameters on context.xml file, do not see any
> connection pool details here.
>
> <Resource
> name="jdbc/db2"
> auth="Container"
> type="javax.sql.DataSource"
> driverClassName="com.ibm.db2.jcc.DB2Driver"
> url="jdbc:db2://30.177.13.12:3700/TIREHQ"
> maxActive="200"
> maxIdle="30"
> maxWait="10000"
> username="xxxxxx"
> password="*******" />
Don't forget to change this password!
Regards,
Simon
> <Resource
>
>> I have one more question , Sorry to bother again .
>
> Can the below parameters can aid us with this issue , as given on the
> below Technote , if yes how we need to determine the timings for these
> parameters.
>
> minEvictableIdleTimeMillis
> timeBetweenEvictionRunsMillis
> validationQuery
> removeAbandoned
> removeAbandonedTimeout
>
> https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0098601
>
>
> Thanks & Regards,
>
> Priyanka Kumawat | Middleware Admin
> T +91.7879364483
> EMail - priyanka.kumawat@dxc.com
> DL - ams-leveraged-webadmin-offshore@dxc.com
>
> DXC Technology
>
> -----Original Message-----
> From: Christopher Schultz <ch...@christopherschultz.net>
> Sent: 21 October 2022 00:50
> To: Kumawat, Priyanka <pr...@dxc.com>; Tomcat Users List
> <us...@tomcat.apache.org>
> Subject: Re: DB2 database locks
>
> Priyanka,
>
> On 10/20/22 13:15, Kumawat, Priyanka wrote:
>> Thankyou muck for the explanation for this !!! we have got from below
>> mail that it is likely to be an application coding issue and they
>> needs to fix or use commit etc for long running transactions .
>>
>> The one steps that you have given below to set the "query timeout" ,
>> is this one we can set up on Tomcat side?
> That depends upon how you are obtaining you database connections. If you
> are using a connection pool provided by Tomcat (either tomcat-pool or
> dbcp-pool) then you can configure according to the documentation for
> whichever component you are using (they have similar but different
> configuration styles).
>
> -chris
>
>
> DXC Technology Company -- This message is transmitted to you by or on
> behalf of DXC Technology Company or one of its affiliates. It is intended
> exclusively for the addressee. The substance of this message, along with
> any attachments, may contain proprietary, confidential or privileged
> information or information that is otherwise legally exempt from
> disclosure. Any unauthorized review, use, disclosure or distribution is
> prohibited. If you are not the intended recipient of this message, you are
> not authorized to read, print, retain, copy or disseminate any part of
> this message. If you have received this message in error, please destroy
> and delete all copies and notify the sender by return e-mail. Regardless
> of content, this e-mail shall not operate to bind DXC Technology Company
> or any of its affiliates to any order or other contract unless pursuant to
> explicit written agreement or government initiative expressly permitting
> the use of e-mail for such purpose.
> �Т���������������������������������������������������������������������ХF�V�7V'67&�&R�R���âW6W'2�V�7V'67&�&TF��6B�6�R��&pФf�"FF�F����6����G2�R���âW6W'2ֆV�F��6B�6�R��&pР
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: DB2 database locks
Posted by "Kumawat, Priyanka" <pr...@dxc.com>.
Hello Christopher,
Thankyou !
Seems we are not using the connection pooling from Tomcat side , below are the DB configuration parameters on context.xml file, do not see any connection pool details here.
<Resource
name="jdbc/db2"
auth="Container"
type="javax.sql.DataSource"
driverClassName="com.ibm.db2.jcc.DB2Driver"
url="jdbc:db2://30.177.13.12:3700/TIREHQ"
maxActive="200"
maxIdle="30"
maxWait="10000"
username="wing2"
password="w1ngf00t" />
<Resource
> I have one more question , Sorry to bother again .
Can the below parameters can aid us with this issue , as given on the below Technote , if yes how we need to determine the timings for these parameters.
minEvictableIdleTimeMillis
timeBetweenEvictionRunsMillis
validationQuery
removeAbandoned
removeAbandonedTimeout
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0098601
Thanks & Regards,
Priyanka Kumawat | Middleware Admin
T +91.7879364483
EMail - priyanka.kumawat@dxc.com
DL - ams-leveraged-webadmin-offshore@dxc.com
DXC Technology
-----Original Message-----
From: Christopher Schultz <ch...@christopherschultz.net>
Sent: 21 October 2022 00:50
To: Kumawat, Priyanka <pr...@dxc.com>; Tomcat Users List <us...@tomcat.apache.org>
Subject: Re: DB2 database locks
Priyanka,
On 10/20/22 13:15, Kumawat, Priyanka wrote:
> Thankyou muck for the explanation for this !!! we have got from below
> mail that it is likely to be an application coding issue and they
> needs to fix or use commit etc for long running transactions .
>
> The one steps that you have given below to set the "query timeout" ,
> is this one we can set up on Tomcat side?
That depends upon how you are obtaining you database connections. If you are using a connection pool provided by Tomcat (either tomcat-pool or
dbcp-pool) then you can configure according to the documentation for whichever component you are using (they have similar but different configuration styles).
-chris
DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
Re: DB2 database locks
Posted by Christopher Schultz <ch...@christopherschultz.net>.
Priyanka,
On 10/20/22 15:50, Kumawat, Priyanka wrote:
> Seems we are not using the connection pooling from Tomcat side ,
> below are the DB configuration parameters on context.xml file, do not
> see any connection pool details here.
>
> <Resource
> name="jdbc/db2"
> auth="Container"
> type="javax.sql.DataSource"
> driverClassName="com.ibm.db2.jcc.DB2Driver"
> url="jdbc:db2://30.177.13.12:3700/TIREHQ"
> maxActive="200"
> maxIdle="30"
> maxWait="10000"
???!
The above is /absolutely/ the configuration of a database connection
pool. Even if you didn't recognize <Resource> to mean a DB connection
pool, certainly the host and port should have drawn your eye.
You are using Tomcat's built-in DBCP2-based connection pool. You can
find the configuration parameters online. I would highly recommend
reading about the "abandoned" capabilities of the connection pool, and
using them.
>> I have one more question , Sorry to bother again .
>
> Can the below parameters can aid us with this issue , as given on
> the below Technote , if yes how we need to determine the timings for
> these parameters.
>
> minEvictableIdleTimeMillis
> timeBetweenEvictionRunsMillis
> validationQuery
> removeAbandoned
> removeAbandonedTimeout
The validation query can help with ensuring that a connection borrowed
from the pool is still actually able to perform transactions. If you
aren't having any problems with your application being able to query,
then don't worry about that.
The eviction stuff has more to do with maintaining the smallest number
of connections to the database if they are not being used.
The abandoned stuff will help you identify bugs in your application, and
you should DEFINITELY enable these, even in production.
My advice would be to use the "abandoned" features in development as
well with a FIXED-size connection pool containing exactly one
connection. Give your application's apparently leakiness, I'm sure
you'll find 50 bugs during your first day and get them fixed quickly.
Hope that helps,
-chris
> -----Original Message-----
> From: Christopher Schultz <ch...@christopherschultz.net>
> Sent: 21 October 2022 00:50
> To: Kumawat, Priyanka <pr...@dxc.com>; Tomcat Users List <us...@tomcat.apache.org>
> Subject: Re: DB2 database locks
>
> Priyanka,
>
> On 10/20/22 13:15, Kumawat, Priyanka wrote:
>> Thankyou muck for the explanation for this !!! we have got from below
>> mail that it is likely to be an application coding issue and they
>> needs to fix or use commit etc for long running transactions .
>>
>> The one steps that you have given below to set the "query timeout" ,
>> is this one we can set up on Tomcat side?
> That depends upon how you are obtaining you database connections. If you are using a connection pool provided by Tomcat (either tomcat-pool or
> dbcp-pool) then you can configure according to the documentation for whichever component you are using (they have similar but different configuration styles).
>
> -chris
>
>
> DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: DB2 database locks
Posted by "Kumawat, Priyanka" <pr...@dxc.com>.
Hello Christopher,
Thankyou !
Seems we are not using the connection pooling from Tomcat side , below are the DB configuration parameters on context.xml file, do not see any connection pool details here.
<Resource
name="jdbc/db2"
auth="Container"
type="javax.sql.DataSource"
driverClassName="com.ibm.db2.jcc.DB2Driver"
url="jdbc:db2://30.177.13.12:3700/TIREHQ"
maxActive="200"
maxIdle="30"
maxWait="10000"
<Resource
> I have one more question , Sorry to bother again .
Can the below parameters can aid us with this issue , as given on the below Technote , if yes how we need to determine the timings for these parameters.
minEvictableIdleTimeMillis
timeBetweenEvictionRunsMillis
validationQuery
removeAbandoned
removeAbandonedTimeout
https://clicktime.symantec.com/15tpDJaiWQgJkidLe87mk?h=yWdfcnF5c5AA3mR_NqzsE2Vn6i1-jvPL-SPbx3NMDQ8=&u=https://support.hcltechsw.com/csm?id%3Dkb_article%26sysparm_article%3DKB0098601
Thanks & Regards,
Priyanka Kumawat | Middleware Admin
T +91.7879364483
EMail - priyanka.kumawat@dxc.com
DL - ams-leveraged-webadmin-offshore@dxc.com
DXC Technology
-----Original Message-----
From: Christopher Schultz <ch...@christopherschultz.net>
Sent: 21 October 2022 00:50
To: Kumawat, Priyanka <pr...@dxc.com>; Tomcat Users List <us...@tomcat.apache.org>
Subject: Re: DB2 database locks
Priyanka,
On 10/20/22 13:15, Kumawat, Priyanka wrote:
> Thankyou muck for the explanation for this !!! we have got from below
> mail that it is likely to be an application coding issue and they
> needs to fix or use commit etc for long running transactions .
>
> The one steps that you have given below to set the "query timeout" ,
> is this one we can set up on Tomcat side?
That depends upon how you are obtaining you database connections. If you are using a connection pool provided by Tomcat (either tomcat-pool or
dbcp-pool) then you can configure according to the documentation for whichever component you are using (they have similar but different configuration styles).
-chris
DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
Re: DB2 database locks
Posted by Christopher Schultz <ch...@christopherschultz.net>.
Priyanka,
On 10/20/22 13:15, Kumawat, Priyanka wrote:
> Thankyou muck for the explanation for this !!! we have got from below
> mail that it is likely to be an application coding issue and they
> needs to fix or use commit etc for long running transactions .
>
> The one steps that you have given below to set the "query timeout" ,
> is this one we can set up on Tomcat side?
That depends upon how you are obtaining you database connections. If you
are using a connection pool provided by Tomcat (either tomcat-pool or
dbcp-pool) then you can configure according to the documentation for
whichever component you are using (they have similar but different
configuration styles).
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: DB2 database locks
Posted by "Kumawat, Priyanka" <pr...@dxc.com>.
Hi Christopher ,
Thankyou muck for the explanation for this !!! we have got from below mail that it is likely to be an application coding issue and they needs to fix or use commit etc for long running transactions .
The one steps that you have given below to set the "query timeout" , is this one we can set up on Tomcat side ?
Something else that may help in your situation as a band-aid would be to set a "query timeout" on your connections to abandon any query that takes too long. You could set this to a very long timeout like 60 seconds to ensure that your application, if it does get tied-up like this, will at least eventually become available without you having to restart your application server(s).
Thanks & Regards,
Priyanka Kumawat | Middleware Admin
T +91.7879364483
EMail - priyanka.kumawat@dxc.com
DL - ams-leveraged-webadmin-offshore@dxc.com
DXC Technology
-----Original Message-----
From: Christopher Schultz <ch...@christopherschultz.net>
Sent: 19 October 2022 21:28
To: Tomcat Users List <us...@tomcat.apache.org>; Kumawat, Priyanka <pr...@dxc.com>
Subject: Re: DB2 database locks
Priyanka,
Before I respond further, database lock problems are almost certainly not being caused by Tomcat itself. It's far more likely that the
application(s) deployed on Tomcat are responsible for the problem.
Please see below for additional comments.
On 10/18/22 14:55, Kumawat, Priyanka wrote:
> We have been encountered another issue with the Database locks
> recently , yesterday there was been Table locks identified from the
> Database team , and after certain period of time we have received the
> below error on the Apache logs and we have to restart the
> tomcat/Apache instances. >
>
> : [Mon Oct 17 04:21:04.599196 2022] [mpm_event:error] [pid 10576:tid
> 140052698470144] AH00484: server reached MaxRequestWorkers setting,
> consider raising the MaxRequestWorkers setting
This error message is unrelated to database locks, but if you have locked transactions on the database server, that may cause your application threads to stall and block-up the whole network.
> we needed your suggestion as how these errors can cause the Apache to
> go with worker exhaustion error.
>
> Apache version - 2.4.25
Note that this is the Apache httpd version, which is "old" but if you are using a package-managed version might not be actually out of date.
You should check to ensure you are running the latest version of httpd, otherwise you may be exposing you and your users to security vulnerabilities.
> HOLDAPP HOLDER AGNTHLDLCK WAITTAPP WAITER WTAGNTID HOLDMODE OBJTYPE TABNAME SCHEMA WTNGSECS
>
> --------------- ---------- ---------- --------------- ----------
> --------- ---------- ------------------ -------------------------
> ---------- -----------
>
> db2bp DB2INST 25726 db2jcc_applicat WING2 26171 U TABLE_LOCK SALESDOCLI WING2 616
Tomcat can be configured to perform some database operations on your behalf. Among those operations are the following:
1. User authentication
2. Durable session data storage
Neither of those, I suspect, would be using a table called "SALESDOCLI"
and so I repeat my suspicion that your application is at fault, not Tomcat.
There is some good news, though: all the locked tables are the same, so it should be easy to check your application for accesses to that table and see what may be wrong.
I highly recommend that you and/or your programmers read this article for more information about database connection resource management:
https://clicktime.symantec.com/15tStamh3A9TqmP1AZ3rW?h=HtKkO_1alkGcAx1CwAu6RMqlIgFQDAMkZXZP9O3OwkA=&u=https://blog.christopherschultz.net/2009/03/16/properly-handling-pooled-jdbc-connections/
Something else that may help in your situation as a band-aid would be to set a "query timeout" on your connections to abandon any query that takes too long. You could set this to a very long timeout like 60 seconds to ensure that your application, if it does get tied-up like this, will at least eventually become available without you having to restart your application server(s).
Hope that helps,
-chris
DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
Re: DB2 database locks
Posted by Christopher Schultz <ch...@christopherschultz.net>.
Priyanka,
Before I respond further, database lock problems are almost certainly
not being caused by Tomcat itself. It's far more likely that the
application(s) deployed on Tomcat are responsible for the problem.
Please see below for additional comments.
On 10/18/22 14:55, Kumawat, Priyanka wrote:
> We have been encountered another issue with the Database locks
> recently , yesterday there was been Table locks identified from the
> Database team , and after certain period of time we have received
> the below error on the Apache logs and we have to restart the
> tomcat/Apache instances. >
>
> : [Mon Oct 17 04:21:04.599196 2022] [mpm_event:error] [pid 10576:tid
> 140052698470144] AH00484: server reached MaxRequestWorkers setting,
> consider raising the MaxRequestWorkers setting
This error message is unrelated to database locks, but if you have
locked transactions on the database server, that may cause your
application threads to stall and block-up the whole network.
> we needed your suggestion as how these errors can cause the Apache
> to go with worker exhaustion error.
>
> Apache version - 2.4.25
Note that this is the Apache httpd version, which is "old" but if you
are using a package-managed version might not be actually out of date.
You should check to ensure you are running the latest version of httpd,
otherwise you may be exposing you and your users to security
vulnerabilities.
> HOLDAPP HOLDER AGNTHLDLCK WAITTAPP WAITER WTAGNTID HOLDMODE OBJTYPE TABNAME SCHEMA WTNGSECS
>
> --------------- ---------- ---------- --------------- ---------- --------- ---------- ------------------ ------------------------- ---------- -----------
>
> db2bp DB2INST 25726 db2jcc_applicat WING2 26171 U TABLE_LOCK SALESDOCLI WING2 616
Tomcat can be configured to perform some database operations on your
behalf. Among those operations are the following:
1. User authentication
2. Durable session data storage
Neither of those, I suspect, would be using a table called "SALESDOCLI"
and so I repeat my suspicion that your application is at fault, not Tomcat.
There is some good news, though: all the locked tables are the same, so
it should be easy to check your application for accesses to that table
and see what may be wrong.
I highly recommend that you and/or your programmers read this article
for more information about database connection resource management:
https://blog.christopherschultz.net/2009/03/16/properly-handling-pooled-jdbc-connections/
Something else that may help in your situation as a band-aid would be to
set a "query timeout" on your connections to abandon any query that
takes too long. You could set this to a very long timeout like 60
seconds to ensure that your application, if it does get tied-up like
this, will at least eventually become available without you having to
restart your application server(s).
Hope that helps,
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org