Therefore, to enable it, you simply need to add the valve as done below and then restart Tomcat:<\/p>\n\n\n
\n[tomcat@d2-0 ~]$ cd $CATALINA_HOME\/conf\/\n[tomcat@d2-0 conf]$\n[tomcat@d2-0 conf]$ cat server.xml\n<?xml version="1.0" encoding="UTF-8"?>\n...\n<Server port="8005" shutdown="b018b3d58bdbb490a1b2baed3c2efaee">\n ...\n <Service name="Catalina">\n ...\n <Engine name="Catalina" defaultHost="localhost">\n ...\n <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">\n ...\n <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve"\n threshold="120" \/>\n <\/Host>\n <\/Engine>\n <\/Service>\n<\/Server>\n[tomcat@d2-0 conf]$\n[tomcat@d2-0 conf]$ stopTomcat\n **\n ** Apache Tomcat is running with PID: 4210\n **\nUsing CATALINA_BASE: $CATALINA_HOME\nUsing CATALINA_HOME: $CATALINA_HOME\nUsing CATALINA_TMPDIR: $DATA_HOME\/temp\nUsing JRE_HOME: $JAVA_HOME\nUsing CLASSPATH: $CATALINA_HOME\/bin\/bootstrap.jar:$CATALINA_HOME\/bin\/tomcat-juli.jar\nUsing CATALINA_OPTS:\nUsing CATALINA_PID: $DATA_HOME\/tomcat.pid\nNOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base\/java.lang=ALL-UNNAMED --add-opens=java.base\/java.io=ALL-UNNAMED --add-opens=java.base\/java.util=ALL-UNNAMED --add-opens=java.base\/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi\/sun.rmi.transport=ALL-UNNAMED\nTomcat stopped.\n **\n ** Apache Tomcat is shutdown\n **\n[tomcat@d2-0 conf]$\n[tomcat@d2-0 conf]$ startTomcat\n **\n ** Apache Tomcat is shutdown\n **\nCleanup of app_data for "D2"\n\nUsing CATALINA_BASE: $CATALINA_HOME\nUsing CATALINA_HOME: $CATALINA_HOME\nUsing CATALINA_TMPDIR: $DATA_HOME\/temp\nUsing JRE_HOME: $JAVA_HOME\nUsing CLASSPATH: $CATALINA_HOME\/bin\/bootstrap.jar:$CATALINA_HOME\/bin\/tomcat-juli.jar\nUsing CATALINA_OPTS:\nUsing CATALINA_PID: $DATA_HOME\/tomcat.pid\nTomcat started.\n **\n ** Apache Tomcat is running with PID: 8426\n **\n[tomcat@d2-0 conf]$\n<\/pre><\/div>\n\n\nNow that messages are being printed on the logs, it’s a first step but it might take some time to analyze these. For that purpose, you can write a parser to find all messages and extract the needed information. Of course, such tool would be sensitive to the log format (length of date\/timestamp, number of fields you integrated in the logs, etc.). Here is an example of a thread being detected as stuck (“threshold<\/em>” of 120s) and its successful completion:<\/p>\n\n\n\n[tomcat@d2-0 conf]$ cd $CATALINA_HOME\/logs\/\n[tomcat@d2-0 logs]$\n[tomcat@d2-0 logs]$ grep notifyStuckThread catalina.out\n...\n2023-12-13 10:03:21,079 UTC WARNING [Catalina-utility-2] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [https-jsse-nio-8080-exec-417] (id=[27927]) has been active for [122,196] milliseconds (since [12\/13\/23 10:01 AM]) to serve the same request for [https:\/\/dctm-env1.domain.com\/D2\/x3_portal\/searchManagerService] and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is\/are [2] thread(s) in total that are monitored by this Valve and may be stuck.\n...\n2023-12-13 10:03:31,090 UTC WARNING [Catalina-utility-1] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [https-jsse-nio-8080-exec-417] (id=[27927]) was previously reported to be stuck but has completed. It was active for approximately [127,144] milliseconds. There is\/are still [1] thread(s) that are monitored by this Valve and may be stuck.\n...\n[tomcat@d2-0 logs]$\n<\/pre><\/div>\n\n\nOn the above example, the thread started around 10:01:19<\/em>, was detected as stuck 122s<\/em> later (10:03:21<\/em>) and completed after 127s<\/em> (10:03:26<\/em>). It was related to a search request in D2 and at the time of the detection, there was already another thread stuck (2 threads stuck in the “notifyStuckThreadDetected<\/em>“). When it completed, there was still another thread stuck (1 thread stuck in the “notifyStuckThreadCompleted<\/em>“). That’s the kind of information you can get from the Tomcat logs.<\/p>\n\n\n\nHere is an example of parser that will work with this logging format, it’s using “awk<\/em>” to read all the lines, find the “notifyStuckThreadDetected<\/em>” occurrences, find the associated “notifyStuckThreadCompleted<\/em>” occurrences and then display all the needed information in a summary table. In case the thread is still running (didn’t complete yet), it will also mark it as such:<\/p>\n\n\n\n[tomcat@d2-0 logs]$ cd\n[tomcat@d2-0 ~]$\n[tomcat@d2-0 ~]$ cat parse_stuck.awk\nBEGIN {\n print "============================================";\n print "========== COMPLETED LONG THREADS ==========";\n print "============================================";\n printf("%-25s\\t%20s\\t%12s\\t%10s\\t%12s\\t%3s\\t%-s\\n","THREAD","STIME","DTIME","DURATION","CTIME","NUM","REQUEST");\n}\n\n\/.\/ {\n sub("UTC","");\n}\n\n\/org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected\/ {\n thread=substr($7,2,length($7)-2);\n dtime[thread]=$2;\n tmp=substr($0,index($0,"since")+6);\n stime[thread]=substr(tmp,1,index(tmp,")")-1);\n tmp=substr($0,index($0,"active for ")+11);\n duration[thread]=substr(tmp,1,index(tmp," ")-1);\n tmp=substr($0,index($0,"request for ")+12);\n request[thread]=substr(tmp,1,index(tmp," ")-1);\n tmp=substr($0,index($0,"is\/are ")+7);\n count_stuck[thread]=substr(tmp,1,index(tmp," ")-1);\n ended[thread]=0;\n}\n\n\/org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted\/ {\n thread=substr($7,2,length($7)-2);\n tmp=substr($0,index($0,"approximately ")+14);\n duration[thread]=substr(tmp,1,index(tmp," ")-1);\n ctime[thread]=$2;\n ended[thread]=1;\n tmp=substr($0,index($0,"is\/are still [")+14);\n nb_stuck[thread]=substr(tmp,1,index(tmp,"]")-1);\n\n printf("%-25s\\t%20s\\t%s\\t%10s\\t%s\\t%3d\\t%-s\\n",thread,stime[thread],dtime[thread],duration[thread],ctime[thread],nb_stuck[thread],request[thread]);\n\n dtime[thread]="";\n ctime[thread]="";\n stime[thread]=="";\n duration[thread]=="";\n request[thread]=="";\n count_stuck[thread]=="";\n nb_stuck[thread]=="";\n ended[thread]=="";\n}\n\nEND {\n print "";\n print "============================================";\n print "======= CURRENTLY STUCK LONG THREADS =======";\n print "============================================";\n printf("%-25s\\t%20s\\t%12s\\t%10s\\t%-s\\n","THREAD","STIME","DTIME","DURATION","REQUEST");\n for ( i in ended ) {\n if (ended[i]==0) {\n printf("%-25s\\t%20s\\t%s\\t%10s\\t%-s\\n",i,stime[i],dtime[i],duration[i],request[i]);\n }\n }\n}\n[tomcat@d2-0 ~]$\n<\/pre><\/div>\n\n\nThe execution of this small parser is quite simple, here are two examples:<\/p>\n\n\n
\n[tomcat@d2-0 ~]$ cat $CATALINA_HOME\/logs\/catalina.out | awk -f parse_stuck.awk\n============================================\n========== COMPLETED LONG THREADS ==========\n============================================\nTHREAD STIME DTIME DURATION CTIME NUM REQUEST\nhttps-jsse-nio-8080-exec-420 [12\/14\/23, 4:53 AM] 04:55:44,045 [228,883] 04:57:24,983 0 [https:\/\/dctm-env1.domain.com\/D2\/servlet\/ExportContent?uid=...]\nhttps-jsse-nio-8080-exec-463 [12\/14\/23, 5:03 AM] 05:05:36,427 [240,259] 05:07:31,980 0 [https:\/\/dctm-env1.domain.com\/D2\/x3_portal\/searchManagerService]\nhttps-jsse-nio-8080-exec-502 [12\/14\/23, 5:34 AM] 05:36:34,645 [185,688] 05:37:38,489 0 [https:\/\/dctm-env1.domain.com\/D2\/servlet\/ExportContent?uid=...]\nhttps-jsse-nio-8080-exec-355 [12\/14\/23, 7:41 AM] 07:43:48,877 [165,236] 07:44:38,900 0 [https:\/\/dctm-env1.domain.com\/D2\/x3_portal\/doclistService]\n\n============================================\n======= CURRENTLY STUCK LONG THREADS =======\n============================================\nTHREAD STIME DTIME DURATION REQUEST\nhttps-jsse-nio-8080-exec-355 [12\/14\/23, 11:49 AM] 11:51:22,124 [121,961] [https:\/\/dctm-env1.domain.com\/D2\/x3_portal\/doclistService]\n[tomcat@d2-0 ~]$\n<\/pre><\/div>\n\n\n[tomcat@d2-0 ~]$ cat $CATALINA_HOME\/logs\/catalina.out | awk -f parse_stuck.awk\n============================================\n========== COMPLETED LONG THREADS ==========\n============================================\nTHREAD STIME DTIME DURATION CTIME NUM REQUEST\nhttps-jsse-nio-8080-exec-33 [12\/6\/23, 2:37 PM] 14:39:47,521 [280,031] 14:42:27,965 0 [https:\/\/dctm-env2.domain.com\/D2\/x3_portal\/checkoutDocumentService]\nhttps-jsse-nio-8080-exec-21 [12\/6\/23, 4:36 PM] 16:38:45,420 [268,730] 16:41:15,626 0 [https:\/\/dctm-env2.domain.com\/D2\/x3_portal\/searchManagerService]\nhttps-jsse-nio-8080-exec-29 [12\/12\/23, 9:26 PM] 21:28:57,339 [154,656] 21:29:27,356 1 [https:\/\/dctm-env2.domain.com\/D2\/x3_portal\/propertiesService]\nhttps-jsse-nio-8080-exec-33 [12\/12\/23, 9:26 PM] 21:28:47,332 [168,044] 21:29:27,357 0 [https:\/\/dctm-env2.domain.com\/D2\/x3_portal\/propertiesService]\n\n============================================\n======= CURRENTLY STUCK LONG THREADS =======\n============================================\nTHREAD STIME DTIME DURATION REQUEST\n[tomcat@d2-0 ~]$\n<\/pre><\/div>\n\n\nThe different columns are the following ones:<\/p>\n\n\n\n
\n- THREAD: Name of the thread, can be used to find the start\/end of the request<\/li>\n\n\n\n
- STIME: Start date\/time of the thread<\/li>\n\n\n\n
- DTIME: Detection time of the thread (~120s after STIME)<\/li>\n\n\n\n
- DURATION: Total duration of the thread<\/li>\n\n\n\n
- CTIME: Completion time of the thread (~DURATIONs after STIME)<\/li>\n\n\n\n
- NUM: Number of threads still stuck<\/li>\n\n\n\n
- REQUEST: URL used that triggered the thread<\/li>\n<\/ul>\n\n\n\n
That concludes this blog, hopefully you find this information useful to debug\/improve your applications. Don’t hesitate to change the threshold of 120 seconds in the Tomcat configuration to something relevant for your use-case.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Most Application Servers allow for long and\/or stuck threads detection, to let you know that something is currently very slow, waiting on something or just simply stuck. On tomcat, this isn’t enabled by default, and you need to manually configure it as needed. But once done, it will start displaying information into the logs that […]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[525],"tags":[839,2609,551,552,771,3204],"type_dbi":[],"class_list":["post-29794","post","type-post","status-publish","format-standard","hentry","category-enterprise-content-management","tag-apache","tag-documentum-2","tag-stuck","tag-thread","tag-tomcat","tag-valve"],"acf":[],"yoast_head":"\n
HowTo - Detect and analyze long\/stuck threads in Tomcat - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"HowTo - Detect and analyze long\/stuck threads in Tomcat\" \/>\n<meta property=\"og:description\" content=\"Most Application Servers allow for long and\/or stuck threads detection, to let you know that something is currently very slow, waiting on something or just simply stuck. On tomcat, this isn’t enabled by default, and you need to manually configure it as needed. But once done, it will start displaying information into the logs that […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2023-12-18T07:15:00+00:00\" \/>\n<meta name=\"author\" content=\"Morgan Patou\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@MorganPatou\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Morgan Patou\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"HowTo – Detect and analyze long\/stuck threads in Tomcat\",\"datePublished\":\"2023-12-18T07:15:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/\"},\"wordCount\":579,\"commentCount\":0,\"keywords\":[\"Apache\",\"Documentum\",\"Stuck\",\"Thread\",\"Tomcat\",\"Valve\"],\"articleSection\":[\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/\",\"name\":\"HowTo - Detect and analyze long\/stuck threads in Tomcat - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2023-12-18T07:15:00+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"HowTo – Detect and analyze long\/stuck threads in Tomcat\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\",\"name\":\"Morgan Patou\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"caption\":\"Morgan Patou\"},\"description\":\"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex & critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.\",\"sameAs\":[\"https:\/\/blog.dbi-services.com\/author\/morgan-patou\/\",\"https:\/\/x.com\/MorganPatou\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"HowTo - Detect and analyze long\/stuck threads in Tomcat - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/","og_locale":"en_US","og_type":"article","og_title":"HowTo - Detect and analyze long\/stuck threads in Tomcat","og_description":"Most Application Servers allow for long and\/or stuck threads detection, to let you know that something is currently very slow, waiting on something or just simply stuck. On tomcat, this isn’t enabled by default, and you need to manually configure it as needed. But once done, it will start displaying information into the logs that […]","og_url":"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/","og_site_name":"dbi Blog","article_published_time":"2023-12-18T07:15:00+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"HowTo – Detect and analyze long\/stuck threads in Tomcat","datePublished":"2023-12-18T07:15:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/"},"wordCount":579,"commentCount":0,"keywords":["Apache","Documentum","Stuck","Thread","Tomcat","Valve"],"articleSection":["Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/","url":"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/","name":"HowTo - Detect and analyze long\/stuck threads in Tomcat - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2023-12-18T07:15:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/howto-detect-and-analyze-long-stuck-threads-in-tomcat\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"HowTo – Detect and analyze long\/stuck threads in Tomcat"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8","name":"Morgan Patou","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","caption":"Morgan Patou"},"description":"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex & critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.","sameAs":["https:\/\/blog.dbi-services.com\/author\/morgan-patou\/","https:\/\/x.com\/MorganPatou"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/29794","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=29794"}],"version-history":[{"count":2,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/29794\/revisions"}],"predecessor-version":[{"id":29797,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/29794\/revisions\/29797"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=29794"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=29794"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=29794"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=29794"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}