Can't enable scheduler after update v3.2.3

[Damian Egli]

Hi, after upgrading to 3.2.3 the plugin can't be enabled. We run jira version:

JIRA 6.3.15 build: 6346

The stacktrace is attached. I also tried to uninstall the plugin and reintall it again. Same error. Further I tried to download the plugin and do the installation via upload instead of a direct installation via UPM

Regards, Damian

[jost]

Hi Damian

We will analyze this error and let you know about solution.

Regards, Jacek

[Bartosz Gilewski]

Hi Damian,

New version of The Scheduler (3.2.4) is now avalible on Marketplace. Please to try it and let us know if it is working properly now.

Regards, Bartosz Gilewski

[Damian Egli]

Hi Bartosz,

unfortunately it doesn't work. Please see the attached logfile fragment

Regards, Damian

[Bartosz Gilewski]

Hi Damian,

Could you send the whole log file to our mail ([e-mail])?

Regards, Bartosz

[jost]

Hi Damian,

The logfile fragment indicates that you have some problems with database connection. More specifically, JIRA saves configuration of the database in dbconfig.xml file and for some reasons Plugin throw error while try to read database schema. Content of this file should look similar to this:

<?xml version="1.0" encoding="UTF-8"?>
<jira-database-config>
<name>defaultDS</name>
<delegator-name>default</delegator-name>
<database-type>mssql</database-type>
<schema-name>dbo</schema-name>

<jdbc-datasource>
<url>jdbc:jtds:sqlserver://localhost:1433/jiradatabase</url>
               <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
               <username>DBADMIN</username>
               <password>DBADMIN</password>
               <pool-min-size>20</pool-min-size>
               <pool-max-size>20</pool-max-size>
               <pool-max-wait>30000</pool-max-wait>
               <pool-max-idle>20</pool-max-idle>
               <pool-remove-abandoned>true</pool-remove-abandoned>
               <pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>
    </jdbc-datasource>

</jira-database-config>

Please find this file in your JIRA HOME and make sure that this file is complete and is contain tag "<schema-name>".

Unfortunately i'm not able to reproduce this bug. So i need fragment of logfile containing start jira and installing The Scheduler plugin. Could you restart Jira server and try to install scheduler? Then send us piece of logs showing this case. Could you write which database are you using?

[Damian Egli]

Indeed, this helped. But it's weird - we run Jira for more than 3 years this way and never had any issue about the database connection ;-)

[jost]

Hi Damian,

Do you mean that restart JIRA resolved this problem?

Regards

[Damian Egli]

Hi,

yes, after I added the scheme tag to my config file, I restarted Jira and then I could update your plugin. But as I said: your plugin is the only one of those we use, that couldn't handle the default scheme! Since years we had this config and everything worked perfect.

Regards, Damian