File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JBoss/WildFly and the fly likes NameNotFoundException Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "NameNotFoundException" Watch "NameNotFoundException" New topic


madhukar chendra

Joined: Jan 06, 2005
Posts: 3

I saw on google search about this problem. No one has solution to this.

I am trying to deploy Message driven bean into Jboss-3.2.1 server and getting the following error.
Can any one help me why I am getting this error?

WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=local/SampleMDB,service=EJB

javax.naming.NameNotFoundException: DefaultJMSProvider not bound

ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'

org.jboss.deployment.DeploymentInfo@e9a284c4 { url=file:/C:/jboss-3.2.1/server/default/deploy/jms/jbossmq-destinations-service.xml }
deployer: org.jboss.deployment.SARDeployer@1d2b01b
status: Deployment FAILED reason: create operation failed for package file:/C:/jboss-3.2.1/server/default/deploy/jms/jbossmq-destinations-service.xml; - nested throwable: (org.jboss.deployment.DeploymentException: Trying to install an already registered mbean:,name=testQueue)
state: FAILED
watch: file:/C:/jboss-3.2.1/server/default/deploy/jms/jbossmq-destinations-service.xml

Depends On Me:
, ObjectName:,name=DLQ
I Depend On:

Depends On Me: , ObjectName: jboss.j2ee:jndiName=local/SampleMDB,service=EJB
state: FAILED
I Depend On:
Depends On Me: javax.naming.NameNotFoundException: DefaultJMSProvider not bound]

Here is the XML code I am using to deploy MDB.

ejb-jar.xml code:


<description />

jboss.xml code:

<configuration-name>Standard Message Driven Bean</configuration-name>


<mbean code=""
<depends optional-attribute-name="DestinationManager"></depends>

Sean Stidman

Joined: Jan 22, 2005
Posts: 2
Hi Madhukar,

I was bored so I searched for the solution to your problem. I found the following explanation at

This is due to the fact that the jms configuration is in /deploy/jms folder in JBoss 3.2.1.
By default the deploy folder is parsed first for deployments and then its subfolders.
So your EAR is deployed before the JMS implementation.

To get rid of that problem go in your conf/jboss-service.xml and change the value of RecursiveSearch to true.

<attribute name="RecursiveSearch">True</attribute>

I hope that works for you,

madhukar chendra

Joined: Jan 06, 2005
Posts: 3
Hi Sean,

Thank you very much. Whatever you said is coorect and if change attribute to "true" it is working.
ray frid
Ranch Hand

Joined: Dec 23, 2010
Posts: 79
I have the same problem and unfortunely the attribute RecursiveSearch already was set as true and the problem still occours.

any idea?

Peter Johnson

Joined: May 14, 2008
Posts: 5852

Same problem? You're using Jboss-3.2.1???

JBoss In Action
I agree. Here's the link:
subject: NameNotFoundException
It's not a secret anymore!