Skip to content

MySQL storage_engine problem #239

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vrmerlin opened this issue Mar 30, 2018 · 2 comments
Closed

MySQL storage_engine problem #239

vrmerlin opened this issue Mar 30, 2018 · 2 comments
Labels
bug Something isn't working

Comments

@vrmerlin
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 5.3.5
  • Ruby: 2.0.0p648
  • Distribution: Puppet Enterprise
  • Module version: 3.4.0

How to reproduce (e.g Puppet code you use)

  class { 'jira':
    version             => '7.8.1',
    installdir          => '/opt/atlassian-jira',
    homedir             => '/myatlassian/jira',
    db                  => 'mysql',
    dbtype              => 'mysql',
    dbname              => 'jiradb',
    dbuser              => 'jiradbuser',
    dbdriver            => 'com.mysql.jdbc.Driver',
    dbpassword          => 'XXX',
    dbserver            => 'localhost',
    javahome            => '/usr/java/default',
    jvm_xmx             => '3584m',
    jvm_xms             => '3584m',
    mysql_connector_version => '5.1.46',
  }

What are you seeing

The file dbconfig.xml is being modified by Puppet to have this JDBC URL:

jdbc:mysql://localhost:5432/jiradb?useUnicode=true&characterEncoding=UTF8&sessionVariables=storage_engine=InnoDB

However, JIRA is coming up and complaining this: "The connection URL in your dbconfig.xml file contains the storage_engine parameter, which has been deprecated. This needs to be replaced with the default_storage_engine parameter."

What behaviour did you expect instead

How do I change the sessionVariable to match what JIRA 7.8.1 is expecting?

@bastelfreak
Copy link
Member

I just merged #216 which should fix this. I'm going to release a new version now. Please report back if it doesn't fix your issue.

@bastelfreak bastelfreak added the bug Something isn't working label Mar 30, 2018
@vrmerlin
Copy link
Author

vrmerlin commented Apr 5, 2018

Yep, that fixed the issue! Thanks :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants