Hi, That has been fixed. Now my error is this :
| 2008-12-19 21:08:01,862 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-2) Failure in jms activation org.jboss.resource.adapter.jms.inflow.jmsactivations...@1899788(ra=org.jboss.resource.adapter.jms.jmsresourceadap...@1f0c437 destination=queue/CartQueue destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) | javax.naming.NameNotFoundException: queue 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:396) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673) | at javax.naming.InitialContext.lookup(InitialContext.java:351) | 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:204) | at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) | at java.lang.Thread.run(Thread.java:595) Going nuts with Jboss5. This kind of tedious setup would not help anyone. When the whole world speaks about backward compatibility, forcing people to undergo such a pain is undue. With folks like jaikiran, yes, we can live with it. Jaikiran helps all of us a lot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197675#4197675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197675 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
