Unable to get JBoss to start.

Hi,
Have you configured all the steps mentioned?
Please check the below links:
docs.appian.com/.../Configuring_JBoss.html
docs.appian.com/.../Windows_Installation_Guide.html

Hey Neil,

Have gone through similar issue earlier. From the logs it states " Could not find datasource: java:/jdbc/AppianDS
05:56:13,"

So check if u have configured the files such as 1.custom.properties( settings #conf.data.APPIAN_DATA_SOURCE to correct jndi mentioned in appian-mysql-ds.xml.)

Also check if you have added the correct host , port and source names in appian-mysql-ds.xml.

Thanks ,
Thoufiq

Yes followed all steps

That helped be but when I check the Web Link JBoss is running but I came access <hostip:8080>/suite/tempo.

 

Below is my service log now:

JBoss Bootstrap Environment

JBOSS_HOME: /home/ec2-user/EAP-6.4.0

JAVA: /usr/java/jdk1.8.0_131/bin/java

JAVA_OPTS: -XX:+UseCompressedOops -verbose:gc -Xloggc:"/home/ec2-user/EAP-6.4 .0/standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCL ogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnlo ading -Xms2048m -Xmx4096m -XX:+HeapDumpOnOutOfMemoryError -Dsun.rmi.dgc.client.g cInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -XX:+CMSClassUnloading Enabled -XX:+UseConcMarkSweepGC -Dorg.apache.catalina.connector.URI_ENCODING=UTF -8 -Duser.timezone=GMT -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -server -Dappian.home.ear=/home/ec2-user/appian_home/ear - Djboss.as.management.blocking.timeout=3600 -Dorg.jboss.resolver.warning=true -Dj boss.server.default.config=standalone.xml

=========================================================================

13:22:19,596 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final- redhat-1
13:22:19,737 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
13:22:19,804 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) starting
13:22:21,209 WARN [org.jboss.messaging] (ServerService Thread Pool -- 5) JBAS01 1618: There is no resource matching the expiry-address jms.queue.ExpiryQueue for the address-settings #, expired messages from destinations matching this addres s-setting will be lost!
13:22:21,210 WARN [org.jboss.messaging] (ServerService Thread Pool -- 5) JBAS01 1619: There is no resource matching the dead-letter-address jms.queue.DLQ for th e address-settings #, undelivered messages from destinations matching this addre ss-setting will be lost!
13:22:21,293 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.13.GA-re dhat-1
13:22:21,300 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementati on Version 3.0.13.GA-redhat-1
13:22:21,314 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Cr eating http management service using socket-binding (management-http)
13:22:21,318 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.3.4.Final-redhat-1
13:22:21,436 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Po ol -- 33) JBAS010280: Activating Infinispan subsystem.
13:22:21,501 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBA S010408: Starting JCA Subsystem (IronJacamar 1.0.31.Final-redhat-1)
13:22:21,552 INFO [org.jboss.as.connector.subsystems.datasources] (ServerServic e Thread Pool -- 29) JBAS010404: Deploying non-JDBC-compliant driver class com.m ysql.jdbc.Driver (version 5.1)
13:22:21,555 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 39) JBAS0126 15: Activated the following JSF Implementations: [main, 1.2]
13:22:21,613 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 41) JBAS0 11800: Activating Naming Subsystem
13:22:21,628 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: St arting Naming Service
13:22:21,629 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS01 5400: Bound mail session [java:jboss/mail/Default]
13:22:21,754 INFO [org.jboss.as.security] (ServerService Thread Pool -- 46) JBA S013371: Activating Security Subsystem
13:22:21,766 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013370: Current PicketBox version=4.1.1.Final-redhat-1
13:22:21,784 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 48) JBAS0101 53: Node identifier property is set to the default value. Please make sure it is unique.
13:22:21,835 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015537: Activating WebServices Extension
13:22:22,034 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) H Q221000: live server is starting with configuration HornetQ Configuration (clust ered=false,backup=false,sharedStore=true,journalDirectory=/home/ec2-user/EAP-6.4 .0/standalone/data/messagingjournal,bindingsDirectory=/home/ec2-user/EAP-6.4.0/s tandalone/data/messagingbindings,largeMessagesDirectory=/home/ec2-user/EAP-6.4.0 /standalone/data/messaginglargemessages,pagingDirectory=/home/ec2-user/EAP-6.4.0 /standalone/data/messagingpaging)
13:22:22,035 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) H Q221006: Waiting to obtain live lock
13:22:22,132 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) H Q221012: Using AIO Journal
13:22:22,142 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080
13:22:22,183 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080
13:22:22,199 INFO [org.apache.coyote.ajp] (MSC service thread 1-1) JBWEB003046: Starting Coyote AJP/1.3 on ajp-/0.0.0.0:8009
13:22:22,433 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:9999
13:22:22,463 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 0.0.0.0:4447
13:22:22,475 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) H Q221034: Waiting to obtain live lock
13:22:22,475 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) H Q221035: Live Server Obtained live lock
13:22:22,493 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBW S022052: Starting JBoss Web Services - Stack CXF Server 4.3.4.Final-redhat-1
13:22:22,756 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) H Q221020: Started Netty Acceptor version 3.6.10.Final-266dbdf 0.0.0.0:5455 for CO RE protocol
13:22:22,757 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) H Q221020: Started Netty Acceptor version 3.6.10.Final-266dbdf 0.0.0.0:5445 for CO RE protocol
13:22:22,762 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) H Q221007: Server is now live
13:22:22,763 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) H Q221001: HornetQ Server version 2.3.25.Final (2.3.x, 123) [ba04a308-12b0-11e8-bc b4-0dbfec32df52]
13:22:22,790 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 53) HQ 121005: Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "ip-172-31-25-247.ap-southeast-2.compute.internal". If this new address is i ncorrect please manually configure the connector to use the proper one.
13:22:22,811 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JB AS011601: Bound messaging object to jndi name java:/jms/AppianProcessIntegration ConnectionFactory
13:22:22,811 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JB AS011601: Bound messaging object to jndi name java:jboss/exported/jms/AppianProc essIntegrationConnectionFactory
13:22:22,827 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) H Q221003: trying to deploy queue jms.queue.jms/ProcessQueue
13:22:22,842 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JB AS011601: Bound messaging object to jndi name java:/jms/AppianProcessIntegration Queue
13:22:22,842 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JB AS011601: Bound messaging object to jndi name java:jboss/exported/jms/AppianProc essIntegrationQueue
13:22:22,861 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) JBAS010406: Registered connection factory java:/JmsXA
13:22:22,888 INFO [org.hornetq.ra] (MSC service thread 1-3) HornetQ resource ad aptor started
13:22:22,888 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAda pterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002 : Deployed: file://RaActivatorhornetq-ra
13:22:22,890 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
13:22:22,976 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http mana gement interface listening on 127.0.0.1:9990/management
13:22:22,977 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin con sole listening on http://127.0.0.1:9990
13:22:22,977 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) started in 3648ms - Started 172 of 209 serv ices (64 services are lazy, passive or on-demand)

 

Regards,

Noel

Based on the latest startup, the Appian EAR didn't get deployed. (You can tell this from the amount of services started at the end of the startup output.) Ensure that the <APPIAN_HOME>/ear/suite.ear.dodeploy file exists and remove any .failed or .undepoyed files from <APPIAN_HOME>/ear. Also check that <JBOSS_HOME>/standalone/deployments/*-ds.xml.dodeploy exists

Hey Neil,

We have faced similar issue earlier.I believe you have gone through all steps which are mentioned in appian document,

if you found suite.ear.failed unnder <APPIAN_HOME>/ear/suite.ear directory make sure you renamed it to suite.ear.dodeploy and one more thing you need to check under <JBOSS_HOME>/standalone/deployments/,if you found any appian-mysql-ds.xml.unployed make sure rename it to appian-mysql-ds.xml.dodeploy.

Note:While making these changes you should stop your appian engines,Otherwise there is a chance to get conflicts.