New installation, JBOSS not working, Fatal error

Hi prakash/Vimal,

Yes, That worked. I created a new schema in my SQL workbench for AppianPrimary . Looks like now I am connected to DB.

secondaly I have appended the xa-datasource-property name= url with  &useSSL=False to avoid the SSL error while connecting to DB.

However, I hit an another road block. when I am trying to start my Jboss, the processing (CMD message) stops or stuck after the below message.

JBAS014777:   Services which failed to start:      service jboss.web.deployment.

default-host./suite

looks like I am missing something more here. Have attached new server log file. Thank you very much for this.

1513.server.log 

<?xml version="1.0" encoding="UTF-8"?>
<datasources xmlns="http://www.jboss.org/ironjacamar/schema">
  <!-- System Datasource -->
  <xa-datasource 
      jndi-name="jdbc/AppianPrimary" 
      pool-name="MySqlDS"
      enabled="true" 
      use-java-context="false">
    <xa-datasource-property name="URL">jdbc:mysql://localhost:3306/AppianPrimary?useOldAliasMetadataBehavior=true&useSSL=false</xa-datasource-property>
    <xa-datasource-property name="useUnicode">true</xa-datasource-property>
    <xa-datasource-property name="characterEncoding">UTF-8</xa-datasource-property>
    <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
    <driver>com.mysql.jdbc</driver>
    <security>
      <security-domain>ds-name-security-primary</security-domain>
    </security>
    <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
    <xa-pool>
      <min-pool-size>5</min-pool-size>
      <max-pool-size>100</max-pool-size>
    </xa-pool>
    <timeout>
      <blocking-timeout-millis>5000</blocking-timeout-millis>
      <idle-timeout-minutes>5</idle-timeout-minutes>
    </timeout>
  </xa-datasource>
</datasources>

it is still generating .failed file for appian-mysql-ds.xml

PS: How to contact the Appian documentation team ? In the quick start guide, in installing MySQL server/workbench part they suggest to create schemas as Appian_schema and BUSINESS_SCHEMA, while in appian-mysql-ds.xml.<environment> they are referring as AppianDS. a naive like me would struggle for days to figure out.

Hi Praveen,

From your screenshots my understanding is you are trying to connect to a database called "appian_schema".  But in appian-ds-mysql.xml file you have given the value as AppianPrimary which actually doesn't exists in your Local MySql.

Based on 7127.server.log, there are two things to be cleared first

1. Search Server should started before we start Application Server. It seems like there are few issues in that as per the below

08:22:01,699 INFO  [stdout] (ServerService Thread Pool -- 164) com.appiancorp.suiteapi.common.exceptions.AppianException: The search server cannot be reached. Failed to connect to server at [localhost:9300]. Check that the search server is started. If running multiple application servers, check that appian-topology.xml is properly configured with the search cluster details. The appian-topology.xml file must be distributed to each /ear/suite.ear/conf/ and /search-server/conf/ directory. See documentation for details. (APNX-1-4274-001)

2. Connecting to Unkonw Database 'AppianPrimary' instead of appian_schema.

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown database 'appianprimary'

Please follow the below steps:

1. Stop Application Server

2. Delete the file appian-ds-mysql.xml.xxxxxxx. As it should recreate automatically.

3. Rename suite.ear.XXXXXXX to suite.ear.dodeploy

4. Make sure search server is running in Port 9300.

5. Change your appian-ds-mysql.xml file as below

<?xml version="1.0" encoding="UTF-8"?>
<datasources xmlns="http://www.jboss.org/ironjacamar/schema">
  <!-- System Datasource -->
  <xa-datasource 
      jndi-name="jdbc/AppianPrimary" 
      pool-name="MySqlDS"
      enabled="true" 
      use-java-context="false">
    <xa-datasource-property name="URL">jdbc:mysql://localhost:3306/appian_schema?useOldAliasMetadataBehavior=true</xa-datasource-property>
    <xa-datasource-property name="useUnicode">true</xa-datasource-property>
    <xa-datasource-property name="characterEncoding">UTF-8</xa-datasource-property>
    <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
    <driver>com.mysql.jdbc</driver>
    <security>
      <security-domain>ds-name-security-primary</security-domain>
    </security>
    <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
    <xa-pool>
      <min-pool-size>5</min-pool-size>
      <max-pool-size>100</max-pool-size>
    </xa-pool>
    <timeout>
      <blocking-timeout-millis>5000</blocking-timeout-millis>
      <idle-timeout-minutes>5</idle-timeout-minutes>
    </timeout>
  </xa-datasource>
</datasources>

6. Start Application Server
7. Please attach the log file after following the above steps if there are still any issues.

Hi Praveen,

From your screenshots my understanding is you are trying to connect to a database called "appian_schema".  But in appian-ds-mysql.xml file you have given the value as AppianPrimary which actually doesn't exists in your Local MySql.

Based on 7127.server.log, there are two things to be cleared first

1. Search Server should started before we start Application Server. It seems like there are few issues in that as per the below

08:22:01,699 INFO  [stdout] (ServerService Thread Pool -- 164) com.appiancorp.suiteapi.common.exceptions.AppianException: The search server cannot be reached. Failed to connect to server at [localhost:9300]. Check that the search server is started. If running multiple application servers, check that appian-topology.xml is properly configured with the search cluster details. The appian-topology.xml file must be distributed to each /ear/suite.ear/conf/ and /search-server/conf/ directory. See documentation for details. (APNX-1-4274-001)

2. Connecting to Unkonw Database 'AppianPrimary' instead of appian_schema.

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown database 'appianprimary'

Please follow the below steps:

1. Stop Application Server

2. Delete the file appian-ds-mysql.xml.xxxxxxx. As it should recreate automatically.

3. Rename suite.ear.XXXXXXX to suite.ear.dodeploy

4. Make sure search server is running in Port 9300.

5. Change your appian-ds-mysql.xml file as below

<?xml version="1.0" encoding="UTF-8"?>
<datasources xmlns="http://www.jboss.org/ironjacamar/schema">
  <!-- System Datasource -->
  <xa-datasource 
      jndi-name="jdbc/AppianPrimary" 
      pool-name="MySqlDS"
      enabled="true" 
      use-java-context="false">
    <xa-datasource-property name="URL">jdbc:mysql://localhost:3306/appian_schema?useOldAliasMetadataBehavior=true</xa-datasource-property>
    <xa-datasource-property name="useUnicode">true</xa-datasource-property>
    <xa-datasource-property name="characterEncoding">UTF-8</xa-datasource-property>
    <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
    <driver>com.mysql.jdbc</driver>
    <security>
      <security-domain>ds-name-security-primary</security-domain>
    </security>
    <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
    <xa-pool>
      <min-pool-size>5</min-pool-size>
      <max-pool-size>100</max-pool-size>
    </xa-pool>
    <timeout>
      <blocking-timeout-millis>5000</blocking-timeout-millis>
      <idle-timeout-minutes>5</idle-timeout-minutes>
    </timeout>
  </xa-datasource>
</datasources>

6. Start Application Server
7. Please attach the log file after following the above steps if there are still any issues.