"JBAS015003: Found suite.ear in deployment directory. To trigger deployment create a file called suite.ear.dodeploy" but file is already present

I am getting the above error even though the file is already present. I used the Appian Configure script to deploy the configuration and it seemed to deploy correctly. Seemingly due to this error (as I can't find any other issues, unless someone can enlighten me?) the server shuts down a few seconds after startup. Can anyone recommend steps to resolve this?

sh-4.2$ /opt/eap/bin/standalone.sh
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /opt/eap

  JAVA: /etc/alternatives/apaas/jdk/default/bin/java

  JAVA_OPTS:  -XX:+UseCompressedOops -verbose:gc -Xloggc:"/opt/eap/standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation
 -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms2048m -Xmx4096m -XX:+HeapDumpOnOutOfMemoryError -Dsun.rmi.dgc.client.gcInterval=36
00000 -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 -server -Dappian.home.ear=/usr/local/appian/ear -Djboss.as.managem
ent.blocking.timeout=3600 -Dorg.jboss.resolver.warning=true -Djboss.server.default.config=standalone.xml

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

23:19:28,184 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.7.Final-redhat-1
23:19:28,477 INFO  [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
23:19:28,537 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.4.4.GA (AS 7.5.4.Final-redhat-4) starting
23:19:31,468 WARN  [org.jboss.messaging] (ServerService Thread Pool -- 7) JBAS011618: There is no resource matching the expiry-address jms.queue.ExpiryQueue f
or the address-settings #, expired messages from destinations matching this address-setting will be lost!
23:19:31,468 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!
23:19:33,113 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found suite.ear in deployment directory. To trigger de
ployment create a file called suite.ear.dodeploy
23:19:33,389 INFO  [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.14.GA-redhat-1
23:19:33,391 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
23:19:33,470 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.14.GA-redhat-1
23:19:33,581 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.3.5.Final-redhat-1
23:19:33,767 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.
23:19:33,784 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015537: Activating WebServices Extension
23:19:33,880 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.
23:19:33,881 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 46) JBAS013371: Activating Security Subsystem
23:19:33,966 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 41) JBAS011800: Activating Naming Subsystem
23:19:34,080 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 39) JBAS012615: Activated the following JSF Implementations: [main, 1.2]
23:19:34,176 INFO  [org.jboss.as.security] (MSC service thread 1-8) JBAS013370: Current PicketBox version=4.1.1.Final-redhat-1
23:19:34,478 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-16) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.32.Final-redhat-1)
23:19:34,585 INFO  [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service
23:19:34,585 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-15) JBAS015400: Bound mail session [java:jboss/mail/Default]
23:19:35,180 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class org.h2.
Driver (version 1.3)
23:19:35,568 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)
/opt/eap/bin/standalone.sh: line 306:   950 Killed                  "/etc/alternatives/apaas/jdk/default/bin/java" -D"[Standalone]" -XX:+UseCompressedOops -ve
rbose:gc -Xloggc:"/opt/eap/standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileS
ize=3M -XX:-TraceClassUnloading -Xms2048m -Xmx4096m -XX:+HeapDumpOnOutOfMemoryError -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=36
00000 -XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC -Dorg.apache.catalina.connector.URI_ENCODING=UTF-8 -Duser.timezone=GMT -Djava.awt.headless=true -D
java.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -server -Dappian.home.ear=/usr/local/appian/ear -Djboss.as.management.blocking.timeout=3600 -Dorg.jboss.re
solver.warning=true -Djboss.server.default.config=standalone.xml "-Dorg.jboss.boot.log.file=/opt/eap/standalone/log/server.log" "-Dlogging.configuration=file:
/opt/eap/standalone/configuration/logging.properties" -jar "/opt/eap/jboss-modules.jar" -mp "/opt/eap/modules:/opt/eap/custom_modules" -jaxpmodule javax.xml.j
axp-provider org.jboss.as.standalone -Djboss.home.dir="/opt/eap" -Djboss.server.base.dir="/opt/eap/standalone"
sh-4.2$ ls -l /usr/local/appian/ear
total 12
drwxrwxr-x. 12 root   root 4096 Nov 30 15:27 suite.ear
-rw-rw-r--.  1 root   root  180 Nov 30 15:29 suite.ear.dodeploy
-rw-r--r--.  1 appian root    9 Nov 30 18:19 suite.ear.isdeploying
sh-4.2$

  Discussion posts and replies are publicly visible

Parents
  • there might be a suite.ear.failed file in the appian/ear folder....please inspect that folder again and change suite.ear.failed to suite.ear.dodeploy. In appian/ear the only two things that must be present is suite.ear and suite.ear.dodeploy. Also the same kind of thing must exist in jboss-eap-6.4/standalone/deployments folder where appian-ds.xml and appian-ds.xml.dodeploy file must be present
Reply
  • there might be a suite.ear.failed file in the appian/ear folder....please inspect that folder again and change suite.ear.failed to suite.ear.dodeploy. In appian/ear the only two things that must be present is suite.ear and suite.ear.dodeploy. Also the same kind of thing must exist in jboss-eap-6.4/standalone/deployments folder where appian-ds.xml and appian-ds.xml.dodeploy file must be present
Children
No Data