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 Coderanch by igor bolsovitch, 1 year ago
via Coderanch by Ram Appu, 1 year ago
via Coderanch by Ram Appu, 1 year ago
javax.naming.NameNotFoundException: DLQ not bound	at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)	at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)	at org.jnp.server.NamingServer.getObject(NamingServer.java:785)	at org.jnp.server.NamingServer.lookup(NamingServer.java:443)	at org.jnp.server.NamingServer.lookup(NamingServer.java:399)	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:722)	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682)	at javax.naming.InitialContext.lookup(InitialContext.java:392)	at org.jboss.util.naming.Util.lookup(Util.java:222)	at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQDestination(AbstractDLQHandler.java:106)	at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:82)	at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)	at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413)	at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351)	at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729)	at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:213)	at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)	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)