JVM Exiting error when Dependent Module is RemovedJVM Exiting error when Dependent Module is Removedhttps://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=1117891222026-04-06T08:45:17Z2026-04-06T08:45:17ZRE: JVM Exiting error when Dependent Module is RemovedAndrew Jardinehttps://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1117928922018-12-12T20:29:43Z2018-12-12T20:29:43ZUgh. <a href="https://community.liferay.com/blogs/-/blogs/exiting-the-jvm-">https://community.liferay.com/blogs/-/blogs/exiting-the-jvm-</a>Andrew Jardine2018-12-12T20:29:43ZJVM Exiting error when Dependent Module is RemovedAndrew Jardinehttps://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=1117891212018-12-12T16:32:15Z2018-12-12T16:32:15Z<p>Hey guys, </p>
<p>I am hoping that someone else is plagued by this and has a solution
for me.I have a module-web with a dependency on sb-module-api. If I
remove the sb-module-api, I get an ERROR in the log saying that the
module-web can't resolve an Import-Package -- which I expect since I
removed it. But, rather than simply stopping the dependent module-web
so that it is no longer available, I am getting</p>
<pre>
[org_apache_felix_fileinstall:112] Exiting the JVM</pre>
<p>.. at which point I have to go through a nightmarish process of
cleaning the state and removing modules etc. so that I can actually
start the server again.<br /> I am on Linux, with the latest JDK
8_191. My friend is on a Mac with JDK 8_125 and has the same
experience with the error <em>BUT</em> his JVM does NOT exit.</p>
<p> </p>
<p>Any suggestions?</p>Andrew Jardine2018-12-12T16:32:15Z