Local machine installation without FQDN and Error with starting up a local demo installation

Hey the error is: Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown database 'appian17.4_primary'

Do you have a database by that name? Please verify the two databases that we provided inside appian-ds.xml exists and also root has the full permission to access it. Please use the following sql statements to grant permission:

use appian17.4_primary;
grant all on appian17.4_primary.* to root@localhost;
use appian17.4_business;
grant all on appian17.4_business.* to root@localhost;


Also please change the hostname in custom.properties from 127.0.0.1:8080 to localhost:8080

I have the followed the instructions to grant permission from your previous advice. And for the database - while configuring MYSQL workbench I created appian and business database schemas - per the quick guide instructions (if that is what you are referring to as database)

Was the names of the databases that you created called appian17.4_primary and appian17.4_business? The server.log file shows it can't find a database by that name....

ok then change the appian-ds.xml to like this:

<?xml version="1.0" encoding="UTF-8"?>
<datasources xmlns="www.jboss.org/.../schema">
<xa-datasource
jndi-name="jdbc/AppianPrimaryDS"
pool-name="MySqlDS"
enabled="true"
use-java-context="false">
<xa-datasource-property name="serverName">localhost</xa-datasource-property>
<xa-datasource-property name="portNumber">3306</xa-datasource-property>
<xa-datasource-property name="databaseName">APPIAN_SCHEMA</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 xmlns="www.jboss.org/.../schema">
<xa-datasource
jndi-name="jdbc/AppianBusinessDS"
pool-name="MySqlDS"
enabled="true"
use-java-context="false">
<xa-datasource-property name="serverName">localhost</xa-datasource-property>
<xa-datasource-property name="portNumber">3306</xa-datasource-property>
<xa-datasource-property name="databaseName">BUSINESS_SCHEMA</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-business</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>

Sure, will follow the above instruction and keep you updated soon. Thanks

Any update on this?

When I tried doing the above instructions there is a new error while starting JBOSS -

15:56:04,589 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 6) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "security"),
("security-domain" => "ds-name-security-primary")
]) - failure description: "JBAS014803: Duplicate resource [
(\"subsystem\" => \"security\"),
(\"security-domain\" => \"ds-name-security-primary\")
]"
15:56:04,621 WARN [org.jboss.messaging] (ServerService Thread Pool -- 15) JBAS011618: There is no resource matching the expiry-address jms.queue.ExpiryQueue for the address-settings #, expired messages from destinations matching this address-setting will be lost!
15:56:04,777 WARN [org.jboss.messaging] (ServerService Thread Pool -- 15) JBAS011619: There is no resource matching the dead-letter-address jms.queue.DLQ for the address-settings #, undelivered messages from destinations matching this address-setting will be lost!
15:56:10,422 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015051: Deployment content C:\appian17.4\appian\bin\jboss\jboss-eap-6.4\standalone\deployments\appian-mysql-ds.xml appears to be incomplete and is not progressing toward completion. This content cannot be auto-deployed.
15:56:10,437 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "JBAS014784: Failed executing subsystem security boot operations"
15:56:10,437 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"JBAS014784: Failed executing subsystem security boot operations\""
15:56:10,453 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
15:56:10,484 INFO [org.jboss.as] (MSC service thread 1-8) JBAS015950: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) stopped in 4ms

The reason why jboss stopped after a few lines is because you don't have enough RAM space to run everything...assuming you are running appian engines, search-server on the same machine....if you have additional things opened up on your laptop like a few browsers, its going to consume a lot of RAM space...so I would recommend the following two things:

1. Close out unnecessary things like any open browsers when you are about to start jboss.
2. If you believe that you have closed out everything else and it still doesn't start, then we can change the memory settings....Open up jboss-eap-6.4/bin/standalone.conf.bat file and edit the following:

Change the below line from:
set USER_MEM_ARGS=-Xms2048m -Xmx4096m -XX:+HeapDumpOnOutOfMemoryError

To:

set USER_MEM_ARGS=-Xms1024m -Xmx2048m -XX:+HeapDumpOnOutOfMemoryError

Or even lesser:

set USER_MEM_ARGS=-Xms512m -Xmx1024m -XX:+HeapDumpOnOutOfMemoryError

The lower the memory setting we enforce, jboss will be slower to execute....just to let you know....

Try this out and let me know if you encounter any issues still..

Error Jboss.doc

Hi Aswin,

 

I changed the memory settings as you suggested, but still encounter the same exact error message. Please see the complete results of the commands in the attachment. Looking forward for your advice.

Thank you!