JBoss (jboss-4.0.0DR4.zip) generates a bad create table stat

[mherv]

Hi, I thought I made all the necessary changes to assign MYSQL as the default Database for JBOSS (all). and I removed all the hsqldb configuration files

However, at startup, jboss tries to create a table with warchar(256) fields that MySQL doesn't support (hypersonic SQL did support them)

Following is a snippet of the error log.

It doesn't stop JBOSS (all) to start, and the jmx console to show up, but it doesn't seem nice, and I don't know what the consequences could be to leave it like that.

any help appreciated

here comes the snippet
====================================
2004-07-08 18:32:08,343 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.MetaDataEntity] Executing SQL: CREATE TABLE JBOSS_METADATA_ENTITY_BEANS (IDENTITY VARCHAR(256) NOT NULL, XML VARCHAR(256), NAME VARCHAR(256), LAST_MODIFIED BIGINT NOT NULL, previous_identity_fk VARCHAR(256), child_identity_fk VARCHAR(256), CONSTRAINT pk_JBOSS_METADATA_ENTITY_BEANS PRIMARY KEY (IDENTITY))
2004-07-08 18:32:08,359 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.MetaDataEntity] Could not create table JBOSS_METADATA_ENTITY_BEANS
2004-07-08 18:32:08,359 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
2004-07-08 18:32:08,359 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2004-07-08 18:32:08,359 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2004-07-08 18:32:08,359 ERROR [org.jboss.ejb.EntityContainer] Starting failed jboss.j2ee:jndiName=ejb/media/MetaDataEntity,service=EJB
org.jboss.deployment.DeploymentException: Error while creating table JBOSS_METADATA_ENTITY_BEANS; - nested throwable: (java.sql.SQLException: Invalid argument value, message from server: "Too big column length for column 'IDENTITY' (max = 255). Use BLOB instead")
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.createTable(JDBCStartCommand.java:495)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.execute(JDBCStartCommand.java:184)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:492)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:396)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157)
at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:346)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)

[aloubyansky]

Are you using mySQL datasource-mapping?

[mherv]

Thanks for your reply Alexey

Yes this was what I was doing. The mySQL mapping is used most of the time, but it seems that a part of JBOSS does'nt recognize it and tries to use hypersonic sql what ever the parameters would be.

Snce my first message, I made a search for hypersonic in the *.xml files of "all" configuration, and delected all the hypersonic mappings.

Upon reboot, I got an error message telling me that
the hypersonic mappings was missing in
jbosscmp-jdbc.xml
(and not standardjbosscmp-jdbc.xml) this is odd because the other file couln't be found

As I couldn't know who was looking for the mapping, I found a quick and dirty turn around for the problem by duplicating the mySQL mapping and renaming it Hypersonic SQL.

The only error that I couln't understand at the moment is this one :
2004-07-09 12:04:11,734 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
MBeans waiting for other MBeans:

At the moment, I don't intent to investigate on this because I don't think it is so serious. Thanks to let me know if it is

Best regards, Marc

[mherv]

I think the problem came from this:
I removed hsqldb-jdbc2-service.xml from the all\deploy\jms folder, but I did not replace it by mysql-jdbc2-service.xml.

Didn't try to see if it still asks for hypersonic sql, but it was definately missing.

Best regards, Marc