JMS error by the time of starting Jboss

[chenna1978]

Hi,

I am using jboss-3.2.1 and I wrote one MDB and made an ear.
If I deploy an ear after starting jboss it deploys without any problems, where as if I restart the Jboss server after deploying it is redeploying an ear and getting the following errors.

08:59:22,734 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:

Incompletely deployed packages:

MBeans waiting for classes:

MBeans waiting for other MBeans:
[ObjectName: jboss.j2ee:jndiName=local/TestMDB,service=EJB
state: FAILED
I Depend On:
Depends On Me: javax.naming.NameNotFoundException: DefaultJMSProvider not bound, ObjectName: jboss.j2ee:jndiName=local/QuoteReportMDB,service=EJB
state: FAILED
I Depend On:
Depends On Me: javax.naming.NameNotFoundException: DefaultJMSProvider not bound]

08:59:22,750 INFO [URLDeploymentScanner] Started

08:59:22,843 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.1/server/default/conf/jboss-service.xml

08:59:22,843 INFO [Server] JBoss (MX MicroKernel) [3.2.1 (build: CVSTag=JBoss_3_2_1 date=200305041533)] Started in 28s:140ms


I am not getting the above errors if i redeploy an ear after jboss server started. Do I need to redeploy an ear each time when jboss server starts? I don't want to redeploy an ear each time when jboss server starts.
Does any one has this kind of problem?


Thanks in advacne.

[chenna1978]

Hi,

I got solution to the above problem.

The problem 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 my EAR is deployed before the JMS implementation.

To get rid of this problem I changed the value of RecursiveSearch to true in conf/jboss-service.xml i.e
True

Thanks.