Re: [Ejbca-develop] Problem Creating CA

[Tomas G. <to...@pr...>]

Did you do an 'ant deploy' after changing the references in XML-files? 
Specifically src/ra/META-INF/jbosscmp-jdbc.xml must have the correct datasource 
and the correct database. I think you are using MySQL right? I think it tries to 
create the table in DefaultDS perhaps instead of in your MySQL. The sql-command:

CREATE TABLE ADMINPREFERENCESDATA (id VARCHAR(250) BINARY NOT NULL, data 
LONGBLOB, CONSTRAINT PK_ADMINPREFERENCESDATA PRIMARY KEY (id));

executes nicely in my MySQL database without errors.

Cheers,
Tomas

Peter Param wrote:
>>Hi, you error states that the datasource is not properly configured. 
> 
> 
>>Did you perhaps enter only EjbcaDS instead of java:/EjbcaDS once? In that
> 
> case you have 
> to search all xml files for instances of EjbcaDS and change it to
> java:/EjbcaDS.
> 
> I have ..but i still get errors running up the Jboss app.  Its unable to
> create the table ADMINPREFERENCESDATA , the logs say the following:
> 
> 9:13:29,382 ERROR [EntityContainer] Starting failed
> jboss.j2ee:jndiName=local/EndEntityProfileData,service=EJB
> org.jboss.deployment.DeploymentException: Error while creating table
> ADMINPREFERENCESDATA; - nested throwable: (java.sql.SQLException: Unexpected
> token: BINARY in statement [CREATE TABLE ADMINPREFERENCESDATA (id VARCHAR(250)
> BINARY NOT NULL, data LONGBLOB, CONSTRAINT PK_ADMINPREFERENCESDATA PRIMARY KEY
> (id))])
> 	at
> org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.createTable(JDBCStartCommand.java:497)
> 	at
> org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.execute(JDBCStartCommand.java:186)
> 	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:147)
> 	at
> org.jboss.ejb.EntityContainer.startService(EntityContainer.java:337)
> 	at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
> 	^
>                 |
>                 |  // many, many lines later!
>                 |
>                 v
> Caused by: java.sql.SQLException: Unexpected token: BINARY in statement
> [CREATE TABLE ADMINPREFERENCESDATA (id VARCHAR(250) BINARY NOT NULL, data
> LONGBLOB, CONSTRAINT PK_ADMINPREFERENCESDATA PRIMARY KEY (id))]
> 	at org.hsqldb.Trace.getError(Unknown Source)
> 	at org.hsqldb.jdbcResultSet.<init>(Unknown Source)
> 	at org.hsqldb.jdbcConnection.executeStandalone(Unknown Source)
> 	at org.hsqldb.jdbcConnection.execute(Unknown Source)
> 	at org.hsqldb.jdbcStatement.fetchResult(Unknown Source)
> 	at org.hsqldb.jdbcStatement.executeUpdate(Unknown Source)
> 	at
> org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:281)
> 	at
> org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand.createTable(JDBCStartCommand.java:484)
> 	... 123 more
> 
> cheers
> 
> Peter
> 
> 
> 
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
> 
> This footnote also confirms that this email message has been
> virus scanned and although no viruses were detected by the system,
> St Vincent's Hospital accepts no liability for any consequential
> damage resulting from email containing any computer viruses.
> 
> **********************************************************************