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 middlewaremagic.com by Unknown author, 2 years ago
TestQ -- service jboss.naming.context.java.jboss.exported.TestQ
via csdn.net by Unknown author, 2 years ago
jms/RemoteConnectionFactory -- service jboss.naming.context.java.jboss.exported.jms.RemoteConnectionFactory
via middlewaremagic.com by Unknown author, 1 year ago
cf — service jboss.naming.context.java.jboss.exported.cf
via middlewaremagic.com by Unknown author, 2 years ago
TestQ -- service jboss.naming.context.java.jboss.exported.TestQ
via csdn.net by Unknown author, 2 years ago
jms/RemoteConnectionFactory -- service jboss.naming.context.java.jboss.exported.jms.RemoteConnectionFactory
javax.naming.NameNotFoundException: test -- service jboss.naming.context.java.jboss.exported.test	at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)	at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127)	at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73)	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:662)