Author Topic: ODWEK Causing Hung Threads  (Read 1324 times)

jsquizz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 565
    • View Profile
ODWEK Causing Hung Threads
« on: April 04, 2019, 11:13:39 AM »
Let me preface this by saying I am no ODWEK expert.

We have been getting these frequently:

[4/3/19 14:14:59:723 EDT] 0000000c ThreadMonitor W   WSVR0605W: Thread "WebContainer : 11" (00000089) has been active for 748703 milliseconds and may be hung.  There is/are 3 thread(s) in total in the server that may be hung.
                at com.ibm.edms.od.ArsWWWInterface.apiSearchWithCriteria(Native Method)
                at com.ibm.edms.od.ArsWWWInterface.searchWithCriteria(ArsWWWInterface.java:653)

The first thing I noticed is that we have excessive 65/226 messages, about 20k an hour.

The next thing I noticed is that our users are using strange date ranges, from 4/4/2017 - 4/4/2021...

I did some testing in the thick client..I pulled a 65 record and searched it.

using 4/4/17 - 4/4/19, it took me 8 seconds to get all hits
using 4/4/17 - 4/4/21, it took almost 44 seconds to get all the hits

Does this make sense to anyone? I am not sure why users would be searching a date range like that, unless its hard coded.
#CMOD #DB2 #AFP2PDF #TSM #AIX #RHEL #AWS #AZURE #GCP #EVERYTHING