topic Re: Starting activiti at ServletContext Initialization causes wait forever at Servlet Context destroy in Alfresco Archive

Starting activiti at ServletContext Initialization causes wait forever at Servlet Context destroy

edsonrichter — Mon, 06 Jun 2016 19:33:01 GMT

I've a simple Activiti web app running on Tomcat (either 7.0.68 or 8.0.39).I cant shutdown it *** on windows *** - and I'm not sure about running in Linux (since Threading is differente in Linux and Windows, I think it is important to alert that this is happening in Windows).Configuration:<?xml v

Re: Starting activiti at ServletContext Initialization causes wait forever at Servlet Context destroy

edsonrichter — Mon, 06 Jun 2016 19:49:28 GMT

Just to be sure: Using 5.20.0, Tomcat (7.0.68 or 8.0.33), JDK 1.8.0-91x64 on Windows Server 2008r2

Re: Starting activiti at ServletContext Initialization causes wait forever at Servlet Context destroy

edsonrichter — Mon, 06 Jun 2016 20:24:27 GMT

When I start running

ProcessEngines.init()

There are four threads that doesn't exists with I don't call init() method.
The threads are "RMI RenewClean", "RMI Readper", "RMI TCP Accepto-0", and "RMI TCP Accept-1099"

Would these threads be related to Activiti? How can I avoid them to start up?

Re: Starting activiti at ServletContext Initialization causes wait forever at Servlet Context destroy

edsonrichter — Tue, 07 Jun 2016 00:48:05 GMT

Ok, seems the deakdlock is caused by activiti-jmx library.
Removed from the system, now it is working well either on Tomcat 7 and Tomcat 8.