[ https://issues.jboss.org/browse/WFLY-4280?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on WFLY-4280: ----------------------------------------- And you have no other modifications to the Wildfly container? I am still not able to re-produce this. I get: {noformat} /opt/java/wildfly/bin]$ ./standalone.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /opt/java/wildfly JAVA: /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/bin/java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= 10:51:22,245 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final 10:51:27,014 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final 10:51:27,902 INFO [org.jboss.as] (MSC service thread 1-8) JBAS015899: WildFly 8.2.0.Final "Tweek" starting 10:51:37,091 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) 10:51:37,333 INFO [org.xnio] (MSC service thread 1-5) XNIO version 3.3.0.Final 10:51:37,450 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.3.0.Final 10:51:37,569 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique. 10:51:37,569 INFO [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem 10:51:37,764 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main] 10:51:37,796 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem. 10:51:37,797 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension 10:51:37,831 INFO [org.jboss.as.security] (MSC service thread 1-7) JBAS013170: Current PicketBox version=4.0.21.Final 10:51:37,886 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem 10:51:38,046 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors 10:51:38,356 INFO [org.jboss.as.connector.logging] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final) 10:51:38,622 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.0.Final starting 10:51:38,622 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017502: Undertow 1.1.0.Final starting 10:51:39,768 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 10:51:40,015 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = h2 10:51:40,658 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path /opt/java/wildfly/welcome-content 10:51:40,664 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.6.Final 10:51:40,975 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service 10:51:40,976 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default] 10:51:41,226 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017525: Started server default-server. 10:51:41,398 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017531: Host default-host starting 10:51:42,310 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 10:51:43,638 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 10:51:43,708 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory /opt/java/wildfly/standalone/deployments 10:51:43,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "hv-861-1.0-SNAPSHOT.jar" (runtime-name: "hv-861-1.0-SNAPSHOT.jar") 10:51:45,947 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment hv-861-1.0-SNAPSHOT.jar 10:51:46,344 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final 10:51:46,353 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.1.3.Final 10:51:46,694 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016005: Starting Services for CDI deployment: hv-861-1.0-SNAPSHOT.jar 10:51:46,832 INFO [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 2.2.6 (Final) 10:51:46,898 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) JBAS016008: Starting weld service for deployment hv-861-1.0-SNAPSHOT.jar 10:51:48,823 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "hv-861-1.0-SNAPSHOT.jar" (runtime-name : "hv-861-1.0-SNAPSHOT.jar") 10:51:48,883 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 10:51:48,884 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 10:51:48,885 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 29171ms - Started 225 of 280 services (90 services are lazy, passive or on-demand) {noformat} The same for the HotSpot 1.8 JVM. The only difference I can see now is that you are using the OpenJDK. If it is a VM based problem, it would also explain, why we have not been able to re-produce it. I will try with OpenJDK. Any chance you could try a different JVM as well? -- This message was sent by Atlassian JIRA (v6.3.11#6341)