Issue with quick install 18.2

Thank you both for your help.

I have now managed to get the server started and, although it looks as though it has started correctly (when I hit myFQDN:8080 it responds), when I do http:myFQDN:8080/suite nothing responds.

I have once again attached the output of starting jboss here - any advice would be greatly appreciated.

Thanks again for both coming back so quickly.

Kind regards,

Howard

https://pastebin.com/1gffVAbG

Taking a quick guess - it looks like JBoss can't deploying the suite WAR as it thinks its already loaded (which I don't think is the case based on the startup log and inability to access the /suite endpoint). As Jose mentioned, there are marker files that JBoss uses to deploy, and I think that's the culprit.

I would stop JBoss, then go into your <install>/ear folder and look for a file name suite.ear.<something> and rename it to suite.ear.dodeploy then start JBoss again.

Hi Justin,

Thanks for coming back again.

I have done as suggested and I am getting a different error now, I was wondering if you could take a look? I got this once, decided to uninstall appian and rebuild it with a new jboss directory and is coming up with the same issue:

https://pastebin.com/F6Ck0tm9

Many thanks for your help,

Howard

The error that jumps out to me is:

org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS13:32:59,136 INFO  [stdout] (ServerService Thread Pool -- 423) javax.naming.NameNotFoundException: jdbc/AppianDS -- service jboss.naming.context.java.jdbc.AppianDS

I would double check Step #5 in the guide: https://docs.appian.com/suite/help/18.2/Quick_Start_Installation_Guide_for_Windows_and_JBoss.html#custom-properties If that AppianDS value doesn't match what's in the ds.xml file under ../jboss/standalone/deployments/appian-mysql-ds.xml, then you can get that error. More info on the mysql db config files is here: https://docs.appian.com/suite/help/18.2/Configuring_Relational_Databases.html#mysql11

The error that jumps out to me is:

org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS13:32:59,136 INFO  [stdout] (ServerService Thread Pool -- 423) javax.naming.NameNotFoundException: jdbc/AppianDS -- service jboss.naming.context.java.jdbc.AppianDS

I would double check Step #5 in the guide: https://docs.appian.com/suite/help/18.2/Quick_Start_Installation_Guide_for_Windows_and_JBoss.html#custom-properties If that AppianDS value doesn't match what's in the ds.xml file under ../jboss/standalone/deployments/appian-mysql-ds.xml, then you can get that error. More info on the mysql db config files is here: https://docs.appian.com/suite/help/18.2/Configuring_Relational_Databases.html#mysql11

Thanks for the reply once again. I can confirm that these are both the same, unfortunately.

The contents of the appian-mysql-ds.xml is:

<?xml version="1.0" encoding="UTF-8"?>
<datasources xmlns="">www.jboss.org/.../schema">
<!-- System Datasource -->
<xa-datasource
jndi-name="jdbc/AppianDS"
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>

And the custom.properties is:

## Appian must have a dedicated data source. Set the value to the JNDI name of
## the data source that will be used as the Appian data source.
## Note: This data source must point to a separate tablespace than any listed
## in the conf.data.datasources configuration.
conf.data.APPIAN_DATA_SOURCE=jdbc/AppianDS
## Comma-separated list of JNDI names of data sources on the application server
## that will be used to store business data. This list is used by the Query
## Database smart service and Data Stores.
#conf.data.datasources=

EDIT: I've confirmed than when I remove the .dodeploy in ear suite everything launches without an issue and I get the successful startup message - does that indicate that's where the issue is?

Then my next guess is the ds.xml file didn't deploy at all. What files are under jboss/standalone/deployments? You need to have appian-mysql-ds.xml and another file called appian-mysql-ds.xml.dodeploy. The latter file will be renamed as appian-mysql-ds.xml.deployed when it loads properly, and appian-mysql-ds.xml.failed (or similar) if not.

I'd read this article next to see if one of the solutions there solve this: https://community.appian.com/support/w/kb/235/kb-1009-could-not-find-datasource-error-thrown-during-jboss-startup

Thanks for your help.

I will have to pick this up again tomorrow, however - I redeployed from the repo to restore the ds.xml.dodeploy and ran again with the same result. I have checked the article you linked and can find nothing else to rectify according to that. I have appian-mysql-dsI.undeployed now have pasted the results below:

https://pastebin.com/97BLiLVL

All the best,

Howard

Your DS is getting loaded now:

15:53:03,540 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [jdbc/AppianDS]

The error now is something with your keystore file, though the error isn't very helpful to suggest a clear course of action.

Caused by: com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: An unexpected error occurred while trying to load the keystore. (APNX-1-4210-005)

I haven't seen the root cause of "Caused by: java.io.EOFException" before with this - normally the error is more descriptive, such as the file is out of sync with the primary database. Others might have some ideas, but I suggest asking Appian Support.