-
1. Re: Incomplete Deployment listing (for the nth time)
dimitris Apr 19, 2006 3:41 AM (in response to jpebe001)The EJBTimer service needs the Default datasource, that you have probably removed. Either add it back, or point the ejbtimer service to use your primary DB.
-
2. Re: Incomplete Deployment listing (for the nth time)
jpebe001 Apr 19, 2006 4:27 AM (in response to jpebe001)Hi Dimitris, and all those who care for a read,
A partial improvement!
Needless to say I changed the ejb-deployer.xml config file to<depends optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=MySqlDS</depends>
(was pointing to the now defunct DefaultDS) but I still get the following deployment errors on JBoss startup:10:12:50,953 ERROR [URLDeploymentScanner] (URLDeploymentScanner.java:507) - Incomplete Deployment listing: MBeans waiting for other MBeans: ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo state: CONFIGURED I Depend On: jboss:service=TransactionManager jboss.jca:service=DataSourceBinding,name=DefaultDS Depends On Me: MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM: ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS state: NOTYETINSTALLED I Depend On: Depends On Me: jboss:service=KeyGeneratorFactory,type=HiLo
Again, I have searched for all DefaultDS in the whole JBoss home directory and have found no live instances (all commented out).
I cannot find any instances of HiLo either.
Can someone please explain about this ? The mystery intensifies.
Maltese Jboss User
JP -
3. Re: Incomplete Deployment listing (for the nth time)
dimitris Apr 19, 2006 5:22 AM (in response to jpebe001)Have you tried searching the wiki?
http://wiki.jboss.org/wiki/Wiki.jsp?page=ChangeTheDatabase -
4. Re: Incomplete Deployment listing (for the nth time)
jpebe001 Apr 21, 2006 4:58 AM (in response to jpebe001)The problem is that I can find no instance of HiLo or of DefaultDS in any of my config files (I did a Windows search in all files for them - with null results - but then again maybe I should not trust Windows Search).
I do not think this problem has anything to do with changing the database. We have been using mysql since ages.
Many Thanks
JP -
5. Re: Incomplete Deployment listing (for the nth time)
haplo_3 Oct 8, 2006 11:36 PM (in response to jpebe001)did you manage to fix the problem?
i have the same problem -
6. Re: Incomplete Deployment listing (for the nth time)
jpebe001 Oct 9, 2006 3:19 AM (in response to jpebe001)NO, unfortunately not.
The application works fine though. I suggest you do as we did here (just ignore it).
I guess this is what happens when you don't sign (and pay) support contacts :) -
7. Re: Incomplete Deployment listing (for the nth time)
damien Jan 16, 2008 6:29 PM (in response to jpebe001)I know this is an old topic, but I came across this same issue in a 4.2.2 install. The datasource needs to be modified in deploy/uuid-key-generator.sar/META-INF/jboss-service.xml
-- Damien -
8. Re: Incomplete Deployment listing (for the nth time)
sukumarp Aug 14, 2009 12:57 AM (in response to jpebe001)Hi,
Can you please elaborate the change you made on deploy/uuid-key-generator.sar/META-INF/jboss-service.xml file to fix this issue?
Thanks,
Sukumar. -
9. Re: Incomplete Deployment listing (for the nth time)
mailming Sep 10, 2009 6:08 PM (in response to jpebe001)for jboss server 4.2.0 timer services default ds engine is hsql
if you want the error eliminated the following files are needed.
./server/default/deploy/hsqldb-ds.xml
./server/default/lib/hsqldb-plugin.jar
./server/default/lib/hsqldb.jar
mailming
mailming@gmail.com