3 Replies Latest reply on Jun 24, 2016 11:19 AM by James Perkins

    Wildfly startup timeout | McAfee blocks/slows down server startup

    Andre Iske Newbie



      since I had to changed my development notebook, I am forced to develop on Windows 7 where a McAfee virus scanner is running. This virus scanner is managed by the IT of my company. So I am neither able to disable McAfee nor change the configuration myself. This McAfee virus scanner is blocking something during the startup of my wildfly server, so that the server runs into a timeout exception (see logfile below). But before I can ask the IT service desk for a change of the McAfee configuration, I need to know what exactly is blocked by McAfee (is it a file or the opening of a port). Are there any tools or log files that I could use to find out, what is going on there?

      I am very sure, that McAfee causes this problem, because on a virtual machine everything runs fine. I first thought that the component jars of my ear-file are blocked, but this couldn't be the problem. The server also runs into this timeout without anything to deploy.  


      I really hope somebody is able to help me.


      Greets André


      16:15:21,635 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final

      16:15:21,843 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final

      16:15:21,903 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting

      16:15:22,898 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found server.ear in deployment directory. To trigger deployment create a file called server.ear.dodeploy

      16:15:22,921 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)

      16:15:22,935 INFO  [org.xnio] (MSC service thread 1-4) XNIO version 3.3.4.Final

      16:15:22,940 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.3.4.Final

      2016-06-22 16:15:22,981 WARN  [ServerService Thread Pool -- 50] [] org.jboss.as.txn: WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.

      2016-06-22 16:15:22,987 INFO  [ServerService Thread Pool -- 36] [] org.jboss.as.clustering.infinispan: WFLYCLINF0001: Activating Infinispan subsystem.

      2016-06-22 16:15:22,988 INFO  [ServerService Thread Pool -- 44] [] org.jboss.as.naming: WFLYNAM0001: Activating Naming Subsystem

      2016-06-22 16:15:23,000 INFO  [ServerService Thread Pool -- 52] [] org.jboss.as.webservices: WFLYWS0002: Activating WebServices Extension

      2016-06-22 16:15:23,005 INFO  [ServerService Thread Pool -- 49] [] org.jboss.as.security: WFLYSEC0002: Activating Security Subsystem

      2016-06-22 16:15:23,027 INFO  [ServerService Thread Pool -- 42] [] org.jboss.as.jsf: WFLYJSF0007: Activated the following JSF Implementations: [main]

      2016-06-22 16:15:23,035 INFO  [MSC service thread 1-5] [] org.jboss.as.connector: WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)

      2016-06-22 16:15:23,047 INFO  [MSC service thread 1-1] [] org.jboss.as.security: WFLYSEC0001: Current PicketBox version=4.9.4.Final

      2016-06-22 16:15:23,063 INFO  [ServerService Thread Pool -- 51] [] org.wildfly.extension.undertow: WFLYUT0003: Undertow 1.3.15.Final starting

      2016-06-22 16:15:23,063 INFO  [MSC service thread 1-2] [] org.wildfly.extension.undertow: WFLYUT0003: Undertow 1.3.15.Final starting

      2016-06-22 16:15:23,087 INFO  [MSC service thread 1-1] [] org.jboss.as.naming: WFLYNAM0003: Starting Naming Service

      2016-06-22 16:15:23,090 INFO  [MSC service thread 1-2] [] org.jboss.as.mail.extension: WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]

      2016-06-22 16:15:23,099 INFO  [ServerService Thread Pool -- 31] [] org.jboss.as.connector.subsystems.datasources: WFLYJCA0005: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.4)

      2016-06-22 16:15:23,103 INFO  [MSC service thread 1-8] [] org.jboss.as.connector.deployers.jdbc: WFLYJCA0018: Started Driver service with driver-name = serverDriver

      2016-06-22 16:15:23,254 INFO  [ServerService Thread Pool -- 51] [] org.wildfly.extension.undertow: WFLYUT0014: Creating file handler for path 'C:\workspaces\SpOS_trunk\applicationserver\target\wildfly/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']

      2016-06-22 16:15:23,639 INFO  [MSC service thread 1-3] [] org.jboss.as.connector.subsystems.datasources: WFLYJCA0001: Bound data source [java:jboss/datasources/serverDS]

      2016-06-22 16:15:23,648 INFO  [MSC service thread 1-7] [] org.jboss.as.server.deployment.scanner: WFLYDS0013: Started FileSystemDeploymentService for directory C:\workspaces\SpOS_trunk\applicationserver\target\wildfly\standalone\deployments

      2016-06-22 16:15:26,098 INFO  [MSC service thread 1-7] [] org.jboss.remoting: JBoss Remoting version 4.0.18.Final

      2016-06-22 16:20:23,653 ERROR [Controller Boot Thread] [] org.jboss.as.controller.management-operation: WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[

          ("core-service" => "management"),

          ("management-interface" => "http-interface")