Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Test Connectivity fails on JNDI server instance



User is getting a classNotFound exception while performing test connectivity on a JNDI server instance. Observed in Jboss6.4 and Jboss 6.2 application servers.

Error Messages

Required classes are not available, please check the configuration

Error Details:
java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory

Steps to Reproduce

Test Connectivity by using Context factory as org.jnp.interfaces.NamingContextFactory on JNDI-Server.

Root Cause

A software use or operation error 

As per the Jboss application server documents,  one should not use the JNP protocol with JBoss AS7/EAP6.x versions and must change to ejb-client or remote-naming as the JNDI naming implementation.


Perform the following local-change:

Instead of using JNP: "org.jnp.interfaces.NamingContextFactory", use the below remote-naming for JBoss EAP 6.x

Context Factory : "org.jboss.naming.remote.client.initialcontextfactory"
Provider URL : "remote://hostname:portnumber"



Published April 11, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us