java.lang.NullpointerException when syncronizing a single select ++ field with SQL

Description

Hi!

We have purchased several paid licenses for Custom Fields++.
When trying to sync a single select ++ field with my SQL database I get the following error (see below attachment and logs ouput). Previously we had Jira v.7.9.0 and an older version of your plugin (dont know which one exactly) and it was all fine and worked like a charm. Currently I have JIRA 7.12.3. I have also attached the query I am exectuing for your record. When I run it in VS Managment Studio, it runs fine without any problems and returns the exact results I want to have in my dropdown list.

Currently we cannot run without this being fixed. Thanks,

Kind regards,

Evgeni

2018-11-13 10:17:19,248 Caesium-1-4 ERROR ServiceRunner [c.d.j.c.i.ss.dbsynch.DBSynchronizationManager] Skipping an option synchronization due to error
java.lang.NullPointerException
at com.deniz.jira.cf.imp.ss.dbsynch.a.a(SourceFile:108)
at com.deniz.jira.cf.imp.ss.dbsynch.a.a(SourceFile:85)
at com.deniz.jira.cf.imp.ss.dbsynch.DBSynchronizationManager.processRowsFromDBTable(SourceFile:179)
at com.deniz.jira.cf.imp.ss.dbsynch.DBSynchronizationManager.synchronize(SourceFile:122)
at com.deniz.jira.cf.imp.ss.dbsynch.DBSynchronizationManager.synchronizeAll(SourceFile:79)
at com.deniz.jira.cf.imp.ss.dbsynch.c.execute(SourceFile:21)
at com.atlassian.sal.jira.scheduling.JiraPluginScheduler$JobDescriptor.runJob(JiraPluginScheduler.java:110)
at com.atlassian.sal.jira.scheduling.JiraPluginScheduler.runJob(JiraPluginScheduler.java:80)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:410)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:388)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)
at java.lang.Thread.run(Thread.java:748)

Environment

Microsoft Server 2016, JIRA 7.12.3

Activity

Show:
Deniz Oğuz
November 15, 2018, 8:04 AM
Edited

Another option is, I can make a beta release where this issue is handled more silently, with just logging erroneous option and not giving a NullPointerException. Assuming that this is the same problem described in CF‌-64

Evgeni Pirianov
November 15, 2018, 8:18 AM

Hi, I have quite a few sql based fields with a query and a few ones with normal lists which I can recreate. I checked (did not really understand how the guy resolved it ) but I will make the following:

1. disable plug-in
2. will delete all rows from the table.
3. enable plug-in
4. run the syncs again for each sql table

Is that correct ?
You also mentioned backuping JIRA, what do you mean -> what option is that and where do I find it ?

Thanks.

Deniz Oğuz
November 15, 2018, 8:34 AM

Yes, these are the correct steps. I’m %99 sure that there is an option in database and AO_00C882_EX_OP_INFO table but not exist in customfieldoptions table. CF‌-64 was caused by this and it has the same stack trace with you. Either we need to manually find which row causing this and delte it or we need to clear everything and let it to recreate.

to backup the system, just double press G key on any Jira screen, and select “Backup System”. You can check documentation here, https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html.

Note that your normal lists option values will not be deleted, only their css style, icon and description will be deleted.

Deniz Oğuz
November 22, 2018, 7:45 PM

Hi,

Did you able to solve this issue?

Evgeni Pirianov
November 26, 2018, 12:24 PM

Hi,

yes, issue is gone, sorry was away for a while. thanks for the help, much appreciated! You may close it - maybe its not a bad idea to print a different error instead of nullpointer in the next release, it is a bit confusing and shocking

Kind regards, Evgeni

Fixed

Assignee

Deniz Oğuz

Reporter

Evgeni Pirianov

Labels

None

Source

None

Jira Version

None

Database Type/Version

None

Browser Type/Version

None

Fix versions

Affects versions

Priority

Major
Configure