Wildfly 8.2.0 reports "XNIO001001: No XNIO provider found" during launch and fails

[thschaef42]

Hello everybody,

My Wildfly 8.2.0 server used to run fine, but since two days it fails to start reporting a missing XNIO provider.

Last thing I did before the server stopped running fine, was a connect from an Eclipse Mars IDE using a server adapter configured as "Controlled by: Management operations" and "Server lifecycle is externally managed = true". After that it failed launching ...

I have absolutly no glue what happened.

So I tried to run another Wildfly installation which runs fine on another Windows machine, but got the same error when I unpacked it and ran it on my problematic one. The same happens when I try to run a brandnew Wildfly 10. So it seems that the Wildfly configuration(s) and installation(s) are fine and do not cause the problem, but my machine or any software installation seem to cause it ...

The Windows10 and the Java 8 JDK were not touched. Nevertheless I replaced the SDK8 by another one that runs fine on my other machine - with the same result. And the same happened for a JDK7 installation.

C:\jboss-wildfly-8.2.0\bin>set JAVA_HOME=C:\Program Files\Java\jdk7

Calling "C:\jboss-wildfly-8.2.0\bin\standalone.conf.bat"

Setting JAVA property to "C:\Program Files\Java\jdk7\bin\java"

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

  JBoss Bootstrap Environment

  JBOSS_HOME: "C:\jboss-wildfly-8.2.0"

  JAVA: "C:\Program Files\Java\jdk7\bin\java"

  JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman"

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

20:23:37,420 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final

20:23:37,652 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final

20:23:37,736 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015899: WildFly 8.2.0.Final "Tweek" starting

20:23:38,701 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment h2console.war

20:23:38,718 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment nest.war

20:23:38,723 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found nest.war in deployment directory. To trigger deployment create a file called nest.war.dodeploy

20:23:38,738 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

20:23:38,770 INFO  [org.xnio] (MSC service thread 1-6) XNIO version 3.3.0.Final

20:23:38,770 INFO  [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.3.0.Final

20:23:38,785 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.remoting.endpoint.management: org.jboss.msc.service.StartException in service jboss.remoting.endpoint.management: Failed to start service

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]

        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]

Caused by: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found

        at org.xnio.Xnio.doGetInstance(Xnio.java:238)

        at org.xnio.Xnio.getInstance(Xnio.java:193)

        at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:112)

        at org.jboss.as.remoting.ManagementEndpointService.createEndpoint(ManagementEndpointService.java:45)

        at org.jboss.as.remoting.EndpointService.start(EndpointService.java:76)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        ... 3 more

...

...

20:23:39,022 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current PicketBox version=4.0.21.Final

20:23:39,016 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]

20:23:39,015 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

20:23:39,379 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) JBAS010417: Started Driver service with driver-name = mysql

20:23:39,344 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.io.worker.default: org.jboss.msc.service.StartException in service jboss.io.worker.default: Failed to start service

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]

        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]

Caused by: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found

        at org.xnio.Xnio.doGetInstance(Xnio.java:238)

        at org.xnio.Xnio.getInstance(Xnio.java:193)

        at org.wildfly.extension.io.WorkerService.start(WorkerService.java:50)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        ... 3 more

I also tried to pass the XNIO related JARS directly to the server using the startup code below, but without any sucess:

set CP=C:\jboss-wildfly-8.2.0\xnio-nio-3.3.0.Final.jar;C:\jboss-wildfly-8.2.0\netty-xnio-transport-0.1.1.Final.jar;C:\jboss-wildfly-8.2.0\xnio-api-3.3.0.Final.jar

  "%JAVA%" %JAVA_OPTS% ^

   "-Dorg.jboss.boot.log.file=%JBOSS_LOG_DIR%\server.log -classpath %CP%" ^

   "-Dlogging.configuration=file:%JBOSS_CONFIG_DIR%/logging.properties" ^

      -jar "%JBOSS_HOME%\jboss-modules.jar" ^

      -mp "%JBOSS_MODULEPATH%" ^

      -jaxpmodule "javax.xml.jaxp-provider" ^

       org.jboss.as.standalone ^

      "-Djboss.home.dir=%JBOSS_HOME%" ^

       %SERVER_OPTS%

