<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>KB-1123 "Class Path entry &lt;JAR1&gt; in &lt;location of JAR2&gt; does not point to a valid jar for a Class-Path reference" error thrown during application server startup</title><link>https://community.appian.com/support/w/kb/345/kb-1123-class-path-entry-jar1-in-location-of-jar2-does-not-point-to-a-valid-jar-for-a-class-path-reference-error-thrown-during-application-server-startup</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>KB-1123 "Class Path entry &lt;JAR1&gt; in &lt;location of JAR2&gt; does not point to a valid jar for a Class-Path reference" error thrown during application server startup</title><link>https://community.appian.com/support/w/kb/345/kb-1123-class-path-entry-jar1-in-location-of-jar2-does-not-point-to-a-valid-jar-for-a-class-path-reference-error-thrown-during-application-server-startup</link><pubDate>Fri, 24 Feb 2017 13:50:06 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:d78d938d-d0cb-40f0-8360-1ab210cd24fe</guid><dc:creator>Nick Vigilante</dc:creator><comments>https://community.appian.com/support/w/kb/345/kb-1123-class-path-entry-jar1-in-location-of-jar2-does-not-point-to-a-valid-jar-for-a-class-path-reference-error-thrown-during-application-server-startup#comments</comments><description>Current Revision posted to Appian Knowledge Base by Nick Vigilante on 2/24/2017 1:50:06 PM&lt;br /&gt;
&lt;div class="row content_container"&gt;
&lt;h2 id="symptoms"&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;When starting the application server, the following warning message is printed in the server logs:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;WARN [&amp;hellip;] JBAS015960: Class Path entry JAR1.jar in /&amp;lt;APPIAN_HOME&amp;gt;/ear/suite.ear/lib/JAR2.jar does not point to a valid jar for a Class-Path reference.
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; The jar files in the warning message above are meant as an example. The following Cause and Action categories use the jar names above but should be replaced to reflect the warning message.&lt;/p&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;
&lt;p&gt;The message explains that the &lt;strong&gt;JAR2.jar&lt;/strong&gt; file in the example above is pointing to &lt;strong&gt;JAR1.jar&lt;/strong&gt; from the same directory. However, that file cannot be found.&lt;/p&gt;
&lt;p&gt;This can be safely ignored as a more recent version of &lt;strong&gt;JAR1.jar&lt;/strong&gt; file is present in the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/ear/suite.ear/lib&lt;/code&gt; directory in the base install.&lt;/p&gt;
&lt;h2 id="action"&gt;Action&lt;/h2&gt;
&lt;p&gt;As mentioned above, this is an informative warning that can be safely ignored as long as a &lt;strong&gt;JAR1.jar&lt;/strong&gt; file has not been removed from the &lt;code&gt;&amp;lt;APPIAN_HOME&amp;gt;/ear/suite.ear/lib&lt;/code&gt; directory.&lt;/p&gt;
&lt;h2 id="affected-versions"&gt;Affected Versions&lt;/h2&gt;
&lt;p&gt;This article applies to all versions of Appian.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Last Reviewed:&amp;nbsp;February 2017&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: installation, application server&lt;/div&gt;
</description></item></channel></rss>