Scheduler failing in JIRA 6.4.7

[Susan Hauth]

Scheduler is failing in JIRA 6.4.7 - See attached logs. Tried uninstall and re-install.

[Susan Hauth]

This is a critical bug and it's been 4 days. Can someone address it!

[Paweł Kulicki]

Hi Susan,

Sorry for late answer. We already analyze this error and will let you know about a possible solution.

Regards, Pawel

[Paweł Kulicki]

Unfortunately we cannot reproduce this bug. We tested it on Jira 6.4.7 with MS SQL Database in version 10.50.4000 (the same as yours).

Could you describe use case step by step what you are doing that you are getting this error? Are you upgraded recently MS Sql Database?

[Susan Hauth]

We don't do anything to get this error. We simply install the plugin and then these errors show up in the error log. But there is no Scheduled issues tab in the Project Overview and no scheduled issues generated. The plugin installs without error but then nothing seems to be activated. When I try to select "Scheduled Issue" under the System-Security, I get an error "404 - Oops you've found a dead link".

It's probable that we recently upgraded our Database but I can't say for sure until tomorrow when our system admin returns.

[Paweł Kulicki]

Thank you for the information, we are still analyze this error.

When you will be talk with your system admin, please ask him about metadata from tables which The Scheduler uses and send me that data. We think that this error may be due to the add of constraints on the columns by MSSql.

[Susan Hauth]

Spoke to our System Admin and he's not sure what you mean. He asked if you could provide a t-sql script?

[Paweł Kulicki]

In Microsoft SQL Management Studio, select table AO_A406ED_SCHEDULED_ISSUE, click on the right mouse button->Script Table as->CREATE To->New Query Editor Window, then copy the script and send to me.

[Susan Hauth]

Please find attached

[Susan Hauth]

Hi Pawel, Any progress? We have now upgraded to JIRA 6.4.7 and are waiting on a response from you so that we can get The Scheduler working. Cheers...Susan

[Paweł Kulicki]

Hi Susan,

After analysis of your log file we suppose that this error could be due to configuration of your instance. Our assumption is based on many errors in your log file with are connected with other plugins. For example :

com.valiantys.jira.plugins.vertygo.sla.utils.MissingSLAConfigurationException: Unable to get AgreementTime with id '33'
               at com.valiantys.jira.plugins.vertygo.sla.manager.impl.SLAConfigServiceImpl.getMandatoryAgreementTime(SLAConfigServiceImpl.java:142)
               at com.valiantys.jira.plugins.vertygo.sla.searcher.indexer.SLADataIndexer.addDocumentFields(SLADataIndexer.java:129)
               at com.valiantys.jira.plugins.vertygo.sla.searcher.indexer.SLADataIndexer.addDocumentFieldsSearchable(SLADataIndexer.java:86)

or

2015-07-02 16:22:46,446 Timer-1 ERROR      [osgi.container.felix.FelixOsgiContainerManager] JarContent: Unable to read bytes.
java.lang.IllegalStateException: zip file closed
               at java.util.zip.ZipFile.ensureOpen(Unknown Source)
               at java.util.zip.ZipFile.getEntry(Unknown Source)
               at java.util.jar.JarFile.getEntry(Unknown Source)

or

2015-07-02 16:29:55,164 localhost-startStop-1 ERROR      [atlassian.jira.service.OfBizServiceConfigStore] Unable to create a service config for service with the name : CRM Cron Service to copy changes from CRM to JIRA. 
com.atlassian.jira.service.OfBizServiceConfigStore$ClassNotFoundServiceException: Could not find class: com.atlassian.jira.plugin.customfield.crm_integrator.control.CreateIssueCron
               at com.atlassian.jira.service.OfBizServiceConfigStore.instantiateServiceContainer(OfBizServiceConfigStore.java:252)
               at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceContainer(OfBizServiceConfigStore.java:212)

We may think that as a result of above some updates hasn’t been perform in the database. On our side we performed following test: We installed old JIRA, old version of scheduler, than we upgraded JIRA, and Scheduler. Normally in this scenario constraint mentioned below should be removed and it has been removed in our environment. We can see that it still exists in yours.

So we suggest to invoke below script manually.

ALTER TABLE [jiradbschema].[AO_A406ED_SCHEDULED_ISSUE] DROP CONSTRAINT [U_AO_A406ED_SCHEDUL1453239299]

And please let us know about the results – does it help to solve the problem ?

Nevertheless we encourage you to bypass all the mentioned problems which are in the logs (and which are not connected with scheduler itself) as maybe that’s the reason of this whole failure.

Regards, Pawel

[Susan Hauth]

Hi, Just want to let you know that drop constraint SQL statement did the trick. You can close this ticket and many thanks for your assistance.

[Raju Adluru]

Pawel, i tried this fix in JIRA v 7.1.2 with MS SQL, i am still getting below error. do we need restart JIRA after this change?

Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
    Database:
      - name:Microsoft SQL Server
      - version:11.00.3128
      - minor version:0
      - major version:11
    Driver:
      - name:jTDS Type 4 JDBC Driver for MS SQL Server and Sybase
      - version:1.3.1
    
    java.sql.SQLException: The object 'U_AO_A406ED_SCHEDUL1453239299' is dependent on column 'NAME'.
  at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate(EntityManagedActiveObjects.java:47) [?:?]
  at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory$1.doInTransaction(AbstractActiveObjectsFactory.java:77) [?:?]
  at com.atlassian.activeobjects.internal.AbstractActiveObjectsFactory$1.doInTransaction(AbstractActiveObjectsFactory.java:72) [?:?]
  at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:25) [?:?]
  at com.atlassian.jira.DefaultHostContextAccessor.doInTransaction(DefaultHostContextAccessor.java:34) [DefaultHostContextAccessor.class:?]
  at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source) [?:?]
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [?:1.8.0_74]
Show less
Caused by: java.sql.SQLException: The object 'U_AO_A406ED_SCHEDUL1453239299' is dependent on column 'NAME'.
  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372) [jtds-1.3.1.jar:1.3.1]
  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988) [jtds-1.3.1.jar:1.3.1]
  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421) [jtds-1.3.1.jar:1.3.1]
Attachment