DefaultJMSProvider not bound

[raickman]

Hi,

I am using JBoss v 4.0.4 GA, on Solaris platform and don't understand this:

I get the following error when starting JBoss:

-------------------------------------------------------------------------------------
13:26:43,391 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:ear=app-3.5.3.ear,jar=workflow-1.0.0.jar,name=BusinessProcessMessageBean,service=EJB3
State: FAILED
Reason: javax.naming.NameNotFoundException: DefaultJMSProvider not bound
I Depend On:
persistence.units:ear=app-3.5.3.ear,jar=workflow-1.0.0.jar,unitName=manager1

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.j2ee:ear=app-3.5.3.ear,jar=workflow-1.0.0.jar,name=BusinessProcessMessageBean,service=EJB3
State: FAILED
Reason: javax.naming.NameNotFoundException: DefaultJMSProvider not bound
I Depend On:
persistence.units:ear=app-3.5.3.ear,jar=workflow-1.0.0.jar,unitName=manager1
-------------------------------------------------------------------------------------

In the deploy directory, I put in infoqueue-destinations-service.xml:

<mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=myNotificationQueue">
 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
 <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
 <attribute name="SecurityConf">
 <security>
 <role name="administrator" read="true" write="true" create="true"/>
 <role name="user" read="true" write="true" create="true"/>
 </security>
 </attribute>
 </mbean>

In jboss-service.xml:

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

If I drop my ear file when JBoss is already started, everthing works!
Om my Windows localhost JBoss with same config, everything works too.
Could you please tell me what I m doing wrong ?

Thanks

[raickman]

I forgot, my MDB is clustered

@MessageDriven(
 activationConfig={@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
 @ActivationConfigProperty(propertyName="destination", propertyValue="queue/myNotificationQueue")})
@Clustered(partition=ClusterConfig.CLUSTER_PARTION, loadBalancePolicy=FirstAvailableIdenticalAllProxies.class)
@ApplicationException(rollback=true)
@TransactionManagement(TransactionManagementType.CONTAINER)

[raickman]

Please help. Still don't know why the DefaultJMSProvider is not bound.



--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.j2ee:ear=cmds-app-3.5.4.ear,jar=cmds-workflow-1.0.0.jar,name=BusinessProcessMessageBean,service=EJB3
State: FAILED
Reason: javax.naming.NameNotFoundException: DefaultJMSProvider not bound

ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss:service=KeyGeneratorFactory,type=HiLo

[bershath27]

>>ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
>>State: NOTYETINSTALLED
>>Depends On Me:

did you change the default datasource JNDI name, DefaultDS or change the database ? the error is no datasource been bound under DefaultDS.

thanks
Tyronne Wickramarathne

[raickman]

I m using Oracle DataBase but not as DefaultDS, sp I ve replaced both of the files 'hsql...-service.xml' from deploy/jms by 'oracle...-service.xml'.

In the JBoss log file, I can't see that the DefaultDS has been bound, but the hsql-ds.xml is in deploy.

If I hot deploy, all JMS_MESSAGEs are stored in our Oracle DB, and no exception is thrown. I don't know what is referencing the DefaultDS in this config.

Thanks for you answer

[sraick]

My problem is, only on Unix Sun Solaris, that the DefaultDS is bound after the DefaultJMSProvider. On Windows OS, DefaultDS is bound before and everything works.

Would it be possible that the recursive scan on Solaris doesn't work as it would?