I think I see what the problem is. The certificate fields are too long for using the standard mappings that JBoss uses for MS-SQL (the same is for MySQL and Oracle so nothing strange). The standard mapping between String and JDBC type only allows 256 bytes, we need 1-3KB, depending on cert contents. CRLs can be veeeeeery large.
You have to make a new jaws.xml in src/ca/META-INF
There are already example files for mysql and oracle, you can edit one of those and use the datatype that works for large. Then simply rename the file to jaws.xml, build and try again.
You will need to drop the currently created tables, since new ones will be created using the new datatypes.
If you get it to work, I would like to get my hands on your jaws.xml file.
Regards,
Tomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks much Tomas. I was able to get fresh DB going and it worked for Oracle. Quite possible it could be the way I was accessing DB.
I may go towards MySQL to get this going given that Oracle may have issues going forward.
Question: Does following look like good plan for Oracle to MySQL switch or am I missing it big time
1) Shutdown Existing App server
2) Export Oracle into dump file
3) Build new environment with fresh MySQL DB connection
4) Shutdown new App Server
5) Import Oracle dump into MySQL DB (new)
6) Update data-source in standard.xml
7) Start new app server
What about other customizations in app server or they all are in deployment* and standard.xml file?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has anyone succesffuly used EJBCA with MS SQL Server? EJBCA creates the tables but the CA doesn't work.
Could not create entity:java.sql.SQLException: [HLK-PROJECTS]String or binary data would be truncated.
I think I see what the problem is. The certificate fields are too long for using the standard mappings that JBoss uses for MS-SQL (the same is for MySQL and Oracle so nothing strange). The standard mapping between String and JDBC type only allows 256 bytes, we need 1-3KB, depending on cert contents. CRLs can be veeeeeery large.
You have to make a new jaws.xml in src/ca/META-INF
There are already example files for mysql and oracle, you can edit one of those and use the datatype that works for large. Then simply rename the file to jaws.xml, build and try again.
You will need to drop the currently created tables, since new ones will be created using the new datatypes.
If you get it to work, I would like to get my hands on your jaws.xml file.
Regards,
Tomas
Thanks much Tomas. I was able to get fresh DB going and it worked for Oracle. Quite possible it could be the way I was accessing DB.
I may go towards MySQL to get this going given that Oracle may have issues going forward.
Question: Does following look like good plan for Oracle to MySQL switch or am I missing it big time
1) Shutdown Existing App server
2) Export Oracle into dump file
3) Build new environment with fresh MySQL DB connection
4) Shutdown new App Server
5) Import Oracle dump into MySQL DB (new)
6) Update data-source in standard.xml
7) Start new app server
What about other customizations in app server or they all are in deployment* and standard.xml file?
Hi Tarun,
This is a thread about MS-SQL. Before I answer, can you move this to a new thread instead.
Cheers,
Tomas