Does anybody have any idea what causes this problem? I didn't find anything that fits to my problem in the net ...

I appreciate any help!

Thanks,

Thomas

[ctomc]

your server is beeing run by JDK7 not jdk8

JAVA: "C:\Program Files\Java\jdk7\bin\java"

[thschaef42]

Hi Tomaz,

you are right - a made a couple of tests with different VMs to find out, if the VM installation may be responsible for my problem.

The tests I did:

After my installed JDK8 failed, I transferred a working JDK7 and JDK8 from my other laptop to my problematic one to test them.

Result: I got the same XNIO error as with my original JDK8, so at the end I reverted to the original JDK8 I used before.

I pasted the server.log running under a JDK8 U74 below.

Another interesting finding:

I zipped the complete Wildfly installation, transferred it to my other laptop, extracted it there and launched it (JDK installation, MySQL Installation / configuration are identical). It worked perfect without any error!

-> So as a result, the Wildfly installation itself cannot produce my problem.

But anything seems to be wrong on my "installation" that impacts the XNIO of the Wildfly.

Calling "C:\jboss-wildfly-8.2.0\bin\standalone.conf.bat"

Setting JAVA property to "C:\Program Files\Java\jdk8\bin\java"

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

  JBoss Bootstrap Environment

  JBOSS_HOME: "C:\jboss-wildfly-8.2.0"

  JAVA: "C:\Program Files\Java\jdk8\bin\java"

  JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman"

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

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0

17:37:40,971 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final

17:37:41,172 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final

17:37:41,230 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015899: WildFly 8.2.0.Final "Tweek" starting

17:37:42,446 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment h2console.war

17:37:42,472 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

17:37:42,497 INFO  [org.xnio] (MSC service thread 1-6) XNIO version 3.3.0.Final

17:37:42,516 INFO  [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.3.0.Final

17:37:42,587 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

17:37:42,595 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

17:37:42,595 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.

17:37:42,912 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.io.worker.default: org.jboss.msc.service.StartException in service jboss.io.worker.default: Failed to start service

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.8.0_74]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.8.0_74]

        at java.lang.Thread.run(Unknown Source) [rt.jar:1.8.0_74]

Caused by: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found

        at org.xnio.Xnio.doGetInstance(Xnio.java:238)

        at org.xnio.Xnio.getInstance(Xnio.java:193)

        at org.wildfly.extension.io.WorkerService.start(WorkerService.java:50)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        ... 3 more

17:37:42,907 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017502: Undertow 1.1.0.Final starting

17:37:42,907 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.0.Final starting

17:37:42,884 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]

17:37:42,868 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.remoting.endpoint.management: org.jboss.msc.service.StartException in service jboss.remoting.endpoint.management: Failed to start service

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.8.0_74]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.8.0_74]

        at java.lang.Thread.run(Unknown Source) [rt.jar:1.8.0_74]

Caused by: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found

        at org.xnio.Xnio.doGetInstance(Xnio.java:238)

        at org.xnio.Xnio.getInstance(Xnio.java:193)

        at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:112)

        at org.jboss.as.remoting.ManagementEndpointService.createEndpoint(ManagementEndpointService.java:45)

        at org.jboss.as.remoting.EndpointService.start(EndpointService.java:76)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        ... 3 more

17:37:42,829 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem

17:37:42,810 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem

17:37:42,809 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

17:37:42,807 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.

17:37:42,720 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = h2

...

...

Best regards,

Thomas

[thschaef42]

Hi again,

And another finding:

