![]() ![]() Most recent operation stop timestamp = 09:40:02.391793 Most recent operation start timestamp = 09:40:02.391735 UOW completion status = Committed - Commit Statement Previous UOW completion timestamp = 09:40:02.079211Įlapsed time of last completed uow (sec.ms)= 0.001282 Application SnapshotĬonnection request start timestamp = 09:38:33.022561Ĭonnect request completion timestamp = 09:38:33.023248Īpplication idle time = 6 minutes 14 seconds Here you can see also UOW completion status is Committed, which I understand this app-handle has no commit-pendings pending. In other words: an "UOW Waiting" state application doing currently nothing but waiting shows an unfinished query running, which is a paradox. On the other hand, I have not explained how such connections cause batch-jobs to never finish because that is exactly what I don't know and wish to know. The application is in uow waiting state, that is, it should be waiting for work once previous work was completed. Issue happens on both but more often with dbvis. These pictures show a complex query probably coming from a dbvisualizer but sometimes the query is just a "Select current schema from sysdummy1 " and yet never finishes.Īpplications connecting to the database are Websphere Application Server (WAS) 8.5 and dbvis (dbvisualizer). There are NO locks of any kind (lock timeouts or deadlocks). The issue is: Sometimes certain requests get kind of "hung" because they don't seem to do anything yet they are still connected for hours (if not forced before) and don't release the thread which causes batch jobs to never finish until these requests are forced off.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |