We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-20953

While updating the local pull request, DVCSConnector.MessageExecutor fails with "Invalid column name 'REQUEST_ID'"

      Issue Summary

      DVCSConnector.MessageExecutor fails to consume message on updating pull requests locally with failure message >> "Invalid column name 'REQUEST_ID'"

      Steps to Reproduce

      1. Upgrade to Jira 8.16.
      2. Let the DVCS sync work as usual with updates on GitHub coming in.

      Expected Results

      Pull request updates happens seamlessly.

      Actual Results

      The below exception is thrown in the atlassian-jira.log file:

      com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'REQUEST_ID'.
      	at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.deleteWithSQL(EntityManagedActiveObjects.java:128)
      	at com.atlassian.jira.plugins.dvcs.dao.impl.RepositoryPullRequestDaoImpl.lambda$removeDuplicates$2(RepositoryPullRequestDaoImpl.java:152)
      	at java.lang.Iterable.forEach(Iterable.java:75)
      	at com.atlassian.jira.plugins.dvcs.dao.impl.RepositoryPullRequestDaoImpl.removeDuplicates(RepositoryPullRequestDaoImpl.java:151)
      	at com.atlassian.jira.plugins.dvcs.dao.impl.RepositoryPullRequestDaoImpl.lambda$savePullRequest$0(RepositoryPullRequestDaoImpl.java:112)
      	at com.atlassian.jira.plugins.dvcs.dao.impl.RepositoryPullRequestDaoImpl.savePullRequest(RepositoryPullRequestDaoImpl.java:108)
      	at com.atlassian.jira.plugins.dvcs.service.PullRequestServiceImpl.createPullRequest(PullRequestServiceImpl.java:119)
      	at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestProcessor.updateLocalPullRequest(GitHubPullRequestProcessor.java:126)
      	at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestProcessor.processPullRequest(GitHubPullRequestProcessor.java:90)
      	at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestProcessor.processPullRequest(GitHubPullRequestProcessor.java:83)
      	at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:75)
      	at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:25)
      	at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$MessageRunnable.doRun(MessageExecutor.java:342)
      	at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$ReleaseTokenAndEnqueueNextMessage.run(MessageExecutor.java:256)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'REQUEST_ID'.
      	at net.java.ao.ForwardingPreparedStatement.executeUpdate(ForwardingPreparedStatement.java:45)
      	at net.java.ao.ParameterMetadataCachingPreparedStatement.executeUpdate(ParameterMetadataCachingPreparedStatement.java:10)
      	at net.java.ao.EntityManager.deleteWithSQL(EntityManager.java:593)
      	at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.deleteWithSQL(EntityManagedActiveObjects.java:126)
      	... 94 more
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Software Data Center'
            1. Jira Software Data Center
            2. JSWSERVER-20953

            While updating the local pull request, DVCSConnector.MessageExecutor fails with "Invalid column name 'REQUEST_ID'"

                Issue Summary

                DVCSConnector.MessageExecutor fails to consume message on updating pull requests locally with failure message >> "Invalid column name 'REQUEST_ID'"

                Steps to Reproduce

                1. Upgrade to Jira 8.16.
                2. Let the DVCS sync work as usual with updates on GitHub coming in.

                Expected Results

                Pull request updates happens seamlessly.

                Actual Results

                The below exception is thrown in the atlassian-jira.log file:

                com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'REQUEST_ID'.
                	at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.deleteWithSQL(EntityManagedActiveObjects.java:128)
                	at com.atlassian.jira.plugins.dvcs.dao.impl.RepositoryPullRequestDaoImpl.lambda$removeDuplicates$2(RepositoryPullRequestDaoImpl.java:152)
                	at java.lang.Iterable.forEach(Iterable.java:75)
                	at com.atlassian.jira.plugins.dvcs.dao.impl.RepositoryPullRequestDaoImpl.removeDuplicates(RepositoryPullRequestDaoImpl.java:151)
                	at com.atlassian.jira.plugins.dvcs.dao.impl.RepositoryPullRequestDaoImpl.lambda$savePullRequest$0(RepositoryPullRequestDaoImpl.java:112)
                	at com.atlassian.jira.plugins.dvcs.dao.impl.RepositoryPullRequestDaoImpl.savePullRequest(RepositoryPullRequestDaoImpl.java:108)
                	at com.atlassian.jira.plugins.dvcs.service.PullRequestServiceImpl.createPullRequest(PullRequestServiceImpl.java:119)
                	at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestProcessor.updateLocalPullRequest(GitHubPullRequestProcessor.java:126)
                	at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestProcessor.processPullRequest(GitHubPullRequestProcessor.java:90)
                	at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestProcessor.processPullRequest(GitHubPullRequestProcessor.java:83)
                	at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:75)
                	at com.atlassian.jira.plugins.dvcs.sync.GitHubPullRequestSynchronizeMessageConsumer.onReceive(GitHubPullRequestSynchronizeMessageConsumer.java:25)
                	at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$MessageRunnable.doRun(MessageExecutor.java:342)
                	at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$ReleaseTokenAndEnqueueNextMessage.run(MessageExecutor.java:256)
                	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
                	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
                	at java.lang.Thread.run(Thread.java:748)
                Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'REQUEST_ID'.
                	at net.java.ao.ForwardingPreparedStatement.executeUpdate(ForwardingPreparedStatement.java:45)
                	at net.java.ao.ParameterMetadataCachingPreparedStatement.executeUpdate(ParameterMetadataCachingPreparedStatement.java:10)
                	at net.java.ao.EntityManager.deleteWithSQL(EntityManager.java:593)
                	at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.deleteWithSQL(EntityManagedActiveObjects.java:126)
                	... 94 more
                

                Workaround

                Currently there is no known workaround for this behavior. A workaround will be added here when available

                        rarmstrong@atlassian.com Rory Armstrong (Inactive)
                        vpandey2@atlassian.com Vikas Pandey (Inactive)
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            rarmstrong@atlassian.com Rory Armstrong (Inactive)
                            vpandey2@atlassian.com Vikas Pandey (Inactive)
                            Affected customers:
                            0 This affects my team
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: