JBoss 4.0: Dependency on DefaultDS

[cepage]

I am attempting to move an app from 3.2.5 to 4.0.0. I started with the 'standard' server, and I removed JMS, HSQLDB, and the DefaultDS data source definition.

When I attempt to deploy my app, which has CMP's bound to another datasource, I get the following stacktrace:

11:40:49,109 ERROR [EntityContainer] Starting failed jboss.j2ee:jndiName=java%3a/ejb/WorkflowEntry,service=EJB
org.jboss.deployment.DeploymentException:
Failed to obtain type-mapping metadata from the metadata library MBean:
jboss.jdbc:service=metadata,datasource=DefaultDS is not registered.;
- nested throwable: (javax.management.InstanceNotFoundException:
jboss.jdbc:service=metadata,datasource=DefaultDS is not registered.)
 at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityMetaData.obtainTypeMappingFromLibrary(JDBCEntityMetaData.java:1482)
 at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityMetaData.<init>(JDBCEntityMetaData.java:502)
 at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCApplicationMetaData.<init>(JDBCApplicationMetaData.java:312)
 at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCXmlFileLoader.load(JDBCXmlFileLoader.java:67)
 at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadJDBCEntityMetaData(JDBCStoreManager.java:721)
 at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:409)
 at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:353)
 at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157)
 at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:340)

Who is dependent on DefaultDS? I could not find anything incriminating in jboss-jdbc-metdata.sar.

Thanks,
Corby

[helgaw]

You will find references to DefaultDS within files such as login-config.xml and ejb-deployer.xml. Seems to me that DefaultDS is used to persist some internal stuff within the app server.

I had the same problem and in the end I just restored the hsqldb-ds.xml file (which I had deleted since I'm using mysql).

Now I haven't had the time to find out why this is so, or if there is a way to change it.

[rram]

I faced the same problem. Traced it to the following in mysql-ds.xml file.


<type-mapping>mySQL</type-mapping>


This needs to be uncommented/enabled so that the corresponding type-mapping from standardjbosscmp-jdbc.xml is selected.

This fixed the error.