-
1. Re: DefaultJMSProvider not bound
raickman Aug 9, 2007 7:15 AM (in response to 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)
-
2. Re: DefaultJMSProvider not bound
raickman Sep 18, 2007 5:41 AM (in response to 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 -
3. Re: DefaultJMSProvider not bound
bershath27 Sep 18, 2007 6:51 AM (in response to raickman)>>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 -
4. Re: DefaultJMSProvider not bound
raickman Sep 18, 2007 7:06 AM (in response to 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 -
5. Re: DefaultJMSProvider not bound
sraick Sep 19, 2007 3:30 AM (in response to raickman)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?