Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Google Groups by Roberto, 1 year ago
org.jnp.interfaces.NamingContextFactory]
via co.jp by Unknown author, 2 years ago
via Google Groups by Jarek, 7 months ago
org.jnp.interfaces.NamingContextFactory]
via jboss.org by Unknown author, 1 year ago
via Oracle Community by 843833, 1 year ago
org.jnp.interfaces.NamingContextFactory]
via Google Groups by TrICkY, 6 months ago
org.jnp.interfaces.NamingContextFactory]
java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)	at javax.naming.InitialContext.init(InitialContext.java:223)	at javax.naming.InitialContext.(InitialContext.java:197)	at com.mycompany.TEST.servlet.TESTSipServlet.getSipActionBean(TESTSipServlet.java:238)	at com.mycompany.TEST.servlet.TESTSipServlet.doSuccessResponse(TESTSipServlet.java:180)	at javax.servlet.sip.SipServlet.doResponse(SipServlet.java:268)	at com.mycompany.TEST.servlet.TESTSipServlet.doResponse(TESTSipServlet.java:147)	at javax.servlet.sip.SipServlet.service(SipServlet.java:327)	at org.mobicents.servlet.sip.core.dispatchers.MessageDispatcher.callServlet(MessageDispatcher.java:281)	at org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher$1.dispatch(ResponseDispatcher.java:297)	at org.mobicents.servlet.sip.core.dispatchers.DispatchTask.dispatchAndHandleExceptions(DispatchTask.java:55)	at org.mobicents.servlet.sip.core.dispatchers.DispatchTask.run(DispatchTask.java:50)	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)	at java.lang.Thread.run(Thread.java:619)