When I trying to deploy my application to a remote Linux server, also running Wildfly, using the Eclipse wildfly-maven-plugin, I get a similar error indicating an XNIO problem on my laptop.

Any ideas?

Thanks & regards,

Thomas

...

...

...

[INFO] --- maven-war-plugin:2.4:war (default-war) @ test ---

[INFO] Packaging webapp

[INFO] Assembling webapp [test] in [C:\Users\thoma\workspace-mars\test\target\test]

[INFO] Processing war project

[INFO] Copying webapp resources [C:\Users\thoma\workspace-mars\test\src\main\webapp]

[INFO] Webapp assembled in [820 msecs]

[INFO] Building war: C:\Users\thoma\workspace-mars\test\target\test.war

[INFO]

[INFO] <<< wildfly-maven-plugin:1.0.0.Beta1:deploy (default-cli) < package @ test <<<

[INFO]

[INFO] --- wildfly-maven-plugin:1.0.0.Beta1:deploy (default-cli) @ test ---

Mär 04, 2016 5:55:44 PM org.xnio.Xnio <clinit>

INFO: XNIO version 3.1.0.CR7

Mär 04, 2016 5:55:44 PM org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version 3.1.0.CR7

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 10.310 s

[INFO] Finished at: 2016-03-04T17:55:44+01:00

[INFO] Final Memory: 25M/270M

[INFO] ------------------------------------------------------------------------

---------------------------------------------------

constituent[0]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/

constituent[1]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/takari-local-repository-0.9.0.jar

constituent[2]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/takari-filemanager-0.7.0.jar

constituent[3]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-core-3.3.3.jar

constituent[4]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-model-3.3.3.jar

constituent[5]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-settings-3.3.3.jar

constituent[6]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-settings-builder-3.3.3.jar

constituent[7]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-builder-support-3.3.3.jar

constituent[8]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-repository-metadata-3.3.3.jar

constituent[9]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-artifact-3.3.3.jar

constituent[10]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-plugin-api-3.3.3.jar

constituent[11]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-model-builder-3.3.3.jar

constituent[12]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-aether-provider-3.3.3.jar

constituent[13]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/aether-api-1.0.2.v20150114.jar

constituent[14]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/aether-util-1.0.2.v20150114.jar

constituent[15]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/plexus-interpolation-1.21.jar

constituent[16]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/plexus-utils-3.0.20.jar

constituent[17]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/plexus-component-annotations-1.5.5.jar

constituent[18]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/plexus-sec-dispatcher-1.3.jar

constituent[19]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-embedder-3.3.3.jar

constituent[20]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/plexus-cipher-1.7.jar

constituent[21]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/commons-cli-1.2.jar

constituent[22]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/maven-compat-3.3.3.jar

constituent[23]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/wagon-provider-api-2.9.jar

constituent[24]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/org.eclipse.sisu.plexus-0.3.0.jar

constituent[25]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/cdi-api-1.0.jar

constituent[26]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/jsr250-api-1.0.jar

constituent[27]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/org.eclipse.sisu.inject-0.3.0.jar

constituent[28]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/sisu-guice-3.2.5-no_aop.jar

constituent[29]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/guava-18.0.jar

constituent[30]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/aether-impl-1.0.2.v20150114.jar

constituent[31]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/aether-spi-1.0.2.v20150114.jar

constituent[32]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/aether-connector-okhttp-0.15.0.jar

constituent[33]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/okhttp-2.3.0.jar

constituent[34]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/okio-1.3.0.jar

constituent[35]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/aether-connector-basic-1.0.2.v20150114.jar

constituent[36]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/aether-transport-wagon-1.0.2.v20150114.jar

constituent[37]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/wagon-file-2.9.jar

constituent[38]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/commons-lang-2.6.jar

constituent[39]: file:/C:/apps/eclipse-mars/configuration/org.eclipse.osgi/913/0/.cp/

