<?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-1041 "Empty result set, expected one row" thrown during JBoss startup</title><link>https://community.appian.com/support/w/kb/266/kb-1041-empty-result-set-expected-one-row-thrown-during-jboss-startup</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>KB-1041 "Empty result set, expected one row" thrown during JBoss startup</title><link>https://community.appian.com/support/w/kb/266/kb-1041-empty-result-set-expected-one-row-thrown-during-jboss-startup</link><pubDate>Mon, 30 Jul 2018 04:00:06 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:a28c9774-af55-4ac5-87ad-037070658682</guid><dc:creator>Parmida Borhani</dc:creator><comments>https://community.appian.com/support/w/kb/266/kb-1041-empty-result-set-expected-one-row-thrown-during-jboss-startup#comments</comments><description>Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 4:00:06 AM&lt;br /&gt;
&lt;div class="row content_container"&gt;
&lt;h2 id="symptoms"&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;When starting JBoss, the following error is printed in application server log found under &lt;code&gt;&amp;lt;JBOSS_HOME&amp;gt;/standalone/logs&lt;/code&gt;:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 52) JBWEB000287: Exception sending context initialized event to listener instance of class com.appiancorp.common.config.ConfigurationLoader: com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: An unexpected error occurred while trying to initialize and validate the Appian data source. (APNX-1-4179-004)
...
Caused by: java.lang.IllegalStateException: [jdbc/AppianPrimaryDS] Error during schema migration.
...
Caused by: java.lang.IllegalStateException: liquibase.exception.LockException: liquibase.exception.DatabaseException: Empty result set, expected one row
...
Caused by: liquibase.exception.LockException: liquibase.exception.DatabaseException: Empty result set, expected one row
...
Caused by: liquibase.exception.DatabaseException: Empty result set, expected one row
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;JBoss then fails to deploy.&lt;/p&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;
&lt;p&gt;This error message is returned when the &lt;code&gt;DATABASECHANGELOCK&lt;/code&gt; table of the Appian data source is empty. The cause of an empty table is a manual error that resulted in the table being cleared.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; This error can disguise the broader issue of all tables of the data source being empty.&lt;/p&gt;
&lt;h2 id="action"&gt;Action&lt;/h2&gt;
&lt;p&gt;Make sure that the &lt;code&gt;DATABASECHANGELOCK&lt;/code&gt; table (and only that table) is empty by accessing the Appian data store from the database side. If it is empty, use the following SQL command to repopulate the table:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;INSERT INTO DATABASE.CHANGELOGLOCK VALUES (1, 0, NULL,NULL)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; This command applies to a MySQL database; please adapt the command to the database vendor.&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: database, infrastructure&lt;/div&gt;
</description></item><item><title>KB-1041 "Empty result set, expected one row" thrown during JBoss startup</title><link>https://community.appian.com/support/w/kb/266/kb-1041-empty-result-set-expected-one-row-thrown-during-jboss-startup/revision/1</link><pubDate>Tue, 14 Feb 2017 14:48:34 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:a28c9774-af55-4ac5-87ad-037070658682</guid><dc:creator>Nick Vigilante</dc:creator><comments>https://community.appian.com/support/w/kb/266/kb-1041-empty-result-set-expected-one-row-thrown-during-jboss-startup#comments</comments><description>Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/14/2017 2:48:34 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 JBoss, the following error is printed in application server log found under &lt;code&gt;&amp;lt;JBOSS_HOME&amp;gt;/standalone/logs&lt;/code&gt;:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 52) JBWEB000287: Exception sending context initialized event to listener instance of class com.appiancorp.common.config.ConfigurationLoader: com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: An unexpected error occurred while trying to initialize and validate the Appian data source. (APNX-1-4179-004)
...
Caused by: java.lang.IllegalStateException: [jdbc/AppianPrimaryDS] Error during schema migration.
...
Caused by: java.lang.IllegalStateException: liquibase.exception.LockException: liquibase.exception.DatabaseException: Empty result set, expected one row
...
Caused by: liquibase.exception.LockException: liquibase.exception.DatabaseException: Empty result set, expected one row
...
Caused by: liquibase.exception.DatabaseException: Empty result set, expected one row
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;JBoss then fails to deploy.&lt;/p&gt;
&lt;h2 id="cause"&gt;Cause&lt;/h2&gt;
&lt;p&gt;This error message is returned when the &lt;code&gt;DATABASECHANGELOCK&lt;/code&gt; table of the Appian data source is empty. The cause of an empty table is a manual error that resulted in the table being cleared.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; This error can disguise the broader issue of all tables of the data source being empty.&lt;/p&gt;
&lt;h2 id="action"&gt;Action&lt;/h2&gt;
&lt;p&gt;Make sure that the &lt;code&gt;DATABASECHANGELOCK&lt;/code&gt; table (and only that table) is empty by accessing the Appian data store from the database side. If it is empty, use the following SQL command to repopulate the table:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;INSERT INTO DATABASE.CHANGELOGLOCK VALUES (1, 0, NULL,NULL)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; This command applies to a MySQL database; please adapt the command to the database vendor.&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: database&lt;/div&gt;
</description></item></channel></rss>