https://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hellen-USTelligent Community 12https://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hellMon, 26 Mar 2018 00:53:39 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:6bf0cf7e-387c-4dae-bd77-5175fdcf203eParmida Borhanihttps://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hell#commentsCurrent Revision posted to Appian Knowledge Base by Parmida Borhani on 3/26/2018 12:53:39 AM<br /> <h2>Symptoms</h2> <p>The search server fails to start and the following error is seen in the search-server.log:</p> <pre>[INFO ][com.appian.es.bootstrap.NodeInit] Failed to initialize ElasticSearch node on port 9302. If other ports for this host are specified in appian-topology.xml, those will be tried as well.<br />java.lang.IllegalStateException: failed to load bundle [file:/E:/appian/search-server/plugins/appian-es-auth/appian-es-auth-0.60.0.jar, file:/E:/appian/search-server/plugins/appian-es-auth/appian-es-auth-0.60.1.jar] due to jar hell</pre> <pre>Caused by: java.lang.IllegalStateException: jar hell!</pre> <h2>Cause</h2> <p>This is due to having multiple versions of the same <strong>appian-es-auth-*.jar</strong> JAR file in place, usually encountered from a misapplied hotfix. This particular error shows that the system is finding both 0.60.0 and 0.60.1 versions of the same JAR.&nbsp;</p> <h2>Action</h2> <p>There should only be one version of the JAR file. To resolve the issue, re-apply the hotfix.</p> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p>Last Reviewed: March 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: installation, search server</div> https://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hell/revision/4Sun, 25 Mar 2018 20:52:42 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:6bf0cf7e-387c-4dae-bd77-5175fdcf203eParmida Borhanihttps://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hell#commentsRevision 4 posted to Appian Knowledge Base by Parmida Borhani on 3/25/2018 8:52:42 PM<br /> <h2>Symptoms</h2> <p>The search server fails to start and the following error is seen in the search-server.log:</p> <pre>[INFO ][com.appian.es.bootstrap.NodeInit] Failed to initialize ElasticSearch node on port 9302. If other ports for this host are specified in appian-topology.xml, those will be tried as well.<br />java.lang.IllegalStateException: failed to load bundle [file:/E:/appian/search-server/plugins/appian-es-auth/appian-es-auth-0.60.0.jar, file:/E:/appian/search-server/plugins/appian-es-auth/appian-es-auth-0.60.1.jar] due to jar hell</pre> <pre>Caused by: java.lang.IllegalStateException: jar hell!</pre> <h2>Cause</h2> <p>This is due to having multiple versions of the same <strong>appian-es-auth-*.jar</strong> JAR file in place, usually encountered from a misapplied hotfix. This particular error shows that the system is finding both 0.60.0 and 0.60.1 versions of the same JAR.&nbsp;</p> <h2>Action</h2> <p>There should only be one version of the JAR file. To resolve the issue, re-apply the hotfix.</p> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p>Last Reviewed: March 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: installation, search server</div> https://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hell/revision/3Fri, 23 Mar 2018 02:00:28 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:6bf0cf7e-387c-4dae-bd77-5175fdcf203eParmida Borhanihttps://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hell#commentsRevision 3 posted to Appian Knowledge Base by Parmida Borhani on 3/23/2018 2:00:28 AM<br /> <h2>Symptoms</h2> <p>The search server fails to start and the following error is seen in the search-server.log:</p> <pre>[INFO ][com.appian.es.bootstrap.NodeInit] Failed to initialize ElasticSearch node on port 9302. If other ports for this host are specified in appian-topology.xml, those will be tried as well.<br />java.lang.IllegalStateException: failed to load bundle [file:/E:/appian/search-server/plugins/appian-es-auth/appian-es-auth-0.60.0.jar, file:/E:/appian/search-server/plugins/appian-es-auth/appian-es-auth-0.60.1.jar] due to jar hell</pre> <pre>Caused by: java.lang.IllegalStateException: jar hell!</pre> <h2>Cause</h2> <p>This is due to having multiple versions of the same <strong>appian-es-auth-*.jar</strong> JAR file in place, usually encountered from a misapplied hotfix. This particular error shows that the system is finding both 0.60.0 and 0.60.1 versions of the same JAR.&nbsp;</p> <h2>Action</h2> <p>There should only be one version of the JAR file. To resolve the issue, re-apply the hotfix.</p> <h2>Affected Versions</h2> <p>This article applies to all versions of Appian.</p> <p>Last Reviewed: March 2018</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: installation, search server</div> https://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hell/revision/1Thu, 21 Dec 2017 05:17:49 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:6bf0cf7e-387c-4dae-bd77-5175fdcf203eParmida Borhanihttps://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hell#commentsRevision 1 posted to Appian Knowledge Base by Parmida Borhani on 12/21/2017 5:17:49 AM<br /> <p>work in progress...</p> <p>Symptoms</p> <p>The search server fails to start and the following error is seen in the search-server.log:</p> <p>[2017-12-16 20:20:40,268][INFO ][com.appian.es.bootstrap.NodeInit] Failed to initialize ElasticSearch node on port 9302. If other ports for this host are specified in appian-topology.xml, those will be tried as well.<br />java.lang.IllegalStateException: failed to load bundle [file:/E:/appian/search-server/plugins/appian-es-auth/appian-es-auth-0.60.0.jar, file:/E:/appian/search-server/plugins/appian-es-auth/appian-es-auth-0.60.1.jar] due to jar hell</p> <p>Caused by: java.lang.IllegalStateException: jar hell!</p> <p>Cause</p> <p>This is due to having multiple versions of the same JAR file in place. The error shows that the system is finding both 0.60.0 and 0.60.1 versions of the same JAR.&nbsp;</p> <p>Action</p> <p>Remove one.</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: search server</div> https://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hell/revision/2Thu, 21 Dec 2017 00:18:05 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:6bf0cf7e-387c-4dae-bd77-5175fdcf203eParmida Borhanihttps://community.appian.com/support/w/kb/732/kb-1528-search-server-does-not-start-with-java-lang-illegalstateexception-failed-to-load-bundle-due-to-jar-hell#commentsRevision 2 posted to Appian Knowledge Base by Parmida Borhani on 12/21/2017 12:18:05 AM<br /> <p>work in progress...</p> <p>Symptoms</p> <p>The search server fails to start and the following error is seen in the search-server.log:</p> <p>[2017-12-16 20:20:40,268][INFO ][com.appian.es.bootstrap.NodeInit] Failed to initialize ElasticSearch node on port 9302. If other ports for this host are specified in appian-topology.xml, those will be tried as well.<br />java.lang.IllegalStateException: failed to load bundle [file:/E:/appian/search-server/plugins/appian-es-auth/appian-es-auth-0.60.0.jar, file:/E:/appian/search-server/plugins/appian-es-auth/appian-es-auth-0.60.1.jar] due to jar hell</p> <p>Caused by: java.lang.IllegalStateException: jar hell!</p> <p>Cause</p> <p>This is due to having multiple versions of the same JAR file in place. The error shows that the system is finding both 0.60.0 and 0.60.1 versions of the same JAR.&nbsp;</p> <p>Action</p> <p>Remove one.</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: search server</div>