constituent[40]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime.slf4j.simple_1.6.2.20150902-0001/

constituent[41]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime.slf4j.simple_1.6.2.20150902-0001/jars/slf4j-simple-1.7.5.jar

constituent[42]: file:/C:/apps/eclipse-mars/configuration/org.eclipse.osgi/18/0/.cp/

---------------------------------------------------

Exception in thread "main" java.util.ServiceConfigurationError: org.xnio.XnioProvider: Provider org.xnio.nio.NioXnioProvider could not be instantiated

    at java.util.ServiceLoader.fail(Unknown Source)

    at java.util.ServiceLoader.access$100(Unknown Source)

    at java.util.ServiceLoader$LazyIterator.nextService(Unknown Source)

    at java.util.ServiceLoader$LazyIterator.next(Unknown Source)

    at java.util.ServiceLoader$1.next(Unknown Source)

    at org.xnio.Xnio.doGetInstance(Xnio.java:199)

    at org.xnio.Xnio.getInstance(Xnio.java:158)

    at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:73)

    at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:124)

    at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)

    at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)

    at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90)

    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)

    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)

    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)

    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)

    at org.wildfly.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:234)

    at org.wildfly.plugin.common.AbstractServerConnection.getClient(AbstractServerConnection.java:156)

    at org.wildfly.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:133)

    at org.wildfly.plugin.deployment.AbstractDeployment.validate(AbstractDeployment.java:192)

    at org.wildfly.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:136)

    at org.wildfly.plugin.deployment.AbstractAppDeployment.doExecute(AbstractAppDeployment.java:70)

    at org.wildfly.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:111)

    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)

    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)

    at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

    at java.lang.reflect.Method.invoke(Unknown Source)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: java.lang.ExceptionInInitializerError

    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

    at java.lang.reflect.Constructor.newInstance(Unknown Source)

    at java.lang.Class.newInstance(Unknown Source)

    ... 43 more

Caused by: java.lang.IllegalStateException: XNIO007004: No functional selector provider is available

    at org.xnio.nio.NioXnio$2.run(NioXnio.java:141)

    at org.xnio.nio.NioXnio$2.run(NioXnio.java:68)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.xnio.nio.NioXnio.<init>(NioXnio.java:67)

    at org.xnio.nio.NioXnioProvider.<clinit>(NioXnioProvider.java:30)

    ... 48 more

[dmlloyd]

This kind of error is a class of error I like to call "Not Good".  However, I think the cause might be simple: somehow you're pulling in a VERY old version of XNIO - not even a final release.  Make sure that your build has an XNIO version of 3.3.5.Final and hopefully you will see better results.

[thschaef42]

Hi David,

thanks for your reply - and I fully agree to your optinion about my error class :-)

Three comments regarding your suggestion to use XNIO 3.3.5:

- The Wildfly 8.2.0 server ran fine in the past using the factory delivered versions of XNIO which were: xnio-nio-3.3.0.Final.jar, netty-xnio-transport-0.1.1.Final.jar, xnio-api-3.3.0.Final.jar. I never updated them, so the JARs before and after my problem occured remained the same.

- And my "problematic" Wildfly runs fine on another laptop, which brings me to the conclusion, that it has something to do with my laptops Windows-, Java- or Whatever-environment that suddently changed, but not the Wildfly installation and configuration itself. By the way, I'm using a Windows 10 64-bit ...

- The brandnew downloaded Wildfly 10 is equipped with: xnio-nio-3.3.4.Final.jar, netty-xnio-transport-0.1.1.Final.jar, xnio-api-3.3.4.Final.jar, httpcore-nio-4.4.1.jar, but shows (and throws) the same errors and exceptions.

Nevertheless I would like to test your suggestion, but I don't know where to get the 3.3.5 XNIO JARs from? The latest version available in the Wildfly packages is 3.3.4; at XNIO - JBoss Community, they offer the 3.0 as latest available version - the 3.1 isn't available for download.

