Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-18408

Upgrade Task 410 can throw weird exceptions on Postgres/Oracle

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 4.0
    • None
    • Dashboard & Gadgets
    • None

    Description

      2009-08-13 15:26:02,109 http-8090-Processor8 INFO anonymous 52614x25x1 19v1v4w /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Converts Legacy Portlets to Gadgets including user preferences.
      org.postgresql.util.PSQLException: Unknown Types value.
      	at org.postgresql.jdbc2.AbstractJdbc2Statement.setNull(AbstractJdbc2Statement.java:1094)
      	at org.postgresql.jdbc3.AbstractJdbc3Statement.setNull(AbstractJdbc3Statement.java:1447)
      	at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.setNull(DelegatingPreparedStatement.java:105)
      	at org.ofbiz.core.entity.jdbc.SQLProcessor.setValue(SQLProcessor.java:903)
      	at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.setValue(DefaultOfBizDelegator.java:787)
      	at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:520)
      	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build410.doUpgrade(UpgradeTask_Build410.java:78)
      	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:478)
      	at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(UpgradeManagerImpl.java:398)
      	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:335)
      	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:286)
      	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:243)
      	at com.atlassian.jira.action.admin.DataImport.doExecute(DataImport.java:241)
      

      This is caused by the fact that NULL is being set as the value with the JDBC Types.JAVA_OBJECT (as it can't determine in this case that it should be a VARCHAR as it's null). Some JDBC drivers don't like this and complain.

      In this case, simply using empty string suffices, as the application handles empty string as though it was null.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jed Jed Wesley-Smith (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 0.5h
                0.5h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 0.5h
                0.5h