How to solve 'No matching XNIO provider found' exception, faced while creation of InitialContext in JMS client code of BPMS 6 ?

Solution Verified - Updated -


  • BPMS 6 supports the use of JMS messages for starting and managing business processes as well as managing Human Tasks through command request messages [1]. However, when creating the InitialContext at runtime the standalone JMS client code throws No matching XNIO provider found exception as shown below. How to fix this issue?
Caused by: java.lang.RuntimeException: Unable to create InitialContext
    at: com.sample.test.InitialContextCreation.getRemoteInitialContext(
Caused by: javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.IllegalArgumentException: No matching XNIO provider found]
    at org.jboss.naming.remote.client.ClientUtil.namingException(
    at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(
    at javax.naming.spi.NamingManager.getInitialContext(
    at javax.naming.InitialContext.getDefaultInitCtx(
    at javax.naming.InitialContext.init(
    at javax.naming.InitialContext.<init>(
    at: com.sample.test.InitialContextCreation.getRemoteInitialContext(
    ... 33 more
Caused by: java.lang.IllegalArgumentException: No matching XNIO provider found
    at org.xnio.Xnio.doGetInstance(
    at org.xnio.Xnio.getInstance(
    at org.jboss.remoting3.Remoting.createEndpoint(
    at org.jboss.naming.remote.client.EndpointCache.get(
    at org.jboss.naming.remote.client.InitialContextFactory.createEndpoint(
    at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateEndpoint(
    at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(
    at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(
    ... 38 more

[1] 17.3. JMS


  • Red Hat JBoss BPM Suite (BPMS)
    • 6.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In