[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18912: --------------------------------------- This is the log from server start: {code} 09:39:08,685 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 2621ms - Started 151 of 189 services (56 services are lazy, passive or on-demand) 09:39:08,796 INFO [org.jboss.as.protocol] (Remoting "marvin:MANAGEMENT" read-1) JBAS012119: cancelled task by interrupting thread Thread[management-handler-thread - 1,5,management-handler-thread] 09:39:08,858 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/rasp/tmp/deploy 09:39:23,875 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy 09:39:35,044 INFO [org.jboss.as.protocol] (Remoting "marvin:MANAGEMENT" read-1) JBAS012119: cancelled task by interrupting thread Thread[management-handler-thread - 1,5,management-handler-thread] {code} As you can see sometimes this "cancelled task" thing happens, but I'm not sure if it's relevant here and why it happens. But the main thing is that in this instance no .dodeploy was created. -- This message was sent by Atlassian JIRA (v6.3.8#6338)