Hi ,
When we start Jboss server appian-mysql-ds.xml is failed and suite.ear file id deployed .
We have restated two/three times but still we are getting same error , Before start the Jboss deleted all extensions .undeployed, .isdeploying or .failed files also but
still we are getting same error.
i have installed below software for Local Installation:
Is there any issue with Jboss version ?, because in System requirement page mentioned minimum 6.4.14 OR Later.
https://docs.appian.com/suite/help/18.1/System_Requirements.html.
We have found one KB For same error message and Please find below link.
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
Can anyone please help me out on his issue.
Please find below log file.
07:25:30,473 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:25:30,608 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "appian-mysql-ds.xml" (runtime-name : "appian-mysql-ds.xml") 07:25:30,613 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "suite.ear" (runtime-name : "suite.ear") 07:25:30,615 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014777: 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"
Discussion posts and replies are publicly visible
Please find attached Log File.
07:22:04,283 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.6.Final-redhat-1 07:22:04,462 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1 07:22:04,535 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) starting 07:22:04,541 DEBUG [org.jboss.as.config] (MSC service thread 1-7) 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 = 07:22:04,542 DEBUG [org.jboss.as.config] (MSC service thread 1-7) 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 07:22:06,143 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! 07:22:06,155 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! 07:22:38,292 INFO [org.xnio] (MSC service thread 1-8) XNIO Version 3.0.13.GA-redhat-1 07:22:38,300 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) 07:22:38,307 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.0.13.GA-redhat-1 07:22:38,380 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem. 07:22:38,411 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 41) JBAS011800: Activating Naming Subsystem 07:22:38,429 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015537: Activating WebServices Extension 07:22:38,431 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. 07:22:38,443 INFO [org.jboss.as.security] (ServerService Thread Pool -- 46) JBAS013371: Activating Security Subsystem 07:22:38,495 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 39) JBAS012615: Activated the following JSF Implementations: [main, 1.2] 07:22:38,498 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013370: Current PicketBox version=4.1.1.Final-redhat-1 07:22:38,598 INFO [org.jboss.as.connector.logging] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.31.Final-redhat-1) 07:22:38,694 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service 07:22:38,706 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default] 07:22:38,927 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 3.3.4.Final-redhat-1 07:22:39,148 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) 07:22:39,692 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on 127.0.0.1:9999 07:22:39,697 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 0.0.0.0:4447 07:22:39,825 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080 07:22:39,858 WARN [org.jboss.as.messaging] (MSC service thread 1-7) 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 07:22:39,836 INFO [org.apache.coyote.ajp] (MSC service thread 1-5) JBWEB003046: Starting Coyote AJP/1.3 on ajp-/0.0.0.0:8009 07:22:39,956 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080 07:22:40,003 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.4.Final-redhat-1 07:22:40,102 WARN [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010489: -ds.xml file deployments are deprecated. Support may be removed in a future version. 07:22:40,217 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) 07:22:40,259 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: 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" 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: JBAS010464: Exception deploying datasource java:/jdbc/AppianPrimary at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:162) 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: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.java:/jdbc/AppianPrimary is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:236) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:742) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:345) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:330) at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:158) ... 6 more 07:22:40,273 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/jdbc/AppianPrimary] 07:22:40,278 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221006: Waiting to obtain live lock 07:22:40,422 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221013: Using NIO Journal 07:22:40,785 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221034: Waiting to obtain live lock 07:22:40,785 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221035: Live Server Obtained live lock 07:22:41,993 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 07:22:41,998 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 07:22:42,011 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221007: Server is now live 07:22:42,017 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] 07:22:42,027 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 52) 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. 07:22:42,067 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:/jms/AppianProcessIntegrationConnectionFactory 07:22:42,069 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/AppianProcessIntegrationConnectionFactory 07:22:42,135 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/JmsXA 07:22:42,142 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 53) HQ221003: trying to deploy queue jms.queue.jms/ProcessQueue 07:22:42,360 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JBAS011601: Bound messaging object to jndi name java:/jms/AppianProcessIntegrationQueue 07:22:42,367 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started 07:22:42,422 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/AppianProcessIntegrationQueue 07:22:42,445 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra 07:22:42,490 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-5) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] 07:23:30,528 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. 07:23:30,667 WARN [org.jboss.as.dependency.private] (MSC service thread 1-7) 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. 07:23:30,688 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. 07:23:30,713 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. 07:23:30,745 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. 07:23:30,745 WARN [org.jboss.as.dependency.private] (MSC service thread 1-7) 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. 07:23:33,193 WARN [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016012: Deployment deployment "suite.ear" contains CDI annotations but beans.xml was not found. 07:23:33,213 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/ 07:23:33,322 ERROR [stderr] (MSC service thread 1-4) log4j:WARN No appenders could be found for logger (org.apache.commons.configuration.PropertiesConfiguration). 07:23:33,350 ERROR [stderr] (MSC service thread 1-4) log4j:WARN Please initialize the log4j system properly. 07:23:33,396 ERROR [stderr] (MSC service thread 1-4) log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. 07:23:34,488 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-5) IJ020002: Deployed: file:/C:/Appian18.1/ear/suite.ear/email-poller.rar/ 07:23:34,492 INFO [org.jboss.web] (ServerService Thread Pool -- 144) JBAS018210: Register web context: /suite 07:23:34,544 INFO [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-4) IJ020002: Deployed: file:/C:/Appian18.1/ear/suite.ear/unattended-request-poller.rar/ 07:23:35,566 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 144) Initializing Spring root WebApplicationContext 07:23:39,685 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:39,683 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.persistence.search.SearchServerClientConfiguration - Using the Search Server client configuration specified in appian-topology.xml. 07:23:39,845 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:39,844 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.persistence.search.AppianSearchSpringConfig - initializing client with server addresses: [localhost:9300] 07:23:40,621 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:40,621 [ServerService Thread Pool -- 144] 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 C822EA8B, network.server=false, node.client=true, path.logs=C:\Appian18.1\logs, transport.ping_schedule=5s} 07:23:40,623 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:40,623 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.persistence.search.AppianSearchSpringConfig - client configured nodes: [{#transport#-1}{localhost}{127.0.0.1:9300}] 07:23:40,624 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:40,624 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.persistence.search.AppianSearchSpringConfig - client connected nodes: [{Node localhost:9300}{UeoWZfVPRNa6gTFuN6d2Ng}{localhost}{127.0.0.1:9300}] 07:23:40,726 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:40,726 [ServerService Thread Pool -- 144] 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 07:23:47,518 ERROR [stderr] (ServerService Thread Pool -- 144) Thu May 31 07:23:47 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. 07:23:48,607 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:48,605 [ServerService Thread Pool -- 144] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Checking schema and migrating if necessary (appian/db/changelog/db-changelog-master.xml)... 07:23:55,110 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:55,110 [ServerService Thread Pool -- 144] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Schema check/migration completed successfully. 07:23:55,115 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:55,115 [ServerService Thread Pool -- 144] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Verifying that entity mappings match the schema... 07:23:55,956 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:55,956 [ServerService Thread Pool -- 144] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Mappings and schema validated successfully. 07:23:57,249 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:23:57,248 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.crypto.KeyStoreConfig - KeyStoreConfig initialized in 0 seconds 07:24:03,115 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:03,114 [ServerService Thread Pool -- 144] INFO com.appiancorp.rdbms.config.PrimaryDataSourceConfig - Validating and initializing the Appian data source: java:/jdbc/AppianPrimary 07:24:03,158 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:03,158 [ServerService Thread Pool -- 144] 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 )] 07:24:14,809 ERROR [stderr] (ServerService Thread Pool -- 144) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found 07:24:23,180 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,178 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:24:23,189 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,188 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:24:23,199 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,199 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:24:23,248 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,247 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:24:23,292 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,291 [ServerService Thread Pool -- 144] INFO com.appiancorp.ix.spring.IaSpringContextListener - Enabling ia listener for Appian data source transactions. 07:24:23,311 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,311 [ServerService Thread Pool -- 144] INFO com.appiancorp.ix.spring.IaSpringContextListener - Scheduling ia replication timer with a 60000 ms delay. 07:24:23,328 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,328 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:24:23,334 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,333 [ServerService Thread Pool -- 144] INFO com.appiancorp.tempo.rdbms.index.NewsIndexSpringContextListener - Enabling news listener for Appian data source transactions. 07:24:23,360 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,360 [ServerService Thread Pool -- 144] INFO com.appiancorp.tempo.rdbms.index.NewsIndexSpringContextListener - Scheduling news replication timer with a 60000 ms delay. 07:24:23,365 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,363 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextRefreshedEvent: org.springframework.context.event.ContextRefreshedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:24:23,375 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,374 [ServerService Thread Pool -- 144] INFO com.appiancorp.applicationpatch.PatchSchemaSpringContextListener - Checking for patch schemas in Data Server... 07:24:23,770 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:23,769 [ServerService Thread Pool -- 144] INFO com.appiancorp.applicationpatch.PatchSchemaSpringContextListener - Schemas already exist. 07:24:35,177 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:24:35,177 [ServerService Thread Pool -- 144] INFO com.appiancorp.rdbms.datasource.BusinessDataSourceValidator - Validating data sources. 07:24:37,269 INFO [stdout] (Appian Timer - 2) 2018-05-31 07:24:37,267 [Appian Timer - 2] WARN com.appiancorp.common.sigar.SigarLoader - Sigar native library not found at /native/sigar/sigar-amd64-winnt.dll 07:24:37,316 INFO [stdout] (Appian Timer - 2) 2018-05-31 07:24:37,316 [Appian Timer - 2] WARN com.appiancorp.common.sigar.SigarLoader - Sigar native library not available. Some system metrics are not available on Windows. 07:25:06,948 ERROR [stderr] (Spring executor 3) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found 07:25:25,235 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,234 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - SAP' (appian.integration.sap) version 1.0.67-hf1. 07:25:25,236 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,236 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - HTTP' (appian.integration.httpclient) version 18.1.81. 07:25:25,237 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,237 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - SharePoint' (appian.integration.sharepoint) version 1.0.67-hf1. 07:25:25,239 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,239 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - Siebel' (appian.integration.siebel) version 1.0.67-hf1. 07:25:25,240 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,240 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - CMIS' (appian.integration.cmis) version 1.0.67-hf1. 07:25:25,241 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,241 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Atlassian REST - Module Types' (com.atlassian.plugins.rest.atlassian-rest-module) version 2.6.7. 07:25:25,243 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,243 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Functions' (appian.system.scripting-functions) version 18.1.81. 07:25:25,247 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,247 [ServerService Thread Pool -- 144] 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. 07:25:25,250 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,249 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Smart Services' (appian.system.smart-services) version 18.1.81. 07:25:25,253 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,253 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - Salesforce' (appian.integration.salesforce) version 1.0.67-hf1. 07:25:25,255 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,255 [ServerService Thread Pool -- 144] 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. 07:25:25,256 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,256 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian REST API' (appian.system.rest-api) version 18.1.81. 07:25:25,258 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,258 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.LoggingPluginEventListener - Successfully installed Plug-in 'Appian Integration - Dynamics' (appian.integration.dynamics) version 1.0.67-hf1. 07:25:25,269 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,269 [ServerService Thread Pool -- 144] INFO com.appiancorp.plugins.PluginLoader - Appian Plug-in Framework started in 0:00:50.049 07:25:25,282 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,282 [ServerService Thread Pool -- 144] INFO com.appiancorp.applications.BundledApplicationsLoader - Loading system objects. 07:25:25,301 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:25,301 [ServerService Thread Pool -- 144] INFO com.appiancorp.applications.BundledApplicationsLoader - Completed loading system objects in 0:00:00.017 07:25:26,334 INFO [stdout] (ServerService Thread Pool -- 144) 2018-05-31 07:25:26,333 [ServerService Thread Pool -- 144] INFO com.appiancorp.common.web.WeblogicSessionAttributeClassLoaderRequestFilter - WeblogicSessionAttributeClassLoaderRequestFilter enabled = false server info = JBoss Web/7.5.7.Final-redhat-1 07:25:27,927 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 144) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok) 07:25:28,432 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 144) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok) 07:25:28,770 ERROR [stderr] (pool-15-thread-1) Thu May 31 07:25:28 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. 07:25:30,235 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) JBAS014142: Started message driven bean 'UnattendedRequestHandlerBean' with 'suite.ear#unattended-request-poller.rar' resource adapter 07:25:30,318 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) JBAS014142: Started message driven bean 'JmsProcessIntegrationHandlerBean' with 'hornetq-ra' resource adapter 07:25:30,412 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) JBAS014142: Started message driven bean 'EmailHandlerBean' with 'suite.ear#email-poller.rar' resource adapter 07:25:30,473 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:25:30,608 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "appian-mysql-ds.xml" (runtime-name : "appian-mysql-ds.xml") 07:25:30,613 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "suite.ear" (runtime-name : "suite.ear") 07:25:30,615 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014777: 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" 07:25:30,972 INFO [org.jboss.web] (ServerService Thread Pool -- 7) JBAS018224: Unregister web context: /suite 07:25:31,008 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 7) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called 07:25:31,011 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 7) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called 07:25:31,825 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,825 [ServerService Thread Pool -- 7] INFO com.appiancorp.plugins.PluginLoader - Appian Plug-in Framework stopped in 0:00:00.789 07:25:31,866 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 7) Closing Spring root WebApplicationContext 07:25:31,868 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,868 [ServerService Thread Pool -- 7] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextClosedEvent: org.springframework.context.event.ContextClosedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:25:31,872 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,872 [ServerService Thread Pool -- 7] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextClosedEvent: org.springframework.context.event.ContextClosedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:25:31,873 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,873 [ServerService Thread Pool -- 7] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextClosedEvent: org.springframework.context.event.ContextClosedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:25:31,881 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,881 [ServerService Thread Pool -- 7] INFO com.appiancorp.process.background.EngineWorkControllerRunnable - Engine Work Controller for process-execution0: Shutting down 07:25:31,883 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,883 [ServerService Thread Pool -- 7] INFO com.appiancorp.process.background.EngineWorkControllerRunnable - Engine Work Controller for process-execution1: Shutting down 07:25:31,883 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,883 [ServerService Thread Pool -- 7] INFO com.appiancorp.process.background.EngineWorkControllerRunnable - Engine Work Controller for process-design: Shutting down 07:25:31,884 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,884 [ServerService Thread Pool -- 7] INFO com.appiancorp.process.background.EngineWorkControllerRunnable - Engine Work Controller for process-execution2: Shutting down 07:25:31,885 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,885 [ServerService Thread Pool -- 7] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextClosedEvent: org.springframework.context.event.ContextClosedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:25:31,894 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,893 [ServerService Thread Pool -- 7] INFO com.appiancorp.ix.spring.IaSpringContextListener - Canceling ia replication timer: java.util.Timer@4eb98417 07:25:31,894 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,894 [ServerService Thread Pool -- 7] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextClosedEvent: org.springframework.context.event.ContextClosedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:25:31,896 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,896 [ServerService Thread Pool -- 7] INFO com.appiancorp.tempo.rdbms.index.NewsIndexSpringContextListener - Canceling news replication timer: java.util.Timer@1a42fc7c 07:25:31,897 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,896 [ServerService Thread Pool -- 7] INFO com.appiancorp.common.spring.AbstractSpringContextListener - Received ContextClosedEvent: org.springframework.context.event.ContextClosedEvent[source=Root WebApplicationContext: startup date [Thu May 31 07:23:35 GMT 2018]; root of context hierarchy] 07:25:31,997 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:31,997 [ServerService Thread Pool -- 7] INFO com.appian.es.client.TransportClientManager - Shutting down client. 07:25:32,164 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:32,164 [ServerService Thread Pool -- 7] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Checking for active transactions... 07:25:32,169 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:32,169 [ServerService Thread Pool -- 7] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Closing JPA EntityManagerFactory... 07:25:32,172 INFO [stdout] (ServerService Thread Pool -- 7) 2018-05-31 07:25:32,172 [ServerService Thread Pool -- 7] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [java:/jdbc/AppianPrimary] Closed successfully. 07:25:33,495 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 07:25:33,497 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 07:25:33,498 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) started in 209541ms - Started 178 of 215 services (64 services are lazy, passive or on-demand) 07:25:34,667 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "appian-mysql-ds.xml" (runtime-name: "appian-mysql-ds.xml") 07:25:34,668 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015858: Undeployed "suite.ear" (runtime-name: "suite.ear") 07:25:34,669 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."appian-mysql-ds.xml".FIRST_MODULE_USE 10:29:11,048 ERROR [org.hornetq.core.server] (Thread-3 (HornetQ-scheduled-threads-1350766722)) HQ224033: Failed to broadcast connector configs: java.net.SocketException: Network is unreachable: Datagram send failed at java.net.TwoStacksPlainDatagramSocketImpl.send(Native Method) [rt.jar:1.8.0_92] at java.net.DatagramSocket.send(DatagramSocket.java:693) [rt.jar:1.8.0_92] at org.hornetq.api.core.UDPBroadcastGroupConfiguration$UDPBroadcastEndpoint.broadcast(UDPBroadcastGroupConfiguration.java:136) [hornetq-core-client-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1] at org.hornetq.core.server.cluster.impl.BroadcastGroupImpl.broadcastConnectors(BroadcastGroupImpl.java:216) [hornetq-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1] at org.hornetq.core.server.cluster.impl.BroadcastGroupImpl.run(BroadcastGroupImpl.java:228) [hornetq-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_92] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [rt.jar:1.8.0_92] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_92] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [rt.jar:1.8.0_92] 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] 10:29:36,563 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 10:39:19,028 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session b43acfbb-64a3-11e8-8fe6-5b204bee02b0 10:39:19,050 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session b43acfbb-64a3-11e8-8fe6-5b204bee02b0 10:39:19,188 INFO [org.hornetq.core.server] (hornetq-failure-check-thread) HQ221021: failed to remove connection 10:39:19,558 WARN [org.hornetq.jms.server] (Thread-8 (HornetQ-client-global-threads-1502001656)) HQ122014: Notified of connection failure in xa recovery connectionFactory for provider ClientSessionFactoryImpl [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=6813e097-64a3-11e8-8fe6-5b204bee02b0, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryGroupConfiguration=null], connectorConfig=TransportConfiguration(name=6813e097-64a3-11e8-8fe6-5b204bee02b0, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0, backupConfig=null] will attempt reconnect on next pass: HornetQException[errorType=NOT_CONNECTED message=HQ119006: Channel disconnected] at org.hornetq.core.client.impl.ClientSessionFactoryImpl.connectionDestroyed(ClientSessionFactoryImpl.java:425) [hornetq-core-client-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1] at org.hornetq.core.remoting.impl.invm.InVMConnector$Listener$1.run(InVMConnector.java:214) [hornetq-server-2.3.25.Final-redhat-1.jar:2.3.25.Final-redhat-1] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105) [hornetq-core-client-2.3.25.Final-redhat-1.jar:2.3.25.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] 10:39:21,891 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA] 10:39:23,051 INFO [org.apache.catalina.core] (MSC service thread 1-1) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started 10:39:24,877 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010409: Unbound data source [java:/jdbc/AppianPrimary] 10:39:25,871 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/0.0.0.0:8080 10:39:26,040 INFO [org.apache.coyote.ajp] (MSC service thread 1-4) JBWEB003048: Pausing Coyote AJP/1.3 on ajp-/0.0.0.0:8009 10:39:26,041 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/0.0.0.0:8080 10:39:26,210 INFO [org.apache.coyote.ajp] (MSC service thread 1-4) JBWEB003051: Stopping Coyote AJP/1.3 on ajp-/0.0.0.0:8009 10:39:27,538 INFO [org.hornetq.ra] (ServerService Thread Pool -- 325) HQ151003: HornetQ resource adaptor stopped 10:39:30,493 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 325) HQ221002: HornetQ Server version 2.3.25.Final (2.3.x, 123) [a28867fa-6372-11e8-9beb-9b82e56ab4b7] stopped 10:39:30,871 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015950: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) stopped in 8166ms
<?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="URL">jdbc:mysql://localhost:3306/appianprimary?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>
Thanks for the Response Benhail.
It seems that is not the issue , PFA Custom Properties file.
I want mention few thing here:
1. When restarted the Jboss Application server , It was connected to Appian Primary DB and Created all The Predefined tables But Unfortunately every time appian-mysql-ds.xml l file is failing.
2. Is there any issue with Jboss Server version , We are using 6.4.0 But Minimum requirement is 6.4.14.
3. We have found similar issue in 6.4.9 and Please find above KB Article.
Custom.Properties File:
==============
####################### custom.properties example file ########################## #### NOTE: DO NOT simply rename this file custom.properties. #### #### This file contains examples of entries for the custom.properties override #### file. The custom.properties file is not installed by default and must be #### created in order to override the default value of a property. Once #### present, the custom.properties file will not be overwritten by subsequent #### upgrade installations. #### The values given in this file are the default values of the configuration #### properties. Override a property's default value by copying the relevant #### entry from this file and placing it in conf/custom.properties with a new #### value. Properties that have no default have <PROVIDE A VALUE> listed as #### the value and must be given a value specific to your environment in order #### to be used. All of the properties are commented with a single #. You #### will have to uncomment the property and give it a value when you copy to #### custom.properties. #### #### The most commonly configured properties are listed here. ###################################################################################################### General ####################### Specifying the scheme. Necessary when SSL is not performed at the app server## level but enabled at different layer.conf.suite.SCHEME=http## Used by both App Server and Engines to build up base URLs for links#conf.suite.APPLICATION_CONTEXT=suite## The SERVER_AND_PORT property should be in the format server:port.## Do not specify the :port if the port is 80 and the SCHEME is http, or the## port is 443 and SCHEME is https. This is the hostname and port portion of## the URL viewed by end users in links (e.g., links in emails)##conf.suite.SERVER_AND_PORT=GSC_20:8080conf.suite.SERVER_AND_PORT=localhost## The STATIC_PORTAL_CSS_SOURCE_URL, STATIC_FORMS_JS_SOURCE_URL, and## STATIC_PORTAL_JS_SOURCE_URL allow specifying an external host## for static javascript and CSS resources, to off-load rendering from## the main server.#conf.static.STATIC_PORTAL_CSS_SOURCE_URL=#conf.static.STATIC_FORMS_JS_SOURCE_URL=#conf.static.STATIC_PORTAL_JS_SOURCE_URL=## The BASE_PATH is the path to the directory that contains the accdocs*## directories referenced in server/_conf/partition.xml. Set this prior to## migration if upgrading from a previous version and the new installation is## in a different location on the file system from the previous installation.## NOTE: The path separator must be a forward slash ("/"), even if using## Windows.#conf.suite.BASE_PATH=## The location of the log files.#conf.suite.AE_LOGS=<install_dir>/logs## ID of the default home page that users see in the designer environment if## they do not have a custom home page#conf.suite.DEFAULT_HOME_PAGE_ID=0## Copyright statements can be overridden using the following properties. The## copyright property allows overriding the entire statement or supports string## formatting using a param substitution syntax: %2$s, %3$s## The copyright statement appears as the footer of the designer and legacy## portal interfaces## Note that \u00A9 is the copyright symbol.#resources.appian.ap.application.appian.ap.copyright=\u00A9%2$s %3$s## The 2 substitution parameters can be individually overridden with the## the properties as follows:## %2$s - the copyright year#resources.appian.ap.application.appian.ap.copyrightYear=2003-<defaults to current year>## %3$s - the company name#resources.appian.ap.application.appian.ap.appianName=Appian Corporation################### Email ##################### Sending Email## The address that will appear as the sender (the "From" address) of## notification and password reset emails from the system.## Defaults to appian-alerts@<serverdomain>#conf.mailhandler.ntf_sndr_addr=## The domain (portion after the "@") for the "from" email address for## addresses created via expressions functions; also applies to the domain## for alert emails when conf.mailhandler.ntf_sndr_addr is not set. Defaults to## the domain of the server.#conf.mailhandler.email.domain=## The host is the FQDN, hostname, or IP address of the SMTP server for sending## email from the system. Muliple SMTP servers can be specified using a comma-## separated list. They will be tried in the order specified. If a port## other than 25 is required, append it to the hostname (e.g., mailhost3:9025)## IMPORTANT: If this is not set, no email will be sent from the system.#conf.mailhandler.mail.smtp.host=<PROVIDE A VALUE>## The username used to connect to the SMTP server above. Set## conf.mailhandler.mail.smtp.auth=true if user/password are used. Leave the## default (false) to indicate that the SMTP server does not require## authentication. If multiple SMTP servers are defined above, the same auth## settings will apply to all servers#conf.mailhandler.mail.smtp.auth=false#conf.mailhandler.mail.user=## The protocol should be set to either smtp or smtps. The default value is smtp.#conf.mailhandler.mail.transport.protocol=smtp## You can enable or require starttls with the "smtp" protocol. Setting## starttls.enable=true will cause outgoing mail to use STARTTLS if supported by## the remote server but will fall back to plain smtp otherwise. Also setting## starttls.required=true will cause mail to fail if the remote server does not## support STARTTLS.#conf.mailhandler.mail.smtp.starttls.enable=false#conf.mailhandler.mail.smtp.starttls.required=false## Receiving Email - see documentation for configuration of ejb-jar.xml## Aliases can be used to route email sent to a particular email address to a## specified process model, process, or event. They are of the form## conf.mailhandler.alias.<recipientName>=<routing> where <recipientName> is an## email account and <routing> is processmodeluuid, processmodelid, process,## or event followed by the corresponding id#conf.mailhandler.alias.HelpDeskRequest=processmodeluuid0004cedf-a045-8000-234b-c0a8031014c0############################## Anonymous Access ################################ DEPRECATED: Set ANONYMOUS_ACCESS=true to receive email messages in process## start nodes. It also enables the use of the ANONYMOUS user.## Setting this property to true does NOT allow users to access the portal## anonymously. The property remains deprecated because it will be renamed in a## future release.#conf.suite.ANONYMOUS_ACCESS=false############################ Single Sign-On ############################## Refer to the documentation on configuring single sign-on through the Spring## Security framework.########################## Data Capping ############################ Data Output Truncation Constants define data truncation limits in## places where data output is capped (like in report cells).#conf.suite.DATA_TRUNC_SENTENCES=200## Notification data caps#conf.suite.ALERT_SUBJECT_LIMIT=150#conf.suite.ALERT_MESSAGE_LIMIT=1000############################### Process Execution ################################# The limit to the number of rows returned in the Database Access node#resources.appian.process.application.arv.limit=10## Whether or not automatic archiving of completed and canceled processes is## enabled. 1=enabled; 0=disabled#server.conf.exec.AUTOARCHIVE=1###################### Analytics ####################### Analytics Report Rows Cap## This number specifies the maximum number of items that can be loaded into## app server memory when processing a report.## It determines the last page that can be retrieved for a report:## last page = floor(maxreportrows/(number of analytics engines * number of rows per page))## In addition, this also determines the maximum number of rows that will be## included when a report is exported or printed.#resources.appian.analytics.application.maxreportrows=30000## Analytics Engine Timeout## How much time each analytics engine is allowed to take to process a request in## milliseconds. The report will time out if the request takes longer to process.#server.conf.processcommon.MAXIMUM_REPORT_MS=2000## Process Search: report used to display results of process searches## the value must be an alias defined in analytics-config(-*).xml#resources.appian.process.application.appian.process.process_search_report=all_processes########################## Data Sources ############################ 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=java:/jdbc/AppianPrimary## 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=jdbc/AppianBusiness################### #### Documents ######################### The minimum allowed size for a document or a folder.#resources.appian.ac.collaboration.MINIMUM_DOCUMENT_NAME_LENGTH=4## The maximum allowed size in bytes for a document#resources.appian.ac.collaboration.MAX_UPLOAD_FILE_SIZE=1024000000## The group id of Collaboration Administrators#resources.appian.ac.collaboration.COLLABORATION_ADMINISTRATION_GROUP_ID=0## The number of Documents, Knowledge Center, or Folders that can be moved## simultaneously#resources.appian.ac.collaboration.MAX_NUMBER_MOVEABLE_OBJECTS=4## The number of megabytes to allocate to new users' quota for documents## uploaded to folders in Personal and Teams knowledge centers. Changing the## value does not affect existing users.#server.conf.collaboration.DEFAULTSPACE=250## Whether documents can be downloaded with the Content-Disposition header set## to "inline" by using inline=true as a request parameter. This property must## be set to true in order to use PDF forms as task forms or to display the## contents of a file stored in Documents inline on a page in the web page## channel.#conf.content.download.inline=false######################### Query Rules ########################### The amount of memory in bytes that will be consumed in the application server## for a single query before the query is halted. Default is 1 MB.#conf.data.query.memory.limit=1048576## The amount of time in seconds that a query will wait for a response from the## database before timing out.#conf.data.query.timeout=10################# JMS ################### A list of client ids to use when connecting to the JMS provider, either## clientIds needs to be defined as a comma-separated list or both## clientIdPrefix and maxConnections must be defined#conf.jms.clientIds=#conf.jms.clientIdPrefix=CLIENT_#conf.jms.maxConnections=20## The name of the JMS topic or queue that contains messages destined for## process#conf.jms.processTopic=Process## Some JMS providers have a prefix before the topic of queue name, if needed## define that prefix here#conf.jms.topicPrefix=#conf.jms.queuePrefix=## If the JMS provider requires a username and password for connection, define## the username here and the password in passwords.properties############################################################## Web Services: Exposing Processes as Web Services ################################################################ See uddi-config.xml.example for how to configure UDDI registries## By default process models exposed as a web service can be found at## SCHEME://SERVER_AND_PORT/APPLICATION_CONTEXT/webservice/processmodel/*?WSDL## If you want a different base URL (part before /webservice..) define that here## An application server or web server connected to the system must be listening#resources.appian.webservices.application.webservice.baseurl=############################### Web Services Node ################################# The following are properties that control the behavior of HTTP connections## made by the Call Web Service Node during service invocation.## Number of seconds to wait to establish a connection with a web service host#conf.node.webservice.connection.timeout=60## Once a connection is established, the number of seconds to wait for a## response to a request#conf.node.webservice.socket.timeout=60## Number of redirect responses (HTTP 304) the web service node will accept#conf.node.webservice.max.redirects=4###################### Plug-ins ######################## The plug-in loading poll interval is the maximum number of seconds that will## pass before loading a new plug-in after it is placed in the plugins## directory. Setting the interval to 0 will cause hot deployment to be## disabled and deploying a new plug-in will require an app server restart.#conf.plugins.poll-interval=60
Please find DB Schema Screen Shot:
Thanks InAdvance
Hello Venkatesh Suram , Yes, you should install jboss EAP 6.4.14 or higher, you are currently using 6.4.0. And try following this: Stop the jboss service. Remove the "java:" of the jdi-name in the appian-ds and custom.properties files as Benhail said. Remove the appian-ds.failed file. Clean jboss cache. Start jboss
sergiob : Thanks for the response.
We have tried with "jdbc/AppianPrimary" JNDI Name in Custom Properties file and mysql-ds.xml, It was giving same error.
Before restart the Server we have followed the below steps:
1. Deleted the server.log file or Rename it to server.log.001 in JBOSS so that JBOSS will create a new log file on start-tup. <JBOSS_HOME>\standalone\log\ 2. Verified the following file exists and does not have the extensions .undeployed, .isdeploying or .failed: <APPIAN_HOME>\_admin\_scripts\configure\templates\ear\suite.ear.dodeploy 3. Deleted the following file if it has the extensions .undeployed, .isdeploying or .failed: <JBOSS_HOME>\standalone\deployments\appian-mysql-ds.xml.deployed
I will try to install Jboss EAP 6.4.14 and will share log with you guys,If we face any issues.
Note:
Currently Temp LIC Was expired , Once we will get the New Temp LIC File will restart the server and will let you know and I will share the Log file.
Thanks sergiob , Benhail.