Do you have a link or a suggestion for me?

Thanks & best regards,

Thomas

[dmlloyd]

Right, well 3.3.0.Final is definitely an OK version to use, I don't think that's your problem.  Your problem is here:

[INFO] --- wildfly-maven-plugin:1.0.0.Beta1:deploy (default-cli) @ test ---
Mär 04, 2016 5:55:44 PM org.xnio.Xnio INFO: XNIO version 3.1.0.CR7
Mär 04, 2016 5:55:44 PM org.xnio.nio.NioXnio INFO: XNIO NIO Implementation Version 3.1.0.CR7

The plugin itself is using a very old version of XNIO, which (apparently) doesn't find NIO providers on Windows.  So you can probably get around this in one of two ways:

1. Update the plugin to some version which includes a newer XNIO
2. Insert a dependency declaration inside the plugin to establish the use of a newer XNIO API and NIO artifact

[thschaef42]

Hi David,

I upgraded the wildfly-maven-plugin to version 1.0.2.Final as suggested. It seems to use XNIO version 3.2.2.Final internally.

Unfortunately the same error still occurs during deploy using the plugin or when launching the Wildfly itself :-(

Here is the output of the deploy:

[INFO] --- maven-war-plugin:2.4:war (default-war) @ nest ---

[INFO] Packaging webapp

[INFO] Assembling webapp [nest] in [C:\Users\thoma\workspace-mars\nest\target\nest]

[INFO] Processing war project

[INFO] Copying webapp resources [C:\Users\thoma\workspace-mars\nest\src\main\webapp]

[INFO] Webapp assembled in [182 msecs]

[INFO] Building war: C:\Users\thoma\workspace-mars\nest\target\nest.war

[INFO]

[INFO] <<< wildfly-maven-plugin:1.0.2.Final:deploy (default-cli) < package @ nest <<<

[INFO]

[INFO] --- wildfly-maven-plugin:1.0.2.Final:deploy (default-cli) @ nest ---

Mär 06, 2016 10:14:15 AM org.xnio.Xnio <clinit>

INFO: XNIO version 3.2.2.Final

Mär 06, 2016 10:14:15 AM org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version 3.2.2.Final

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 7.249 s

[INFO] Finished at: 2016-03-06T10:14:15+01:00

[INFO] Final Memory: 26M/262M

[INFO] ------------------------------------------------------------------------

---------------------------------------------------

constituent[0]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/

constituent[1]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/takari-local-repository-0.9.0.jar

constituent[2]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime_1.6.2.20150902-0001/jars/takari-filemanager-0.7.0.jar

...

...

constituent[41]: file:/C:/apps/eclipse-mars/plugins/org.eclipse.m2e.maven.runtime.slf4j.simple_1.6.2.20150902-0001/jars/slf4j-simple-1.7.5.jar

constituent[42]: file:/C:/apps/eclipse-mars/configuration/org.eclipse.osgi/18/0/.cp/

---------------------------------------------------

Exception in thread "main" java.util.ServiceConfigurationError: org.xnio.XnioProvider: Provider org.xnio.nio.NioXnioProvider could not be instantiated

    at java.util.ServiceLoader.fail(Unknown Source)

    at java.util.ServiceLoader.access$100(Unknown Source)

    at java.util.ServiceLoader$LazyIterator.nextService(Unknown Source)

    at java.util.ServiceLoader$LazyIterator.next(Unknown Source)

    at java.util.ServiceLoader$1.next(Unknown Source)

    at org.xnio.Xnio.doGetInstance(Xnio.java:221)

    at org.xnio.Xnio.getInstance(Xnio.java:192)

    at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:112)

    at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:124)

    at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)

    at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)

    at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)

    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)

    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)

    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)

    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)

    at org.wildfly.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:245)

    at org.wildfly.plugin.common.AbstractServerConnection.getClient(AbstractServerConnection.java:162)

    at org.wildfly.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:139)

    at org.wildfly.plugin.deployment.AbstractDeployment.validate(AbstractDeployment.java:192)

    at org.wildfly.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:136)

    at org.wildfly.plugin.deployment.AbstractAppDeployment.doExecute(AbstractAppDeployment.java:70)

    at org.wildfly.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:111)

    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)

    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)

    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)

    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)

    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)

    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)

    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)

    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)

    at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

    at java.lang.reflect.Method.invoke(Unknown Source)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: java.lang.ExceptionInInitializerError

    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

    at java.lang.reflect.Constructor.newInstance(Unknown Source)

    at java.lang.Class.newInstance(Unknown Source)

    ... 43 more

