DB error on Postgres

Issue #10 resolved
Andrew Herron created an issue

I've been having an issue with this plugin for a while, but somehow not noticed - work has been busy and nobody noticed we weren't getting reminders :)

Judging by the logs, it looks like around the time of my 3.1.0 -> 3.1.1 upgrade on the 7th of July I started getting database errors. Here's one generated today on 3.2.0:

2014-08-05 08:00:00,130 ERROR [localScheduler_Worker-8]  c.a.scheduler.core.JobLauncher Scheduled job with ID 'PluginScheduler:com.jeffthms.stash.reminder.PullRequestReminderImpl:job' failed
com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
    - name:PostgreSQL
    - version:9.1.13
    - minor version:1
    - major version:9
Driver:
    - name:PostgreSQL Native Driver
    - version:PostgreSQL 9.0 JDBC4 (build 801)

org.postgresql.util.PSQLException: ERROR: column "person" does not exist
  Position: 71
    at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.find(EntityManagedActiveObjects.java:173) ~[na:na]
    at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects.find(TenantAwareActiveObjects.java:329) ~[na:na]
    at com.jeffthms.stash.reminder.UserSettingServiceImpl.get(UserSettingServiceImpl.java:30) ~[na:na]
    at com.jeffthms.stash.reminder.PullRequestReminderTask.isSendEmailToUser(PullRequestReminderTask.java:343) ~[na:na]
    at com.jeffthms.stash.reminder.PullRequestReminderTask.execute(PullRequestReminderTask.java:116) ~[na:na]
    at com.atlassian.stash.internal.sal.scheduling.PluginSchedulerAdapter$JobDescriptor.runJob(PluginSchedulerAdapter.java:130) ~[stash-platform-3.2.0.jar:na]
    at com.atlassian.stash.internal.sal.scheduling.PluginSchedulerAdapter.runJob(PluginSchedulerAdapter.java:86) ~[stash-platform-3.2.0.jar:na]
    at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:127) [atlassian-scheduler-core-1.2.2.jar:na]
    at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101) [atlassian-scheduler-core-1.2.2.jar:na]
    at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80) [atlassian-scheduler-core-1.2.2.jar:na]
    at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32) [atlassian-scheduler-quartz1-1.2.2.jar:na]
    at org.quartz.core.JobRunShell.run(JobRunShell.java:223) [quartz-1.8.6.jar:na]
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549) [quartz-1.8.6.jar:na]
    ... 21 frames trimmed
Caused by: org.postgresql.util.PSQLException: ERROR: column "person" does not exist
  Position: 71
    at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2102) ~[postgresql-9.1-901.jdbc4.jar:na]
    at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1835) ~[postgresql-9.1-901.jdbc4.jar:na]
    at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257) ~[postgresql-9.1-901.jdbc4.jar:na]
    at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:500) ~[postgresql-9.1-901.jdbc4.jar:na]
    at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:388) ~[postgresql-9.1-901.jdbc4.jar:na]
    at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:273) ~[postgresql-9.1-901.jdbc4.jar:na]
    at com.jolbox.bonecp.PreparedStatementHandle.executeQuery(PreparedStatementHandle.java:172) ~[bonecp-0.7.1.RELEASE.jar:0.7.1.RELEASE]
    at net.java.ao.EntityManager.find(EntityManager.java:765) ~[na:na]
    at net.java.ao.EntityManager.find(EntityManager.java:675) ~[na:na]
    at net.java.ao.EntityManager.find(EntityManager.java:607) ~[na:na]
    at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.find(EntityManagedActiveObjects.java:169) ~[na:na]
    ... 13 common frames omitted

I'm happy to poke around the database if there is any other info you need to help track this down.

Comments (4)

  1. Andrew Herron reporter

    The settings page loads, which is a good sign :)

    I'll let you know tomorrow if the emails work.

  2. Log in to comment