did you find a solution? I see that the bug has been closed with a "works for me"
I'm having the same problem as you, as can see in the dump below my MBean called LimeManagement is started before the CMP beans are availible to be queried.
22:18:19,813 INFO [EntityContainer] Started
22:18:19,814 INFO [LimeManagement] Starting
22:18:19,821 INFO [STDOUT] Queue DefaultInQueue already exists
22:18:19,823 INFO [STDOUT] Queue UnroutableQueue already exists
22:18:19,824 INFO [STDOUT] Queue SendFailedQueue already exists
22:18:19,824 INFO [STDOUT] MBean started
22:18:19,825 INFO [LimeManagement] Started
22:18:19,827 INFO [EntityContainer] Starting
22:18:20,239 INFO [SmscDriverParameterDefinition] Table 'smscdriverparameterdef
inition' already exists
22:18:20,274 INFO [RouteEntity] Table 'route' already exists
22:18:20,339 INFO [ReceiveKeywordEntity] Table 'receivekeyword' already exists
22:18:20,384 INFO [CostEntity] Table 'cost' already exists
22:18:20,553 INFO [BillingEventEntity] Table 'billingevent' already exists
22:18:20,644 INFO [AccountEntity] Table 'account' already exists
22:18:20,687 INFO [ReceiveMapEntity] Table 'receivemap' already exists
22:18:20,739 INFO [PriceListEntity] Table 'pricelist' already exists
I experience similar problem.
Is it possible to post your programmatic solution?
It looks like this is the requirement to have clear Startup service that can be invoked before or after
I have exactly the same issue. Has anybody a solution for it?
Looking for a workaround.... is there a service we can be sure it is started after any deployed EJB? If that service existed, we could set our service dependece to it.
Any help is really appreciated.
Actually, I have just tried the example 03 in chap 2 of the admin and dev guide and it works with JBoss 3.0.8. So... problem solved!