Caused by: java.lang.IllegalStateException: XNIO007004: No functional selector provider is available

    at org.xnio.nio.NioXnio$2.run(NioXnio.java:145)

    at org.xnio.nio.NioXnio$2.run(NioXnio.java:72)

    at java.security.AccessController.doPrivileged(Native Method)

    at org.xnio.nio.NioXnio.<init>(NioXnio.java:71)

    at org.xnio.nio.NioXnioProvider.<clinit>(NioXnioProvider.java:30)

    ... 48 more

Thanks & best regards,

Thomas

[thschaef42]

Hi David and all others,

another question to the Wildfly community:

I've just recognized that my Windows 10 64-bit has installed the two updates KB 3140 743 and KB 3139 907 on March, 2nd.

This might be the date, I experienced the first problems with my installation (but I'm not 100% sure).

Does anybody else have a Windows 10 (64-bit), JDK8 (64-bit) and Wildfly 8.2.0 installation with KB 3140 743 and KB 3139 907 installed?

And what are your experiences?

And I continued to test Davids suggestion and relaced the Wildfly JARs xnio-api-3.3.0.Final.jar by xnio-api-3.3.1.Final.jar and xnio-nio-3.3.0.Final.jar by xnio-nio-3.3.1.Final.jar as downloaded when chosing the latest wildfly-maven-plugin. Until now without success ...

But I didn't find an update of the netty-xnio-transport-0.1.1.Final.jar. It seems that 0.1.1.Final from Jan. 2014 is the latest available version of this jar.

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0

10:41:19,738 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final

10:41:19,908 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final

10:41:19,965 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.2.0.Final "Tweek" starting

10:41:21,186 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment h2console.war

10:41:21,203 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment nest.war

10:41:21,230 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found nest.war in deployment directory. To trigger deployment create a file called nest.war.dodeploy

10:41:21,269 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

10:41:21,304 INFO  [org.xnio] (MSC service thread 1-4) XNIO version 3.3.1.Final

10:41:21,322 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.3.1.Final

10:41:21,365 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.remoting.endpoint.management: org.jboss.msc.service.StartException in service jboss.remoting.endpoint.management: Failed to start service

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.8.0_74]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.8.0_74]

        at java.lang.Thread.run(Unknown Source) [rt.jar:1.8.0_74]

Caused by: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found

        at org.xnio.Xnio.doGetInstance(Xnio.java:238)

        at org.xnio.Xnio.getInstance(Xnio.java:193)

        at org.jboss.remoting3.Remoting.createEndpoint(Remoting.java:112)

        at org.jboss.as.remoting.ManagementEndpointService.createEndpoint(ManagementEndpointService.java:45)

        at org.jboss.as.remoting.EndpointService.start(EndpointService.java:76)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

        ... 3 more

Thanks & regards,

Thomas

[alexslackx]

For anyone else who ran into this issue, in my case it seems to be caused by the OS itself running out of network connection handles. This prevents XNIO starting up as the XNIO NIO implementation relies (indirectly) on networking.

On Windows at least, adding the Handles column to Task Manager will allow you to see which application is consuming lots of handles.