I'm not sure if it's a bug or something that I have not interpreted correctly. Today I was taking a coffee I installed Jira for our beautiful development team, when Jira himself warned me not to use H2 as a database for a production server ... after a little more hot coffee, I agree with Jira that should not be using H2 as a database, I proceed to follow the steps indicated by Atlassian manuals and setup a mySQL database... all very easy and well explained, so I proceed to stop the Jira and start it again to only find me with an error:
JIRA-Bootstrap ERROR [o.o.c.entity.jdbc.DatabaseUtil] Could not create table "PUBLIC.versioncontrol"
I check, double check and triple check the configuration with the "config.sh" script and the same error appears ...
After a little more of hot coffee, it occurred to me to verify the configuration file ...
<url>jdbc:mysql://address=(protocol=tcp)(host=someserver_somewhere)(port=3306)/the_database_name?useUnicode=true&characterEncoding=UTF8&sessionVariables=default_storage_engine=InnoDB</url>
It looked pretty good, but something caught my attention.
<schema-name> PUBLIC </ schema-name>
PUBLIC says ... so I change this by the name of my schema mySQL ... and as magic before my eyes, the service began to work again, now with mySQL as it should.
I have used the configuration tool (config.sh), to generate the file, but whenever I use it, it generates by default the "schema-name" with the name of PUBLIC, so I do not know if it's an error or something I'm doing wrong .
Regards!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.