Hi ,
Unable start Appian services after insaling appian in Local Machine.
service_manager.log
Discussion posts and replies are publicly visible
09:24:42,512 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1 09:24:43,151 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1 09:24:43,259 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) starting 09:24:43,265 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Configured system properties: appian.home.ear = C:\Appian18.1\ear awt.toolkit = sun.awt.windows.WToolkit file.encoding = UTF-8 file.encoding.pkg = sun.io file.separator = \ java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment java.awt.headless = true java.awt.printerjob = sun.awt.windows.WPrinterJob java.class.path = C:\Appian18.1\bin\jboss\jboss-eap-6.4\jboss-modules.jar java.class.version = 52.0 java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_92\jre\lib\endorsed java.ext.dirs = C:\Program Files\Java\jdk1.8.0_92\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext java.home = C:\Program Files\Java\jdk1.8.0_92\jre java.io.tmpdir = C:\Users\VENKAT~1\AppData\Local\Temp\ java.library.path = C:\Program Files\Java\jdk1.8.0_92\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Lenovo\FusionEngine;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Common Files\lenovo\easyplussdk\bin;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\TortoiseSVN\bin;C:\Program Files\nodejs\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\WINDOWS\System32\OpenSSH\;C:\Appian18.1\bin\jboss\jboss-eap-6.4\bin;C:\Program Files\Java\jdk1.8.0_92\bin;C:\OpenSSL-Win64\bin;C:\Program Files\MySQL\MySQL Server 5.7\bin;C:\OpenSSL-Win64\bin;C:\Program Files (x86)\MySQL\MySQL Utilities 1.6\;C:\Users\Venkatesh\AppData\Local\Microsoft\WindowsApps;. java.net.preferIPv4Stack = true java.runtime.name = Java(TM) SE Runtime Environment java.runtime.version = 1.8.0_92-b14 java.specification.name = Java Platform API Specification java.specification.vendor = Oracle Corporation java.specification.version = 1.8 java.util.logging.manager = org.jboss.logmanager.LogManager java.vendor = Oracle Corporation java.vendor.url = http://java.oracle.com/ java.vendor.url.bug = http://bugreport.sun.com/bugreport/ java.version = 1.8.0_92 java.vm.info = mixed mode java.vm.name = Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name = Java Virtual Machine Specification java.vm.specification.vendor = Oracle Corporation java.vm.specification.version = 1.8 java.vm.vendor = Oracle Corporation java.vm.version = 25.92-b14 javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory jboss.as.management.blocking.timeout = 3600 jboss.home.dir = C:\Appian18.1\bin\jboss\jboss-eap-6.4 jboss.host.name = gsc_20 jboss.modules.dir = C:\Appian18.1\bin\jboss\jboss-eap-6.4\modules jboss.node.name = gsc_20 jboss.qualified.host.name = gsc_20 jboss.server.base.dir = C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone jboss.server.config.dir = C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\configuration jboss.server.data.dir = C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\data jboss.server.default.config = standalone.xml jboss.server.deploy.dir = C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\data\content jboss.server.log.dir = C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\log jboss.server.name = gsc_20 jboss.server.persist.config = true jboss.server.temp.dir = C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\tmp line.separator = logging.configuration = file:C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\configuration/logging.properties module.path = C:\Appian18.1\bin\jboss\jboss-eap-6.4\modules org.apache.catalina.connector.URI_ENCODING = UTF-8 org.jboss.boot.log.file = C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\log\server.log org.jboss.resolver.warning = true org.xml.sax.driver = __redirected.__XMLReaderFactory os.arch = amd64 os.name = Windows 10 os.version = 10.0 path.separator = ; program.name = standalone.bat sun.arch.data.model = 64 sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_92\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_92\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_92\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_92\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_92\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_92\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_92\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_92\jre\classes sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_92\jre\bin sun.cpu.endian = little sun.cpu.isalist = amd64 sun.desktop = windows sun.io.unicode.encoding = UnicodeLittle sun.java.command = C:\Appian18.1\bin\jboss\jboss-eap-6.4\jboss-modules.jar -mp C:\Appian18.1\bin\jboss\jboss-eap-6.4\modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=C:\Appian18.1\bin\jboss\jboss-eap-6.4 sun.java.launcher = SUN_STANDARD sun.jnu.encoding = Cp1252 sun.management.compiler = HotSpot 64-Bit Tiered Compilers sun.os.patch.level = sun.rmi.dgc.client.gcInterval = 3600000 sun.rmi.dgc.server.gcInterval = 3600000 sun.stderr.encoding = cp437 sun.stdout.encoding = cp437 user.country = US user.dir = C:\Appian18.1\bin\jboss\jboss-eap-6.4\bin user.home = C:\Users\Venkatesh user.language = en user.name = Venkatesh user.script = user.timezone = GMT user.variant = 09:24:43,266 DEBUG [org.jboss.as.config] (MSC service thread 1-6) VM Arguments: -Xloggc:C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\log\gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms2048m -Xmx4096m -XX:+HeapDumpOnOutOfMemoryError -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -XX:+CMSClassUnloadingEnabled -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 -Dappian.home.ear=C:\Appian18.1\ear -Djboss.as.management.blocking.timeout=3600 -Dorg.jboss.resolver.warning=true -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\log\server.log -Dlogging.configuration=file:C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\configuration/logging.properties 09:24:46,371 WARN [org.jboss.messaging] (ServerService Thread Pool -- 7) 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! 09:24:46,372 WARN [org.jboss.messaging] (ServerService Thread Pool -- 7) 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! 09:25:24,940 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015051: Deployment content C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\deployments\appian-ds.xml appears to be incomplete and is not progressing toward completion. This content cannot be auto-deployed. 09:25:25,277 INFO [org.xnio] (MSC service thread 1-8) XNIO Version 3.0.13.GA-redhat-1 09:25:25,289 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) 09:25:25,295 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.0.13.GA-redhat-1 09:25:25,603 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015537: Activating WebServices Extension 09:25:25,615 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem. 09:25:25,630 INFO [org.jboss.as.security] (ServerService Thread Pool -- 46) JBAS013371: Activating Security Subsystem 09:25:25,636 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 48) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique. 09:25:25,652 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 41) JBAS011800: Activating Naming Subsystem 09:25:25,712 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013370: Current PicketBox version=4.1.1.Final-redhat-1 09:25:25,720 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 39) JBAS012615: Activated the following JSF Implementations: [main, 1.2] 09:25:25,720 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.31.Final-redhat-1) 09:25:26,451 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1) 09:25:26,900 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 3.3.4.Final-redhat-1 09:25:27,000 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service 09:25:27,002 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default] 09:25:27,011 WARN [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal 09:25:27,359 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\data\messagingjournal,bindingsDirectory=C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\data\messagingbindings,largeMessagesDirectory=C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\data\messaginglargemessages,pagingDirectory=C:\Appian18.1\bin\jboss\jboss-eap-6.4\standalone\data\messagingpaging) 09:25:27,369 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221006: Waiting to obtain live lock 09:25:27,447 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221013: Using NIO Journal 09:25:27,498 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999 09:25:27,560 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 0.0.0.0:4447 09:25:27,752 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/AppianPrimary] 09:25:27,855 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221034: Waiting to obtain live lock 09:25:27,860 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221035: Live Server Obtained live lock 09:25:27,867 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080 09:25:27,963 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-6) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080 09:25:27,964 INFO [org.apache.coyote.ajp] (MSC service thread 1-8) JBWEB003046: Starting Coyote AJP/1.3 on ajp-/0.0.0.0:8009 09:25:28,274 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.4.Final-redhat-1 09:25:29,042 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221020: Started Netty Acceptor version 3.6.10.Final-266dbdf 0.0.0.0:5455 for CORE protocol 09:25:29,126 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221020: Started Netty Acceptor version 3.6.10.Final-266dbdf 0.0.0.0:5445 for CORE protocol 09:25:29,189 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221007: Server is now live 09:25:29,190 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221001: HornetQ Server version 2.3.25.Final (2.3.x, 123) [a28867fa-6372-11e8-9beb-9b82e56ab4b7] 09:25:29,199 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221003: trying to deploy queue jms.queue.jms/ProcessQueue 09:25:29,207 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:/jms/AppianProcessIntegrationQueue 09:25:29,208 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/AppianProcessIntegrationQueue 09:25:29,294 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-5) JBAS010406: Registered connection factory java:/JmsXA 09:25:29,347 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 53) HQ121005: Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "GSC_20". If this new address is incorrect please manually configure the connector to use the proper one. 09:25:29,399 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JBAS011601: Bound messaging object to jndi name java:/jms/AppianProcessIntegrationConnectionFactory 09:25:29,416 INFO [org.hornetq.ra] (MSC service thread 1-5) HornetQ resource adaptor started 09:25:29,425 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/AppianProcessIntegrationConnectionFactory 09:25:29,428 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-5) IJ020002: Deployed: file://RaActivatorhornetq-ra 09:25:29,441 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] 09:26:30,712 WARN [org.jboss.as.dependency.private] (MSC service thread 1-8) JBAS015867: Deployment "deployment.suite.ear" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice. 09:26:30,738 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS015867: Deployment "deployment.suite.ear.conf" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice. 09:26:30,742 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS015867: Deployment "deployment.suite.ear.resources" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice. 09:26:30,744 WARN [org.jboss.as.dependency.private] (MSC service thread 1-8) JBAS015867: Deployment "deployment.suite.ear" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice. 09:26:30,744 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS015867: Deployment "deployment.suite.ear.resources" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice. 09:26:30,745 WARN [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS015867: Deployment "deployment.suite.ear.conf" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice. 09:26:31,137 WARN [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016012: Deployment deployment "suite.ear" contains CDI annotations but beans.xml was not found. 09:26:31,217 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) IJ020001: Required license terms for file:/C:/Appian18.1/ear/suite.ear/email-poller.rar/ 09:26:31,402 ERROR [stderr] (MSC service thread 1-7) log4j:WARN No appenders could be found for logger (org.apache.commons.configuration.PropertiesConfiguration). 09:26:31,402 ERROR [stderr] (MSC service thread 1-7) log4j:WARN Please initialize the log4j system properly. 09:26:31,402 ERROR [stderr] (MSC service thread 1-7) log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. 09:26:32,672 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-7) IJ020002: Deployed: file:/C:/Appian18.1/ear/suite.ear/unattended-request-poller.rar/ 09:26:32,675 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) IJ020002: Deployed: file:/C:/Appian18.1/ear/suite.ear/email-poller.rar/ 09:26:33,410 INFO [org.jboss.web] (ServerService Thread Pool -- 60) JBAS018210: Register web context: /suite 09:26:34,261 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 60) Initializing Spring root WebApplicationContext 09:26:38,550 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:38,547 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.persistence.search.SearchServerClientConfiguration - Using the Search Server client configuration specified in appian-topology.xml. 09:26:38,731 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:38,730 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.persistence.search.AppianSearchSpringConfig - initializing client with server addresses: [localhost:9300] 09:26:39,565 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:39,565 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.persistence.search.AppianSearchSpringConfig - client settings: {client.transport.ping_timeout=20s, client.transport.sniff=true, client.type=transport, cluster.name=appian-search-cluster, name=Client 891744DE, network.server=false, node.client=true, path.logs=C:\Appian18.1\logs, transport.ping_schedule=5s} 09:26:39,566 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:39,566 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.persistence.search.AppianSearchSpringConfig - client configured nodes: [{#transport#-1}{localhost}{127.0.0.1:9300}] 09:26:39,567 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:39,567 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.persistence.search.AppianSearchSpringConfig - client connected nodes: [{Node localhost:9300}{NSqsQyvDRHutpGcy6UAyZA}{localhost}{127.0.0.1:9300}] 09:26:39,701 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:39,701 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.persistence.search.AppianSearchSpringConfig - search server: productName=ElasticSearch, productVersion=2.4.5, driverName=org.elasticsearch.client.transport.TransportClient, driverVersion=2.4.5 09:26:46,840 ERROR [stderr] (ServerService Thread Pool -- 60) Wed May 30 09:26:46 GMT 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. 09:26:47,963 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:47,963 [ServerService Thread Pool -- 60] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Checking schema and migrating if necessary (appian/db/changelog/db-changelog-master.xml)... 09:26:53,484 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:53,483 [ServerService Thread Pool -- 60] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Schema check/migration completed successfully. 09:26:53,487 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:53,487 [ServerService Thread Pool -- 60] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Verifying that entity mappings match the schema... 09:26:56,256 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:56,256 [ServerService Thread Pool -- 60] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Mappings and schema validated successfully. 09:26:57,617 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:26:57,616 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.crypto.KeyStoreConfig - KeyStoreConfig initialized in 0 seconds 09:27:01,673 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:01,672 [ServerService Thread Pool -- 60] INFO com.appiancorp.rdbms.config.PrimaryDataSourceConfig - Validating and initializing the Appian data source: java:/jdbc/AppianPrimary 09:27:01,787 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:01,787 [ServerService Thread Pool -- 60] INFO com.appiancorp.rdbms.config.PrimaryDataSourceConfig - Appian data source: java:/jdbc/AppianPrimary DataSourceMetadata[databaseProductName=MySQL, databaseProductVersion=5.7.22-log, driverName=MySQL Connector Java, driverVersion=mysql-connector-java-5.1.46 ( Revision: 9cc87a48e75c2d2e87c1a293b2862ce651cb256e )] 09:27:19,115 ERROR [stderr] (ServerService Thread Pool -- 60) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found 09:27:26,101 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,079 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Wed May 30 09:26:34 GMT 2018]; root of context hierarchy] 09:27:26,134 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,134 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Wed May 30 09:26:34 GMT 2018]; root of context hierarchy] 09:27:26,142 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,142 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Wed May 30 09:26:34 GMT 2018]; root of context hierarchy] 09:27:26,202 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,202 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Wed May 30 09:26:34 GMT 2018]; root of context hierarchy] 09:27:26,251 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,248 [ServerService Thread Pool -- 60] INFO com.appiancorp.ix.spring.IaSpringContextListener - Enabling ia listener for Appian data source transactions. 09:27:26,292 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,292 [ServerService Thread Pool -- 60] INFO com.appiancorp.ix.spring.IaSpringContextListener - Scheduling ia replication timer with a 60000 ms delay. 09:27:26,308 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,308 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Wed May 30 09:26:34 GMT 2018]; root of context hierarchy] 09:27:26,367 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,361 [ServerService Thread Pool -- 60] INFO com.appiancorp.tempo.rdbms.index.NewsIndexSpringContextListener - Enabling news listener for Appian data source transactions. 09:27:26,416 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,416 [ServerService Thread Pool -- 60] INFO com.appiancorp.tempo.rdbms.index.NewsIndexSpringContextListener - Scheduling news replication timer with a 60000 ms delay. 09:27:26,418 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,418 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Wed May 30 09:26:34 GMT 2018]; root of context hierarchy] 09:27:26,436 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,436 [ServerService Thread Pool -- 60] INFO com.appiancorp.applicationpatch.PatchSchemaSpringContextListener - Checking for patch schemas in Data Server... 09:27:26,739 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:26,739 [ServerService Thread Pool -- 60] INFO com.appiancorp.applicationpatch.PatchSchemaSpringContextListener - Schemas already exist. 09:27:38,454 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:27:38,453 [ServerService Thread Pool -- 60] INFO com.appiancorp.rdbms.datasource.BusinessDataSourceValidator - Validating data sources. 09:27:40,305 INFO [stdout] (Appian Timer - 2) 2018-05-30 09:27:40,304 [Appian Timer - 2] WARN com.appiancorp.common.sigar.SigarLoader - Sigar native library not found at /native/sigar/sigar-amd64-winnt.dll 09:27:40,317 INFO [stdout] (Appian Timer - 2) 2018-05-30 09:27:40,317 [Appian Timer - 2] WARN com.appiancorp.common.sigar.SigarLoader - Sigar native library not available. Some system metrics are not available on Windows. 09:28:29,321 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 8) Wed May 30 09:28:29 GMT 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. 09:28:41,005 ERROR [stderr] (Spring executor 11) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found 09:29:25,034 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,033 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - SAP' (appian.integration.sap) version 1.0.67-hf1. 09:29:25,035 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,035 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - HTTP' (appian.integration.httpclient) version 18.1.81. 09:29:25,037 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,036 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - SharePoint' (appian.integration.sharepoint) version 1.0.67-hf1. 09:29:25,038 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,038 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - Siebel' (appian.integration.siebel) version 1.0.67-hf1. 09:29:25,039 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,039 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - CMIS' (appian.integration.cmis) version 1.0.67-hf1. 09:29:25,041 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,040 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Atlassian REST - Module Types' (com.atlassian.plugins.rest.atlassian-rest-module) version 2.6.7. 09:29:25,043 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,042 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Functions' (appian.system.scripting-functions) version 18.1.81. 09:29:25,051 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,051 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Atlassian Template Renderer Velocity 1.6 Plugin' (com.atlassian.templaterenderer.atlassian-template-renderer-velocity16-plugin-1.3.1) version 1.3.1. 09:29:25,053 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,053 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Smart Services' (appian.system.smart-services) version 18.1.81. 09:29:25,055 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,054 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - Salesforce' (appian.integration.salesforce) version 1.0.67-hf1. 09:29:25,056 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,056 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Atlassian Template Renderer API' (com.atlassian.templaterenderer.atlassian-template-renderer-api-1.3.1) version 1.3.1. 09:29:25,069 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,057 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian REST API' (appian.system.rest-api) version 18.1.81. 09:29:25,074 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,074 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - Dynamics' (appian.integration.dynamics) version 1.0.67-hf1. 09:29:25,168 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,168 [ServerService Thread Pool -- 60] INFO com.appiancorp.plugins.PluginLoader - Appian Plug-in Framework started in 0:01:46.672 09:29:25,214 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,213 [ServerService Thread Pool -- 60] INFO com.appiancorp.applications.BundledApplicationsLoader - Loading system objects. 09:29:25,266 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:25,266 [ServerService Thread Pool -- 60] INFO com.appiancorp.applications.BundledApplicationsLoader - Completed loading system objects in 0:00:00.051 09:29:26,236 INFO [stdout] (ServerService Thread Pool -- 60) 2018-05-30 09:29:26,235 [ServerService Thread Pool -- 60] INFO com.appiancorp.common.web.WeblogicSessionAttributeClassLoaderRequestFilter - WeblogicSessionAttributeClassLoaderRequestFilter enabled = false server info = JBoss Web/7.5.7.Final-redhat-1 09:29:27,005 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 60) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok) 09:29:27,609 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 60) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok) 09:29:30,827 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) JBAS014142: Started message driven bean 'UnattendedRequestHandlerBean' with 'suite.ear#unattended-request-poller.rar' resource adapter 09:29:30,896 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) JBAS014142: Started message driven bean 'JmsProcessIntegrationHandlerBean' with 'hornetq-ra' resource adapter 09:29:30,964 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'EmailHandlerBean' with 'suite.ear#email-poller.rar' resource adapter 09:29:31,058 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "suite.ear" (runtime-name : "suite.ear") 09:29:31,180 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."appian-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-ds.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "appian-ds.xml" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_92] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Illegal name "useSSL:false" (PI target, entity/notation name): can not contain a colon (XML Namespaces 1.0#6) at [row,col {unknown-source}]: [11,123] at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:99) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] ... 5 more Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal name "useSSL:false" (PI target, entity/notation name): can not contain a colon (XML Namespaces 1.0#6) at [row,col {unknown-source}]: [11,123] at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:606) at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:479) at com.ctc.wstx.sr.StreamScanner.throwNsColonException(StreamScanner.java:2430) at com.ctc.wstx.sr.StreamScanner.parseFullName(StreamScanner.java:1951) at com.ctc.wstx.sr.StreamScanner.parseEntityName(StreamScanner.java:2050) at com.ctc.wstx.sr.StreamScanner.fullyResolveEntity(StreamScanner.java:1517) at com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4701) at com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.java:4147) at com.ctc.wstx.sr.BasicStreamReader.getElementText(BasicStreamReader.java:679) at org.jboss.jca.common.metadata.AbstractParser.rawElementText(AbstractParser.java:168) at org.jboss.jca.common.metadata.AbstractParser.elementAsString(AbstractParser.java:154) at org.jboss.jca.common.metadata.AbstractParser.parseConfigProperty(AbstractParser.java:826) at org.jboss.jca.common.metadata.ds.v11.DsParser.parseXADataSource(DsParser.java:150) at org.jboss.jca.common.metadata.ds.v10.DsParser.parseDataSources(DsParser.java:185) at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:124) at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:87) at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:89) ... 6 more 09:29:31,281 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "appian-ds.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"appian-ds.xml\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"appian-ds.xml\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"appian-ds.xml\" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Illegal name \"useSSL:false\" (PI target, entity/notation name): can not contain a colon (XML Namespaces 1.0#6) at [row,col {unknown-source}]: [11,123] Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal name \"useSSL:false\" (PI target, entity/notation name): can not contain a colon (XML Namespaces 1.0#6) at [row,col {unknown-source}]: [11,123]"}} 09:29:31,290 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "appian-ds.xml" was rolled back with the following failure message: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"appian-ds.xml\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"appian-ds.xml\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"appian-ds.xml\" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Illegal name \"useSSL:false\" (PI target, entity/notation name): can not contain a colon (XML Namespaces 1.0#6) at [row,col {unknown-source}]: [11,123] Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal name \"useSSL:false\" (PI target, entity/notation name): can not contain a colon (XML Namespaces 1.0#6) at [row,col {unknown-source}]: [11,123]"}} 09:29:31,302 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."appian-ds.xml".PARSE 09:29:31,439 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 09:29:31,442 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 09:29:31,444 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) started in 289911ms - Started 1703 of 1740 services (83 services are lazy, passive or on-demand)
vimalkumars (vimals) : Can you please find the Latest Log File.
Please find attachedscreenshot of Jboss CMD Prompt.
appian-ds.xml file:
<?xml version="1.0" encoding="UTF-8"?> <datasources xmlns="http://www.jboss.org/ironjacamar/schema"> <xa-datasource jndi-name="java:/jdbc/AppianPrimary" 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">appianprimary</xa-datasource-property> <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>
Note:
1. suite.ear fle deployed but appian-ds.xml file failed.
Hi Venkatesh,
Change the url in appian-ds.xml as below
<xa-datasource-property name="URL">jdbc:mysql://localhost:3306/appianprimary?useOldAliasMetadataBehavior=true&useSSL=false</xa-datasource-property>
Also, make sure to verify the below before starting JBOSS
1. Make sure that the suite.ear.dodeploy file exists and does not have the extensions .undeployed, .isdeploying or .failed:
<APPIAN_HOME>\_admin\_scripts\configure\templates\ear\suite.ear.dodeploy
2. Delete the appian-mysql-ds.xml.deployed file if it has the extensions .undeployed, .isdeploying or .failed:
<JBOSS_HOME>\standalone\deployments\appian-mysql-ds.xml.deployed
It is showing same error.
Please find below log error.
We have tried with ; at end but still appian-mysql-ds failed.
We have checked above mentioned steps and still appian-mysql-ds file failed..
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."appian-mysql-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-mysql-ds.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "appian-mysql-ds.xml" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_92] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92]Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL' at [row,col {unknown-source}]: [11,118] at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:99) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] ... 5 moreCaused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL' at [row,col {unknown-source}]: [11,118] at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:639) at com.ctc.wstx.sr.StreamScanner.parseEntityName(StreamScanner.java:2059) at com.ctc.wstx.sr.StreamScanner.fullyResolveEntity(StreamScanner.java:1517) at com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4701) at com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.java:4147) at com.ctc.wstx.sr.BasicStreamReader.getElementText(BasicStreamReader.java:679) at org.jboss.jca.common.metadata.AbstractParser.rawElementText(AbstractParser.java:168) at org.jboss.jca.common.metadata.AbstractParser.elementAsString(AbstractParser.java:154) at org.jboss.jca.common.metadata.AbstractParser.parseConfigProperty(AbstractParser.java:826) at org.jboss.jca.common.metadata.ds.v11.DsParser.parseXADataSource(DsParser.java:150) at org.jboss.jca.common.metadata.ds.v10.DsParser.parseDataSources(DsParser.java:185) at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:124) at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:87) at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:89) ... 6 more
05:30:13,083 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "appian-mysql-ds.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"appian-mysql-ds.xml\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"appian-mysql-ds.xml\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"appian-mysql-ds.xml\" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL' at [row,col {unknown-source}]: [11,118] Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL' at [row,col {unknown-source}]: [11,118]"}}05:30:13,094 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "appian-mysql-ds.xml" was rolled back with the following failure message: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"appian-mysql-ds.xml\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"appian-mysql-ds.xml\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"appian-mysql-ds.xml\" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL' at [row,col {unknown-source}]: [11,118] Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL' at [row,col {unknown-source}]: [11,118]"}}05:30:13,095 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on 127.0.0.1:9990/management05:30:13,145 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:999005:30:13,147 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) started (with errors) in 152198ms - Started 1706 of 1742 services (1 services failed or missing dependencies, 83 services are lazy, passive or on-demand)05:30:13,154 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status reportJBAS014777: Services which failed to start: service jboss.deployment.unit."appian-mysql-ds.xml".PARSE
Yes!!.. Vimal we have tried with above URL.
We have performed below steps:
1. Stopped the Jboss Server.
2. Stopped Search Server and Data Server.
3. Stopped all the Appian Services.
4. We have performed the configure script , and we have used above URL without useSSL Connection in mysql-ds.xml file.
5. After restarting the Appian Services and Jboss , Please find below Log error.
ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "appian-mysql-ds.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"appian-mysql-ds.xml\".FIRST_MODULE_USE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"appian-mysql-ds.xml\".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment \"appian-mysql-ds.xml\" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS010464: Exception deploying datasource java:/jdbc/AppianPrimary Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.java:/jdbc/AppianPrimary is already registered"}}07:00:56,074 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "appian-mysql-ds.xml" (runtime-name : "appian-mysql-ds.xml")07:00:56,080 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "suite.ear" (runtime-name : "suite.ear")07:00:56,103 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status reportJBAS014777: Services which failed to start: service jboss.deployment.unit."appian-mysql-ds.xml".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-mysql-ds.xml".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment "appian-mysql-ds.xml" .
Thanks InAdvance!!
We are using the below software:Details:=====1. MySQL 5.7.222.My SQL Connector 5.1.462.JBOSS 6.4.03. Appian 18.1
4. OS: Windows 10 , 64 Bit.
May be issue with Jboss version.In System Requirements mentioned JBoss version minimum requirement 6.4.xx and Found on KB also related to same issue.
https://community.appian.com/support/w/kb/439/kb-1224-jbas018733-failed-to-process-phase-first_5f00_module_5f00_use-of-deployment-suite-ear-error-returned-during-jboss-startup
Thanks InAdvance.