• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Problem in Deploying MDB bean

 
gourav chouhan
Ranch Hand
Posts: 74
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi friends,
I m getting problem in deploying MDB

2010-05-27 17:56:54,500 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-8) Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@e423cf(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@825030 destination=jms/mdb/MyQueue 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: jms 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:726)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
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.JmsActivation.setupDestination(JmsActivation.java:464)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
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)

2010-05-27 17:57:04,500 INFO [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-8) Attempting to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@e423cf(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@825030 destination=jms/mdb/MyQueue 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)
2010-05-27 17:57:04,500 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-8) Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@e423cf(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@825030 destination=jms/mdb/MyQueue 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)

I getting this error
any one please help me
 
Jaikiran Pai
Marshal
Pie
Posts: 10447
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How and where have you deployed the queue to which this MDB is listening?
 
Vikram Saxena
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Also,

First check would be whether the queue jms/mdb/MyQueue exists. You can check the logs during the server start up and see if the queue is being deployed. If yes, You can write a simple Java program to just lookup the queue and see if you are able to get the queue.
 
gourav chouhan
Ranch Hand
Posts: 74
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How do i deploy the queue ??
i m using jboss 5.1
 
Vikram Saxena
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Simple.

in the \server\<<your_server>>\deploy\messaging folder there is a xml names destination-service.xml.
Make a queue entry in the xml in the following manner :

 
gourav chouhan
Ranch Hand
Posts: 74
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks every one this issues is been resolved
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic