Perhaps your service is getting deployed before the OracleDS is getting deployed. You can add an anonymous mbean dependency to your service to make it wait for the OracleDS ConnectionFactoryLoader mbean, like this:
Check the object name of the ConnectionFactoryLoader to make sure it matches.
Thanks. In 2.4.4 the order of the services in the jboss.jcml controlled the order they were started up, I overlooked this when I migrated to 3.0.
As you pointed out, getting the object name correct was important, in this case:
misspecifying this parameter causes the services to not start at all. Thanks again.